# OnchainDivers Examples

> Executable examples for the OnchainDivers Solana, Polymarket, HyperLiquid, and Robinhood Chain indexers

## Docs

- [Bitcoin 5m Up/Down across two order books](/bitcoin-5m-cross-venue): This feature example starts from a question that requires all three
[OnchainDivers](https://onchaindivers.com) data surfaces: what did the prediction
market see while the underlying BTC futures book moved during one five-minute
resolution window?
- [Global fees API](/fees-api): The fees endpoint returns aggregate costs for one Solana mint. Configure its
complete URL privately; examples never contain the service host or port.
- [Solana Geyser service](/geyser): The original Geyser page has been incorporated into the complete
[Solana Nodes and Low-Latency Feeds](/solana-nodes) offering.
- [Simple microprice research](/microprice-research): This example asks a deliberately small market-microstructure question: does
visible bid/ask imbalance contain information about the midpoint 300
milliseconds later, either on the same venue or across venues?
- [Solana Nodes and Low-Latency Feeds](/solana-nodes): OnchainDivers provides managed Solana data infrastructure for applications that
need anything from a standard filtered gRPC stream to the earliest available
transaction-execution signals. All prices below are monthly in USD.
- [Verified Solana examples](/solana/examples): These queries are stored under `examples/solana/` and executed against the live
database during every strict docs build. Each scan is constrained by time or by
the newest data window.
- [Connect to the Solana indexer](/solana/getting-started): Connection details are provided with your OnchainDivers credentials. Keep them
in environment variables or a local `.env`; do not embed them in source code
- [Solana indexer](/solana): The Solana ClickHouse database exposes decoded DEX activity and reusable helper
tables. The table reference is generated from the live schema during the build.
- [Solana Tables](/solana/tables): Tables containing Solana blockchain data including DEX swaps, token trades, and transaction information.
- [DexScrAIner — AI Trading Assistant](/services/ai-assistant): An AI-powered assistant that answers questions about on-chain trading data using natural language.
- [Services](/services): Beyond data infrastructure, we offer specialized services for blockchain projects and trading operations.
- [WSOL Exchange](/services/wsol-exchange): The most efficient way to wrap and unwrap SOL on Solana.
- [Verified Robinhood Chain examples](/robinhood/examples): Robinhood data uses dedicated read-only credentials because `robinhood` is a
separate ClickHouse database. Configure these values in `.env`:
- [Robinhood Chain indexer](/robinhood): Robinhood Chain is an Ethereum-compatible Arbitrum Layer 2. OnchainDivers
provides its decoded token and Uniswap activity in a dedicated `robinhood`
ClickHouse database, separate from the Solana, Polymarket and HyperLiquid
datasets.
- [Robinhood Chain Tables](/robinhood/tables): Tables containing Robinhood Chain token metadata and decoded Uniswap v3/v4, Pons, and Varo pool, swap, and launchpad events.
- [Pump.fun parent programs: migrated vs not migrated](/research/pumpfun-migration-parent-programs): This study compares Pump.fun launches from the latest 24-hour data window.
For each token it counts distinct buys by `parent_program` during slots
`launch_slot + 1` through `launch_slot + 128`, keeps tokens with at least 48
buys, and labels it migrated when the mint appears in `pfamm_migrations` by
the cohort cutoff. Launches without a complete 128-slot horizon are excluded.
- [Most reliable Pump.fun token creators](/research/reliable-pumpfun-creators): This ranking starts with creators that launched at least five tokens in the
latest 24-hour data window. For every launch it counts distinct trades during
slots `launch_slot + 1` through `launch_slot + 100`, then ranks creators by
the minimum count across their launches. In other words, the leading creator
has the strongest worst-performing launch. Both buys and sells count as trades.
Only launches with a complete 100-slot observation horizon are included.
- [What is the best SWQoS landing provider for Meteora DLMM?](/research/swqos-providers-dlmm): Short answer: there is no single winner — it depends on the tip you are
willing to pay and how much you value landed-vs-failed reliability. This page
is a **data-driven shortlist** of the transaction-landing (SWQoS) relays that
Meteora DLMM traders actually pay, rebuilt from on-chain data on every
documentation build so you can compare them yourself.
- [What is the best SWQoS landing provider for PumpSwap?](/research/swqos-providers-pumpswap): Short answer: there is no single winner — it depends on the tip you are
willing to pay and how much you value landed-vs-failed reliability. This page
is a **data-driven shortlist** of the transaction-landing (SWQoS) relays that
PumpSwap traders actually pay, rebuilt from on-chain data on every
documentation build so you can compare them yourself.
- [What is the best SWQoS landing provider for Pump.fun?](/research/swqos-providers): Short answer: there is no single winner — it depends on the tip you are
willing to pay and how much you value landed-vs-failed reliability. This page
is a **data-driven shortlist** of the transaction-landing (SWQoS) relays that
Pump.fun traders actually pay, rebuilt from on-chain data on every
documentation build so you can compare them yourself.
- [Detecting wallet operator changes](/research/wallet-fingerprint-changes): A profitable public wallet can attract copytraders. If control of that wallet
changes, the address stays the same while the transaction builder often does not.
The indexer makes those construction details queryable, so monitoring can look
beyond PnL and token selection.
- [Verified Polymarket examples](/polymarket/examples): The checked-in query uses the current qualified table name and its partitioning
timestamp. It returns both token and USDC amounts, fees, maker attribution and
transaction context.
- [Polymarket indexer](/polymarket): The Polymarket database combines decoded Polygon fill events with current event
and market metadata.
- [Polymarket Tables](/polymarket/tables): Tables containing Polymarket prediction market data including order books, trades, and market information.
- [Verified HyperLiquid examples](/hyperliquid/examples): The query reads the current raw fill table and retains wallet, fee, builder,
TWAP and liquidation context through the underlying row.
- [HyperLiquid indexer](/hyperliquid): The HyperLiquid database exposes raw block fills together with derived order and
wallet views.
- [HyperLiquid Tables](/hyperliquid/tables): Tables containing HyperLiquid perpetual exchange data including trades, orders, and funding rates.