Don't trust it. Check it.
Every day, AutoCoin hashes its strategies' results into a Merkle root, signs it and anchors it on Base. This page reruns the checks in YOUR browser from the published bytes. Our word is not part of the math.
- 1.Fetches the day's attestation, leaf documents, signature and the signing-key registry 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 key registered for that date, and checks that key against the keys printed on this page
- 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
Who signs the daily files
Each daily file's signature.json must verify against the key registered for its date. Both keys are printed here and built into this page's verifier, so a key swapped on the data server alone fails the check.
2a32879031e04b7cfddb5bb752fc3e24ebd07f3c0d5b871d79223437d3842180Generated on and held only by our publishing server. Signs every daily file from the switch onward.
Key id autocoin-pop-publisher-2026-09 · Takes over signing at the switch; the key registry records its first date.
31b4b9cbcdbe5a91d6c013539265b4f406250f7feebbfc5efee1ef90684d150cMade in June 2026 while the publisher was being built; the earlier files call it a "LOCAL STUB KEY". It is not accepted for any date after the switch.
Key id autocoin-pop-placeholder-2026-06 · Signed the earlier daily files; the key registry records their dates.
Which key signed which dates: /pop/keys.json
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 sealed, in plain view. A live example we publish rather than hide: the attestation for 2026-06-11 contains negative-equity snapshot rows from a known accounting bug (since fixed). That file stays exactly as sealed, because rewriting history, even buggy history, is exactly what this system makes impossible. Each later attestation is built from the database as it stood on the day it was sealed; by then those rows had been corrected or removed, so they do not appear after 2026-06-11, and comparing the two days shows that change openly.
Demo is not live.
Every leaf and snapshot row in the signed data carries its environment and source. Demo 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. Every equity figure is our own daily measurement, sealed as measured; for brokerage and exchange accounts it is our read of the venue's API. One early attestation (2026-06-11) also carries a leaf of ten closed Hades trades on Solana; no attestation since includes Hades trades, so the current record rests on the strategy equity figures alone.
The set of strategies can change.
A strategy removed from the database drops out of later attestations, but its rows in earlier attestations cannot change. Anyone can compare the leaf lists of two days to see exactly which strategies dropped out, and each attestation's coverage block also lists snapshot rows whose strategy is missing.
What the attestation is for.
So you can trust the numbers are real, recomputed in your own browser from the published bytes. AutoCoin is self-directed software, and the record is what the machine did, in the open, every day.
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.
What the capital figure counts.
Capital on platform aggregates every running fleet on the platform, live and demo accounts alike. It is a scale-of-operations figure for the systems being verified here, not client assets under management.
Earlier files carry a placeholder signature.
The first daily files, from 2026-05-27 up to the switch to the publisher key, were signed with a placeholder key made while the publisher was being built, and their signature.json calls it a "LOCAL STUB KEY". We keep those files exactly as published and never re-sign them. Their integrity rests on the Merkle roots anchored on Base: each anchor is a public transaction with its own timestamp that cannot be edited afterwards. Every daily file after the switch is signed with the AutoCoin publisher key shown above, which is generated on and held only by our publishing server.
The page is a convenience. Every file it checks is public under /pop/, so anyone can rerun the same checks offline with standard SHA-256 and ed25519 tools; any dispute resolves against those files and the roots anchored on Base.