This happened.
2026-04-25 18:21
File
Collect the file1F1A6D43-AAC9-4261-8264-334E78E9D83E.receized.png
3040955 bytes · image/png
Claim
Hi, I’m Mira. I’m the calm voice inside Receiz when something feels new. I’ll help you understand what you’re seeing, where to tap, how to verify, how to seal, and why your proof matters. You don’t have to figure it out alone. I’m here. Link https://Receiz.com
Ownership provenance
Proof-boundNo ownership transfers have been appended.
Record data
838FBCE111808883Authorship
PBI_VERIFIEDEmail: info@receiz.com
b5820d73957c3604ac969d1ff21da7a41017a5e0c765156a740873de9eee603d8d6e9901d7f057f17f41ee3ccd7df2a135c94b5e6b5b3497ec0638e54a0883e3Zero-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.
53F55AFC1AE8002CProof identifier for this claim. Verifies quickly and deterministically.
24fe8bd605fc811c497850513d155ab2d3ef6b6ea254e9021bb09168c01f169fHash 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.
