agglayer/aggkit v0.12.0-rc4

on GitHub

This release candidate is cut from the head of develop. The notes below are written relative to v0.12.0-rc3; the changes that make up v0.12.0 itself are described in the v0.12.0-rc1 notes.

🚀 What's New

• Skip missing (null) blocks on non-Ethereum networks (#1936, fixes #1935): on some non-Ethereum networks block numbers are not contiguous and eth_getBlockByNumber returns null for the missing ones, so a sync window ending on one of them made the sync retry forever. The new exceptional setting SupportNonEthereumWithMaxGapsInBlocks (in Common.L2RPC and L1NetworkConfig.RPC) makes the client resolve a missing block below the chain head to the nearest previous existing block, looking back at most N blocks. It is disabled by default (0, unchanged behaviour) and must be left at 0 on regular EVM chains. It is not supported by the multidownloader, which refuses to start with it enabled (not needed for now, tracked in #1937).
• Removal of the eth_getLogs completeness check (#1933, fixes #1930): reverts #1773. It removes the logsBloom completeness verification in the multidownloader and the legacy sync downloader, BlockHeader.LogsBloom, and the checkpoint-escalated reorg in l1infotreesync. This also fixes the slowdown of the l1infotreesync initial sync. The l1infotreesync0005 migration is kept (the l1info_checkpoint table is now unused).

⚠️ Breaking Changes

• 🛠️ Config: none. The new SupportNonEthereumWithMaxGapsInBlocks defaults to 0.
• 🔌 API/CLI: none.
• 🗑️ Deprecated Features: the completeness check and the checkpoint-escalated reorg introduced in #1773 are removed.

📋 Configuration Updates

[Common.L2RPC]
SupportNonEthereumWithMaxGapsInBlocks = 0   # 0 = disabled (default)

[L1NetworkConfig.RPC]
SupportNonEthereumWithMaxGapsInBlocks = 0

🔌 API Updates

• No changes in the Bridge service API, the Proxy API or other APIs.

Full Changelog: v0.12.0-rc3...v0.12.0-rc4