Crypto Globe · 05

Crypto data providers

Every on-chain read CryptoSphere makes, where it comes from, and how it's combined into a single dossier per wallet.

EVM transfersEtherscan-family + Blockscout v2 (fallback) — ERC-20 and native, paginated.

EVM token balancesEthplorer — top holdings priced in USD.

Solana signaturesPublic RPC paginated aggressively for accurate inflow/outflow + firstSeen.

Solana token pricesJupiter v3 price API.

Bitcoinmempool.space — balance, tx history, counterparties.

TRONTronScan — TRX + TRC-20 transfers.

L2sBSC, Base, Polygon, Arbitrum, Optimism via their respective explorer APIs.

Token holders/api/public/holders — large-holder index per token.

Entity labelsSeed registry (curated exchanges, mixers, casinos, OFAC, scams) + logo.dev for brand artwork.

Caching & rate limits

Every external read goes through a server route with a short-TTL stale-while-revalidate cache. Wallet enrichment is cached for 60 seconds in the client and ~30 seconds at the edge so a typical investigation pivots through dozens of nodes without re-hitting the same provider. The trace endpoint caps fetches at 14 per request to stay inside the Worker time budget.

GET /api/public/wallet?chain=eth&address=0xabc…
GET /api/public/wallet-associates?address=0xabc…
GET /api/public/trace-victim?address=0xabc…&maxHops=3&minUsd=50
GET /api/public/holders?token=USDC

Privacy stance

CryptoSphere reads only public on-chain state. There's no KYC database, no custodian lookup, and no PII. Heuristic labels (mixer / sanctioned / scam) come from public registries (OFAC SDN, community-curated heist clusters) — treat them as investigative leads, not legal attribution.

← Previous

Forensic Case Brief

GeoSnag

ourwrld / documentation

← Back home Launch terminal