how does deploy QDay chain (abelianL2)
os: centos 7.9
cpu: amd64
docker :20.10
docker-compose
The deployment of QDay chain is performed as follows
Enter the account module Execute the following command
npm i
node wallets.js | tee wallets.txt
If it is executed normally, the wallets.txt file will be generated, which contains the account required for deployment
abe-node deployment manual
Wait for the node deployment to complete and observe whether the deployment is successful. If the deployment is successful, you can proceed to the next step
- zkevm-contracts deployment
How to use? Please read zkevm-contracts
After successfully executing the relevant operations, save the two generated files (deploy_output.json, genesis.json) as the basis for the next deployment
The output of step 2 is the dependency of the relevant configuration of this step, which requires special attention
Note that the genesis file adds the following elements in the header
"l1Config": {
"chainId": 9000,
"polygonZkEVMAddress": "0xdde8f57d008D36C9476c5DF5525F7C5B52B03647",
"maticTokenAddress": "0x68715d6F60e00c55cb43EFC223D1D38b4BDb9638",
"polygonZkEVMGlobalExitRootAddress": "0xE593b85fc5351b1CF9051012110B35F79C36F2E4"
},
"genesisBlockNumber": 32,
This operation consists of 2 parts: Deploy contracts, transfer assets
- indexer
The following fields are frequently changed:
indexer.toml
database-source
bitcoin.toml
network-name
rpc-host
rpc-user
rpc-pass
indexer-listen-address
eth-rpc-url
eth-priv-key
contract-address
aa-b2-api
For the use of other fields, refer to Configuration Instructions
- committer
[committer Configuration Instructions
Bridge Deployment Instructions
-
Bridge service includes two parts, front-end and back-end
-
This service depends on https certificates and domain names
-
Check balance, you can use EVM-compatible wallet metamask
-
Deploy block browser, EVM-compatible browser blockscout