This happened.
2026-09-01 16:31
File
DAE1CB41-B147-413E-8ED1-B40E1B203A6B.png
2531371 bytes · image/png
Source file is paid and locked. Collecting requires payment of $5.99.
Claim
August 15: I published the dependency chain before the products arrived. Persistence → authority → identity → provenance → history → portability. Seventeen days later, the field was already walking into it. I didn’t move the test. I opened the record. Link https://bjklock.com/p/a4d61c66-c62b-4003-9212-4ce7eb191f6f
Ownership provenance
Proof-boundNo ownership transfers have been appended.
Record data
476337A213936243Authorship
PBI_VERIFIEDEmail: bjklock.com@gmail.com
37bf6451065af617e6f59e96e20bfa6fe57b4d20f18935093275d039570d5a9c38589cc62dd62427a02b3da272bc30d5f3f1d7b9b4845d0ca920ad4596998ecfZero-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.
B516B2311E95CEA7Proof identifier for this claim. Verifies quickly and deterministically.
1bd2a5449fc019c01d986dcf8fbdc0271f6d4a1192c84f64b51a38357dd4035eHash 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.
