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

Home / Solutions / DeFi & Trading

DeFi & Trading

Real-time data for protocols managing billions

Index every swap, liquidation, and position change across 225+ networks. SQD validates data through a 6-step cryptographic pipeline, because when a missed event means a missed liquidation, "eventually consistent" isn't good enough.

Talk to us Try the Portal API

73% Fewer RPC calls

27ms P50 response time

6 Validation checks

Minutes Backfill time

Trusted by leading enterprises

Capabilities

Built for DeFi & Trading at scale

Cross-chain pool & swap indexing

Track every swap, mint, burn, and sync event across any AMM on any chain in a single query. No per-DEX adapters, no per-chain endpoints. One handler processes Uniswap V3 on Ethereum and PancakeSwap on BSC with identical TypeScript code.

Liquidation & health factor monitoring

Stream borrow, repay, and liquidation events from Aave, Compound, Morpho, and any lending protocol in real time. Combine state diffs with event logs to reconstruct health factors without polling RPCs, catch undercollateralized positions before the liquidation bots do.

TVL with validated event data

Calculate TVL from cryptographically verified transfer and deposit events, not from unreliable balance snapshots. SQD rebuilds Merkle-Patricia tries and validates receipt hashes, your TVL numbers match the chain, not an approximation of it.

MEV & order flow analysis

Full transaction traces and state diffs expose sandwich attacks, arbitrage paths, and front-running patterns. Reconstruct the exact execution order within a block, including internal calls and delegate calls that basic event indexing misses entirely.

Why It Matters

Most indexers skip internal transactions. That's where the money moves.

A Uniswap V3 swap triggers a top-level call, but the actual token transfers happen in nested internal calls. A Compound liquidation involves delegate calls across multiple contracts. If your indexer only captures event logs, you're seeing the receipt, not the execution.

SQD captures full execution traces including internal calls, delegate calls, and state diffs. When GMX moved from The Graph to SQD, they went from juggling dozens of subgraph handlers to processing multiple blockchain events in a single handler, with faster query performance and simpler debugging.

Curvance saw catch-up times drop from 3-5 days to minutes, and RPC calls reduced by 73%, from 1M to 270K per day. That's not optimization. That's a different architecture.

Data Validation Pipeline

Multi-RPC verification Cross-reference data across multiple RPC providers to detect inconsistencies before they reach your application

Merkle-Patricia trie rebuild Reconstruct the transaction root and validate structural integrity against the block header

Bloom filter verification Verify that log bloom filter bits match the actual events emitted, catches missing or phantom events

Receipt hash validation Compare the receipt trie root against network consensus to guarantee transaction outcome accuracy

State root verification Validate the world-state root hash to confirm storage mutations are authentic

Worker signing Every response is cryptographically signed by the serving worker, so you can trace exactly which node produced your data

Playground

Try the Portal API

Live queries against real blockchain data. Pick a network, choose a query, hit run.

Public endpoint is free, no API key needed. See plans for dedicated portals and higher limits.

Network+200 more

Query

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

Ethereumethereum-mainnet/stream

Transactions hitting the Uniswap router

These are example queries, explore the full Playground →

Use Cases

What teams build with SQD

Protocol analytics dashboards with cross-chain aggregation

Yield aggregator backends computing real APYs from onchain data

Liquidation keepers with sub-second event delivery

DEX aggregator data feeds across 225+ networks

Portfolio tracking with validated position data

Onchain order flow reconstruction for MEV research

Other ways teams use SQD

Analytics

Query full-history data from genesis across 225+ networks without running a single node.

AI Agents

LLMs can't parse raw hex calldata.

Wallets & Payments

Your users don't care which chain their tokens are on, they want to see everything in one feed.

Frequently asked questions

What's the latency on real-time DEX data?

The Portal serves DEX data (swaps, pool state, liquidity events) from chain head through the same endpoint as historical data. Latency depends on chain and tier; benchmarks measured by an independent customer running production traffic are on the Portal page. For latency-sensitive market-making or HFT execution, a co-located RPC node is still appropriate; SQD covers everything downstream of execution, including PnL accounting, risk monitoring, and client reporting. Production references include GMX and Levr.Bet.

Does SQD support liquidation events?

Yes. Liquidation events on lending and perpetual protocols (Aave, Compound, Morpho, GMX, dYdX, Hyperliquid, and similar) are indexed the same way any contract event is: define the ABI and SQD's typed decoders return liquidation events with borrower, collateral, debt, liquidator, and price-feed fields. Full execution traces and state diffs are available alongside event logs for reconstructing the liquidation path.

Which DEXes are pre-indexed?

SQD does not maintain pre-indexed datasets per DEX. Instead, any DEX with public onchain contracts can be indexed by pointing a Squid SDK indexer at the relevant factory and pair/pool contracts. Factory contracts can be tracked dynamically (Uniswap V2/V3/V4-style patterns) so new pools appear in the index automatically without manual contract updates. Production indexers for GMX, PancakeSwap, and UNCX are reference implementations.

Get started

Your blockchain data infrastructure, handled.

Private Portal. Dedicated. Validated. Managed. Tell us what you're building, we'll show you what it looks like on SQD.

Talk to Us Try the Public API

200+

Networks with
validated data

99.9%

Uptime SLA
for Enterprise

> 2 PB

Blockchain data
indexed & served