MadeOnSolMade on Sol
RobinhoodBlogAdvertise
Sign 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.

Discover

  • All Tools
  • Stacks
  • KOL Tracker
  • Deployer Hunter
  • KOL Scout Leaderboard
  • Robinhood Chain
  • Robinhood Wallet Scanner
  • Robinhood API
  • Robinhood Chain Stats
  • Robinhood Chain Tools
  • Solana API
  • Token Surge Alerts
  • WebSocket Streaming
  • Sniper Deploy Alerts
  • MCP Servers & SDKs
  • Datasets
  • API Pricing
  • Enterprise API
  • x402 for AI agents
  • Robinhood Chain x402
  • Yields
  • Blog
  • Blog Archive
  • Solana Glossary

Best Of

  • Best Trading Bots
  • Best DEXs
  • Best Wallets
  • Best Analytics
  • Best DeFi
  • Best Snipers

Compare

  • Wallets
  • DEXs
  • Snipers
  • TG Bots
  • Terminals
  • Analytics
  • Portfolio
  • Copy Trading
  • Security
  • Liquid Staking
  • RPC Providers
  • Bridges
  • Launchpads
  • NFT Marketplaces
  • Lending
  • Bot Calculator
  • Perps
  • Scanners
  • Data APIs

Resources

  • Submit a Tool
  • API Docs
  • Get an API Key
  • For Businesses
  • Affiliate Program
  • Changelog
  • API Status
  • Latency Benchmarks
  • Data Integrity
  • Data Dictionary
  • Tool Uptime
  • Signal Scorecard
  • Compare KOLs
  • Leaderboard
  • Community
  • Site Stats
  • Advertise

Legal

  • About
  • Contact
  • Terms
  • Privacy
  • Security
  • Methodology
  • 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

Follow us on XPowered by:constant·k — Private Solana RPC Services
Data Dictionary

Data Dictionary

Every dataset behind the MadeOnSol Solana & Robinhood Chain API — what it contains, how far back it goes, and whether a gap in it could ever be recovered. Coverage windows below are measured nightly against the live database, not asserted from memory; the same measurements are available at GET /api/v1/manifests.

Trade tape

Solana all-DEX trade tape

Every buy/sell across pump.fun, PumpSwap, Raydium, Orca, and Meteora — MEV-stripped, with executed price vs. pool price at the slot.

Permanent history
Coverage: Jun 1, 2026 → presentRows: ~443.5MBacks: /tokens/{mint}/trades, the DEX firehose WebSocket, dataset SKU exports
Permanent. The newest ~3 months live in Postgres; older months are exported to Parquet on two independent object-storage providers under Object Lock and served back transparently through the same endpoint — nothing is deleted, only relocated.

Robinhood Chain all-DEX trade tape

The same trade-tape treatment as token_trades, for Robinhood Chain (chain ID 4663) — Uniswap v2/v3/v4 and Pons.

Permanent history
Coverage: May 22, 2026 → presentRows: ~275.5MBacks: /rhc/trades, /rhc/tokens/{address}/trades, the RHC WebSocket channels
Permanent, same Parquet-archive mechanism as token_trades.

Price & momentum

Solana 1-minute OHLC candles

Price, market cap, liquidity, and volume per token, bucketed to the minute.

Permanent history
Coverage: Jun 17, 2026 → presentRows: ~241.2MBacks: /tokens/{mint}/candles, chart data across the site and API
Permanent, but accumulate-only with no rebuild path — candles are built incrementally as trades arrive and cannot be recomputed from raw trade history after the fact. If a bucket is ever missed or corrupted (an ingestion outage, a bug), that gap is permanent unless corrected by hand; it does not self-heal the way most of our other derived tables do.

Robinhood Chain 1-minute OHLC candles

The same candle treatment as token_ohlc_1m, for Robinhood Chain tokens.

Permanent history
Coverage: — → —Rows: ~—Backs: /rhc/tokens/{address}/candles
Permanent, same accumulate-only caveat as token_ohlc_1m applies.

Live token price & market-cap state

Current price, market cap, and liquidity state per token, updated continuously as trades arrive.

Rolling / current state
Coverage: May 6, 2026 → presentRows: ~3.3MBacks: Real-time price fields across /tokens and /token/{mint} responses
Not a historical archive — rows are pruned 90 days after a token's last trade. For price history over time, use token_ohlc_1m instead; this table reflects current state only.

Token momentum surge & revival events

