This happened.
2026-09-04 11:16
File
EA1FE270-8F0C-40C3-993D-800CF5EEF732.png
2337619 bytes · image/png
Source file is paid and locked. Collecting requires payment of $5.99.
Claim
Hash it. Sign it. Merkle it. Call it provenance. If I can move your wall clock and change the claimed order, you did not prove when—you preserved a time claim. Temporal authority begins where created_at stops. Welcome to Question 11. 🌬️🧾 Link https://bjklock.com/p/63ad27cc-cc98-4a15-8809-e2e8f9b37a9e
Ownership provenance
Proof-boundNo ownership transfers have been appended.
Record data
C66554F413982145Authorship
PBI_VERIFIEDEmail: bjklock.com@gmail.com
b35de37919b956689e539c9864b0894bcc35feb315d4aa3c78187fc702498ccacf3e7301553d018c938e7bfe6fe02458755ab0b73f12d04dd4f768f96d9c0d79Zero-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.
4D55630F855E17C0Proof identifier for this claim. Verifies quickly and deterministically.
0234e9a9a040f41142f0f4afa4227bc77e132ac949c9482620ea1f01ac022d31Hash 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.
