[DRAFT] V2 => V3 Contract Upgrade #33
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
JamesEarle
force-pushed
the
feat/token-upgrade
branch
2 times, most recently
from
f0c7ade to
18f6387
Compare
Whytecrowe
reviewed
Sep 23, 2025
Whytecrowe
reviewed
Oct 2, 2025
Whytecrowe
reviewed
Oct 2, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Upgrades for the zeroDAOToken contract to
onlyOwnerfunctions as we intend to renounce ownership in the future_transferto include a burning mechanism if thetoaddress is the contract