Infra Graveyard Weekly #03: Polygon dropped Erigon, and historical eth_getProof went with it

Deprecations and shutdowns in crypto infrastructure, the part a developer has to act on. "Days left" counts from 17 August 2026, and all times are UTC.

1. Deadline board

Closed since #02: Gnosisscan shut down 2026-08-11 23:59 UTC — the only board deadline that fell due this week. More on what that proves in the deep dive below.

DFK Chain retires in 11 days. Our open-source scanner of what would strand there: github.com/sergeipalii/dfk-chain-sunset.

2. New this week

Polygon dropped Erigon, and historical eth_getProof went with it [quiet]

What changed. Polygon PoS ended Erigon support on 2026-08-01 (announced on the forum 2026-05-12). The recommended replacement for archive needs is Bor with PBSS — but Bor does not store trie nodes, so historical eth_getProof is not served at all: only the last 128 blocks answer.

Who is affected. Anyone running a Polygon archive node or depending on historical state proofs, plus anyone using Erigon-specific namespaces through a provider. QuickNode moved from Erigon to Bor and removed erigon_* entirely, along with trace_filter, trace_get and trace_rawTransaction (Amoy 2026-07-01, mainnet 2026-07-15). The remaining trace_* methods still work — Bor serves them — and debug_trace* is the intended replacement for tracing. For historical proofs on Bor there is no replacement; that needs a third-party archive source.

Deadline. Already in effect since 2026-08-01.

Action. Check now whether anything in your stack relies on historical eth_getProof, erigon_*, trace_filter, trace_get or trace_rawTransaction. A team learns about this one not from the announcement — it read like a routine client recommendation — but the moment a production call stops answering.

Primary source: forum.polygon.technology/t/sunsetting-erigon-support/21872.

BitMEX is winding down in steps, not on one day [loud]

What changed. 2026-08-11 12:00 UTC: 18 derivative contracts delisted (announced 2026-08-02; the reason stated plainly — insufficient interest plus the exchange closing). 2026-08-14 12:00 UTC: five spot pairs — FTR, HYPE, STLS, LOT, ETH — stopped trading, open orders cancelled.

Who is affected. Anyone still holding positions or balances on BitMEX.

Deadline. Both steps above are already behind. Ahead: 2026-08-26 04:00 (new positions blocked, force-close begins) and 2026-09-23 04:00 (withdrawal-only; leftovers cost $50/mo or 1%/yr, whichever is greater).

Action. Close positions and withdraw before 2026-08-26 04:00 UTC.

Primary sources: bitmex.com/blog/delisting-aug2026-site, bitmex.com/blog/delisting-spot-aug2026.

3. Quiet changes

Sui: your provider's deadline may not be upstream's deadline [quiet]

Per Sui's own docs (checked 2026-08-10): JSON-RPC is already off on the Foundation's mainnet full nodes — "the week of July 27, 2026", a past event. What remains is code removal, "mid-October 2026", still with no exact day. Tatum's changelog merges the two into one: "fully deactivated at the end of July 2026". GetBlock describes it correctly, with the two events separated; upstream docs agree.

One provider out of those we checked — so this is an illustration of a rule, not an epidemic: when your dependency runs through an intermediary, verify the intermediary's date against upstream. They are sometimes two different dates describing two different events.

Primary sources: docs.sui.io/references/sui-api, docs.tatum.io/changelog/sui-json-rpc-migration-notice.

4. Deep dive: what a deadline board is for

Gnosisscan shut down on 2026-08-11 at 23:59 UTC. The line sat in issue #02's board with the date and a one-line action — repoint explorer links to a surviving Gnosis explorer — published nine days ahead. A reader who saw the line migrated on their own schedule. A reader who learned about it from the news afterwards did the same work as an emergency.

This is the first board deadline that fell due since we started publishing the board, which makes it the first verifiable case of the format doing its job. It is also the answer to a fair question: why keep lines with deadlines in 2027 and 2028 that nobody needs to act on yet? Because the value of the board is entirely in the distance between the line appearing and the date arriving. A deadline you meet in a changelog with a year to spare is an errand; the same deadline met in production is an incident.

The harder lesson this week points the other way: a shutdown that bypasses the board is more dangerous than one on it. Polygon's Erigon sunset had an announcement, a date and three months of lead time — and still lands on teams as a surprise, because the announcement read as an operational recommendation ("switch clients") while the consequence was a capability disappearing (historical proofs). No date check would have caught it. What catches it is a different question: when a vendor changes its recommended client, don't ask when — ask what the new client doesn't do.

5. Watch

• QuickNode Functions is deprecated — the docs are already gone, but no shutdown date is named anywhere. A dateless line doesn't qualify for the board; the moment a date appears, it's an item.
• Checked and dry this week: Etherscan changelog (nothing in August), Alchemy (the 2026-08-06 entry is node upgrades only), Chainlink (last entry 2026-07-26), Ethereum Foundation blog, The Graph, and the archived-repos sweep (nothing above the star threshold).

---

Infra Graveyard Weekly covers developer-facing deprecations and shutdowns in crypto infrastructure — the changelog layer, not the headlines. Subscribe via RSS.