Products
Data Access Portal API SQD Network Supported Chains
Development SDK SQD Cloud SQD 360
Solutions
By Use Case DeFi & Trading Analytics AI Agents Wallets & Payments Compliance
By Industry Stablecoins RWA All Customers
Developers
Get Started Documentation Subsquid Subsquid Labs Dev Chat
Resources
Learn Blog Changelog
Company About Ecosystem Brand Assets
Customers Pricing
Talk to us
All chains
Ink

Ink

EVM Layer 2 / Chain ID 57073

Ink is a DeFi-focused Layer 2 blockchain by Kraken, built on the OP Stack for fast and affordable decentralized finance.

Website
Quick Facts
Networks 1
Runtime EVM
Chain ID 57073
Real-time Yes
Data tables 5
Category Layer 2
Networks
1
Data tables
5
Chain ID
57073
Runtime
EVM
Coverage
Real-time + archive
Start block
0 (genesis)
License
Open-source SDK

Networks

ink-mainnet
Real-time EVM mainnet 5 tables

Ink on SQD

Validated at ingestion

Ink 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

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

Archive plus real-time

Single Portal endpoint serves Ink from genesis through the current head, with sub-second hot-path latency. No separate streaming pipeline to wire up.

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

Build with Ink data

Common production patterns teams build with SQD on Ink.

DeFi & Trading

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

Analytics

Build dashboards and metrics from full Ink historical state.

AI Agents

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

Wallets & Payments

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

Compliance & KYT

Validated Ink data for transaction monitoring and audits.

Stablecoins

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

Real-World Assets

Auditable Ink 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.

traces

Internal transactions and call traces showing the full execution path of each transaction.

state_diffs

State changes per transaction, storage slot modifications, balance changes, and nonce updates.

Stream Ink data in two lines

Example below uses the public Ink endpoint, no API key required for development. For full SDK reference, see the documentation.

1curl --compressed -X POST \
2 'https://portal.sqd.dev/datasets/ink-mainnet/stream' \
3 -H 'Content-Type: application/json' \
4 -d '{
5 "type": "evm",
6 "fromBlock": 0,
7 "toBlock": 100,
8 "fields": {
9 "block": {"number":true,"timestamp":true},
10 "transaction": {
11 "hash": true,
12 "from": true,
13 "to": true,
14 "value": true
15 }
16 },
17 "transactions": [{}]
18 }'
ink-mainnet/stream
EVM · blocks 0–100

Frequently asked questions

How does SQD compare to running an Ink RPC node?
An Ink RPC node serves raw bytes for recent state and rate-limits per request. SQD's Portal pre-indexes the full Ink archive into decoded, schema-typed tables (blocks, transactions, logs & traces) 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 Ink data?
The public Portal endpoint at portal.sqd.dev/datasets/ink-mainnet is free for development with no API key. 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 Ink 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 Ink 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 Ink explorer, the SQD Portal is what you would back it with.
Can I self-host SQD's Ink indexer?
Yes. Both the Squid SDK and the Pipes SDK are open-source. You can run an Ink 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 Ink data to a data warehouse or pipeline?
Yes. The Pipes SDK streams Ink 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 Ink data?
Every Ink 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 Ink data?
Yes. Ink is served with both real-time and historical data from the same Portal endpoint, with sub-second latency on the hot path. No separate streaming pipeline to wire up.

See other chains supported by SQD

Abstract Arbitrum Base Blast BOB Immutable zkEVM Katana Linea

Start building with Ink

Access Ink data through the SQD Portal, free tier available.

Try the Portal Read Docs