status-im
/
nimbus-eth2
mirror of https://github.com/status-im/nimbus-eth2.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
nimbus-eth2/scripts
History
Zahary Karadjov 0bcdabfcdf Detect another invalid SSZ input found through fuzzing 
The first offset of an SSZ object should always have a fixed constant
value. Otherwise, some unused bytes may appear between the fixed portion
and the dynamic portion.

Please note that this fix shutds down the minimal forward compatibility
currently supported by the SSZ format (and thus, the expected behavior
must be clarified in the SSZ spec).
 		2020-05-30 14:47:35 +03:00
..
README.md Allow running local nodes without attached validators 2019-11-11 23:29:36 +00:00
attach_validators.sh Removed all code related to the old network metadata files 2019-10-29 01:04:52 +02:00
connect_to_testnet.nims connect_to_testnet.nims: enable metrics [skip ci] 2020-05-27 22:35:40 +02:00
depositContract.v.py Fixed deposit/contract 2019-11-07 17:23:06 +00:00
launch_local_testnet.sh Jenkins: support running 2 parallel jobs on the same node (#1025) 2020-05-14 19:34:47 +02:00
load-testnet-nim-flags.sh Mechanically remove all mentions of the daemon from the code 2020-03-23 14:59:33 +02:00
reset_testnet.sh cleanup [skip ci] 2020-02-11 18:43:57 +01:00
reset_testnet0.sh Helpful scripts for resetting the testnets 2019-03-19 21:50:22 +02:00
reset_testnet1.sh Helpful scripts for resetting the testnets 2019-03-19 21:50:22 +02:00
run_ssz_fuzzing_test.nims Detect another invalid SSZ input found through fuzzing 2020-05-30 14:47:35 +03:00
setup_official_tests.sh Use the new nim-eth2-scenarios path for the test vectors 2020-02-17 15:26:11 +00:00
testnet0.env Mechanically remove all mentions of the daemon from the code 2020-03-23 14:59:33 +02:00
testnet1.env fix mainnet finalization (#906) 2020-04-20 19:27:52 +02:00

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 \
    --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