You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 24, 2022. It is now read-only.
When we use OZ proxy contracts, there is a sense of not understanding exactly how the code works. Viewing the underlying solidity that makes the contracts possible would be a big bonus.
When deploying using OZ CLI, would it be possible to create a new folder in our contract directory with the OZ Solidity that powers the upgradability? As well as give us the ABIs? That would be massively helpful.
Thanks!
The text was updated successfully, but these errors were encountered:
Hi @crazyrabbitLTC ! Thanks for the suggestion, it is really appreciated.
The project owner will review your suggestion as soon as they can.
There is a plan to move the proxy contracts to OpenZeppelin Contracts: #1528
I have also seen some general request to have OpenZeppelin Contracts easily accessible.
Please wait until we have discussed this idea before writing any code or submitting a Pull Request, so we can go through the design beforehand. We don’t want you to waste your time!
We're considering building something for users to "install" the contracts they want into their source code (rather than node modules). It's an early idea but it's definitely in our minds!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This is a feature request:
When we use OZ proxy contracts, there is a sense of not understanding exactly how the code works. Viewing the underlying solidity that makes the contracts possible would be a big bonus.
When deploying using OZ CLI, would it be possible to create a new folder in our contract directory with the OZ Solidity that powers the upgradability? As well as give us the ABIs? That would be massively helpful.
Thanks!
The text was updated successfully, but these errors were encountered: