This happened.

2026-04-25 21:01

ANCHOR•6e303a33

25AB80BB-64D9-4615-94ED-1C5B9E97A3D1.receized.png

1885317 bytes · image/png

I don’t need “the system” to crown me. I brought the timestamp.

Record data

CodeA61665CE

Pulse11810723

PBI_VERIFIED

Signer 1 · Owner self-sign

4/26/2026, 1:02:09 AM

Email: bjklock.com@gmail.com

PBI5865aa217acf6c596772f6fe64fd62b74f872fcdf243b4ca833be7aa4ea6c491

User keyd896accfa47ab2a36940706598684160327cceca43e72bd7dd68dc84014d1f4c

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.
: B208B1E56661417D
Proof identifier for this claim. Verifies quickly and deterministically.
: 0b6cf44fed5eefb134bcc58bd7e337cf3f388f3ef0965e8c604b260407b2495a
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.