-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update how to write and deploy an NFT tutorial to use OpenZeppelin 5.x #11847
Conversation
✅ Deploy Preview for ethereumorg ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
public/content/developers/docs/smart-contracts/composability/index.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR @M4x28 !
@all-contributors please add @M4x28 for docs |
I've put up a pull request to add @M4x28! 🎉 |
Congrats, your important contribution to this open-source project has earned you a GitPOAP! Be sure to join the Ethereum.org discord if you are interested in contributing further to the project or have any questions for the team. GitPOAP: 2024 Ethereum.org Contributor: Head to gitpoap.io & connect your GitHub account to mint! Learn more about GitPOAPs here. |
Code changes to make the guide compatible with openzeppelin version 5.x.
Description
Adaptation of the code in the MyNFT.sol file to the new version of openzeppelin 5.x, addition of the OWNER_ACCOUNT_ADDRESS field in the .env file with consequent modification of the deploy.js file with passage of the OWNER_ACCOUNT_ADDRESS parameter to the deploy() method.
Related Issue
Remove Counters.sol