search

BeaconCMS / beacon

Open-source content management system (CMS) built with Phoenix LiveView. Faster render times to boost SEO performance, even for the most content-heavy pages.
https://beaconcms.org
MIT License
1.04k stars 101 forks source link

Blockchain go to "Processing queued blocks for slashing detection" #572

Closed CoNETProject closed 3 months ago

CoNETProject commented 3 months ago

Hi there,

I developed a POS chain with GETH (version 1.14.3-stable-f6388d0b) & beacon. The chain running great & the block come to 448,593. I have over 70 nodes to maintenance the chain until I copy a full node's file to another new node. Then I try to launch the new node (geth & beacon & validator) to join.

Then the entire chain stops producing blocks and enters “Processing queued blocks for slashing detection”

time="2024-08-04 23:40:39" level=warning msg="Execution client is not syncing" prefix=execution
time="2024-08-04 23:40:43" level=info msg="Processing queued blocks for slashing detection" currentEpoch=74821 currentSlot=448926 numBlocks=0 prefix=slasher
time="2024-08-04 23:40:43" level=info msg="Pruning old attestations and proposals for slasher" currentEpoch=74784 prefix=slasher pruningAllBeforeEpoch=70688
time="2024-08-04 23:40:43" level=info msg="Done pruning old attestations and proposals for slasher" elapsed=217.291µs prefix=slasher
time="2024-08-04 23:40:51" level=info msg="Peer summary" activePeers=39 inbound=20 outbound=19 prefix=p2p

My question is:

  1. How long the chain can finish the "slashing detection" goto normal?
  2. Is that can be a kind of "attack" to a POS ETH?

Thanks