A receipt in EdgeRecord is a small, signed JSON object that proves a piece of state existed and was sealed at a specific moment. Receipts are the unit of trust the platform produces.
Anatomy of a receipt
{
"type": "Proof of Existence",
"domain": "example.com",
"ledger": "edgerecord-demo",
"receipt": "wr_demo_immutable"
}
Each field is small, intentional, and independently verifiable.
Why receipts
- They survive the system that produced them.
- They can be shown to third parties without leaking source data.
- They are simple to archive — plain JSON, no proprietary format.
Where receipts come from
You can produce receipts via the API, the CLI, or any of the Integrations.
Verifying receipts
See Verifying a Record for a step-by-step walkthrough. The deeper cryptographic story lives in Security & Compliance.