This happened.
2026-06-16 17:11
File
D5018A17-8A1C-4A3A-BEA4-9DCB284EC748.png
1860233 bytes · image/png
Source file is paid and locked. Collecting requires payment of $5.99.
Claim
I had the wrapper. I know the machine. Articles, blue checks, listicles, clippers, dashboards — all rendered authority. The title can change. The slug still snitches. Receiz is the deeper law: proof travels with the object. When the server drops, what remains? Link https://bjklock.com/p/d7e1829b-90aa-4c47-af8e-d739ac51740c
Ownership provenance
Proof-boundNo ownership transfers have been appended.
Record data
0E08A7A612666134Authorship
PBI_VERIFIEDEmail: bjklock.com@gmail.com
5f6715c3f941e93314946b2e3ab5a3e15d43987c79c9f640b901d2dd4a7abe945b39166b68c0754e0da8cd108cc38405426316a69e0a63a68772b3176b1112b8Zero-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.
A7CAAC66A1AEDBDBProof identifier for this claim. Verifies quickly and deterministically.
0e352ebe5a1177c0a31606288a5969dae15c62cd6a4bed27972c0768619d7364Hash 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.
