chore(eth): update Erigon 3.5.2->3.5.5

[cranycrane]

Updates the Erigon pin in all six Ethereum configs (mainnet, mainnet archive, Sepolia, Sepolia archive, Hoodi, Hoodi archive) from 3.5.2 to 3.5.5: version, both binary_urls (amd64 and the arm64 entry under platforms), and both verification_source hashes.

Why 3.5.2 needs to go

Blockbook builds its ERC20 transfer index from eth_getLogs, so an Erigon bug that misnumbers or invents logs is written straight into RocksDB and stays there. 3.5.2 is exposed to both known variants, and the fixes for both are in 3.5.5 only:

• #23064 (cherry-pick of #23061 into release/3.5) — receipt domains were never rolled back on an in-RAM reorg unwind: GetDiffset built a [kv.DomainLen] array but filled only the four domains that existed before ReceiptDomain was added, so ReceiptDomain/RCacheDomain came back nil. Small reorgs near the tip then leave eth_getLogs serving phantom logs with the wrong logIndex while eth_getBlockReceipts for the same block stays correct. The corruption survives restarts and gets frozen into the snapshot files. See erigontech/erigon#23062 — the first reported occurrence was on v3.5.2.
• #22951 — wrong logIndex on archive nodes, from receipt-domain reads bypassing the overlay DomainReader. Affects v3.5.1–v3.5.4.

Picked up on the way through 3.5.3/3.5.4:

• #22459 — JSON-RPC handleBatch deadlock; a filtered batch could wedge on wg.Wait() and time out. Blockbook batches heavily via BatchCallContext (token balances/metadata in bchain/coins/eth/contract.go).
• #22700 — native (C-allocated) memory leak in the RPC gzip path, ~9–15 GiB/day on an archive node with response compression enabled.

Notes

• Drop-in at every hop, no re-sync required (per each release's own notes).
• Checksums taken from the release's erigon_v3.5.5_checksums.txt.
• No exec_command_template change needed — nothing in 3.5.3/3.5.4/3.5.5 deprecates a flag we pass. 3.5.3's new --rpc.logs.querylimit is a different knob from our --rpc.logs.maxresults and its default preserves current behaviour.
• Upgrading does not repair damage already on disk. Nodes that ran 3.5.2 should be checked per suspect block by diffing eth_getLogs against eth_getBlockReceipts; if they disagree, the derived domains need the documented rebuild, and the affected block ranges need a Blockbook reindex.
• v3.5.2/v3.5.3 mainnet archive: small reorgs near tip leave persistent corruption in the derived receipt/log domains; eth_getLogs contradicts the node's own eth_getBlockReceipts, survives restarts, gets frozen into snapshot files erigontech/erigon#23062 is still open (its second defect, reorg paths that skip the on-disk unwind entirely, is milestoned 3.7.0), so this narrows the exposure rather than closing it.

🤖 Generated with Claude Code