A receipt, field by field
This is the shape of what Steganosaur issues when a work is protected: the commitment, the instant, the signer, the profiles it was sealed under, and a plain sentence under each one saying what it is for.
Every value below is a sample. The digests and the key identifier were written by hand for this page: they attest to nothing, no service holds a record under these identifiers, and nothing here can be checked. The shape is real; the content is not.
- File
- sample-artifact.txt
The name you gave the work. A name is a label, and nothing checks it.
- Digest
- sha-256:82b2b8f148c53de39e0b8e558d5d285961a93b60eb283b060a2e5ec9a27155cd
The commitment. Bytes that hash to this value are the bytes this record is about; any other bytes are not.
- Size
- 196 bytes
As reported when the commitment was made.
- Recorded at
When Steganosaur sealed the record. It is not a creation date and it is not a priority date.
- Record
- rec_3f8n2k7q1m5v9d0xswphtj6bzc
The Ownership Record this receipt projects.
- Receipt
- rcpt_7q4k2m9v0d8xp3wsn6fhj1tzbc
This receipt. A receipt is a projection of a record at a disclosure tier, not a second record.
- Signer
- Steganosaur issuing key (demonstration)
kid:5c2a9e41d7b0f863The key that sealed the record. That a key signed something says nothing about who holds it.
- Suite
- own-cs/1 — Ed25519
The signature suite. Verification support for a registered suite is never withdrawn.
- Schema
- own-receipt/1 · own-rc/1 · own-cbor/1
The receipt container, the record profile and the canonical encoding. Every schema is versioned.
- Disclosure tier
- Full — record body, envelope, signer key and attachments
A reduced or existence-only receipt omits payloads. The tier is applied when the receipt is assembled.
- Custody
- Local commitment — Steganosaur holds no copy of this file
A local commitment records a digest the holder computed. No original is preserved here.
- Metadata read
- No C2PA manifest · no XMP packet · no embedded identifier
What the file said about itself at inspection. A statement in a file is a thing somebody wrote.
- Protection state
- Sealed · no publication copy issued
A publication copy is a separate file, made by the command line. None was produced for this sample.
- Provenance
- Source record · no derivative registered
A publication copy is not yet bound into its source's record or shown in the Wallet; that is the next phase.
- Verification state
- Not evaluated by this document
A receipt carries evidence; a verification is a separate request with its own signals.
- Timestamp
- RFC 3161 token — not acquired for this sample
An external timestamp is an attachment. Held is not verified: a verification evaluates it.
A receipt records that a commitment was made at an instant under a key. Nothing here states who authored this work, who owns it, or that any right subsists.
What it establishes
- That bytes with this digest existed in this form no later than the recorded instant.
- That a key with this identifier sealed that commitment.
- That the record has not been altered since, because a signature covers its canonical bytes.
What it does not
- Who created the work, or that the account holder created it.
- That any right subsists in it, or who holds one.
- Any priority over a person who recorded something similar earlier or later.
- Anything a government registry establishes — this is recorded with Steganosaur; not a government copyright registration.
These are the fields of a receipt, rendered for reading. A real receipt is bytes in a versioned container, and the thing that makes it worth anything is that someone else can read those bytes without asking us.