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/tests/simulation/run_node.sh

35 lines
794 B
Bash
Raw Normal View History

add initial block pool (#139) * implement in-memory block graph * store tail block in database * resolve unknown parents by syncing them from peers * introduce concept of resolved blocks and attestations - those that follow minimal protocol rules * update state head lazily * log more stuff * shortHash -> shortLog * start 9/10 beacon nodes by default, last can be started manually * see also #134 * fix start.sh epoch length
2019-02-28 21:21:29 +00:00
#!/bin/bash
set -eux
. $(dirname $0)/vars.sh
if [[ "$1" == "0" ]]; then
BOOTSTRAP_NODES_FLAG=""
fi
DATA_DIR=$SIMULATION_DIR/node-${1}
beacon node sim: various improvements (fixes #111) (#156) * allow running more or fewer validators * use deterministic key generation for tests to avoid exhausting system RNG * update README with simulator docs * write the data of each validator to separate file, instead of a big chainstart.json (makes it easier to run different validator counts)
2019-03-07 13:59:28 +00:00
V_PREFIX="$VALIDATORS_DIR/v$(printf '%06d' ${1})"
PORT=$(printf '5%04d' ${1})
allow setting advertised external ip * detect it in start.sh
2019-03-19 03:57:19 +00:00
MYIP=$(curl -s ifconfig.me)
beacon node sim: various improvements (fixes #111) (#156) * allow running more or fewer validators * use deterministic key generation for tests to avoid exhausting system RNG * update README with simulator docs * write the data of each validator to separate file, instead of a big chainstart.json (makes it easier to run different validator counts)
2019-03-07 13:59:28 +00:00
add initial block pool (#139) * implement in-memory block graph * store tail block in database * resolve unknown parents by syncing them from peers * introduce concept of resolved blocks and attestations - those that follow minimal protocol rules * update state head lazily * log more stuff * shortHash -> shortLog * start 9/10 beacon nodes by default, last can be started manually * see also #134 * fix start.sh epoch length
2019-02-28 21:21:29 +00:00
$BEACON_NODE_BIN \
Automate the creation of the network metadata files With these changes, running a simulation is very close to running an actual testnet. Some checks have been added in the client to make sure you are not connecting to an incompatible network (e.g. a network running with a different number of shards).
2019-03-19 17:22:17 +00:00
--network:$NETWORK_METADATA_FILE \
add initial block pool (#139) * implement in-memory block graph * store tail block in database * resolve unknown parents by syncing them from peers * introduce concept of resolved blocks and attestations - those that follow minimal protocol rules * update state head lazily * log more stuff * shortHash -> shortLog * start 9/10 beacon nodes by default, last can be started manually * see also #134 * fix start.sh epoch length
2019-02-28 21:21:29 +00:00
--dataDir:$DATA_DIR \
Command-line and data storage handling for testnets
2019-03-18 03:54:08 +00:00
--validator:${V_PREFIX}0.privkey \
--validator:${V_PREFIX}1.privkey \
--validator:${V_PREFIX}2.privkey \
--validator:${V_PREFIX}3.privkey \
--validator:${V_PREFIX}4.privkey \
--validator:${V_PREFIX}5.privkey \
--validator:${V_PREFIX}6.privkey \
--validator:${V_PREFIX}7.privkey \
--validator:${V_PREFIX}8.privkey \
--validator:${V_PREFIX}9.privkey \
beacon node sim: various improvements (fixes #111) (#156) * allow running more or fewer validators * use deterministic key generation for tests to avoid exhausting system RNG * update README with simulator docs * write the data of each validator to separate file, instead of a big chainstart.json (makes it easier to run different validator counts)
2019-03-07 13:59:28 +00:00
--tcpPort:$PORT \
--udpPort:$PORT \
allow setting advertised external ip * detect it in start.sh
2019-03-19 03:57:19 +00:00
--nat:extip:$MYIP \
Automate the creation of the network metadata files With these changes, running a simulation is very close to running an actual testnet. Some checks have been added in the client to make sure you are not connecting to an incompatible network (e.g. a network running with a different number of shards).
2019-03-19 17:22:17 +00:00
--stateSnapshot:$SNAPSHOT_FILE