Jacek Sieka fd4de5de0f
start untangling beaconnode (#589)
* Move BeaconNode type to its own file (fewer imports)
* disentangle sync protocol/request manager
* fix some old nimisms
* de-fear some logs
* simplify eth1 data production
* add stack tracing to release builds
* drop release compile flag for testnet
2019-11-25 15:36:25 +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