-
Notifications
You must be signed in to change notification settings - Fork 1
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
feat: final gov deployment allocations and merkle tree #168
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
baroooo
reviewed
Apr 19, 2024
baroooo
approved these changes
Apr 19, 2024
philbow61
approved these changes
Apr 19, 2024
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.
💯
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.
Description
This PR partially completes mento-protocol/mento-core#405 as we currently don't have all the final addresses for each allocation, so not all the addresses are final (the ones that need to be updated have been marked with a TODO).
The following however has been updated:
Final token allocation according to the forum post
Merkle tree generated from the final snapshot (airdrop-amounts-per-address.csv
in https://github.com/mento-protocol/airdrop-snapshot/tree/main/final-snapshots)update: this is no longer the final snapshot as there are still some modifications being made. I have also replaced one of the recipients in the original CSV with one of our test accounts which we'll use in the integration tests
Fractal signer address on Alfajores to now use the mainnet signerreverted: we need the staging signer for the integration tests CI
Other changes left to do:
Other changes
I made each allocation address unique (even if temporary) so that we can verify that there's no address mix-up. Reach out if you need the private key for any of them for testing purposes.
Tested
Ran a simulation of the deployment on Alfajores