This happened.
2026-07-29 19:56
File
17F72665-DC37-4EC7-844A-232F631828CB.png
2164265 bytes · image/png
Source file is paid and locked. Collecting requires payment of $5.99.
Claim
Everyone is racing to identify which AI made the fake. Wrong layer. By the time you’re guessing, provenance is already gone. Receiz doesn’t detect history after the fact—it preserves identity, ownership, provenance, and continuity inside the object itself. Run the test. 🌬️🧾
Ownership provenance
Proof-boundNo ownership transfers have been appended.
Record data
4BC1D31613377566Authorship
PBI_VERIFIEDEmail: bjklock.com@gmail.com
dca2a98eeaf9a6513c028d28a95721a9f692e4424694b640149ae0696ced201438fa7a2d8c78fd74115c099485103c2d8c7192317b10ad8db8a8c84308e7d641Zero-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.
96BD121E854AEAFCProof identifier for this claim. Verifies quickly and deterministically.
165c93aab74792bc2b03bc4df2353bcb5147bfaacfc3db01521259540f45e0e7Hash 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.
