deploy new timelock-manager-reversible #23
Merged
Conversation
This file contains 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
bbenligiray
approved these changes
May 22, 2024
There was a problem hiding this comment.
This is the original deployment that I made back in the day, which we used with no problems: https://github.com/api3dao/api3-contracts/blob/master/packages/timelock-manager/deployments-3/mainnet/TimelockManagerReversible.json / https://etherscan.io/address/0x310BBf92A36031F778C32FEaCa458251FD36F451
This is the new deployment: https://etherscan.io/address/0x0Ee5223f5a4CC53867557435BC417cB8975A14CE
I confirmed on Etherscan that
- The deployed bytecodes match
- For the new deployment,
api3Tokenis correct andowneris the (recently updated) 1B20N24 multisig address
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Deployed a new timelock-manager-reversible contract for vesting to users