This happened.
2026-08-29 19:37
File
59E6557E-0F05-443D-8342-FBF1FFF5C8DA.png
3745245 bytes · image/png
Source file is paid and locked. Collecting requires payment of $5.99.
Claim
I followed one name backward. It led from the Mohawk Valley to Soest, Scheda, Voland, Henry IV, and the rupture that split sacred kingship from the temporal order. The bloodline survived. The bell kept the rhythm. The name that emerged was Klock. Link https://bjklock.com/p/4f47e987-e116-41b8-9e25-3e25b408f36b
Ownership provenance
Proof-boundNo ownership transfers have been appended.
Record data
0213EC4713888873Authorship
PBI_VERIFIEDEmail: bjklock.com@gmail.com
8c72ef43475b59e3f4acf0090931f01dbf8d969f192adc2d500cde78425c6308975bc3ae6b0673947c27098c2a119ca96fbed35c09b4d448f70fd5cbc149cba8Zero-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.
3A088BA9F3418987Proof identifier for this claim. Verifies quickly and deterministically.
2928f5b66472f2ec4511ac9d3102530d716f1c65502ca4cfd53ca27283296ba5Hash 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.
