registry/discharge

Discharging each collected duty against the transaction (#157 token-destinations-and-refunds, #177).

Responsibility

Once the fold has walked every request, dutiesFault checks each collected Duty in order against the transaction’s outputs and inputs: a delivered active token sits in the output its request named with its deposit, and a retirement consumes its one active witness. Lovelace owed to payees is settled by registry/settlement after duties hold.

Dependencies

Imports registry/duty (the duties), registry/refusal (deposit-returned), types and lib. Imported by registry/modify, and by the Aiken suite for the token-missing reason.

Assumptions

The fold has already refused anything its trie walk, admission or mint check refuses; duties are discharged only for a fold that reached here.
cageAddress is the address of the state input being spent.

Invariants

Duties are checked in list order and the first failing duty’s reason is the answer, so exactly one reason is reported.
A delivered token’s carrier is the only output holding that asset, holds exactly the merged count, matches the named destination and holds at least the summed deposit; otherwise destination or deposit-returned.
Retirement requires exactly one input carrying exactly one active witness (token-missing).
ReturnDeposit is settled by registry/settlement.

Functions

dutiesFault(
  pins: State,
  cageAddress: Address,
  duties: List<Duty>,
  tx: Transaction,
) -> Option<String>

Why the transaction does not discharge the fold’s collected duties, or None when every one holds. Checked in order; the first fault is the reason, and ReturnDeposit always pass here.

tokenMissingRefusal() -> String

Why a retirement whose key IS Active still refuses: the transaction does not present that key’s one active witness for the burn to destroy (#177 I177-CHAIN). Lean: token-missing.