SQD Network

DipDup uses SQD Network 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. DipDup uses the configured gateway when possible and falls back to EVM nodes for the latest data and realtime updates.

SQD Portal

SQD Portal 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:

datasources:
  sqd_portal:
    kind: evm.sqd_portal
    url: https://portal.sqd.dev/datasets/ethereum-mainnet
    # api_key: ${SQD_PORTAL_API_KEY:-}  # optional

Adding to an index

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:

indexes:
  eth_usdt_events:
    kind: evm.events
    datasources:
      - sqd_portal
      - etherscan
      - evm_node
    handlers:
      - callback: on_transfer
        contract: eth_usdt
        name: Transfer

v2 archive gateway

The original worker-based v2.archive gateway uses the evm.subsquid kind:

datasources:
  subsquid:
    kind: evm.subsquid
    url: ${SUBSQUID_URL:-https://v2.archive.subsquid.io/network/ethereum-mainnet}
    api_key: ${SUBSQUID_API_KEY:-}

v2.archive.subsquid.io gateways require an API key since 2026-05-19. Provide it via the api_key field; SQD Cloud users are unaffected.