Turing

Substrate Substrate

Turing is a Substrate-based blockchain network indexed by the SQD Network. Access real-time and historical data including blocks, transactions, and event logs through the SQD Portal API.

Quick Facts

Networks 1

Runtime Substrate

Real-time No

Data tables 0

Category Substrate

Networks: 1
Runtime: Substrate
Coverage: Archive
Start block: 0 (genesis)
License: Open-source SDK

Networks

turing-mainnet

Substrate mainnet 0 tables

Turing on SQD

Validated at ingestion

Turing data is validated by SQD Network workers before it reaches the Portal. Validation is performed across the network rather than by a single ingestion node, so a faulty upstream source can't poison the dataset.

Decoded, schema-typed

Turing data served as decoded, schema-typed tables, ready to query. Your indexer queries the data directly without writing SCALE parsers.

Full historical archive

SQD's Turing archive covers historical state in one endpoint. Real-time on the roadmap.

Open-source SDK

Both the Squid SDK and the Pipes SDK are open-source. Connectors for Postgres, ClickHouse, MongoDB, SQLite and Parquet, plus a custom-target hook. Run your Turing indexer on your own infrastructure or on SQD Cloud.

Build with Turing data

Common production patterns teams build with SQD on Turing.

DeFi & Trading

Index swaps, liquidations, and positions on Turing in real time.

Analytics

Build dashboards and metrics from full Turing historical state.

AI Agents

Give agents structured, decoded Turing data with the MCP server.

Wallets & Payments

Power balance, transfer, and history views for Turing wallets.

Compliance & KYT

Validated Turing data for transaction monitoring and audits.

Stablecoins

Track every mint, burn, and transfer of Turing stablecoins.

Real-World Assets

Auditable Turing data for tokenized RWA issuance and transfers.

Stream Turing data in two lines

Example below uses the public Turing endpoint, free for development. For full SDK reference, see the documentation.

1curl --compressed -X POST \
'https://portal.sqd.dev/datasets/turing-mainnet/stream' \
-H 'Content-Type: application/json' \
-d '{
    "type": "substrate",
    "fromBlock": 0,
    "toBlock": 100,
    "fields": {
      "block": {"number":true,"timestamp":true},
      "event": {"name":true,"args":true}
    },
    "events": [{}]
  }'

turing-mainnet/stream

Substrate · blocks 0–100

Frequently asked questions

How does SQD compare to running a Turing RPC node?

A Turing RPC node serves raw bytes for recent state and rate-limits per request. SQD's Portal pre-indexes the full Turing archive into decoded, schema-typed tables (blocks, transactions, logs) and serves them as a single streaming endpoint. You skip the multi-day node sync, archive storage, monitoring, and scale-out work, and pay only for the data you stream.

What does SQD cost for Turing data?

The public Portal endpoint at portal.sqd.dev/datasets/turing-mainnet is free for development. Production workloads run on the SQD Portal with tiered pricing based on the network and request volume. See the pricing page for current tiers, or contact us for an enterprise quote.

How is SQD's Turing data different from Subscan?

Block explorers are read-optimized for human browsing of single blocks or addresses. SQD is built for programmatic indexing: stream millions of Turing blocks into your own database, run analytical queries across the full history, and back production applications with decoded data. Output is structured tables, not HTML pages, and there are no per-call rate limits geared toward UI traffic. If you wanted to build your own Turing explorer, the SQD Portal is what you would back it with.

Can I self-host SQD's Turing indexer?

Yes. Both the Squid SDK and the Pipes SDK are open-source. You can run a Turing indexer on your own infrastructure pointing at the SQD Network or the Portal. SQD Cloud also offers managed hosting if you'd rather not operate it yourself.

Can I export Turing data to a data warehouse or pipeline?

Yes. The Pipes SDK streams Turing data from the Portal into Postgres, ClickHouse, MongoDB, SQLite, Parquet, or a custom target you implement. See the SDK docs for the connector reference.

Does SQD validate Turing data?

Every Turing block ingested into SQD is validated by the SQD Network workers (hash chain, parent reference, and where applicable finality) before it reaches the Portal. Validation is performed across the network, not by a single ingestion process, so a faulty upstream node can't poison the dataset.

Does SQD support real-time Turing data?

Turing historical data is available through the Portal archive. Real-time streaming for Turing is on the roadmap, contact us to flag your use case for prioritization.