Verify any signed attestation, in your browser.
Paste a canonical payload, a signature, and the key you expect signed it. This page recovers the signer, rehashes the payload, and checks freshness entirely on your machine. No keys, no backend, nothing sent anywhere. Do not trust the issuer, and do not trust us. Check it yourself.
It proves a snapshot is authentic and fresh: that a named key signed those exact figures at that time. It is attestation tooling, not an audit, and it does not certify solvency.
Pre-loaded with Kerne's own hourly signed attestation from /api/por/signed so you can watch a real one pass, then edit a field and watch it fail. The same checks run on any issuer's signed snapshot, not just Kerne's. Want to read any stablecoin's live supply and reserve transparency instead? Use Verify Any Stablecoin. Or get your own machine-signed, point-in-time read of any single address, delivered on the page in about two minutes, with the instant signed read. Reading an ERC-4626 vault instead of a token? Use Verify Any Vault.
What the three checks are
Each is something you confirm directly, not something you take on faith. They are the same checks the relay behind /api/por/signed runs server-side, re-expressed here so you run them yourself.
The 65-byte signature is recovered, with audited secp256k1, to the address that produced it: standard EIP-191 personal_sign over the raw 32-byte attestation hash. You compare that recovered address to the key you expected.
The attestation hash is recomputed as sha256 of the exact canonical payload, and the signer is recovered over that derived hash, never over a hash you have to trust. Edit a single character in the payload and the recovered address no longer matches. The figures are bound to the signature, not printed next to it.
The timestamp lives inside the signed payload, so freshness is measured from the signed time itself, not from a relabelled wrapper. A genuinely signed but old snapshot reads as stale rather than passing.
Or start from a specific stablecoin
Each token below has its own diligence page: a live on-chain read of its supply and an honest, sourced answer to "can I verify its reserves myself, without trusting an attestor?" The reserve-leg verdict is on each card.
What a PASS means, stated plainly
A PASS proves that a specific key signed a specific reserve snapshot at a specific time, and that the published figures match what was signed. It is not an audit of anyone's contracts, not a guarantee that an issuer is solvent, and not financial, legal, or accounting advice. The reserve figures come from the issuer's own addresses and any venue balances they report. This tool makes those figures verifiable; it does not vouch for the business behind them. That honesty is the point: a proof anyone can check is worth more than a claim nobody can. If reserves are short, a faithful attestation will faithfully show the shortfall; it does not and cannot cure it.
What a PASS does not tell you: reachable depth
A signature binds a backing figure to a key and a time. It does not tell you how much of that backing you could actually withdraw right now. Those come apart whenever reserves are split across contracts, because a redemption is a single transaction against a single contract and pays only from that contract's own reserve. An issuer can be fully backed and still leave you unable to exit at size. The question to ask any issuer, including us, is not just what the reserves total, but how much is reachable in one transaction and from which address.
Our own answer, read live from the reserves
Instant, one transaction
$995.00
89.66% of outstanding kUSD
Total reachable, sequential
$1,110.89
across all PSM contracts
- 0xaBDE1138aa1Ce88d1dF06422C0c3b05D70569803 holds $30.00
- 0xFf3025ec18e301855aB0f36Ec6ECa115a29A5Fbc holds $85.89 (redeem only, minting role revoked)
- 0x07eBb486e11BD217e6085eb5ab663e4517595993 holds $995.00 (redeem only, minting role revoked)
New mints deposit their USDC into the live mint contract, so that reserve deepens with mint flow. The redeem only contracts hold the reserves from their own mint windows and are drawn down by redemptions. Reserves cannot be shuffled between contracts by an administrator: the module has no admin withdrawal, so USDC leaves only through a redemption or a fee skim.
Verify under redemptionDepth in /api/por →Want one of these over your own reserves?
Kerne produces a signed, point-in-time statement of your reserves that anyone verifies the same way you just did, without trusting you. A one-time snapshot, or a live endpoint that re-signs every hour.
Kerne is infrastructure and a service provider, not an auditor, custodian, or investment adviser. This tool is attestation tooling: it proves the authenticity, integrity, and freshness of a signed reserve snapshot. It is not an audit, a solvency opinion, or any form of investment, legal, tax, or accounting advice. Kerne is early: it has one completed external audit, published in full on July 31, 2026, and its deployed vault runs earlier bytecode than the reviewed commit, disclosed at kerne.fi/dataroom; this tooling stands on cryptography you verify independently, not on our posture. Everything you paste is verified locally in your browser and is not transmitted to Kerne.