Jacek Sieka 521b0ed6ba
Clean 20200205 (#729)
* beacon node code cleanup
* rudimentary error checking on mainnet monitor
* start client even when sending deposit
* work around missing block number exception
* connect to testnet with web3 url
* pretty-print digests in json
2020-02-07 08:13:38 +01:00
..
2020-02-07 08:13:38 +01:00
2019-11-07 17:23:06 +00:00

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=$NETWORK_DIR/data \
    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