Skip to main content

Custom NFT

What is a custom NFT?​

With the Request NFT Custom Contract Deployment API, you can select various options and deploy an NFT contract in the form you want.

EVM-based platforms are currently supported.






Permission system​

The supported permission systems are as follows.

PermissionDescription
OWNABLEThe administrator has all permissions.
ROLESPermissions can be separated for each function.

Ownable​

The administrator has all permissions on the contract. The ownership can be transferred using the Request NFT Contract Method Execution API. (transferOwnership)


Roles​

Permissions can be separated by function. You can grant or revoke each permission using the Request NFT Contract Method Execution API. (grant, revoke)






NFT features​

You can enable the following NFT features.

Feature

Description

[Common]

BURNABLE

The NFT owner can burn their own NFT.

OWNER_BURNABLE

The administrator can burn a specific NFT.

PAUSABLE

The administrator can pause the contract. (PAUSE, UNPAUSE)
While the contract is paused, items cannot be minted or burned.

MINTABLE

The administrator can mint NFTs.
If this feature is disabled, NFT items cannot be minted.

AIRDROP

The administrator can mint the same kind of NFT to multiple addresses.

[ERC-721]

ENUMERABLE

The full list of NFTs can be checked on the blockchain.
Supports methods such as tokenOfOwnerByIndex, totalSupply, and tokenByIndex that can be queried on the contract via RPC.

URI_STORAGE

Receives and links a URI each time an NFT is minted.
A URI must be entered when minting an NFT.

INCREMENTAL

Assigns NFT item numbers sequentially starting from 0.
No token ID is entered when minting an NFT.

[ERC-1155]

SUPPLY

The total supply per token ID can be checked.
Supports methods that can be queried on the contract via RPC.

UPDATABLE_URI

The administrator can modify the URI.



Request example

curl --request POST \
--url https://{{apiEndpoint}}/2.0/wallets/55/nfts/contracts/custom-deployments \
--header 'Authorization: Bearer ' \
--header 'accept: application/json' \
--header 'content-type: application/json' \
--data '
{
"contractSpec": "ERC721",
"nftRoleSystem": "ownable",
"nftFeatures": [
"MINTABLE",
"BURNABLE",
"OWNER_BURNABLE"
],
"requestId": "random-string",
"contractName": "test",
"tokenSymbol": "TEST",
"senderAddress": "0x3840a99FFB6A6c85CEB5697EEC0C55b1734baDaC"
}
'

Response example

{
"uuid": "745dc90f-8888-46f9-a9b5-a65ea5073d45"
}