Fired events when a token's price/volume crosses a surge or dormant-token-revival threshold, with the +1h outcome attached.

Rolling / current state
Coverage: Aug 28, 2026 → presentRows: ~9KBacks: /tokens/surges, the token:surges WebSocket channel
A 60-day rolling window, not a permanent archive.

Deployer & reputation

Deployer token history

Every token a tracked deployer wallet has launched, with bonding outcome.

Permanent history
Coverage: Jan 25, 2024 → presentRows: ~74KBacks: /deployer-hunter/{wallet}, /deployer-hunter/{wallet}/tokens
Kept forever — this is core deployer-reputation data, not a rolling log.

Deployer registry

The indexed deployer-wallet roster with current reputation tier and bonding-rate statistics.

Permanent history
Coverage: Mar 20, 2026 → presentRows: ~1.1MBacks: /deployer-hunter/{wallet}, the deployer-hunter leaderboard
Kept forever, continuously updated as new activity is observed.

Point-in-time deployer reputation history

One row per deployer per day their reputation state changed — the record behind our as-of (no look-ahead) reputation queries.

Permanent history
Coverage: Apr 8, 2026 → presentRows: ~2.2MBacks: /deployer-hunter/{wallet}/as-of?date=, /deployer-hunter/{wallet}/history
Kept forever, write-on-change. One known gap: 2026-07-10 has no snapshot (a cron failure that day) — that day's changes appear folded into the following day's row rather than dated separately.

Wallet intelligence

Tracked KOL wallet trades

Every trade from our tracked roster of influencer and smart-money wallets, with entry market cap and PnL context.

Permanent history
Coverage: Mar 19, 2026 → presentRows: ~4.8MBacks: /kol/feed, /kol/{wallet}, the kol:trades WebSocket channel
Kept forever as of a 2026-06-05 policy change (previously pruned at 180 days). Trades older than that window at the time of the change were already deleted and cannot be recovered — history is complete from that point forward, not before it.

Point-in-time wallet flag history

Write-on-change history of wallet flags — deployer, alpha, dump-cluster, KOL, sniper, and bundler tags — per wallet.

Permanent history
Coverage: Aug 28, 2026 → presentRows: ~1.1MBacks: /wallet/{address}/flags?as_of=
Kept forever from 2026-08-28 onward, when point-in-time tracking began. There is no retroactive history before that date — only the current-state flags, not what a wallet was flagged as on an earlier date.

Token metadata

Token lock & vesting schedules

Streamflow, Jupiter Lock, and Bonfida vesting/lock accounts subscribed per token.

Rolling / current state
Coverage: Aug 18, 2026 → presentRows: ~524KBacks: /tokens/{mint}/locks

Creator fee-share events

Pump.fun fee-sharing and social-handle claim events per token.

Rolling / current state
Coverage: Aug 17, 2026 → presentRows: ~328KBacks: /tokens/fee-claims, /tokens/{mint}/fee-shares

Frequently Asked Questions

How far back does MadeOnSol's data go?

It depends on the dataset — trade tape and candles go back to when we started capturing that specific stream (see the coverage window on each entry below, measured nightly, not estimated). Deployer and KOL reputation data is continuously enriched, so its usefulness grows with time rather than having a fixed start date.

Can old data ever be lost or become unbackfillable?

For most datasets, no — trade tape and candle data are either kept permanently in Postgres or exported to a dual-provider Parquet archive under Object Lock before being relocated, so nothing is deleted. A few datasets have genuine, disclosed exceptions: 1-minute candles (token_ohlc_1m / rhc_ohlc_1m) are built incrementally and have no rebuild path, so a gap from an outage is permanent unless corrected by hand. See each entry's backfill note below.

What does 'permanent' mean if a table is also pruned?

A few datasets in this dictionary are marked as rolling windows rather than permanent (e.g. token_prices, token_surge_events) — those reflect current state or a recent window by design, not full history. Where a permanent-history equivalent exists (e.g. token_ohlc_1m for price history vs token_prices for live state), we say so.

Where do the coverage numbers on this page come from?

A nightly job measures rows written in the last 24 hours, the earliest and latest event timestamp, and a row-count estimate for each dataset, and writes one row per dataset per night. The same numbers are available programmatically at GET /api/v1/manifests (any valid API key).

Related

Data IntegrityHow we keep it audit-gradeDataset DownloadsLicensed CSV/Parquet exportsAPI Pricing Free tier, 200 req/day