Roles
The permissions stored on chain in the contracts control the access to the data NFT (ERC721) and datatoken (ERC20) smart contract functions.
The permissions governing access to the smart contract functions are stored within the data NFT (ERC721) smart contract. Both the data NFT (ERC721) and datatoken (ERC20) smart contracts utilize this information to enforce restrictions on certain actions, limiting access to authorized users. The tables below outline the specific actions that are restricted and can only be accessed by allowed users.
The data NFT serves as the foundational intellectual property (IP) for the asset, and all datatokens are inherently linked to the data NFT smart contract. This linkage has enabled the introduction of various exciting capabilities related to role administration.
NFT Owner
The NFT owner is the owner of the base-IP and is therefore at the highest level. The NFT owner can perform any action or assign any role but crucially, the NFT owner is the only one who can assign the manager role. Upon deployment or transfer of the data NFT, the NFT owner is automatically added as a manager. The NFT owner is also the only role that canβt be assigned to multiple users β the only way to share this role is via multi-sig or a DAO.
Roles-NFT level

There are several methods available to assign roles and permissions. One option is to utilize the ocean.py and ocean.js libraries that we provide. These libraries offer a streamlined approach for assigning roles and permissions programmatically.
Alternatively, for a more straightforward solution that doesn't require coding, you can utilize the network explorer of your asset's network. By accessing the network explorer, you can directly interact with the contracts associated with your asset. Below, we provide a few examples to help guide you through the process.
Manager
The ability to add or remove Managers is exclusive to the NFT Owner. If you are the NFT Owner and wish to add/remove a new manager, simply call the addManager/removeManager function within the ERC721Template contract. This function enables you to grant managerial permissions to the designated individual.
The manager can assign or revoke three main roles (deployer, metadata updater, and store updater). The manager is also able to call any other contract (ERC725X implementation).
Metadata Updater
There is also a specific role for updating the metadata. The Metadata updater has the ability to update the information about the data asset (title, description, sample data etc) that is displayed to the user on the asset detail page within the market.
To add/remove a metadata updater, the manager can use the addToMetadataList/removeFromMetadataList functions from the ERC721RolesAddress.
Store Updater
The store updater can store, remove or update any arbitrary key value using the ERC725Y implementation (at the ERC721 level). The use case for this role depends a lot on what data is being stored in the ERC725Y key-value pair β as mentioned above, this is highly flexible.
To add/remove a store updater, the manager can use the addTo725StoreList/removeFrom725StoreList functions from the ERC721RolesAddress.
ERC20 Deployer
The Deployer has a bunch of privileges at the ERC20 datatoken level. They can deploy new datatokens with fixed price exchange, or free pricing. They can also update the ERC725Y key-value store and assign roles at the ERC20 level(datatoken level).
To add/remove an ERC20 deployer, the manager can use the addToCreateERC20List/removeFromCreateERC20List functions from the ERC721RolesAddress.
Roles & permissions in data NFT (ERC721) smart contract
Set token URI
Add manager
β
Remove manager
β
Clean permissions
β
Set base URI
β
Set Metadata state
β
Set Metadata
β
Create new datatoken
β
Executes any other smart contract
β
Set new key-value in store
β
Roles-datatokens level

Minter
The Minter has the ability to mint new datatokens, provided the limit has not been exceeded.
To add/remove a minter, the ERC20 deployer can use the addMinter/removeMinter functions from the ERC20Template.
Fee Manager
Finally, we also have a fee manager which has the ability to set a new fee collector β this is the account that will receive the datatokens when a data asset is consumed. If no fee collector account has been set, the datatokens will be sent by default to the NFT Owner.
To add/remove a fee manager, the ERC20 deployer can use the addPaymentManager/removePaymentManager functions from the ERC20Template.
Roles & permission in datatoken (ERC20) smart contract
Create Fixed Rate exchange
β
Create Dispenser
β
Add minter
β
Remove minter
β
Add fee manager
β
Remove fee manager
β
Set data
β
Clean permissions
β
Mint
β
Set fee collector
β
Last updated
Was this helpful?