Further simplifications and removal of support for multiple network back-ends per testnet. |
||
---|---|---|
.. | ||
README.md | ||
attach_validators.sh | ||
build_testnet_node.sh | ||
download_validator_keys.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 \
--network=$NETWORK_NAME \
--dataDir=$DATA_DIR/node-0 \
createTestnet \
--networkId=$NETWORK_ID \
--validatorsDir=$NETWORK_DIR \
--totalValidators=$VALIDATOR_COUNT \
--lastUserValidator=$LAST_USER_VALIDATOR \
--outputGenesis=$NETWORK_DIR/genesis.json \
--outputNetwork=$NETWORK_DIR/network.json \
--bootstrapAddress=$PUBLIC_IP \
--genesisOffset=600 # Delay in seconds
Replace ENV vars with values that make sense to you.
Full tutorial coming soon.