What happens on August 20
- Ingestion stops.
- Access ends on v2 gateways and Portal, wherever the dataset is served today.
Affected datasets
All 67 datasets
All 67 datasets
0g-testnetacalaaleph-zeroaleph-zero-evm-mainnetarthera-mainnetavailbasiliskberachain-bartiobifrost-kusamabifrost-polkadotbitfinity-mainnetbitgert-mainnetbridge-hub-kusamabridge-hub-polkadotcantocentrifugecereclovercollectives-polkadotcrustcyber-mainnetdarwiniadarwinia-crabdegen-chaindfk-chaindogechain-mainnetequilibriumfrequencygelato-arbitrum-blueberryimmutable-zkevm-mainnetintegriteeinterlayjoystreamkarurakhalakiltkintsugilitentrymerlin-mainnetmoonsamanakachainneon-devnetneon-mainnetozean-testnetpaseopendulumpeople-chainphalapicassoplume-devnetpolkadexpolymeshposeidon-testnetreefreef-testnetrobonomicsshibuya-substrateshiden-mainnetshiden-substrateskale-nebulasora-mainnetsubsocial-parachainsuperseed-mainnettanssiternoaturing-availturing-mainnet
What to do
Each entry above is the dataset name you’d see at the end of a Portal URL or in your Pipes config. Check your data sources against the list. Nothing you run should still depend on one of these after August 20. If you need to keep indexing one of these chains, you can run it off your own RPC instead:- Stay on your current processor. Drop
setGateway()and keepsetRpcEndpoint(). - Or upgrade to
EvmRpcDataSourceBuilderon EVM. Same query surface as the Portal stream, withsetRpc(...)in place ofsetPortal(...). - A private Portal. Run the Portal API yourself.
FAQ
Will any of these datasets come back?
Will any of these datasets come back?
Not in the current plan. If you need one of them, get in touch before August 20.
Where will future retirements be announced?
Where will future retirements be announced?
Here on the Announcements page and in our Telegram community.