This happened.

2026-04-25 14:42

1E938A44-D532-47FC-BA57-89F23BBEE1CE.receized.png

2300534 bytes · image/png

Claim

They post for attention. You seal for proof. Receiz turns an original into something people can verify, hold, access, and participate in. That’s the difference between content and an asset.

Record data

CodeD8CB277C
Pulse11806378

Authorship

PBI_VERIFIED
Signer 1 · Owner self-sign
4/25/2026, 6:42:53 PM

Email: receiz.com@gmail.com

PBI9e017ddfb7ec52f54b6cadff23d3cab0c26947e8ad3b85e7cead0320ba98891a
User keyc1d9dc02c7f806d413c2d9aefd88751b98dba1fff9756f0cfe7419c4aa2ae4a8
Zero-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
Groth16

Proof system used for verification.

BEE4C3914D124F0D

Proof identifier for this claim. Verifies quickly and deterministically.

2509ce854b2b632a4606b0c1e35d1d4a9187a8000d1abd73802177782f28fcc4

Hash 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.

https://receiz.com/v/20260425_1442/D8CB277C/11806378?a=2086d3f7&ms=1777142543575