Zahary Karadjov ee2448b221 Simple validator onboarding
On your very first connection to each testnet, you'll be asked to
become a validator. Please consult our private repo for a Goerli
Eth1 private key that you can use for deposits.

Other changes:

* Added a simple wrapper ./connect-to-testnet script calling the
  nims file in the correct environment. No extension was used to
  make the command the same on Unix and Windows.

* Bumped a number of modules with fixes from this week

* `make testnet0` and `make testnet1` will no longer delete your
  existing database. This is considered a more appropriate behavior
  for testing forward sync.
2019-12-03 02:23:17 +02: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