Lighthouse: Witti: Did not trigger genesis

Created on 22 May 2020  ·  4Comments  ·  Source: sigp/lighthouse

~/.opt/sigp/lighthouse master* 1h 19m 18s
❯ lighthouse bn --http \
--testnet-dir ~/.opt/goerli/witti/lighthouse \
--eth1-endpoint http://127.0.0.1:9779
May 22 21:09:51.214 WARN Ethereum 2.0 is pre-release. This software is experimental.
May 22 21:09:51.214 INFO Data directory initialised              datadir: /home/user/.lighthouse
May 22 21:09:51.228 INFO Waiting for eth2 genesis from eth1      deposit_contract: 0x9eed6a5741e3d071d70817bed551d0078e9a2706, contract_deploy_block: 2740461, eth1_endpoint: http://127.0.0.1:9779, service: beacon
May 22 21:09:58.317 INFO Imported deposit log(s)                 new: 8, total: 8, latest_block: 2741153, service: beacon            
May 22 21:09:58.317 INFO Minimum genesis deposit count met       block_number: 2740838, deposit_count: 6, service: beacon            
May 22 21:09:58.376 INFO Inspected new eth1 block                block_number: 2740838, msg: did not trigger genesis, service: beacon
May 22 21:09:58.376 INFO Inspected new eth1 block                block_number: 2740839, msg: did not trigger genesis, service: beacon
May 22 21:09:58.376 INFO Inspected new eth1 block                block_number: 2740840, msg: did not trigger genesis, service: beacon
May 22 21:09:58.376 INFO Inspected new eth1 block                block_number: 2740841, msg: did not trigger genesis, service: beacon
May 22 21:09:58.377 INFO Inspected new eth1 block                block_number: 2740842, msg: did not trigger genesis, service: beacon
May 22 21:10:05.451 INFO Inspected new eth1 block                block_number: 2740843, msg: did not trigger genesis, service: beacon
May 22 21:10:05.451 INFO Inspected new eth1 block                block_number: 2740844, msg: did not trigger genesis, service: beacon
May 22 21:10:05.452 INFO Inspected new eth1 block                block_number: 2740845, msg: did not trigger genesis, service: beacon
May 22 21:10:05.452 INFO Inspected new eth1 block                block_number: 2740846, msg: did not trigger genesis, service: beacon
May 22 21:10:05.452 INFO Inspected new eth1 block                block_number: 2740847, msg: did not trigger genesis, service: beacon

Genesis was at 21:00:00 CEST, Prysm and Teku already chewing blocks.

master @ ea56dcb179d66b21f5e0af3bd6a3f62fc04d6736

Most helpful comment

May 25 18:55:18.918 INFO Connected to beacon node                version: Lighthouse/v0.1.2-unstable/x86_64-linux
May 25 18:55:18.920 INFO Starting node prior to genesis          seconds_to_wait: 111881

:+1: 0:00:00 am UTC, May 27, 2020

All 4 comments

So, I left it running and it launched the chain at 7:00:00 CEST - 10 hours later than Teku and Prysm.

Config: https://github.com/goerli/witti/tree/master/lighthouse

It's reproducible by the way. Once it _has_ a genesis,

  1. stop the node
  2. delete the beacon chain
  3. restart the node
  4. lh shows "did not trigger genesis" again even though it found a genesis earlier
May 23 11:15:06.001 WARN Low peer count                          peer_count: 0, service: slot_notifier
May 23 11:15:06.002 INFO Searching for peers                     current_slot: 1275, head_slot: 0, finalized_epoch: 0, finalized_root: 0x0000…0000, peers: 0, service: slot_notifier
May 23 11:15:12.101 WARN Skipping more than an epoch             request_slot: 1216, head_slot: 0, service: beacon
May 23 11:15:12.111 WARN Skipping more than an epoch             request_slot: 1248, head_slot: 0, service: beacon
May 23 11:15:18.001 WARN Low peer count                          peer_count: 0, service: slot_notifier
May 23 11:15:18.001 INFO Searching for peers                     current_slot: 1276, head_slot: 0, finalized_epoch: 0, finalized_root: 0x0000…0000, peers: 0, service: slot_notifier
May 23 11:15:24.102 WARN Skipping more than an epoch             request_slot: 1216, head_slot: 0, service: beacon
May 23 11:15:24.108 WARN Skipping more than an epoch             request_slot: 1276, head_slot: 0, service: beacon
May 23 11:15:24.109 WARN Skipping more than an epoch             request_slot: 1248, head_slot: 0, service: beacon
^C
May 23 11:15:25.668 INFO Shutting down..
May 23 11:15:25.668 INFO HTTP service shutdown                   service: http
May 23 11:15:25.668 INFO Saved DHT state                         service: network
May 23 11:15:25.668 INFO Network service shutdown                service: network
May 23 11:15:25.669 INFO Sync Manager shutdown                   service: sync
May 23 11:15:25.674 INFO Saved beacon chain to disk              service: beacon

