This happened.
2026-03-23 17:44
ANCHOR•6315b197
Claim
I didn’t just author the primitives. I implemented them. That’s the part they still don’t know how to face. Link https://bjklock.com/p/the-invariants-they-couldnt-ignore
Record data
Code
E788D68EPulse
11263939Authorship
PBI_VERIFIEDSigner 1 · Owner self-sign
3/23/2026, 9:45:33 PM
Email: bjklock.com@gmail.com
PBI
89a3e79d3f538ac62893ac301e4b64ab53efced9f803b315f548e18ace594befUser key
372e241fc43bd4ab7de5880bdb888de7b0cf7210090bf06dc5ac9b09f53a1d48Zero-knowledge proof
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
Groth16Proof system used for verification.
641F9021F1099785Proof identifier for this claim. Verifies quickly and deterministically.
1e4da07d365f427b39837623e3a75738e05fc093a62da20fc5a8bf7c0260fd97Hash 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.
