DPTF Data Tables

DPTF|PropertiesTable

This table stores information about DPTF Token Properties, containing exactly 30 distinct properties. Each entry is uniquely identified by the DPTF Token ID.

1. owner-konto:string – Stores the Standard or Smart Ouronet Account that owns the DPTF Token, also known as the Token Manager (TM). Ownership must be verified to perform operations related to token properties.

2. name:string – Stores the full name of the token. Must be 2 to 50 characters long and can contain both uppercase and lowercase letters. Special rules apply to LP Tokens.

3. ticker:string – Stores the token's ticker symbol. Must be 2 to 30 characters long, using uppercase letters only. Special rules apply to LP Tokens.

4. decimals:integer – Defines the token's precision, which must be between 2 and 24.

5. can-change-owner:bool – Indicates whether the Token Manager can be changed.

6. can-upgrade:bool – If <true>, the TM can modify properties 5, 6, 7, 8, 9, and 10.

7. can-add-special-role:bool – If <true>, the TM can assign special roles to DPTF Accounts.

8. can-freeze:bool – If <true>, the TM can freeze a DPTF Account, preventing token transfers to or from it.

9. can-wipe:bool – If <true>, the TM can fully or partially wipe a frozen DPTF Account, permanently reducing token supply by removing or decreasing DPTF balances.

10. can-pause:bool – If <true>, the TM can pause the DPTF Token, preventing all transfers under any circumstances.

11. is-paused:bool – Indicates whether the DPTF Token is paused. A token can only be paused if can-pause is set to <true>, but it can be unpaused regardless of this property.

12. supply:decimal – Stores the total supply of the DPTF Token.

13. origin-mint:bool – Initially set to false when a DPTF Token is issued. While false, an Origin Mint can be executed. This is the first minting event after issuance, requiring only token ownership (not minting permissions). Origin Minting:

    • Can only occur while the supply is zero

    • Can be executed only once

    • Sets origin-mint permanently to false after execution

    • Indicates whether an Origin Mint event has occurred

14. origin-mint-amount:decimal – Records the amount minted during an Origin Mint event. This value is immutable and defaults to 0.0, meaning no Origin Mint has been performed.

15. role-transfer-amount:integer – Tracks the number of DPTF Accounts with the role-transfer property set to <true>. If this number is greater than 0, special transfer restrictions apply, allowing transfers only if at least one party (sender or receiver) has <role-transfer>=<true>

16. fee-toggle:bool – If <true>, DPTF Fee Properties (18,19) apply to DPTF transfers. If <true>, fee properties (even if configured) are ignored.

17. min-move:decimal – Specifies the minimum transferable amount of a DPTF Token. Transfers below this threshold are not allowed. However, this restriction does not apply to:

    • Gas collection

    • The Token Owner Account

    • Accounts with an active role-transfer

    • The Ouroboros and Dalos Smart Ouronet Accounts

18. fee-promile:decimal – Specifies the transfer fee in Promille (‰).

    • Must be between 1.0 and 900.0

    • Does not apply to gas collection

    • Exemptions apply to accounts with <role-fee-exemption> set to true

    • A value of -1.0 is allowed and enables the Volumetric Transaction Tax (VTT) as the fee mechanism

19. fee-target:string – Specifies the DPTF Account designated to collect DPTF Fees. By default, fees are collected by the Ouroboros Smart Ouronet Account, from which the Token Owner can withdraw accumulated funds, even if transfer restrictions apply.

    The fee-target can be set to:

    • Dalos Smart Ouronet Account – Redirecting fees here donates them to Ouronet Custodians. This action can be executed using the DPTF|C_DonateFees function from the TS01-C1 Module.

    • Default reset – The DPTF|C_ResetFeeTarget function (from the same module) restores the fee-target to its default setting.

    • Any Standard Ouronet Account – Apart from the Ouroboros and Dalos Smart Ouronet Accounts (the only Smart Accounts permitted for this role), the fee target can be assigned to any Standard Ouronet Account.

20. fee-lock:bool – Allows the Token Manager (TM) to permanently lock fee settings once configured. When set to <true>, the parameters 16,17,18,19 cannot be changed. Modifying this parameters once <fee-lock> is set to <true>, requires setting it back to <false>. However, this has special restrictions:

    1. Unlocking the <fee-lock> can be performed a maximum of 7 times. Each successive unlock becomes progressively more expensive, making frequent modifications increasingly costly. Once the 7th unlock is executed, further unlocking is no longer possible.

    2. The cost for each unlock is calculated as (10000IGNIS+100KDA)x(1+fee-unlocks). This formula ensures that each additional unlock costs more than the previous one, creating a financial deterrent against frequent changes.

    3. Additionally, every unlock imposes a mandatory secondary fee on Token Transactions. This fee is equal to the VTT multiplied by the number of times a fee unlock has been executed. These fees are collected for the Ouronet Custodians

