MadeOnSolMade on Sol

Data APIs

Solana Data APIRobinhood Chain API

Intelligence

Telegram AlertsKOL TrackerWallet ScannerToken LookupDeployer Hunter
Trading BotsTrading TerminalsWallet TrackingToken Scanners
View all solutions
Optimization guidesAPI DocsWebSocket StreamingMCP & SDKsx402 for AI AgentsAgent Intelligence Gateway
Discover ToolsCompare ToolsSubmit a ToolAdvertiseBlog
Pricing
Get real-time feedsSign in
MadeOnSolMade on Sol

Solana and Robinhood Chain intelligence — KOL wallet tracking, deployer intelligence, all-DEX trade streams, and a developer API. Discover, compare, and build.

Product

  • Solana Data API
  • Solana Wallet Checker
  • Robinhood Chain Wallet Checker
  • Robinhood Chain API
  • Robinhood Chain x402
  • MCP Servers & SDKs
  • x402 for AI Agents
  • Agent Intelligence Gateway
  • Pricing
  • Enterprise / For Businesses

Solutions

  • Trading Bots
  • Wallet Tracking
  • Copy Trading
  • Token Scanners
  • Trading Terminals
  • DEX Data
  • Smart Money
  • Token Risk
  • AI Agents
  • ShredPrism Stream
  • View all solutions

Developers

  • Optimization guides
  • API Docs
  • WebSocket Streaming
  • Changelog
  • API Status
  • Latency Benchmarks
  • Data Integrity
  • Data Dictionary
  • Methodology

Resources

  • All Tools
  • Compare Tools
  • Best Trading Bots
  • Best DEXs
  • Best Wallets
  • Best Analytics
  • Best DeFi
  • Best Snipers
  • Blog
  • Blog Archive
  • Signal Scorecard
  • Tool Uptime
  • Community
  • Submit a Tool
  • Advertise

Company

  • About
  • Contact
  • Security
  • Privacy
  • Terms
  • DPA
  • Disclaimer

© 2026 MadeOnSol

MadeOnSol — eenmanszaak, Hulshout, Belgium · KBO/BTW BE 1039.535.538 (art. 56bis, no VAT charged)

Runs on our own dedicated EU servers — self-hosted data stack, own Robinhood Chain node · security

Powered by:constant·k — Private Solana RPC Services
Browse all guides
Optimization guidesValidate a KOL feed before increasing request volumeProcess webhook retries without duplicate effectsRecover a WebSocket feed after a disconnectReduce REST polling in a trading terminalMerge live candles with historical OHLCVCache KOL rankings while streaming tradesBudget REST calls and WebSocket slotsTake a MadeOnSol API integration from prototype to productionBuild reliable MadeOnSol WebSocket recoveryReduce MadeOnSol API calls with safe backend cachingScale a MadeOnSol terminal to multiple viewersInterpret token amounts, timestamps and data quality correctlyBuild reliable trading alerts with MadeOnSol dataMeasure MadeOnSol usage and choose the right API planKeep Solana top holder rankings in syncBuild a live Solana bundle monitorSize WebSocket bandwidth for a trading terminalCalculate locked liquidity across Solana poolsReconcile Robinhood Chain holder counts and transfersAPI reference
Optimization guidesValidate a KOL feed before increasing request volumeProcess webhook retries without duplicate effectsRecover a WebSocket feed after a disconnectReduce REST polling in a trading terminalMerge live candles with historical OHLCVCache KOL rankings while streaming tradesBudget REST calls and WebSocket slotsTake a MadeOnSol API integration from prototype to productionBuild reliable MadeOnSol WebSocket recoveryReduce MadeOnSol API calls with safe backend cachingScale a MadeOnSol terminal to multiple viewersInterpret token amounts, timestamps and data quality correctlyBuild reliable trading alerts with MadeOnSol dataMeasure MadeOnSol usage and choose the right API planKeep Solana top holder rankings in syncBuild a live Solana bundle monitorSize WebSocket bandwidth for a trading terminalCalculate locked liquidity across Solana poolsReconcile Robinhood Chain holder counts and transfersAPI reference
Optimization guidesKeep Solana top holder rankings in sync

Pro and above · ranked depth depends on plan · Compare plans and subscribe

Keep Solana top holder rankings in sync

Build a live Solana holder table from an indexed REST snapshot and WebSocket rankings. Handle rank changes, stale data and index rebuilds.

By MadeOnSol · Updated 2026-11-19

Integration choice

Use REST for the first paint and the holder channel’s snapshot as the baseline for live updates. Each accepted update carries the complete disclosed ranking. Replacing that list removes wallets that left the top ranks and preserves the index’s ordering.

Before you startImplementation stepsWhat happens when a wallet leaves the top ranks?Separate the last change from the last verificationChoose the right denominator and depthCode examplesCommon mistakesVerify your integrationProduction checklistQuestions

Before you start

  • Use a server-side API key and a mint with holder-index coverage.
  • Keep raw balances as integer strings or BigInt. Prepare a token switch and a reconnect in the test client.

Implementation steps

  1. Set SOLANA_MINT to a covered mint and fetch the indexed snapshot on your backend. Inspect source.method and index.status before using the rows. A census fallback is a separate observation.
  2. Subscribe to token:holders_top for the same mint. Track the holder payload’s mint, epoch and seq separately from the outer connection cursor. Install the channel snapshot before applying updates.
  3. Within one epoch ignore older snapshots and repeated updates. Replace the top array on a newer valid update, including when updates were coalesced. Publish rows, count and finalized slot together.
  4. On an epoch change or resync_required, wait for a new snapshot. If retaining the last verified view, keep its original timestamp and freshness state. A late REST response must not overwrite a newer stream snapshot.

What happens when a wallet leaves the top ranks?

In a three-row example, B can disappear because D overtook it. B may still own tokens. Replace the ordered list, key the display rows by owner and use the reported holder count for the population. Adding D to the old array would leave a plausible but incorrect fourth row.

Separate the last change from the last verification

A quiet token can keep the same ranking while its finalized verification slot advances. A heartbeat can advance verification for the current epoch. If it advertises a sequence ahead of your applied state, request a fresh snapshot. A stale frame carries the last verified observation. Record its age instead of stamping it with the current time.

Choose the right denominator and depth

The indexed ranking aggregates token accounts by owner. Pro exposes up to 10 rows, Ultra 50 and Business 100. The sum of these balances describes the disclosed slice. For a percentage of supply, use supply verified for that mint and slot. Leave the share unknown when the denominator is unavailable.

Code examples

Subscribe on an authenticated Node.js socket

const token = process.env.SOLANA_MINT;
if (!token) throw new Error("Set SOLANA_MINT first");
socket.send(JSON.stringify({
  type: "subscribe",
  sub_id: "solana-live-holder-rankings",
  channels: ["token:holders_top"],
  filters: { mints: [token] }
}));

Read the indexed ranking (server-side shell)

curl -H "Authorization: Bearer $MADEONSOL_API_KEY" "https://madeonsol.com/api/v1/tokens/$SOLANA_MINT/holders?source=index"

Common mistakes and fixes

Common integration mistakes and recommended fixes
MistakeRecommended fix
A wallet appears twice after a rank change.Replace the ordered rows atomically and use the owner as the display key.
A rebuild freezes the view.Reset the epoch baseline on a new snapshot. Sequences from separate epochs cannot be compared.

Verify your integration

Replay a three-row snapshot A/B/C, a newer update D/A/C, then the original snapshot in the same epoch. The final ordering must remain D/A/C. Repeat with a new epoch and with a heartbeat ahead of the applied sequence. Both cases need a new baseline.

Production checklist

  • An older HTTP response cannot overwrite the stream.
  • A departed rank leaves the table.
  • A stale observation retains its verification time.

Frequently asked questions

Can a holder sequence skip a number?

Yes. A valid, newer full-ranking update can cover coalesced changes. A heartbeat alone cannot reconstruct missing rows.

Does an uncovered mint have zero holders?

Coverage describes the index. Inspect the response source and keep the holder count unknown unless a source measured it.

Continue building

  • Build reliable MadeOnSol WebSocket recovery
  • Reduce REST polling in a trading terminal
  • Interpret token amounts, timestamps and data quality correctly

Match your plan to your workload

Compare capacity, channel access and display rights before launching.

Compare plans and subscribe
Read this guide as Markdown
Live terminal demoStreaming referenceAPI tier comparison