You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,6 +10,8 @@ Releases prior to 7.0 has been removed from this file to declutter search result
10
10
11
11
### Added
12
12
13
+
- context: Added `get_evm_portal_datasource` method to access `evm.sqd_portal` datasources from handlers and hooks with a precise type.
14
+
- evm.sqd_portal: Added a new datasource backed by the SQD Portal (`portal.sqd.dev`), a streaming alternative to the v2.archive `evm.subsquid` gateway.
13
15
- evm.subsquid, starknet.subsquid, substrate.subsquid: Added `api_key` option to authenticate with `v2.archive.subsquid.io` gateways, which require a key since 2026-05-19.
description: "DipDup uses Subsquid Network as a source of historical data for EVM-compatible blockchains."
2
+
title: "EVM: SQD Network"
3
+
description: "DipDup uses SQD Network (formerly Subsquid) as a source of historical data for EVM-compatible blockchains, served by the SQD Portal."
4
4
network: "ethereum"
5
5
---
6
6
7
-
# Subsquid Network
7
+
# SQD Network
8
8
9
9
{{ #include 3.datasources/_evm_banner.md }}
10
10
11
11
{{ #include 3.datasources/_subsquid_banner.md }}
12
12
13
-
DipDup uses [Subsquid Network](https://docs.subsquid.io/subsquid-network/reference/evm-api/) as a source of historical data for EVM-compatible blockchains.
13
+
DipDup uses [SQD Network](https://docs.sqd.dev) as a source of historical data for EVM-compatible blockchains. The recommended way to access it is the **SQD Portal** (`evm.sqd_portal`); the older `v2.archive` gateway (`evm.subsquid`) is still supported but [legacy](#v2-archive-gateway). DipDup uses the configured gateway when possible and falls back to EVM nodes for the latest data and realtime updates.
14
14
15
-
Configure the datasource in your project config:
15
+
## SQD Portal
16
+
17
+
[SQD Portal](https://portal.sqd.dev) is the current way to access SQD Network: a single streaming endpoint (NDJSON), keyless for public datasets. Configure it with the `evm.sqd_portal` kind and the per-dataset Portal URL:
`v2.archive.subsquid.io` gateways [require an API key](https://docs.sqd.dev/v2-keys) since 2026-05-19. Provide it via the `api_key` field; SQD Cloud users are unaffected.
27
+
## Adding to an index
22
28
23
-
Then, add it to EVM index definitions:
29
+
Reference the datasource by name in your EVM index definitions. Other datasources — Etherscan for ABIs, an EVM node for realtime data — can be listed alongside it:
`v2.archive.subsquid.io`gateways [require an API key](https://docs.sqd.dev/v2-keys) since 2026-05-19. Provide it via the `api_key` field; SQD Cloud users are unaffected.
DipDup uses [Subsquid Network](https://docs.subsquid.io/subsquid-network/reference/starknet-api/) as a source of historical data for Starknet blockchain.
Subsquid Network [has been rebranded](https://blog.sqd.dev/subsquid-becomes-sqd-meet-our-new-self/) to SQD Network. We keep using old name in documentation and config specification for compatibility reasons.
3
+
Subsquid Network has been [rebranded](https://blog.sqd.dev/subsquid-becomes-sqd-meet-our-new-self/) to **SQD Network**. The `subsquid` datasource kinds (e.g. `evm.subsquid`) keep the original name for backward compatibility.
0 commit comments