Skip to main content
This page provides indicative traffic-cost estimates for all DA Registry actions, including the Token Standard v1 and v2 workflows. Use the estimates to compare the relative traffic generated by each action and workflow variant.

​
Assumptions

  • The baseline assumes minimal input holdings, a single required allowlist credential, no blocklist, and parties hosted on separate participant nodes. Additional holdings, credentials, or blocklist entries may increase the transaction size and cost.
  • V1 allocation estimates assume a free-of-payment (FoP) transfer between a sender and receiver. The settler executes it via the Allocation_ExecuteTransfer choice (using ActAs rights for both parties).
  • V2 allocation estimates use the same FoP setup but create two allocations: allocation 1 for the sender and allocation 2 for the receiver. The settler executes both atomically via the SettlementFactory_SettleBatch choice.
  • The Merge (or self-transfer) estimate is for merging two input holdings into one.
  • The Burn-Mint estimate assumes one registrar, one owner, one holding burned, and one holding minted. The registrar holds ActAs rights for the owner.

​
Workflow Cost Breakdown

Each estimate includes the transaction size in bytes and a corresponding USD estimate. USD values use the applied rate of $60 per MB of transaction data. The figures are indicative rather than fixed prices. Actual costs depend on the transaction context.