Receipts

A receipt is the provenance object. Two kinds exist.

Broadcast receipt

Cut for every live session, automatically (the Mux webhook creates it when a registered handle’s stream goes active; approval is enforced earlier, when the stream is provisioned).

GET /api/streamer/receipts?handle=…
→ { receipts: [{ id, handle, startedAt, endedAt, durationSecs, peakViewers, marketsActive, … }] }

Includes the END CARD recap: markets active, peak viewers, signals filed during the session.

Signal receipt

Every filed signal has a shareable receipt at denpa.ai/receipts/<id> with an OG card (rendered in light mode). It carries the call, the snapshot, the outcome once resolved, and the operator’s public id.

Rules

• The registry MUST cut a receipt for every broadcast session. A fork that mints its own receipts is off-protocol.
• Receipts survive removal for copies already distributed (see terms).
• Receipts are the unit of the share loop: call → receipt → share → follow.