DPMF Data Tables

DPMF|PropertiesTable

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

1. owner-konto:string – Stores the Standard or Smart Ouronet Account that owns the DPMF 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.

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

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, 10 and 12.

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

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

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

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

11. is-paused:bool – Indicates whether the DPMF 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. can-transfer-nft-create-role:bool - Indicates whether the <role-nft-create> can be transferred to another Ouronet Account.

13. supply:decimal – Stores the total supply of the DPMF Token.

14. create-role-account:string – Stores the Ouronet Account that has permission to create new DPMF Tokens. A single Ouronet Account may have this permission.

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. nonces-used:integer – Stores how many new batches have been created so far for the DPMF. Each new batch creation increases this parameter by 1.

17. reward-bearing-token:string Records the ATS Pair the DPMF is part of as Hot-Reward-Bearing-Token.

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

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

DPMF|BalancesTable

This table stores data related to DPMF Accounts, which define the relationship between a DPMF Token and an 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 DPMF Account includes various parameters that determine its behaviour and ability to execute specific DPMF 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. unit:[object{DemiourgosPactMetaFungible.DPMF|Schema}] – This entry stores in a list of objects, the Metadata of all DPMF Batches that exist on a DPMF Account

3. role-nft-add-quantity:bool – Indicates if the Underlying Ouronet Account of the DPMF Account has the permission to add quantity to DPMF Batches it owns.

4. role-nft-burn:bool – Indicates if the Underlying Ouronet Account of the DPMF Account has the permission to burn DPMF Batches it owns.

5. role-nft-create:bool – Indicates if the Underlying Ouronet Account of the DPMF Account has the permission to create new DPMF Batches.

6. role-transfer:bool – When set to true, allows a Full Transfer to or from an Ouronet Account for a DPMF Token, while DPMF Accounts that have this role set to false, cannot send or receives DPMF Tokens, while at least one DPMF Account has this role set to true.

7. a-frozen:bool – Indicates whether the DPMF Account is frozen for this specific DPMF Token. A frozen account cannot send or receive DPMF 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.

DemiourgosPactMetaFungible.DPMF|Schema

This Schema stores the DPMF Batch Information of the DPMF Token. As has been observed above, on a DPMF Account the <unit> entry stores a list of objects following this Schema. The number of objects in the list minus 1 (there is always a blank object being stored), is the number of DPMF Batches the DPMF Account owns. The schema has the following entries:

1. nonce:integer – Stores the nonce value of the DPMF Batch. Each Batch that is created increase the nonce of the DPMT Token by 1.

2. balance:decimal – Stores the balance of the DPMF Batch

3. meta-data:[object] – Stores the meta-data of the DPMF Batch in a list of Pact objects.

DPMF|RoleTable

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

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

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

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

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.