blocks will no longer be generated after the container is restarted

[qymlyl]

1. docker compose stop
2. docker compose start
   blocks will no longer be generated after the container is restarted

[qymlyl]

and every time it restarts, it starts from the first block.

[qymlyl]

after restarting, beacon node will report an error
docker logs -f eth-pos-devnet-beacon-chain-1

[0xWilliamWang]

1. This may be a problem with the design of beacon-chain.
2. When a beacon-chain client is started after the entire network node goes down, it assumes that the peer's head slot is larger than its own. If this is not the case, it will be stuck in waiting. prysm/beacon-chain/p2p/peers/status.go at develop · prysmaticlabs/prysm
3. As a result, all beacon-chains are waiting for nodes with a larger head slot than their own, causing the entire network to be unable to move forward.

[haxjump]

I think this is what you want:

• https://github.com/NBnet/nbnet
• https://github.com/NBnet/nbnet-testnet
  @qymlyl

[fearlesssssssssss]

1. This may be a problem with the design of beacon-chain.
2. When a beacon-chain client is started after the entire network node goes down, it assumes that the peer's head slot is larger than its own. If this is not the case, it will be stuck in waiting. prysm/beacon-chain/p2p/peers/status.go at develop · prysmaticlabs/prysm
3. As a result, all beacon-chains are waiting for nodes with a larger head slot than their own, causing the entire network to be unable to move forward.

what if i clean the beacon-chain data to keep slot lower then geth? i've tried and had new problem:
geth log:
WARN [02-05|16:50:15.755] Beacon client online, but no consensus updates received in a while. Please fix your beacon client to follow the chain!
WARN [02-05|16:52:20.206] Forkchoice requested unknown head hash=ca804e..61db46

[0xWilliamWang]

what if i clean the beacon-chain data to keep slot lower then geth?

@fearlesssssssssss It might be better to create a new beacon chain OffchainLabs/prysm#14447 (comment)