5.3 KiB
| description |
|---|
| Discover all about the extensible & flexible smart contract templates. |
Datatoken Templates
Each data NFT or datatoken within Ocean Protocol is generated from pre-defined template contracts. The templateId parameter specifies the template used for creating a data NFT or datatoken, which can be set during the creation process. The templateId is stored within the smart contract code and can be accessed using the getId() function.
it("#getId - should return templateId", async () => {
const templateId = 1;
assert((await erc20Token.getId()) == templateId);
});
Currently, Ocean Protocol supports 1 template type for data NFTs and 2 template variants for datatokens: the regular template and the enterprise template. While these templates share the same interfaces, they differ in their underlying implementation and may offer additional features.
The details regarding currently supported datatoken templates are as follows:
Regular template
The regular template allows users to buy/sell/hold datatokens. The datatokens can be minted by the address having a MINTER role, making the supply of datatoken variable. This template is assigned templateId =1 and the source code is available here.
Enterprise template
The enterprise template has additional functions apart from methods in the ERC20 interface. This additional feature allows access to the service by paying in the basetoken instead of the datatoken. Internally, the smart contract handles the conversion of basetoken to datatoken, initiating an order to access the service, and minting/burning the datatoken. The total supply of the datatoken effectively remains 0 in the case of the enterprise template. This template is assigned templateId =2 and the source code is available here.
Set the template
When you're creating an ERC20 datatoken, you can specify the desired template by passing on the template index.
{% tabs %}
{% tab title="Ocean.js" %}
To specify the datatoken template via ocean.js, you need to customize the DatatokenCreateParams with your desired templateIndex.
The default template used is 1.
export interface DatatokenCreateParams {
templateIndex: number
minter: string
paymentCollector: string
mpFeeAddress: string
feeToken: string
feeAmount: string
cap: string
name?: string
symbol?: string
}
{% endtab %}
{% tab title="Ocean.py" %} To specify the datatoken template via ocean.py, you need to customize the DatatokenArguments with your desired template_index.
The default template used is 1.
class DatatokenArguments:
def __init__(
self,
name: Optional[str] = "Datatoken 1",
symbol: Optional[str] = "DT1",
template_index: Optional[int] = 1,
minter: Optional[str] = None,
fee_manager: Optional[str] = None,
publish_market_order_fees: Optional = None,
bytess: Optional[List[bytes]] = None,
services: Optional[list] = None,
files: Optional[List[FilesType]] = None,
consumer_parameters: Optional[List[Dict[str, Any]]] = None,
cap: Optional[int] = None,
):
{% endtab %} {% endtabs %}
{% hint style="info" %} By default, all assets published through the Ocean Market use the Enterprise Template. {% endhint %}
Retrieve the template
To identify the template used for a specific asset, you can easily retrieve this information using the network explorer. Here are the steps to follow:
- Visit the network explorer where the asset was published.
- Search for the datatoken address 🔍
- Once you have located the datatoken address, click on the contract tab to access more details.
- Within the contract details, we can identify and determine the template used for the asset.
We like making things easy 😎 so here is an even easier way to retrieve the info for this asset published in the Ocean Market:
{% embed url="https://app.arcade.software/share/wxBPSc42eSYUiawSY8rC" fullWidth="false" %} {% endembed %}
{% hint style="info" %} It's important to note that Ocean Protocol may introduce new templates to support additional variations of data NFTs and datatokens in the future. {% endhint %}