Skip to content

NFT standard in the Creator Economy Protocol has to be compatible with ERC-721  #14

@AlexShkor

Description

@AlexShkor

Since we are building a multi-chain infrastructure for creator economy, we need to be sure that the NFT standard we have in out protocol is compatible with all the others standarts in other chains. At least it should be compatible with ERC-721, because most of the protocols just use it or something similar.

However DEIP standard can be different in some sense. For example I think we mostly need to maintain compatibility for the write model (transactions/operations) not for read interface. And we also need to have a metadata (probably a simple dictionary) for each NFTs.

One crucial difference I see is that in DEIP we have a collections (number of the NFTs) on the different lvl comparing with ERC-721.
I think it worth adding a list of tokenIDs (uint) to each NFT so we can have a collection on every NFT lvl.

Among all the operation ERC-721 has (here is the list):
safeTransferFrom(from, to, tokenId)

  1. transferFrom(from, to, tokenId)

  2. approve(to, tokenId)

  3. setApprovalForAll(operator, _approved)

  4. safeTransferFrom(from, to, tokenId, data)

Looks like that on our side we need just TransferFrom. Please correct me ifI'm wrong but approve(to, tokenId) and setApprovalForAll(operator, _approved) can be implemented with our permission system, which is universal for all the operations.

safeTransferFrom is not necessary in our chain due to specific of domain-chain?

Reference: https://eips.ethereum.org/EIPS/eip-721

Metadata

Metadata

Assignees

Labels

questionFurther information is requested

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions