This happened.

2026-04-25 21:36

ANCHOR•015e1108

6CEE1867-724F-4E2A-8DED-6A902FF9B441.receized.png

1899436 bytes · image/png

I came with proof, not permission.

Record data

CodeCBEFA3FD

Pulse11811128

PBI_VERIFIED

Signer 1 · Owner self-sign

4/26/2026, 1:37:36 AM

Email: bjklock.com@gmail.com

PBI5dca5d12d719c489406df4c4f240c9f999333a63d6861d3c23ad576ffd30ff16

User key6cf8061200b8c673588736b335e55b880e3a1d566dc742056759475dfc63d964

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.
: 7E897BBA09268DB2
Proof identifier for this claim. Verifies quickly and deterministically.
: 18c579cb20fb06e06f8e4001fa584c08ddb93c44e7b83e1d8a458f4bf76db32b
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.