This happened.
2026-09-21 05:40
File
BB31DCCA-1AE7-4497-8450-0A9FD48F5270.png
2109173 bytes · image/png
Source file is paid and locked. Collecting requires payment of $5.99.
Claim
I spent years showing you the objects. Now look underneath them. Kai-Klok doesn’t timestamp Receiz. The pulse exists before the object arrives. Receiz gives digital state a way to meet it, prove where it stood, then carry that history forward. The clock was already moving. Link https://bjklock.com/p/fbc15b22-c82a-4c67-abb3-c4a52ae227bd
Ownership provenance
Proof-boundNo ownership transfers have been appended.
Record data
AE9E71A914258807Authorship
PBI_VERIFIEDEmail: bjklock.com@gmail.com
808b35ef3b399af837315b7d9cbaa460839acba8728d15e4c73bac572ba771f94cbe60dd2717cd294470dc24e8cf16295f6f8e24d7f0487ae0ea5fa295365bf3Zero-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.
0B4D57213D7CFCFAProof identifier for this claim. Verifies quickly and deterministically.
113f11a090b0e7027d3998baf3f6b91d468041c118eefd61829e14baa0af7b48Hash 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.
