No valid eth1_data deposit_contract_rpc on small testnet

avenbreaks commented 10 months ago

Description

I found an error in the lighthouse beacon node that shows Logs there is an error in _No valid eth1_data votes, votes_to_consider empty, outcome: casting state.eth1_data as eth1 vote, genesis_time: 1700129928, earliest_block_timestamp: 1700129868, lowest_block_number: 0, service: deposit_contractrpc. I used the tools from ethpandaops to build a testnet on the eth1 node runs smoothly and the validator can validate the block, but on the beacon node found the error. did I configure it wrong?

Log GETH

INFO [11-16|21:17:56.001] Starting work on payload                 id=0x8ed2d390d53c42e9
INFO [11-16|21:17:56.002] Updated payload                          id=0x8ed2d390d53c42e9 number=29 hash=a66611..d94619 txs=0 withdrawals=0 gas=0 fees=0 root=535442..a1b286 elapsed="44.89µs"
INFO [11-16|21:18:00.020] Stopping work on payload                 id=0x8ed2d390d53c42e9 reason=delivery

Log BN

Nov 16 13:12:44.029 INFO Sync signature included in contribution, validator: 3, src: api, slot: 869, epoch: 27, delay_ms: 7, head: 0x0bd2…988a, service: val_mon
Nov 16 13:12:48.001 INFO Prepared beacon proposer                parent_root: 0x0bd26b59e7dcd0b4f55acddfccbc88f288f9aec317e497d32aed19284b92988a, validator: 45, prepare_slot: 871, service: beacon
Nov 16 13:12:48.006 ERRO No valid eth1_data votes, `votes_to_consider` empty, outcome: casting `state.eth1_data` as eth1 vote, genesis_time: 1700129928, earliest_block_timestamp: 1700129868, lowest_block_number: 0, service: deposit_contract_rpc
Nov 16 13:12:48.019 INFO Signed block published to network via HTTP API, publish_delay: 1.148599ms, slot: 870
Nov 16 13:12:48.028 INFO Sync signature included in block        validator: 19, slot: 870, epoch: 27, head: 0x0bd2…988a, service: val_mon

Log VC

Nov 16 13:13:00.017 INFO Publishing signed block                 signing_time_ms: 9, slot: 871, service: block
Nov 16 13:13:00.032 INFO Successfully published block            slot: 871, graffiti: Some("Validator1"), attestations: 1, deposits: 0, block_type: Full, service: block
Nov 16 13:13:04.030 INFO Successfully published attestations     type: unaggregated, slot: 871, committee_index: 0, head_block: 0x19137a22a97b487b9494ad35f194ab76f0b55884de9a70503fd3c5f754972e2d, validator_indices: [44, 22, 18], count: 3, service: attestation
Nov 16 13:13:04.261 INFO Successfully published sync committee messages, slot: 871, head_block: 0x19137a22a97b487b9494ad35f194ab76f0b55884de9a70503fd3c5f754972e2d, count: 50, service: sync_committee
Nov 16 13:13:06.001 INFO Connected to beacon node(s)             synced: 1, available: 1, total: 1, service: notifier

System OS

A. 2 Server Deployed on AWS With LoadBalancer
B. Ubuntu 22.04
C. 1024 TB SSD NVMe 
D. 8vCPU
E. 16GB RAM

Lighthouse Version

Lighthouse v4.5.0-441fc16
BLS library: blst
SHA256 hardware acceleration: true
Allocator: jemalloc
Profile: release
Specs: mainnet (true), minimal (false), gnosis (false)

Geth Version

geth version 1.13.2-unstable-5c6f4b9f-20230919
go version go1.21.1 linux/amd64

michaelsproul commented 10 months ago

This is expected for networks that are merged from genesis. The deposit contract mechanism does not work for the first hours, and then starts to work. See https://github.com/sigp/lighthouse/issues/4536

michaelsproul commented 10 months ago

Long-term this will be fixed by EIP6110

avenbreaks commented 10 months ago

Hal ini diharapkan untuk jaringan yang digabungkan dari awal. Mekanisme kontrak deposit tidak berfungsi pada jam-jam pertama, dan kemudian mulai berfungsi. Lihat #4536

do I also have to change ETH1_FOLLOW_DISTANCE to higher? because currently the config is at 12

MIN_GENESIS_TIME: 1700129868 GENESIS_DELAY: 60 ETH1_FOLLOW_DISTANCE: 12

sigp / lighthouse