Tanssi

EVM Layer 1 / Chain ID 5678

Tanssi is a EVM-compatible 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 EVM

Chain ID 5678

Real-time No

Data tables 3

Category Layer 1

Networks: 1
Data tables: 3
Chain ID: 5678
Runtime: EVM
Coverage: Archive
Start block: 0 (genesis)
License: Open-source SDK

Networks

tanssi

EVM mainnet 3 tables

Tanssi on SQD

Validated at ingestion

Tanssi 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

3 Tanssi tables (blocks, transactions & logs), decoded and schema-typed, ready to query. Your indexer queries the data directly without writing RLP parsers.

Full historical archive

SQD's Tanssi 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 Tanssi indexer on your own infrastructure or on SQD Cloud.

Build with Tanssi data

Common production patterns teams build with SQD on Tanssi.

DeFi & Trading

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

Analytics

Build dashboards and metrics from full Tanssi historical state.

AI Agents

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

Wallets & Payments

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

Compliance & KYT

Validated Tanssi data for transaction monitoring and audits.

Stablecoins

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

Real-World Assets

Auditable Tanssi data for tokenized RWA issuance and transfers.

Available Data

blocks

Block headers with timestamps, gas usage, miner info, and consensus data.

transactions

All onchain transactions with sender, receiver, value, gas, and input data.

logs

Event logs emitted by smart contracts, the primary source for tracking DeFi, NFT, and token activity.

Stream Tanssi data in two lines

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

1curl --compressed -X POST \
'https://portal.sqd.dev/datasets/tanssi/stream' \
-H 'Content-Type: application/json' \
-d '{
    "type": "evm",
    "fromBlock": 0,
    "toBlock": 100,
    "fields": {
      "block": {"number":true,"timestamp":true},
      "transaction": {
        "hash": true,
        "from": true,
        "to": true,
        "value": true
      }
    },
    "transactions": [{}]
  }'

tanssi/stream

EVM · blocks 0–100

Frequently asked questions

How does SQD compare to running a Tanssi RPC node?

A Tanssi RPC node serves raw bytes for recent state and rate-limits per request. SQD's Portal pre-indexes the full Tanssi 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 Tanssi data?

The public Portal endpoint at portal.sqd.dev/datasets/tanssi 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 Tanssi data different from a block explorer like Etherscan?

Block explorers are read-optimized for human browsing of single blocks or addresses. SQD is built for programmatic indexing: stream millions of Tanssi 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 Tanssi explorer, the SQD Portal is what you would back it with.

Can I self-host SQD's Tanssi indexer?

Yes. Both the Squid SDK and the Pipes SDK are open-source. You can run a Tanssi 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 Tanssi data to a data warehouse or pipeline?

Yes. The Pipes SDK streams Tanssi 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 Tanssi data?

Every Tanssi 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 Tanssi data?

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