This happened.
2026-08-28 15:24
File
AF43454D-0787-4F3B-B417-FFEED2B7FDA0.png
2649720 bytes · image/png
Source file is paid and locked. Collecting requires payment of $5.99.
Claim
A year ago I was already binding memory, identity, provenance, authority, verification, value, and continuity into one machine. Now they’re announcing the pieces as separate “frontiers.” I brought the timestamps. Stop showing me parts. Bring the machine. Link https://bjklock.com/p/83845a40-6115-4ace-99c1-afcf19e07f85
Ownership provenance
Proof-boundNo ownership transfers have been appended.
Record data
2804FC9413869481Authorship
PBI_VERIFIEDEmail: bjklock.com@gmail.com
89ef30628bc5759de51be0190bf71f5450e771bdeb148397d2df73884f485cc0c70db7fdcceead2a44772f148190af1fbdff30d05aac1520b12ce15b30e100a4Zero-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.
7F20E863D5C9D25CProof identifier for this claim. Verifies quickly and deterministically.
2ebef26c5f76a4a8642b88643bc895fa5aa10297ad97a1442a7609d75731d023Hash 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.
