This happened.
2026-09-01 23:00
File
D0A6E0B1-413B-48A7-AF97-EF42881E7B3C.png
1422224 bytes · image/png
Source file is paid and locked. Collecting requires payment of $5.99.
Claim
The strangest part of building the future is watching people call it obvious after it arrives. I kept the before: the questions, releases, proofs, objections, dates. The archive became provenance protection. Hindsight can normalize the result. It cannot move the timestamp. Link https://bjklock.com/p/523dfe0f-375c-4bc3-836e-4282ad6d9c7f
Ownership provenance
Proof-boundNo ownership transfers have been appended.
Record data
A535330D13940706Authorship
PBI_VERIFIEDEmail: bjklock.com@gmail.com
0b42f276af0b717390df45f81a04bc01c70fb197ccca180e8fbb83fde2521544f55d5bca0ba19a4f26f337290020fdf898a966b5bcee5e29237fd519e78b12dbZero-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.
B14C78491FE52538Proof identifier for this claim. Verifies quickly and deterministically.
16b8bbdf2efe25caee5a100af70fb5d982013a8c5f08484d873e1a807db0f1f6Hash 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.
