What a verified record looks like — and how it fails.
This demonstration illustrates record structure and verification layers in the browser. It is not a production issuer, registry, KMS, replay service or trusted timestamp service. Example keys and records must never be reused for production evidence.
Ready. No record has been generated.
Prove it by making it fail.
A demonstration that only ever succeeds proves nothing. Generate a record above, then alter it. Each change re-runs verification from the record itself — the signing input is rebuilt from what the record actually contains, exactly as an independent verifier must do. Watch which layer fails, and which stays intact.
Run the demo above to enable these.
The loan outcome and the record-verification outcome are separate. A declined loan can still produce an accepted, authentic record. This page performs local key generation, signing and verification in the browser. The generated key is ephemeral and is discarded when the page is reloaded. The demonstration is not a production issuer, trust registry, replay service or trusted timestamp service.
What if a valid record is later removed from the history?
The transparency demonstration models inclusion proofs, signed checkpoints and monitor-based rollback detection.