Don't trust it. Check it.
Every day, AutoCoin hashes its bots' results into a Merkle root and signs it. This page recomputes everything in YOUR browser from the published bytes. Our word is not part of the math.
- 1.Fetches the day's attestation, leaf documents, and signature from this site
- 2.Recomputes every leaf hash and the Merkle root from raw bytes, in your browser, using WebCrypto
- 3.Checks the ed25519 signature over the canonical signed message against the published public key
- 4.Checks chain continuity: each day's attestation commits to the previous day's root
- 5.Checks the on-chain anchor transaction on Base, optionally through an RPC URL you provide
What this proves, and what it does not
It proves the record has not been changed. It does not prove the record was correct when written.
We hash what our systems measured. If a measurement was wrong, the wrong number is what gets immortalized, visibly. Live example we publish rather than hide: the data contains negative-equity snapshot rows from a known paper-engine accounting bug (since fixed). They stay attested as-is, because rewriting history, even buggy history, is exactly what this system makes impossible. Corrected values appear as new rows on new dates; the old rows stay.
Paper is not live.
Most bots currently run in paper mode. Every leaf is labeled env: paper or env: live, and every snapshot row carries its source. Paper results are simulations with idealized fills. This page never renders a series without its label.
Backfilled history starts trusting at first publication.
Roots for dates before the first on-chain anchor were generated retroactively. Tamper-evidence is real only from the moment a root lands on-chain; everything earlier is consistent with today's database, not proven unchanged since that date. The anchor timestamp renders next to the attestation date.
We attest our own measurements, not exchange records.
No venue co-signs these numbers. The strongest leaf is Hades: its trades are real Solana transactions, independently checkable on-chain by anyone. Brokerage and exchange equity numbers are our read of venue APIs.
The set of bots can change.
A bot deleted from the database would vanish from future attestations, but its rows in past attestations are immutable, and each attestation's coverage block tracks orphaned bot ids so silent disappearance is detectable.
This is not a performance claim.
Verified data is still trading data: volatile, sometimes negative, never a promise. AutoCoin is a self-directed software tool. Attestations exist so you can trust the numbers are real, not so anyone can promise what the numbers will be.
Pseudonymization is one-way.
Customer identities are not derivable from the published user references. Someone who already knows a specific internal id could confirm its presence; internal ids are not public.
The page is a convenience. The normative reference is the published spec and the offline reference implementation; any dispute resolves against the spec, the reference verifier, and the on-chain roots.