6664f1689f
Multi-client testing requires more portable formats, and SSZ is much better specified than our flavour of Json. Tools like ncli and zcli can be now used to inspect the contents of the SSZ files. |
||
---|---|---|
.. | ||
README.md | ||
attach_validators.sh | ||
connect_to_testnet.nims | ||
process_lfs.sh | ||
reset_testnet.sh | ||
reset_testnet0.sh | ||
reset_testnet1.sh | ||
testnet0.env | ||
testnet1.env |
README.md
Work in progress. Things may and probably will break for the foreseeable future. Do not rely on this for anything.
Connecting to Testnet
To connect to a short-lived testnet we may or may not have running at the moment, use the connect_to_testnet
script like so:
scripts/connect_to_testnet.sh testnet0
Running your own testnet
The beacon_node
binary has a createTestnet
command.
nim c -r beacon_chain/beacon_node \
--data-dir=$DATA_DIR/node-0 \
createTestnet \
--validators-dir=$NETWORK_DIR \
--total-validators=$VALIDATOR_COUNT \
--last-user-validator=$LAST_USER_VALIDATOR \
--output-genesis=$NETWORK_DIR/genesis.ssz \
--output-bootstrap-file=$NETWORK_DIR/bootstrap_nodes.txt \
--bootstrap-address=$PUBLIC_IP \
--genesis-offset=600 # Delay in seconds
Replace ENV vars with values that make sense to you.
Full tutorial coming soon.
Maintaining the Status testnets
For detailed instructions, please see https://github.com/status-im/nimbus-private/blob/master/testnets-maintenance.md