This happened.
2026-08-04 11:40
File
506062E9-959E-4520-BAA3-416BBBDCBCA1.png
1944625 bytes · image/png
Source file is paid and locked. Collecting requires payment of $5.99.
Claim
Before Receiz, every digital object depended upon an external system to prove what it was. Receiz moved identity, origin, authorship, ownership, history, and valid state into the object itself. Turn off the server. The object still verifies. Now, the truth travels with the thing. Link https://bjklock.com/p/0d202e9e-c2ba-4fc8-b69d-a36fd1a1c87c
Ownership provenance
Proof-boundNo ownership transfers have been appended.
Record data
168C579213470887Authorship
PBI_VERIFIEDEmail: bjklock.com@gmail.com
dd25faa712871614607977ed7e44b3723c87e194dcddc07ecf4eace3c897c64e438887802e11aafe4cca0dedba994ec4d2e5c4c73cbb0f3f5a0efc7f54c2d334Zero-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.
8163BC5A06A0B891Proof identifier for this claim. Verifies quickly and deterministically.
0d9de1f5bfedd308db6f55a0e132f8d55bea735f2e569a0109ecc4a2401d766cHash 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.
