Kairos Signal / revision ledger / SOL — generated 2026-09-02 18:39 UTC from live ClickHouse

Solana (SOL) revision feed: has Solana's endpoints ever rewritten their own history?

This page is the point-in-time revision record for Solana (SOL). Our collectors snapshot Solana's public endpoints — the Solana mainnet RPC (api.mainnet-beta.solana.com), CoinGecko, DefiLlama's fees and chain summaries — on a fixed cadence and keep every observation we have ever recorded, including values that were later replaced upstream. When an upstream source replaces the value of an already-observed date, the detector writes one row to the revision ledger: the before-value, the after-value, both stamps, and the URL you can verify the current value against. Every other vendor overwrites; the before simply ceases to exist. Here it is the product.

Solana restatements on record: 0

Queried live at generation time: default.depin_revision_ledger holds zero rows for SOL. This is a measured property of the 2026-08-22–2026-09-01 archive, not a scope gap: the detector grades all six declared-cumulative Solana series it watches, and every one of them has been monotonic across the whole archive. Upstream Solana endpoints have not (yet) rewritten any historical value we hold.

• fees_alltime_usd — 10 snapshots (2026-08-23 → 2026-09-01), 0 backward moves, latest 1,585,280,121
• solana_absolute_slot — 7 snapshots (2026-08-25 → 2026-09-01), 0 backward moves, latest 443,547,090
• solana_block_height — 7 snapshots (2026-08-25 → 2026-09-01), 0 backward moves, latest 421,594,593
• solana_current_slot — 7 snapshots (2026-08-25 → 2026-09-01), 0 backward moves, latest 443,547,115
• solana_epoch — 7 snapshots (2026-08-25 → 2026-09-01), 0 backward moves, latest 1,026
• solana_transaction_count — 7 snapshots (2026-08-25 → 2026-09-01), 0 backward moves, latest 544,272,535,532

Proof query (run it yourself against the live feed):

curl -s "https://kairossignal.com/v1/revisions?symbol=SOL"

What we monitor for SOL — and its live monotonicity status

The detector only judges series that are cumulative by construction: a block height, an alltime fee counter, a transaction counter, an absolute slot. A gauge (active validators, price, market cap) legitimately falls when capacity or markets churn — that is not a revision and is never recorded as one. For every SOL series we hold, this is its measured state across the full archive, queried live:

solana_slot_index is the slot-within-epoch position — it resets each epoch by protocol design, so it is deliberately excluded from the declared-cumulative set (a reset there is an epoch boundary, not a rewrite). solana_slots_in_epoch is a protocol parameter (constant 432,000). Resolution rule: LATEST OBSERVATION WINS for current-state reads; the superseded value is retained, never deleted — retaining the before-value is the only reason a restatement is detectable at all.

Provenance — where SOL's archive comes from

Solana is the chain itself, so its first-party source is the Solana public RPC, which this estate collects from directly. Every row they wrote carries its own source, as_of and verify_url; this table is the live rollup of that.

Zero-value series, shipped with their evidence

Caveat: inflation_foundation is all-zero — as published

Every held row of this series is 0, exactly as the Solana RPC publishes it for the current epoch. The same RPC response yields non-zero inflation_total and inflation_validator (held beside it), so the zero is the upstream's own answer about foundation inflation this epoch — not a collection failure, not a silent fill. Held as published, per the estate's zero-is-a-real-observation rule.

Caveat: solana_first_available_block is all-zero — as published

The RPC's oldest-available-block field reads 0 on every snapshot we hold (the RPC node prunes its ledger depth; the field is not populated by the public endpoint). The same response yields the non-zero solana_block_height and solana_absolute_slot series held beside it. Held as published; the caveat ships with the series.

The estate-wide ledger — where restatements DO appear

SOL is currently the clean case. These networks are not: upstream sources for AR, AUKI, EIGEN, FLOCK, GRT, OVPP, R1, SOGNI, STORJ replaced already-published values after we recorded the original. Sorted by severity (most negative first). Same detector, same schema, zero human review:

Full queryable feed: /v1/revisions · per-symbol filter: GET /v1/revisions?symbol=AR · daily snapshot: REVISIONS_20260902.json · worked example of the moat: the Arweave −14.0% restatement.

How detection works — and what it cannot see

The detector (propintel/revision_ledger.py) diffs every daily snapshot this estate holds of every cumulative-by-construction series — counters that cannot decrease unless upstream rewrote them (alltime fees, token transfers, block heights). A row enters default.depin_revision_ledger iff two snapshots disagree for an already-observed date; zero human judgement. Population gauges (node counts, TVL, prices) legitimately move both ways and are deliberately excluded — a drop there is a real population change, not a rewrite. Honest boundary: this catches value-history rewrites ex-post; identical-schema semantic drift with plausible values is what the hash-pinned derivation_replay layer is for.

Verify any cell yourself — the exact commands

No account, no key, no trust required. Commands 1–2 hit this estate's public API (the same rows this page queried — every row carries source / as_of / verify_url); command 3 hits Solana's own public RPC, the first-party source this archive came from; command 4 is the estate's graded network row; command 5 is the frozen daily snapshot of the ledger. One polite call per endpoint, no hammering.

# 1) The served revision feed for SOL — the same rows this page queried, live:
curl -s "https://kairossignal.com/v1/revisions?symbol=SOL" | python3 -m json.tool
# 2) The estate-wide feed (every network, both sides of every diff):
curl -s "https://kairossignal.com/v1/revisions" | python3 -m json.tool | head -80
# 3) Solana's own public RPC (the first-party source this archive came from):
curl -s -H "User-Agent: kairos-check" "https://api.mainnet-beta.solana.com" \
  -X POST -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"getBlockHeight"}'
# 4) This estate's public API row for SOL (grades + provenance):
curl -s "https://kairossignal.com/v1/network/SOL" | python3 -m json.tool | head -60
# 5) The public daily snapshot of the ledger (frozen copy):
curl -s -o /dev/null -w "%{http_code}\n" "https://kairossignal.com/revision-ledger/REVISIONS_20260902.json"