The registrar and auditor screens rebuilt for a phone: one column, sections collapsed to accordions with a sticky action bar in 2a, and the claims table linearised into stacked claim blocks in 2b rather than scrolled sideways. Same data, same grammar as 1a / 1b.
Try next: "expand section 04 in 2a" · "add a superseded claim to 2b" · "add a filter bar to 2b"
Brand blue #004AAD and periwinkle #8B95FF on the logo's cream #EDE4D8, in the Industry system's wireframe grammar: square corners, hairline rules, registration marks, Barlow Condensed over Barlow. All content is real repo data, the 26 demo vehicles from app/console/demo-vehicles.mjs, slots and rules from docs/FIELDS.md, ledger state and claim bounds from app/scan/demo-data.json.
Switch to Existing vehicle and the list becomes the five retrofit records, including 2016 Audi A4 2.0 TDI, the odometer-rollback attempt, and 2018 BMW 320d, written off with the clean claims declined.
All accepted. A new vehicle proves its four claims by construction, keepers 0, nothing on the record yet.
Each field is created under its integrity rule, fixed on the ledger at creation. None of these five may ever fall. Keepers 0 is what says new, never registered.
A claim the record cannot support aborts during proving and writes nothing, verification then shows “not proven”, never a false tick.
Which vehicle, which field, which bound, never the value. Superseded means the field has moved on since the proof was made: the claim was true of an earlier version.
| Claim | Proven against | State |
|---|---|---|
| Mileage ≤ 150,000 km odometerKm · slot 690615c169…02d86f | d23fc21635…634fc5 | current |
| Write-off category ≤ 0 writeOffCategory · slot 1c35bb205d…eace8d | d362758e70…bf1f5b | current |
| Reported accidents ≤ 0 accidentCount · slot 911f689d64…f095d7 | f5ad92ad0b…5c0791 | current |
| Keepers ≤ 1 ownerCount · slot a155446f51…0477e8 | 01d149526c…2261c7 | current |
| Mileage ≤ 200,000 km odometerKm · slot ab36d4e730…c6c3db | b04fda727e…81cb09 | current |
| Three clean-history claims were not requested, the write-off, accident and keeper proofs would have aborted in-circuit. Absence of a claim is what the verdict page renders, never a quiet “no”. | ||
VINPASSPORT
A zero-knowledge proof was accepted on the ledger. It could not have been produced unless the hidden reading satisfied the bound, and the reading itself was never published.
Proven against the anchored record, attributable to a named registrar, tamper-evident. Not a guarantee that the record matched physical reality when it was written, that is the registrar's word, which is why every passport names one.
Source · Midnight Network · Reg (EU) 2026/1738
VINPASSPORT
Nothing on the ledger answers this question. A failed proof writes nothing, and no proof was recorded, so the honest rendering is “not proven”. Ask the seller for it: if the claim is true of the record, producing it costs one transaction.
Try next: "in 1a show the retrofit list with the Audi rollback selected" · "give 1c a QR-scan landing state" · "expose all 26 slots as a panel view in 1a"