All chains
ADI Chain

ADI Chain

EVM Layer 2 / Chain ID 36900 / Private dataset

ADI Chain is an Ethereum Layer 2 by ADI Foundation, built on the ZKsync stack for compliant onchain infrastructure in emerging markets.

Quick Facts
Access Private dataset
Runtime EVM
Chain ID 36900
Provisioning By request
Category Layer 2
Access
Private dataset
Chain ID
36900
Runtime
EVM
Provisioning
By request
License
Open-source SDK

ADI Chain on SQD

Validated at ingestion

ADI Chain 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

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

Full historical archive

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

Build with ADI Chain data

Common production patterns teams build with SQD on ADI Chain.

Get access to ADI Chain data

ADI Chain is available to Enterprise customers via SQD Private Portal.

Talk to the team

Get ADI Chain data on Private Portal. We'll reply with pricing and onboarding details.

Contact us

Frequently asked questions

How does SQD compare to running an ADI Chain RPC node?
An ADI Chain RPC node serves raw bytes for recent state and rate-limits per request. SQD's Portal pre-indexes the full ADI Chain 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 ADI Chain data?
ADI Chain is available to Enterprise customers via SQD Private Portal. Contact us for pricing.
How is SQD's ADI Chain 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 ADI Chain 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 ADI Chain explorer, the SQD Portal is what you would back it with.
Can I self-host SQD's ADI Chain indexer?
Yes. Both the Squid SDK and the Pipes SDK are open-source. You can run an ADI Chain 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 ADI Chain data to a data warehouse or pipeline?
Yes. The Pipes SDK streams ADI Chain 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 ADI Chain data?
Every ADI Chain 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 ADI Chain data?
ADI Chain historical data is available through the Portal archive. Real-time streaming for ADI Chain is on the roadmap, contact us to flag your use case for prioritization.

See other chains supported by SQD

Learn more

Start building with ADI Chain

Access ADI Chain data through the SQD Private Portal, provisioned by request.