i took from the hash: "0x56c9b4417bafc42766888bae53959de8f0e5ac898eec6b30880c340f45d6ede9", and put this hash in deposit_contract_block.txt
then I tried to execute everything and run as you provide but I get a notification like this: Node is syncing - Service Unavailable: Node is syncing - waiting for peers - Failed to obtain attester duty.
in the beacon node they get peer : info: Searching peers - peers: 1 - slot: 3264964 (skipped 3264964) - head: 0 0 0x9e15…5549 - execution: valid(0x56c9…ede9) - finalized: 0x0000…0000:0
in geth I get something like this: Beacon client online, but never received consensus updates. Please ensure your beacon client is operational to follow the chain!
Genesis time should not be more than 32 slots behind current time. For example if your SECONDS_PER_SLOT value is 12, then genesis time must not be more than 384 seconds in the past when starting the network.
There is a known issue (github.com/ChainSafe/lodestar/issu...) were Lodestar won't be able to sync due to a genesis time to far in the past and no peers to range sync historical data from.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
eth. getBlockByNumber(0)
i took from the hash: "0x56c9b4417bafc42766888bae53959de8f0e5ac898eec6b30880c340f45d6ede9", and put this hash in deposit_contract_block.txt
then I tried to execute everything and run as you provide but I get a notification like this:
Node is syncing - Service Unavailable: Node is syncing - waiting for peers - Failed to obtain attester duty.in the beacon node they get peer :
info: Searching peers - peers: 1 - slot: 3264964 (skipped 3264964) - head: 0 0 0x9e15…5549 - execution: valid(0x56c9…ede9) - finalized: 0x0000…0000:0in geth I get something like this:
Beacon client online, but never received consensus updates. Please ensure your beacon client is operational to follow the chain!slot: 3264964 (skipped 3264964)indicates that something is wrong with your genesis timestamp. it should be less than 32 ideally.sorry, sir, what do you mean, can I just change my timestamp to number 32?
Genesis time should not be more than 32 slots behind current time. For example if your
SECONDS_PER_SLOTvalue is 12, then genesis time must not be more than 384 seconds in the past when starting the network.There is a known issue (github.com/ChainSafe/lodestar/issu...) were Lodestar won't be able to sync due to a genesis time to far in the past and no peers to range sync historical data from.