#
Onboard using CLI
Clone the contracts repository:
git clone https://github.com/git-consensus/contract.git && cd contracts
After setting up and running yarn
, you can run the CLI:
yarn deploy --network mainnet
Choose a wallet address to be used for deployment
Choose role as MAINTAINER
for onboarding
Choose any one of the three options, 1
to deploy both contracts together, 2
to only deploy token contract, 3
to only deploy Governor contract.
[1] Token and Governor
[2] Token
[3] Governor
You will be asked to enter address of the already deployed GitConsensus, TokenFactory and GovernorFactory contracts. You can use default ones or provide addresses dynamically.
For you're clones, you must supply a random strings that will be used for giving the deployed contract clone a pre-determined address. This is also used for address prediction (see: predictAddress())
Enter Token Salt. This can be any string and will be used to predict token address.
Enter Governor Salt. This can be any string (can be same as Token salt) and will be used to predict governor address.
#
Steps for deploying a Token Clone
You will be prompted to enter following details needed for Token Clone creation.
Enter a string as Token Name.
Enter a string as Token Symbol.
Enter an integer value for max mintable per hash.
Enter initial token distributions for the owners of the project.
#
Steps for deploying a Governor Clone
You will be prompted to enter following details for Governor Clone creation.
Enter the voting delay.
Enter the voting period.
Enter the proposal threshold.
Enter the quorum numerator.
The Governor clone will be deployed.
At this point, onboarding to Git Consensus is complete!
#
Release Usage
For using your new Token and Governor during releases, see the release guide.