Skip to content

Blast is shutting down, and leaves every bench it was on - #2971

Merged
Flotapponnier merged 1 commit into
devfrom
chore/remove-blast
Oct 13, 2026
Merged

Flotapponnier merged 1 commit into
devfrom
chore/remove-blast

Conversation

@Flotapponnier

Copy link
Copy Markdown
Collaborator

Blast (the L2) is being shut down; this removes it from every bench, plus its logo.

  • blast-rpc retired: spec deleted, slug added to REMOVED_BENCH_SLUGS + middleware matcher → 410 Gone on the indexed URL.
  • Rows removed from l2-block-time, network-fees, chain-bridged-tvl, with the prose/findings/FAQ that named Blast (l2-block-time answer now 8 L2s; rpc-capabilities copy 25 chains).
  • /chains/blast removed (chain registry, /products/blast redirect, KPI label), plus live and speedtest chain lists, provider-registry entry, public/logos/blast.png and its manifest aliases.
  • Harnesses: l2-block-time, transaction-fee, rpc-capabilities (4 Blast RPC providers + 3 leftover Blast API probes on Arbitrum/Base/BNB that no bench displayed and that Alchemy now serves), chain-kpis, and the RPC bench generator script.
  • Predict Fun's chain label → BNB Chain (label only; data is read by DefiLlama protocol slug).

Kept on purpose: chain-id maps in the bridge harnesses (name translation only), historical mentions of Blast API (the provider) in exclusion notes.

Checks: pnpm validate (246 specs), tsc, bun test (579 pass), go build + go test on the five touched harnesses.

The L2 goes, so does everything we measured on it:
- blast-rpc retired: spec deleted, slug in REMOVED_BENCH_SLUGS and the
  middleware matcher, so the indexed URL answers 410 Gone.
- its rows on l2-block-time, network-fees and chain-bridged-tvl, with
  the prose, findings and FAQs that named it (l2-block-time is 8 L2s).
- the /chains/blast page (chain registry, the /products/blast redirect,
  kpi label), the live and speedtest chain lists, the registry entry and
  the logo.
- harness entries: l2-block-time, transaction-fee, rpc-capabilities
  (the 4 Blast RPC providers, and the 3 leftover Blast API probes on
  Arbitrum, Base and BNB, which no bench showed and which Alchemy now
  answers), chain-kpis, and the RPC bench generator.

Predict Fun's chain label moves to BNB Chain, its other deployment; the
venue is read by DefiLlama protocol slug, so its data does not change.
Chain-id maps in the bridge harnesses stay: they only translate names.
@Flotapponnier
Flotapponnier merged commit 347a4a8 into dev Oct 13, 2026
2 checks passed
@Flotapponnier
Flotapponnier deleted the chore/remove-blast branch October 13, 2026 21:26
Flotapponnier added a commit that referenced this pull request Oct 13, 2026
The L2 goes, so does everything we measured on it:
- blast-rpc retired: spec deleted, slug in REMOVED_BENCH_SLUGS and the
  middleware matcher, so the indexed URL answers 410 Gone.
- its rows on l2-block-time, network-fees and chain-bridged-tvl, with
  the prose, findings and FAQs that named it (l2-block-time is 8 L2s).
- the /chains/blast page (chain registry, the /products/blast redirect,
  kpi label), the live and speedtest chain lists, the registry entry and
  the logo.
- harness entries: l2-block-time, transaction-fee, rpc-capabilities
  (the 4 Blast RPC providers, and the 3 leftover Blast API probes on
  Arbitrum, Base and BNB, which no bench showed and which Alchemy now
  answers), chain-kpis, and the RPC bench generator.

Predict Fun's chain label moves to BNB Chain, its other deployment; the
venue is read by DefiLlama protocol slug, so its data does not change.
Chain-id maps in the bridge harnesses stay: they only translate names.

(cherry picked from commit 347a4a8)
Flotapponnier added a commit that referenced this pull request Oct 13, 2026
It used to 308 to /chains/blast. With the chain gone (#2971) it rendered
an indexable "Blast: chain benchmark" page from the worker's last blob.
Flotapponnier added a commit that referenced this pull request Oct 13, 2026
… (#2976)

It used to 308 to /chains/blast. With the chain gone (#2971) it rendered
an indexable "Blast: chain benchmark" page from the worker's last blob.

(cherry picked from commit 34b2c57)
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.

1 participant