Francisco Giordano
Francisco Giordano
Our current position on this is that the work required to support diamond proxies is too much for us to take on. It is not only about the initial work...
Our position hasn't changed since the previous comment: https://github.com/OpenZeppelin/openzeppelin-contracts/issues/2793#issuecomment-983230289
In theory this makes sense, but there is an edge case that breaks with this change. This edge case has actually come up in conversations in the past as something...
Closing for the reasons explained above.
@Amxx Could we allow `_mint` in the constructor for `tokenIds` that are outside the consecutive range? I suppose they would need to be greater than 2**96. Could we allow `_mint`...
>Could this be combined with Enumerable to prevent overlapping? I don't really see how that's relevant.
Thanks, this is interesting and we will consider it along with #3706. (We're actively discussing mitigations for #3706 and will be acting on that in the next 2 weeks.) In...
Would it be an option to preserve the prior share price after the vault is emptied, instead of resetting to 1:1?
Bumping this. Contracts with EnumerableSet/Map variables that want to expose that data through getters currently have two options: 1. Use `values()` 2. Use `at(i)` and `length()` Option 1 is not...
@natalietop seems to have set up the bounty.