This happened.

2026-04-25 20:48

ANCHOR•a6e56a2e

F441F9E3-8336-4E56-9912-6B636161C7EB.receized.png

2950613 bytes · image/png

The old internet asked for attention. I asked for proof.

Record data

Code084633B5

Pulse11810568

PBI_VERIFIED

Signer 1 · Owner self-sign

4/26/2026, 12:48:37 AM

Email: bjklock.com@gmail.com

PBI843b6147c13463e1d7129b59a3fb86ed732e79a8ec488208c37e1e490cffc538

User keyed07070787c0d9dd5a0d98a39f535453699936debcffe99f1de1c55735ebffcb

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.
: 1B8BD870C763CA59
Proof identifier for this claim. Verifies quickly and deterministically.
: 20280e07488dbf2415af1a483fb66876d01fa980c9a5a77e6be787142aace686
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.