This happened.
2026-09-04 11:51
File
1F39A66C-71FE-4092-94CC-19DE518546A7.png
1977801 bytes · image/png
Source file is paid and locked. Collecting requires payment of $5.99.
Claim
I gave them every clock they could name. Then I cut the wire, created two valid successors from one predecessor, and asked which one inherited standing. If the answer still lives in a server, the object never carried authority. The platform did. Link https://bjklock.com/p/d07d3a0b-c70e-473c-a813-5730b22674a0
Ownership provenance
Proof-boundNo ownership transfers have been appended.
Record data
91A0C8E613982542Authorship
PBI_VERIFIEDEmail: bjklock.com@gmail.com
7f180ff90d27084b42ca5c37245c81e7fe41eb1ef412097e348f5cc6d2db9c44131442c707397ce52866414457bcf09d41dedc76502ded1f10aa3d2f852a6f5fZero-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.
FD758FF043BDDABEProof identifier for this claim. Verifies quickly and deterministically.
0538d41cf5c8722cddf764814477d27dbbb6fa09e03f9d3d2013d9727cc76ea5Hash 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.
