| .. | ||
| config | ||
| config_template | ||
| doc | ||
| docker | ||
| keystore | ||
| scripts | ||
| testdata | ||
| token_data | ||
| .dockerignore | ||
| .gitlab-ci.yml | ||
| 1_deploy_contract_root.sh | ||
| 2_deploy_contract_instance.sh | ||
| 3_deploy_token.sh | ||
| 4_init_custodial.sh | ||
| 5_data_seeding.sh | ||
| config.sh | ||
| from_env.sh | ||
| LICENSE.txt | ||
| nvm.sh | ||
| override_requirements.txt | ||
| README_bloxberg.md | ||
| README.md | ||
| requirements.txt | ||
| run_job.sh | ||
| sarafu_declaration.json | ||
| util.sh | ||
| wait-for-it.sh | ||
CIC-stack system bootstrap scripts
1. Deploy global contracts.
Global contracts are contracts that may or may not be used to contribute to a data store intended for consumption across instances.
In the current version of the scripts, the only contract deployed is the AddressDeclarator. Also, in the current version, the AddressDeclarator is required as a storage backend for some of the instance contracts.
2. Deploy instance contracts.
Instance contracts are contracts whose contents are limited to the context of a single custodial engine system.
This includes a registry of contracts used by the engine, as well as registry contracts for user accounts and tokens.
3. Deploy token.
Deploys a CIC token, adding it to the token registry.
The first token deployed becomes the default token of the instance.
In the current version of the scripts, two token types may be deployed; giftable_erc20_token and erc20_demurrage_token.
This step may be run multiple times, as long as the token symbol is different from all previously deployed tokens.
4. Initialize custodial engine.
Adds system accounts to the custodial engine, and unlocks the initialization seal. After this step, the custodial system is ready to use.
Services dependency graph
- evm
- bootstrap runlevel 1
- bootstrap runlevel 2
- bootstrap runlevel 3
- redis
- postgres
- cic-eth-tasker
- boostrap runlevel 4