Three registers on Flare, each answering a question the interested party is not allowed to answer about itself: did you pay, are the books real, is this the code you published. Every figure below is re-derivable from public RPC by anyone, and the protocol is never the counterparty — it holds no float, seeds no liquidity and underwrites nothing.
V2 RECONCILED
the promises were kept — or provably were not
A default does not record itself — redemptionPaymentDefault has to be called. Zero recorded defaults is the gap, not evidence against one.
[ Open the register ]V3 FALSIFIED
the books are the books
CLEAN, EXCEPTION or DISCLAIMER. A procedure that can only produce good news is marketing, so refusing to conclude is a first-class result.
[ Open the register ]V1 OBSERVABLE
the code is the code
Flare's documented recipe cannot rebuild Flare's own extension images. Resolved here — and only two of five are independently verifiable by anyone else.
[ Open the register ]§ 0.1 — The scale
A verdict tells you what a check said today. It does not tell you how much of the system you could establish for yourself. That is a different question, it is the one this project is built to answer, and it needs its own scale.
| Tier | Means |
|---|---|
| V0ASSERTED | The system states facts about itself and nothing independent confirms them. |
| V1OBSERVABLE | The facts are public, so a stranger can read them without asking permission. |
| V2RECONCILED | Two independent sources are compared, and a disagreement between them would be detected. |
| V3FALSIFIED | The comparison has been proven capable of failing — a fault was injected and it fired. |
Why V3 is the topA reconciliation nobody has ever seen fail is indistinguishable from one that cannot fail. This project shipped exactly that: an identity between two figures derived from the same storage slot, green every period, incapable of being anything else. V2 is where most good monitoring stops, and V2 is where that bug lived comfortably. V3 requires a fault to have been injected and caught — and it lapses after 30 days, because a falsification from six months ago says nothing about the code running today. The tier can go down, including ours.
A tier measures how much an outsider can check, not whether the system is safe, solvent or well-run. V3 means the check has been proven able to fail — not that nothing will.
Two ways inThe 66-second film states the argument; the proof deck walks every surface this project offers — each page, each instrument, each contract — with the evidence beside it. Every figure in both is read from the register that produced it.
Flare Summer SignalThis is a submission to both bounties — Interoperable Asset Products and Confidential Compute Apps. The full write-up covers how each Flare primitive is used, what was newly built, the deployed contract addresses, and the limitations we state rather than hide. [ Read the submission → ]
Everything we got wrong8 errata, 4 of which reached the public before being withdrawn — including a claim that 93 redemption agents had defaulted when every one of them had paid. Each entry names the exact wrong value, the mechanism, and the test that now makes it unconstructable. [ Read the errata → ]
What these will not doSay more than the evidence supports. Unresolved is not unpaid. Determinism is not verification. Unknown is not clean. Each register refuses to conclude where it cannot, and records that refusal rather than rounding it up to a pass.
Fig. 1 — Figures read from each register's own output at build time, never retyped.