registry/admission

Responsibility

Enforce the permanent M1 contract’s two allowed registry edges before fold execution.

Dependencies

Uses the canonical modify decision for state, approvals, proofs, tokens and refunds. Request/action matching follows registry/fold’s matching order exactly.

Assumptions

Missing or excess actions and malformed data are refused by the fold decision. Reject actions retain the original request exit and do not change a leaf.

Invariants

Every updating member is registration or termination, including mixed batches. Nothing in State, a parameter or a redeemer can widen this fixed admission set.

Functions

validModify(
  pins: State,
  input: Input,
  policyId: PolicyId,
  tokenId: TokenId,
  tx: Transaction,
  actions: List<RequestAction>,
) -> Option<String>

Check fixed admission first, then all remaining fold obligations.

registry/admission

Responsibility

Dependencies

Assumptions

Invariants

Functions

validModify( pins: State, input: Input, policyId: PolicyId, tokenId: TokenId, tx: Transaction, actions: List<RequestAction>, ) -> Option<String>