Module receipt 

Receipt domain types: ReceiptStatus, Receipt, ReceiptList.

Requirements trace

• RCP-001 — ReceiptStatus discriminants 0..=4 and 255.
• RCP-002 — Receipt field layout (tx id, height, index, status, fees, state).
• NORMATIVE — receipt domain obligations.
• RCP-003 — ReceiptList: storage, Merkle ReceiptList::root, accessors.
• RCP-004 — ReceiptList::len, success/failure counts, ReceiptList::total_fees.
• SPEC §2.9 — receipt payload context.
• HSH-008 — receipts Merkle algorithm (same as this module’s root helper; see note below).

Rationale

• #[repr(u8)]: Stable single-byte tags for bincode payloads and receipt Merkle leaves (RCP-001 implementation notes).
• Failed = 255: Leaves 5..=254 for future specific failure codes without renumbering existing wire values.
• ReceiptStatus::from_u8: Unknown bytes map to ReceiptStatus::Failed so forward-compatible decoders never panic (RCP-001 implementation notes).
• ReceiptList::push without immediate root update: Batch amortization per RCP-003; callers must ReceiptList::finalize (or use ReceiptList::from_receipts).
• compute_receipts_root: HSH-008 algorithm lives in this module (bincode leaf + MerkleTree); re-exported as crate::compute_receipts_root from the crate root (types::receipt) to avoid merkle_util ↔ Receipt dependency cycles while keeping one normative implementation for ReceiptList.
• Aggregates (RCP-004): failure_count is any status other than ReceiptStatus::Success; ReceiptList::total_fees sums Receipt::fee_charged for all rows (fees still charged on failed execution per spec notes). Used by checkpoint / epoch summaries (CKP-006 when implemented).

Structs

Receipt

Result of executing one transaction inside a block (RCP-002, SPEC §2.9).

ReceiptList

Ordered block receipts with a commitments root (RCP-003, SPEC §2.9).

Enums

ReceiptStatus

Outcome of applying one transaction in a block (SPEC §2.9, RCP-001).

Functions

compute_receipts_root

Merkle root over ordered receipts: SHA-256(bincode(Receipt)) per leaf, then MerkleTree (HSH-008).