Evidence · Stellar Instawards
The record, not the brochure
Every claim on this site ends here: committed bundles of unedited RPC responses, explorer screenshots and verification scripts. Testnet is periodically reset — a hash pointing at a chain that no longer exists proves nothing, so the JSON and the screenshots travel with it.
committed bundles
59
in docs/evidence/, counted at build time — not a remembered number
extensions with hashes
5
9 Sep rescue ×3, 12 Sep manual save, 14 Sep engine save — each with its hash on the history page, plus the disclosed 5 Sep calibration round in the W1 inventory
invented figures
0
a panel with no real number shows no number; an empty cell labelled “not measured” is fine
Verify a bundle yourself
The manual-save proof ships an offline verifier. It checks semantic consistency anchored to the signed envelope — fee, sequence, payer, key and target bound to the transaction, signature and receipt verified, the receipt's own TTL state checked — with integrity via SHA256SUMS first. That is honestly what it checks: consistency with the envelope, not an independent re-observation of history.
Read-only and offline. Corrupt copies fail it; the original passes — six corruptions are rehearsed in the bundle's own review record.
Two manifests do not currently verify
Of the 16 bundles carrying a SHA256SUMS manifest, 14 pass and 2 fail. This is committed state, found while building this page and checked with the repository's own verify-evidence-integrity helper:
- 2026-09-14-scheduled-a-save — an acceptance banner was added to its README without regenerating the manifest, so the manifest no longer matches the file it covers. The transaction it records is unaffected and independently confirmed against the chain; it is the manifest that is stale, not the evidence.
- 2026-09-15-publish-dry-run — its single manifest line names a file that is not in the bundle, so it can never verify as written.
Nothing runs these verifiers in CI, which is how a README edit disarmed a bundle's integrity gate without anyone noticing. It is on this page rather than quietly omitted, because a verification claim nobody has run is the kind of claim this project exists to object to.
Where the deliverables stand
CLI. Scanning, rent estimates, manual extension proven on testnet with hashes. Evidence present.
Auto-bump engine. Decide-only runs, one engine-triggered save from a local timer, alert templates delivered. The production cron running unattended against a crossing is the September gate — open until B crosses.
Dashboard, Action, docs. This preview is the dashboard taking shape; the Action and the published package are Week 4 work. Not done, not claimed.