Peersky
Peersky
> So if the wallet wants more flexibility, it needs the gas overhead of implementing a dispatcher inside these functions. I'm not sure it's better than using a different function...
> The API was designed to provide the minimal required functions. > > * Account validation is the minimal API required to approve **payment** for the transaction (usually, owner's signature...
> * Having wallets get used to the possibility of an implementation upgrade isn't necessarily a bad idea. > * You still rely on those third party security oracles or...
> From my understanding of the EIP/ERC processes, authorship implies authority of the content of the document. Thus, as authors of the ERC, we decided, considering the state of the...
Bumping this as very anticipated feature for https://github.com/peeramid-labs/eds.
@SamWilsn @g11tech How can I claim championship over this ERC? I requested reasonable proposal that allowed to move this ERC quickly forward but could not get it merged due to...
Closes #1487
> Hello, thanks for your PR. However, I would suggest something simpler and more flexible. Instead of creating a new abstract contract, I would just add a single function: >...
> to not have to import OZ library here You did not have external dependency for OZ libraries in this PR. I would still advise blocking re-initialization natively to prevent...
> Of course no, my point was exactly to **not** make our package import OZ as a real dep I miss red that, I see, that's good! Edited my comment