Viktor Kirilov 1482b0430d - work towards more REST API endpoints being implemented
- testnets can now be launched with a separate validator client - make altona SCRIPT_PARAMS="--separateVC"
- reverted the ctrl+C signal handler code reuse - not necessary for the VC anyway (default is good enough)
- added a bit more logging in the VC
- removed unnecessary code in the VC - connect() just parses the address & port...
- fixed a couple more VC issues - when fetching the duties for an epoch fails on the BN side ==> the VC shouldn't be left in a broken state
- documented the currently supported json-rpc endpoints
- added more checks on the BN side for the API - bounds-checking the requests & also checking if the BN itself is synced
- other cleanup

currently a local sim doesn't finalize, but participation in the altona network with a separate VC is painless and works just as well as with in-process validators in a BN
2020-07-08 13:29:03 +03: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