erigontech / erigontech/erigon

Unwind Execution

Open
#15,663 1 comment 0 reactions 0 assignees View on GitHub
performance
Dominant language
Go
Stars
3.6k
Forks
1.5k
Avg merge
1d 16h
Merged PRs (30d)
455

Description

#### System information

Erigon version: `./erigon --version`
3.0.4
OS & Version: Windows/Linux/OSX
Linux
Commit hash:
406d855f
Erigon Command (with flags/config):
erigon --externalcl --chain hoodi --maxpeers 64 --datadir /mnt/data/user1 --ws --http.api=engine,eth,web3,net --authrpc.jwtsecret=/home/user1/jwtsecret --torrent.download.rate=512mb

Consensus Layer:
nimbus

Consensus Layer Command (with flags/config):

#TOML conf for consensus node configuration
#set network (i.e mainnet, hoodi)
network='hoodi'
#set execution client address and port
web3-url=["http://127.0.0.1:8551"]
#set the jwtsecret file produced durin execution client installation
jwt-secret='/home/user1/jwtsecret'
#activate the rest server
rest=true
#automatically update the ip address
enr-auto-update=true
#abilitate MEV
payload-builder=true
local-block-value-boost=10
payload-builder-url='https://127.0.0.1:18550/'
#data dir
data-dir='/mnt/data/user1/nimbus_data'
suggested-fee-recipient=0xeBF513D74d82e6D5f0389657fAc34F2dbB7c3786

Chain/Network:
Hoodi

#### Expected behaviour

Running smoothly

#### Actual behaviour

I got the log below with "aggregator unwind" statements, after that the node went out of sync and I missed two attestations.
What could be the reason for that ?

Jun 19 16:38:45 DESKTOP-7KMJH8K rc.local[934]: [INFO] [06-19|16:38:45.884] [NewPayload] Handling new payload height=635459 hash=0xd309093eb5192b2853d0b58395afed6f662ae86ff8807d23a766215d376aecf6
Jun 19 16:38:45 DESKTOP-7KMJH8K rc.local[934]: [INFO] [06-19|16:38:45.906] [4/6 Execution] Unwind Execution from=635473 to=635458
Jun 19 16:38:45 DESKTOP-7KMJH8K rc.local[934]: [INFO] [06-19|16:38:45.911] aggregator unwind step=5 txUnwindTo=8858473 stepsRangeInDB="accounts:0.7, storage:0.7, code:0.7, commitment:0.0, receipt:0.7, rcache:0.0, logaddrs: 0.7, logtopics: 0.7, tracesfrom: 0.7, tracesto: 0.7"
Jun 19 16:38:46 DESKTOP-7KMJH8K rc.local[936]: INF 2025-06-19 16:38:46.118+02:00 Slot end topics="beacnde" slot=677543 nextActionWait=1s877ms451us942ns nextAttestationSlot=677544 nextProposalSlot=-1 syncCommitteeDuties=none head=ec9ed079:677543
Jun 19 16:38:47 DESKTOP-7KMJH8K rc.local[936]: INF 2025-06-19 16:38:47.670+02:00 State replayed topics="chaindag" blocks=19 slots=37 current=ec9ed079:677543 ancestor=250f0007:677503@677504 target=51a139dc:677523@677541 ancestorStateRoot=ee00e214 targetStateRoot=6db77213 found=false assignDur=124ms179us835ns replayDur=1s406ms595us39ns
Jun 19 16:38:48 DESKTOP-7KMJH8K rc.local[936]: INF 2025-06-19 16:38:48.190+02:00 Missed multiple heartbeats topics="libp2p gossipsub" heartbeat=GossipSub delay=1s174ms764us918ns hinterval=700ms
Jun 19 16:38:48 DESKTOP-7KMJH8K rc.local[936]: INF 2025-06-19 16:38:48.202+02:00 Slot start topics="beacnde" head=ec9ed079:677543 delay=205ms702us125ns finalized=21171:eb9b4627 peers=160 slot=677544 sync=synced epoch=21173
Jun 19 16:38:49 DESKTOP-7KMJH8K rc.local[934]: [INFO] [06-19|16:38:49.880] [p2p] GoodPeers eth68=64 eth67=13
Jun 19 16:38:49 DESKTOP-7KMJH8K rc.local[934]: [INFO] [06-19|16:38:49.972] [mem] memory stats

#### Steps to reproduce the behaviour
Just running a node of hoodi for more than 24 hours.

#### Backtrace

````
[backtrace]
````

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.