contracts: Migration, with LQTY Merkle distribution, end to end#527
Draft
contracts: Migration, with LQTY Merkle distribution, end to end#527
Conversation
Modify LQTYToken too to adapt it to migration.
bingen
force-pushed
the
migration_airdrop
branch
from
c6190c8 to
4f5520d
Compare
bingen
changed the title
bingen
force-pushed
the
migration_airdrop
branch
from
4f5520d to
15b5f6f
Compare
bingen
changed the title
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Given a block number for the migration (defined in
migration/constants.js), queries original LQTY balances from mainnet, generates merkle tree, deploys contracts with the new version, claims the original balances in the new LQTY token and checks (using a mainnet fork). Community Issuance is adjusted accordingly, so the new one would follow the same pace as the original one.Run it with the following commands:
Removes output from previous executions, optional. It will force querying again from the blockchain.
Queries and processes all previous LQTY balances. Queries to the graph/blockchain take ~4h.
Builds a Merkle Tree from the queried balances obtained in the previous step.
Forks mainnet, deploys contracts V2, claims new LQTY tokens for all users and check that balances are right.