If your product, your risk score, or your compliance file depends on our numbers, you need more than an API that answers — you need data that can be reproduced, traced, and proven after the fact. This page describes the machinery that makes MadeOnSol data evidence-grade, all of it live in production today.
The one-line version: point-in-time queryable, request-traceable, immutably archived, continuously verified.
Reputation and risk data is stored write-on-change with full history: deployer reputation snapshots and wallet-flag histories record what we knew and when we knew it. Supported endpoints accept ?as_of=, answering "was this wallet flagged at the time?" — the question a listing review or backtest actually needs — without retroactive relabeling. Nightly fingerprinted dataset manifests (an md5 schema hash plus a content fingerprint) pin what each dataset contained on each date (GET /api/v1/manifests, keyed) — see the data dictionary for what every dataset covers, how far back it goes, and whether a gap in it is backfillable.
Every v1 API response carries an X-Request-Id, logged in an audit trail — 90 days standard, 730 days on Business keys. When a number ends up in your product, your report, or in front of a regulator, you can point at the exact request that produced it.
Every closed month of trade tape and candles is exported to Parquet with per-file SHA-256 checksums in a manifest ledger, stored with two independent providers under S3 Object Lock — write-once retention that we cannot modify or delete during the lock window, by construction. Read-back drills restore and re-verify checksums from cold storage on a schedule.
Correctness is a monitored production system, not a launch-day claim: 136 checks every 15 minutes, a 207-case suite twice daily, and 425 cases nightly compare served values against on-chain ground truth and independent references. Results are public, live, and include the failures.
Live verification & statusLatency claims come with sample sizes, vantages, and error bars — including a continuously self-audited detection head-start metric reconciled against every confirmed launch. Where a comparison was one-off, the page says so and dates it.
Latency benchmarksThree dedicated EU servers across two providers, a warm standby replicating with ~1 minute of data loss tolerance, and a rehearsed full restore (roughly 3–3.5 hours, drilled monthly from off-site backups — measured, not assumed). Deploys are blue-green and zero-downtime; the paid WebSocket streams run on separate processes that deploys never touch.
The paperwork side lives here — how scores are computed, how data is protected, and what we sign: