-
Notifications
You must be signed in to change notification settings - Fork 114
Debugging state reconstruction
tersec edited this page Dec 4, 2018
·
6 revisions
Nimbus will start sync automatically as soon as it connects to enough peers. However if you want to run a clean experiment with networking factored out, you can start nimbus with discovery disabled and a single other eth node to sync from. To do so:
- Launch a local eth node, e.g:
geth --syncmode full --gcmode archive
- Note the enode url printed in the logs, e.g.:
enode://a52e914fa5aa46409e526a342a1e68b4e572c720e6eb1e61ad4a4201937679e7ebd26915bdabb2fdab6add7d85ba537078dbdccca89816a40ffc375572b6f73d@100.67.97.7:30303
- Launch nimbus with discovery disabled and use the enode from above (make sure to replace the ip address with
127.0.0.1
!) as bootnode:
nim c -r ./nimbus/nimbus.nim --port=30304 --nodiscover --bootnodes=enode://a52e914fa5aa46409e526a342a1e68b4e572c720e6eb1e61ad4a4201937679e7ebd26915bdabb2fdab6add7d85ba537078dbdccca89816a40ffc375572b6f73d@127.0.0.1:30303
Nimbus will start syncing with the local eth node.