Skip to content

[Feat]: Decide on Fee Structure for Tokeny Transfers (DvA vs DvD) #6

@sphamjoli

Description

@sphamjoli

Component

Smart contracts

Summary

We need to decide how to implement fee logic for Tokeny-based tokenised asset transfers.
Tokeny supports two models — Delivery vs Approval (DvA) and Delivery vs Delivery (DvD) — each suited to different asset and transfer types.

DvA (Delivery vs Approval):

  • Used for regulated or permissioned assets where transfers require issuer or compliance approval.
  • Fees apply per transfer or approval cycle.
  • Example: Real estate or private equity tokens requiring approval before settlement.

DvD (Delivery vs Delivery):

  • Used for atomic swaps between two tokenised assets.
  • Higher per-execution cost due to dual-asset escrow.
  • Example: P2P or marketplace asset exchanges between verified investors.

Proposal

No response

Acceptance criteria

Choose whether to structure fees around DvA or DvD for the tokenised asset flow.

Context / notes

Tokeny

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions