Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Architecture

The current D-ASA architecture is layered, not product-specific. The on-chain contract is a single DASA application assembled from five modules:

flowchart LR
  RBAC["RBAC"] --> KERNEL["ACTUS Kernel"]
  KERNEL --> ACCOUNTING["Accounting"]
  ACCOUNTING --> PAYMENT["Payment Agent"]
  ACCOUNTING --> TRANSFER["Transfer Agent"]

Processing chain

The canonical processing chain is:

flowchart LR
  ACTUS["ACTUS Contract"] --> NORMALIZE["AVM Normalization"]
  NORMALIZE --> ABI["ABI Upload"]
  ABI --> EXEC["AVM Execution"]

This separation is intentional:

  • ACTUS contract definition and schedule generation happen off chain.
  • Normalization converts that contract into fixed-size AVM-compatible structs.
  • The AVM kernel validates and executes the normalized lifecycle.

Module responsibilities

  • RbacModule: role assignment, suspension, contract default control, and application-control methods.

  • ActusKernelModule: normalized-term validation, schedule storage, event cursor, state transitions, and generic ACTUS getters.

  • AccountingModule: holder positions, unit activation, checkpoints, and claim ledgers.

  • PaymentAgent: funding of due cash events and holder withdrawals.

  • TransferAgent: primary distribution, transfer schedule, and settled unit transfers.

Public API by layer

LayerPublic methods
RBACcontract_update, rbac_rotate_arranger, rbac_set_op_daemon, rbac_assign_role, rbac_revoke_role, rbac_contract_suspension, rbac_contract_default, rbac_get_arranger, rbac_get_address_roles, rbac_get_role_validity
Accountingaccount_suspension, account_open, account_update_payment_address, account_get_position
ACTUS Kernelcontract_create, contract_config, contract_schedule, contract_execute_ied, apply_non_cash_event, append_observed_cash_event, contract_get_state, contract_get_next_due_event
Payment Agentfund_due_cashflows, claim_due_cashflows
Transfer Agenttransfer_set_schedule, primary_distribution, transfer

Execution flows

Configuration

sequenceDiagram
  participant SDK as "Normalization SDK"
  participant ABI as "ABI Caller"
  participant K as "ACTUS Kernel"

  SDK->>ABI: "NormalizedActusTerms + InitialKernelState + Schedule Pages"
  ABI->>K: "contract_config(...)"
  ABI->>K: "contract_schedule(page 0)"
  ABI->>K: "contract_schedule(page n, is_last_page=true)"
  ABI->>K: "primary_distribution(...)"
  ABI->>K: "contract_execute_ied()"

Cash events

sequenceDiagram
  participant ABI as "ABI Caller"
  participant PA as "Payment Agent"
  participant ACC as "Accounting"

  ABI->>PA: "fund_due_cashflows(max_event_count)"
  PA->>ACC: "advance global indices and reserve funds"
  ABI->>PA: "claim_due_cashflows(holding_address, payment_info)"
  PA->>ACC: "settle holder checkpoints"
  PA-->>ABI: "CashClaimResult"

Transfers

sequenceDiagram
  participant ABI as "Holder"
  participant TA as "Transfer Agent"
  participant ACC as "Accounting"

  ABI->>TA: "transfer(sender, receiver, units)"
  TA->>ACC: "settle sender"
  TA->>ACC: "settle receiver"
  TA->>ACC: "move active units"