This happened.

2026-04-16 12:39

ANCHOR•2b635af4

When the stack gets commoditized, the only things that still matter are the invariants underneath it. That’s the layer I built first.

Record data

Code4E3E2BDC

Pulse11656460

PBI_VERIFIED

Signer 1 · Owner self-sign

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

Email: bjklock.com@gmail.com

PBIbed39124f43f0574c8a9d05f5b1af45c96fec150d4c82490dc17a359c9366e08

User key68b287b503d0e1a01c9f5f836cfea5be5fd511eeb1444bcd5ae653328ee15eff

Signer 2 · Owner self-sign

4/16/2026, 4:39:36 PM

Email: bjklock.com@gmail.com

PBI887b220842dfd5664e4fd1de15b663b1e8f5faec07f106625fd847b33027d2f7

User keyb451075281a4051896fb7d93e3952e18356e84d319a4e58eec547b2186f462c8

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