-
Notifications
You must be signed in to change notification settings - Fork 358
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
chore(claim_contracts): update README #1620
base: testnet
Are you sure you want to change the base?
chore(claim_contracts): update README #1620
Conversation
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.
I left some comments. But the functionality is ok
To deploy the token, modify the file `script-config/config.example.json` and set the following values: | ||
|
||
- `safe`: The address of the safe that's going to own the Proxy admin that in turn owns the token and airdrop contracts. | ||
- `salt`: The salt used to generate CREATE2 addresses. |
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.
How should the salt be generated?
|
||
- `safe`: The address of the safe that's going to own the Proxy admin that in turn owns the token and airdrop contracts. | ||
- `salt`: The salt used to generate CREATE2 addresses. | ||
- `deployer`: The address of the account that's going to deploy the contracts. |
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.
Specify that deployer must be a CREATE2 deterministic deploy factory
- `foundation`: The address of the Aligned Foundation account. | ||
- `claimSupplier`: The address of the account that's going to supply the tokens. | ||
- `limitTimestampToClaim`: The claim time limit timestamp. | ||
- `claimMerkleRoot`: The merkle root of all valid token claims. |
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.
The json file includes claimSupplierPrivateKey. Should we have it?
I think #1629 already solved this |
Update README
Description
Updated the README with new deployment instructions using Makefile
Type of change
Please delete options that are not relevant.
Checklist
testnet
, everything else tostaging