Skip to content

Remove the Blast and Abstract datasets from the registries - #189

Closed
karelxfi wants to merge 1 commit into
mainfrom
remove-blast-abstract
Closed

karelxfi wants to merge 1 commit into
mainfrom
remove-blast-abstract

Conversation

@karelxfi

Copy link
Copy Markdown
Contributor

Requested by Karel

Before: blast-l2-mainnet, abstract-mainnet and abstract-testnet were listed in the SQD Network dataset list, the mainnet metadata catalog, the v2 archive list, and the Pipes CLI and create-squid network choices.

After: none of those registries list them, and they are in scripts/retired-datasets.json, so the metadata scripts and tests keep a stale catalog from restoring them.

How: the same files the Blast Sepolia removal touched. The Cloud RPC proxy id blast-l2.http in squid_manifest.json and the rpc-lore.json entry are left alone, since they describe RPC endpoints rather than datasets.

Merging removes the datasets from src/sqd-network/datasets.yml, so it belongs with the dataset retirement itself (ENG-2835, ENG-2881).

Checks: node --test tests/*.test.js (6 pass).

Fixes ENG-3255

🤖 Generated with Claude Code

blast-l2-mainnet, abstract-mainnet and abstract-testnet were retired on
October 20, 2026. Drop them from the SQD Network dataset list, the mainnet
metadata catalog, the v2 archive list and the Pipes CLI and create-squid
network choices, and add them to the retired-datasets list so a stale
catalog cannot restore them.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@karelxfi karelxfi self-assigned this Oct 20, 2026
@karelxfi

Copy link
Copy Markdown
Contributor Author

Anton already merged a different PR

@karelxfi karelxfi closed this Oct 21, 2026
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