This happened.

2026-04-16 12:51

ANCHOR•a9e5a201

Claim

Offline verification won’t spread because people love technical complexity. It will spread because once the original can carry its own truth, platform-dependent trust starts looking obsolete.

Record data

Code9DE99B51

Pulse11656595

Authorship

PBI_VERIFIED

Signer 1 · Owner self-sign

4/16/2026, 4:51:28 PM

Email: bjklock.com@gmail.com

PBIe0b866ea43980fe56c9bbeb6247b095a128d159ad3affc174e7ac35024da9c76

User keyd4554aad7f1ff1a36fb3f2ed276ecd44e83eceb4e487c7f4a3ae65cb977776d2

Zero-knowledge proof

What it means: the issued code, pulse, and timestamp are bound to this proof. If any field is changed, verification fails.

Technical: fields are committed with Poseidon, then validated with a Groth16 proof for fast public verification.

Circuit: Groth16
Proof system used for verification.
: 23D72A6264502B5C
Proof identifier for this claim. Verifies quickly and deterministically.
: 0577b2c1b997110d9ddd17b002f9be143ce93b947c891309829a54a6d7775d5c
Hash commitment that binds the committed fields into the proof.

Practical rule: if it looks the same but isn’t the same, it won’t verify.

Verified viewer Collect record