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
Eclipse

Eclipse

Solana Layer 2

Eclipse is an Ethereum Layer 2 powered by the Solana Virtual Machine, combining Ethereum settlement with SVM execution.

Website
Quick Facts
Networks 2
Runtime Solana
Real-time No
Data tables 6
Category Layer 2
Networks
2
Data tables
6
Runtime
Solana / SVM
Coverage
Archive
Start block
0 (genesis)
License
Open-source SDK

Networks

eclipse-mainnet
Solana mainnet 6 tables
eclipse-testnet
Solana testnet 6 tables

Eclipse on SQD

Validated at ingestion

Eclipse 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

6 Eclipse tables (instructions, transactions, balances & token_balances), decoded and schema-typed, ready to query. Your indexer queries the data directly without writing binary parsers.

Full historical archive

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

Build with Eclipse data

Common production patterns teams build with SQD on Eclipse.

DeFi & Trading

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

Analytics

Build dashboards and metrics from full Eclipse historical state.

AI Agents

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

Wallets & Payments

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

Compliance & KYT

Validated Eclipse data for transaction monitoring and audits.

Stablecoins

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

Real-World Assets

Auditable Eclipse data for tokenized RWA issuance and transfers.

Available Data

instructions

Instructions data for Eclipse.

transactions

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

balances

Balances data for Eclipse.

token_balances

Token_balances data for Eclipse.

rewards

Rewards data for Eclipse.

logs

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

Stream Eclipse data in two lines

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

1curl --compressed -X POST \
2 'https://portal.sqd.dev/datasets/eclipse-mainnet/stream' \
3 -H 'Content-Type: application/json' \
4 -d '{
5 "type": "solana",
6 "fromBlock": 0,
7 "toBlock": 100,
8 "fields": {
9 "block": {"number":true,"timestamp":true},
10 "instruction": {"programId":true,"data":true}
11 },
12 "instructions": [{}]
13 }'
eclipse-mainnet/stream
Solana · blocks 0–100

Frequently asked questions

How does SQD compare to running an Eclipse RPC node?
An Eclipse RPC node serves raw bytes for recent state and rate-limits per request. SQD's Portal pre-indexes the full Eclipse archive into decoded, schema-typed tables (instructions, transactions, balances & token_balances) 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 Eclipse data?
The public Portal endpoint at portal.sqd.dev/datasets/eclipse-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 Eclipse data different from Solscan?
Block explorers are read-optimized for human browsing of single blocks or addresses. SQD is built for programmatic indexing: stream millions of Eclipse 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 Eclipse explorer, the SQD Portal is what you would back it with.
Can I self-host SQD's Eclipse indexer?
Yes. Both the Squid SDK and the Pipes SDK are open-source. You can run an Eclipse 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 Eclipse data to a data warehouse or pipeline?
Yes. The Pipes SDK streams Eclipse 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 Eclipse data?
Every Eclipse 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 Eclipse data?
Eclipse historical data is available through the Portal archive. Real-time streaming for Eclipse is on the roadmap, contact us to flag your use case for prioritization.

See other chains supported by SQD

SOON

Start building with Eclipse

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

Try the Portal Read Docs