~/.opt/sigp/lighthouse master* 1h 42m 35s
❯ rm -rf ~/.lighthouse/beacon 

~/.opt/sigp/lighthouse master*
❯ lighthouse bn --http \     
--testnet-dir ~/.opt/goerli/witti/lighthouse \
--eth1-endpoint http://127.0.0.1:9779
May 23 11:15:43.130 WARN Ethereum 2.0 is pre-release. This software is experimental.
May 23 11:15:43.130 INFO Data directory initialised              datadir: /home/user/.lighthouse
May 23 11:15:43.147 INFO Waiting for eth2 genesis from eth1      deposit_contract: 0x9eed6a5741e3d071d70817bed551d0078e9a2706, contract_deploy_block: 2740461, eth1_endpoint: http://127.0.0.1:9779, service: beacon
May 23 11:15:50.246 INFO Imported deposit log(s)                 new: 8, total: 8, latest_block: 2741153, service: beacon
May 23 11:15:50.247 INFO Minimum genesis deposit count met       block_number: 2740838, deposit_count: 6, service: beacon
May 23 11:15:50.318 INFO Inspected new eth1 block                block_number: 2740838, msg: did not trigger genesis, service: beacon
May 23 11:15:50.318 INFO Inspected new eth1 block                block_number: 2740839, msg: did not trigger genesis, service: beacon
May 23 11:15:50.319 INFO Inspected new eth1 block                block_number: 2740840, msg: did not trigger genesis, service: beacon
May 23 11:15:50.319 INFO Inspected new eth1 block                block_number: 2740841, msg: did not trigger genesis, service: beacon
May 23 11:15:50.319 INFO Inspected new eth1 block                block_number: 2740842, msg: did not trigger genesis, service: beacon
May 23 11:15:57.379 INFO Inspected new eth1 block                block_number: 2740843, msg: did not trigger genesis, service: beacon
May 23 11:15:57.379 INFO Inspected new eth1 block                block_number: 2740844, msg: did not trigger genesis, service: beacon
May 23 11:15:57.379 INFO Inspected new eth1 block                block_number: 2740845, msg: did not trigger genesis, service: beacon
May 23 11:15:57.379 INFO Inspected new eth1 block                block_number: 2740846, msg: did not trigger genesis, service: beacon
May 23 11:15:57.379 INFO Inspected new eth1 block                block_number: 2740847, msg: did not trigger genesis, service: beacon
May 23 11:16:04.437 INFO Inspected new eth1 block                block_number: 2740848, msg: did not trigger genesis, service: beacon

The faster-genesis branch appears to have fixed this issue.

May 25 18:55:20.758 INFO Genesis ceremony complete               genesis_time: 1590537600, genesis_validators: 6, service: beacon
May 25 18:55:20.766 INFO Block production enabled                method: json rpc via http, endpoint: http://127.0.0.1:9779
May 25 18:55:20.770 INFO Beacon chain initialized                head_slot: 0, head_block: 0x19aa…ba12, head_state: 0x773c…5b17, service: beacon

The genesis time appears to be correct. I'll check the root against the other clients once they are able to compute it.

May 25 18:55:18.918 INFO Connected to beacon node                version: Lighthouse/v0.1.2-unstable/x86_64-linux
May 25 18:55:18.920 INFO Starting node prior to genesis          seconds_to_wait: 111881

:+1: 0:00:00 am UTC, May 27, 2020

Was this page helpful?
0 / 5 - 0 ratings

Related issues

paulhauner picture paulhauner  ·  5Comments

paulhauner picture paulhauner  ·  3Comments

jrhea picture jrhea  ·  4Comments

paulhauner picture paulhauner  ·  4Comments

michaelsproul picture michaelsproul  ·  5Comments