21. fee-unlocks:integer – Tracks the number of times a DPTF Fee unlock has been executed. Ideally, a DPTF Token should have zero <fee unlocks>, signaling stability and careful management of fee settings.

22. primary-fee-volume:decimal – Records the total amount of DPTF Token collected through the mandatory DPTF Fee, set by the Token Manager (TM).

23. secondary-fee-volume:decimal – Records additional fees imposed on DPTF Token operations as a result of modifying fee settings after they have been initially locked.

24. reward-token:[string] – Records the ATS-Pairs the DPTF Token is part of as a Reward-Token

25. reward-bearing-token:[string] – Records the ATS-Pairs the DPTF Token is part of as a (cold) Reward-Bearing-Token

26. vesting-link:string – Records the DPMF ID of the DPMF Token that is the Vested Counterpart of the DPTF Token. Once set, this is immutable, as vesting-links cannot be rolled back.

27. sleeping-link:string – Records the DPMF ID of the DPMF Token that is the Sleeping Counterpart of the DPTF Token. Once set, this is immutable, as sleeping-links cannot be rolled back.

28. frozen-link:string – Records the DPTF ID of the DPTF Token that is the Frozen Counterpart of the DPTF Token. Once set, this is immutable, as frozen-links cannot be rolled back. For a DPTF Token that is the Frozen counterpart of a DPTF Token, this value stores the ID of the Original DPTF Token it is linked with via the frozen-link.

29. reservation-link:string – Records the DPTF ID of the DPTF Token that is the Frozen Counterpart of the DPTF Token. Once set, this is immutable, as reservation-links cannot be rolled back. For a DPTF Token that is the Reserved counterpart of a DPTF Token, this value stores the ID of the Original DPTF Token it is linked with via the reservation-link.

30. reservation:bool – Stores whether a DPTF Token is reservable. When set to <true>, Reserved DPTFs can be created from a DPTF, provided a reservation-link has already been established.

DPTF|BalancesTable

This table stores data related to DPTF Accounts, which define the relationship between a DPTF Token and a Ouronet Account. Each entry is uniquely identified by a key in the format: <Token-ID>|<OuronetAccount-ID> This ensures that there is only one record per Token ID per Ouronet Account.

A DPTF Account includes various parameters that determine its behaviour and ability to execute specific DPTF functions. These parameters include:

1. exist:bool – Always set to true when an entry exists in the table. This indicates that a DPTF Account is registered for a given DPTF Token and Ouronet Account.

2. balance:decimal – Stores the DPTF Token balance associated with the Ouronet Account.

3. role-burn:bool – Indicates whether the Ouronet Account has permission to burn DPTF Tokens. Burning tokens reduces the total DPTF supply.

4. role-mint:bool – Indicates whether the Ouronet Account has permission to mint DPTF Tokens. Minting increases the DPTF supply. This applies only to standard minting—Origin-Mint requires DPTF Token ownership instead of this role.

5. role-transfer:bool – If at least one Ouronet Account has this role set to true for a given DPTF Token, special transfer restrictions apply. The token can only be sent to or from Ouronet Accounts where this role is enabled.

6. role-fee-exemption:bool – When set to true, allows a Full Transfer to or from an Ouronet Account for a DPTF Token, bypassing any DPTF Fee settings or Minimum Transfer Value restrictions, if applicable. DPTF Accounts that have this role set to false, while at least one DPTF Account has this role set to true, wont be able to send or receive the DPTF Token.

7. frozen:bool – Indicates whether the DPTF Account is frozen for this specific DPTF Token. A frozen account cannot send or receive DPTF tokens. While this parameter is set to true, the account's balance may be subject to a full or partial wipe by the Token Manager.

DPTF|RoleTable

This Table store a list of Ouronet Accounts for which active roles are set up.

1. r-burn:[string] – Stores a list of all Ouronet Accounts that have an active <role-burn>

2. r-mint:[string] – Stores a list of all Ouronet Accounts that have an active <role-mint>

3. r-fee-exemption:[string] – Stores a list of all Ouronet Accounts that have an active <role-fee-exemption>

4. r-transfer:[string] – Stores a list of all Ouronet Accounts that have an active <role-transfer>

5. a-frozen:[string] – Stores a list of all Ouronet Accounts that have an active <frozen> property, meaning accounts that are frozen.