This happened.
2026-07-25 19:03
File
Collect the file23D90330-5813-4095-8FAB-F7BF1362CA8B.receized.png
1755614 bytes · image/png
Claim
Do not believe me. Run the test offline. The sealed file passes. The screenshot fails. No server, API, database, blockchain, or internet decides the result. The verifier distinguishes the proof object from a picture of it. The proof is in the object. Test it yourself. No trust. — Link https://bjklock.com/p/a777d18e-af00-44fa-ac77-dfd9fe0c60a0
Ownership provenance
Proof-boundNo ownership transfers have been appended.
Record data
0030BB9A13310952Authorship
PBI_VERIFIEDEmail: bjklock.com@gmail.com
fad847d5625f1b4fb6223e12f8c4bb04ba77145ccbc115c741e00596d99633311e00f4f71fa4a8ab28051f8dc820cec0d663435004b0f1e27e808aedb0233d5cZero-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.
60B0247EE654976FProof identifier for this claim. Verifies quickly and deterministically.
22efe5454fa4329487e7f309f9c49103f0c5ea0bd0291332f3f498ae07924111Hash 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.
