A verifier you do not control is a single point of failure.
On June 20, 2026, a synthetic dollar called msUSD lost most of its value within about a day. Not because a market moved against it, but because the outside firm that verified its reserves ended the arrangement and switched the feed off. The next day a separate vault, which by its founder's account had no exposure to msUSD at all, wound down too, swept into the same run. The one thing it shared with msUSD was the verifier. This page is about that specific, now-proven risk, the one that has nothing to do with whether your backing is good: who controls the proof of it.
It is also precise about what did not happen. The verifier did not collapse. It is a funded, growing company that terminated one client it judged out of standard, and it keeps verifying more than a billion dollars for others. msUSD did not fail because its verifier failed. It failed because it had exactly one verifier, and did not control it.
And it is honest about the limit of the answer. A signed snapshot changes who can cut your feed. It does not, and cannot, make a short reserve whole.
Attestation tooling, not an audit: it proves a reserve snapshot is real, untampered, and fresh. It does not certify solvency, and it would not have prevented an msUSD-style depeg if the backing were genuinely short.
This panel reads Kerne's hourly signed attestation from the public endpoint and verifies it in your browser right now. Kerne produces and publishes it; no third party holds it, so no third party can withdraw it. What it checks is also exactly what it does not: read the honesty line at the bottom of the panel.
- Signed by the expected keyThe signature recovers, independently, to the named signing key (signer_matches_expected).
- Figures bound to the signatureThe numbers and timestamp rehash to the signed attestation hash, so they cannot be edited after signing (hash_matches).
- Fresh, not a relabelled old oneLast signed 42 min ago; re-signed every 1 h. Freshness is measured from the signed timestamp itself (is_fresh).
Reproduce the verdict yourself:
curl -s https://kerne.fi/api/por/signed | jq '._meta.verified' # expected: true (the signature recovered, the numbers are bound, it is fresh)
The full recovery snippets (ethers, eth_account, cast) ship inside the endpoint under _meta.verify. A delivered snapshot for your protocol carries your own signer, your own addresses, and your real figures.
What this proves. That a named key signed this snapshot, the figures are bound to that signature, and it is recent. It is attestation, not an audit: it does not certify solvency and does not bless the numbers. A protocol whose reserves were short would still verify; the backing figure is where a shortfall would show.
The same recovery runs as a free tool you drive yourself, pre-loaded with this exact attestation. Recover the signing key from the signature, rehash the canonical payload, check the signed timestamp, then edit a single character and watch it fail. No keys, no backend, nothing leaves your machine.
Verify it yourself at kerne.fi/verifyWhat happened to msUSD
On June 20, 2026, msUSD, a synthetic dollar issued by MainStreet, fell from a dollar to reported lows somewhere between roughly six and twenty-nine cents within about a day, a drop variously reported between about 71 and 90 percent depending on the source and the hour it was read. The exact figure is genuinely unsettled. The trigger was not a trading loss.
Accountable, the third-party firm that provided msUSD's reserve verification, terminated its agreement with MainStreet and stopped publishing the feed, citing what it said was the project's failure to meet its verification standards, a characterization MainStreet disputes and which we address below. With the verification gone, the assurance the market had been pricing on vanished, and the token repriced almost immediately. The loss of verification, not a proven shortfall, is what set the repricing off.
Accountable says MainStreet failed its verification standards. MainStreet says msUSD remains fully backed, that the shutdown of a third-party dashboard does not reflect any loss of assets, and that it moved to support liquidity while seeking a new proof-of-reserves provider. Independent observers have questioned that account, and Kerne is not in a position to evaluate either side. As of June 24, 2026 the dispute is unresolved. We are not in a position to adjudicate it and this page does not try to. We take no view on whether msUSD was solvent.
The verifier did not fail. The dependence did.
It is worth being exact here, because the easy version of this story is wrong. Accountable, the verifier, did not go down. It is an active, funded company: it raised about 7.5 million dollars in a round led by Pantera Capital in late 2025, it reportedly verifies more than a billion dollars in assets, and it continues to serve a roster of other issuers. It made a judgment about one client and walked away from it.
That is the whole point. The thing that failed for msUSD was not the verifier's competence or solvency. It was the structure: a single outside party, holding the only proof the market had, with the unilateral ability to switch it off. When that party exercised an ordinary contractual right, the proof disappeared and the token had nothing left to stand on. Even a capable, well-funded verifier, acting entirely within its rights, can leave a counterparty that depends on it alone with nothing to stand on. Single-verifier dependence is the risk. The verifier being good does not remove it.
Contagion with zero exposure
The clearest evidence that this is structural and not a one-off came the next day. Altura, a vault on HyperEVM that by its founder's account held no exposure to msUSD or MainStreet at all, still saw a meaningful share of its reserves, on the order of 8.5 million dollars, pulled within roughly a day, and opted for an orderly wind-down rather than risk a disorderly run. Under the circumstances that was a responsible call, not a failure. Its founder was explicit that the vault had never held any exposure to MainStreet or its strategies.
So why the run? The only link was the verifier. Altura used the same third-party firm, Accountable, that had just walked away from msUSD. That shared dependency was enough. Holders could not be sure the verifier would keep standing behind Altura either, and once that doubt existed, the safe move was to leave. A protocol that did nothing wrong, and held nothing wrong, was still dragged down, purely because it depended on a verifier it did not run. That is what single-verifier dependence looks like when it spreads.
The lesson, said narrowly
Notice what is true regardless of who is right about msUSD's backing. The proof of its reserves lived with a single party it did not control, and that party was able to withdraw it. Once the feed was gone, holders could not check the backing for themselves, and the market did not wait for the dispute to resolve before repricing. The same dependency, on the same firm, then pulled down a second protocol that had no exposure to the first. Whether the books were fine or not, the availability of the proof was its own point of failure.
That is the only axis on which this story maps onto what Kerne builds, and the boundary is worth stating exactly. We are not saying an external verifier is bad, or that signing your own reserves makes a dollar safe. A proof reports reserves; it does not create them. If MainStreet's backing was in fact short, then no attestation arrangement, self-signed or third-party, would have made it whole; a faithful proof would only have shown the shortfall sooner. The narrow, durable lesson is about control of the proof, not the quality of the assets behind it: when the one thing that lets your counterparties check you depends on someone else's goodwill, you no longer control whether they can.
How the rest of the field verifies
This is not a knock on any of these protocols or their verifiers. Each arrangement below is a credible firm doing real work, and several are more established than Kerne. The point is only structural, and it is the same one msUSD ran into: each of these issuers relies on a verifier it does not operate, publishing on a periodic cadence. Kerne signs its own reserves, hourly, with its own key.
| Issuer | Reserve verification | Cadence |
|---|---|---|
| Ethena (USDe) | Chainlink, LlamaRisk, Chaos Labs, Harris and Trotter | Weekly attestation |
| Falcon (USDf) | HT Digital / Harris and Trotter, Chainlink | Weekly, plus quarterly ISAE 3000 |
| Resolv (USR) | Apostro | Third-party dashboard |
| Neutrl (NUSD) | Accountable | Third-party dashboard |
| Axis (USDx) | Accountable, Chainlink | Third-party dashboard |
| Kerne (kUSD) | Self-signed, verifiable against the chain by anyone | Hourly, self-hosted |
Verifier assignments above are drawn from each issuer's own public disclosures as of June 24, 2026. Self-hosting is a different trade, not a strictly better one: it removes the third-party-availability dependency, and it puts the burden of credibility on cryptography you can re-derive rather than on a name you recognize. Which is why the proof has to be one you can check without trusting us, in the panel above.
What a self-signed attestation does, and does not, prove
Kerne signs its own reserves every hour, with its own key, and publishes the result so anyone can re-derive it. Here is exactly what that buys, and exactly what it does not. Both columns matter equally; a page that only printed the left one would be the very thing this page warns against.
- Removes the third-party-availability dependency
No outside firm can switch Kerne's feed off, because no outside firm holds it. The attestation is produced and published by Kerne and verified by you. That is the one thing that failed for msUSD, and the one thing self-signing fixes.
- Proves authenticity, integrity, and freshness
A named key signed the snapshot, the figures and timestamp are bound to that signature so they cannot be edited after the fact, and the snapshot is recent. Those are the three checks the live panel above runs.
- Stands on inputs you check, not on Kerne's word
A self-signed number is not "trust me." Kerne's on-chain reserves are readable directly on Base, so you re-derive most of the backing against the chain yourself. The off-chain hedge leg is labeled client-reported and bound to the signature, with an independent attestation of that leg being scoped. The signature proves the snapshot is authentic; the chain proves most of the numbers.
- Certify solvency, or bless the numbers
This is attestation tooling. It proves that a specific key signed a specific reserve snapshot at a specific time, and that the published numbers match what was signed. It is not an audit of your contracts, not a guarantee that you are solvent, and not financial, legal, or accounting advice. The reserve figures come from your own on-chain addresses and any venue balances you report. We make those figures verifiable; we do not vouch for your business. That honesty is the point: a proof anyone can check is worth more than a claim nobody can. If your reserves are short, a faithful attestation will faithfully show the shortfall; it does not and cannot cure it.
- Prevent an msUSD-style depeg by itself
A signed feed nobody can cut would have kept the proof available. It would not have changed what the proof said. If a backing is genuinely short, the snapshot shows the shortfall; it does not fill it. A self-signed proof does not make a dollar safe, and any claim that it does is mistaken.
A proof of your reserves that no one else can withdraw
Kerne runs this over its own reserves every hour, and runs it for other issuers as a product. Each piece verifies the same way the panel above does: your counterparties check the cryptography themselves, without trusting you and without trusting us. Attestation tooling, not an audit.
A single, cryptographically signed, point-in-time statement, delivered in 3 to 5 business days. $1,500 flat, one time.
See the snapshotWe watch your pool, reserve ratio, and feed freshness on public data and alert your Discord or Telegram on deviation. From $99 a month.
See monitoringOne line of HTML or markdown drops a live, signed reserve-freshness badge into your footer or README. Free, nothing to install.
Get the badgeSee the live reference instance, the same stack run over Kerne's own reserves every hour, at /api/por/signed, check any signed attestation yourself at kerne.fi/verify, and read the public verification guide at kerne.fi/transparency.
Sources
The msUSD and Altura facts above are drawn from public reporting cross-verified on June 24, 2026, including The Block, crypto.news, Protos, CryptoTimes, KuCoin News, Yahoo Finance, Bitget News, CryptoAdventure, Incrypted, and Blockonomi. Accountable's funding is as reported by Decrypt, Blockworks, and The Defiant (October 2025). Reported figures are headline estimates and vary by source and by the hour they were read; "about" is implied throughout, and drop magnitudes are given as ranges for that reason. Each company's own statements are best sourced from its own canonical channels.
Kerne's claims on this page resolve to live endpoints: /api/por/signed, the in-browser verifier at /verify, and the public verification guide at /transparency. Related reading: the legible synthetic dollar, the Resolv mint-path breakdown, and the buyable Proof of Reserves snapshot.
Kerne is infrastructure and a service provider, not an auditor, custodian, or investment adviser. The signed reserve snapshot is attestation tooling: it proves the authenticity, integrity, and freshness of a reserve snapshot you provide from your own addresses and reported venues. It is not an audit, a solvency opinion, or any form of investment, legal, tax, or accounting advice. Kerne is early and not yet externally audited, disclosed at kerne.fi/dataroom; this tooling stands on cryptography you verify independently, not on our posture. Kerne is not affiliated with MainStreet, Accountable, Altura, or any protocol named on this page; statements attributed to them are as reported by the sources above, and no claim is made here about the solvency of any of them. Nothing here is financial advice.