Skip to content

Add CONFIG_UPDATE_LAST_EVENT_IPFS_HASH checkpoint - #210

Merged
evgeny-stakewise merged 1 commit into
masterfrom
config-update-ipfs-hash
Sep 28, 2026
Merged

evgeny-stakewise merged 1 commit into
masterfrom
config-update-ipfs-hash

Conversation

@evgeny-stakewise

Copy link
Copy Markdown
Contributor

Adds CONFIG_UPDATE_LAST_EVENT_IPFS_HASH to CheckpointsConfig: the configIpfsHash of the Keeper ConfigUpdated event at CONFIG_UPDATE_LAST_EVENT_BLOCK.

With a cold cache and no config update since CONFIG_UPDATE_CHECKPOINT_BLOCK, services currently re-read the event at CONFIG_UPDATE_LAST_EVENT_BLOCK from the execution node. That block is below the recommended pruning block on every network (e.g. hoodi 1,279,009 vs 3,580,000), so on a pruned node eth_getLogs fails with Pruned history unavailable. Shipping the hash lets services fetch the config from IPFS without touching pruned history.

Network Last event block IPFS hash
Mainnet 25,093,055 QmeCywDfupWC7jz5EDHsU5yEb2unAhn8iSGWBUEdrMjdMc
Hoodi 1,279,009 QmVqQyJ1TckGVshvYP7iMXhG46w5i2JyciwDqPkEnXijDH
Gnosis 42,392,284 QmWCdkpTifsge6t2NTwyb89PCXDXFNkfee9T5ZctEfrDDw

Hashes were decoded from the on-chain events. Bumps version to v0.15.1.

@evgeny-stakewise
evgeny-stakewise merged commit 0e6cc2b into master Sep 28, 2026
6 of 7 checks passed
@evgeny-stakewise
evgeny-stakewise deleted the config-update-ipfs-hash branch September 28, 2026 07:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants