Open cryshado opened 2 years ago
Idea is to make standard interface not code. That way developers may implement features required for their own needs, like batch minting, custom metadata building etc while all nft will be compatible for using.
For instance collection in parent repository implement member_content
and member_uri
in the simplest way possible, while example implementation demonstrates more complex but closer to real usage.
I personally do not think that nft minting interface should be covered by standard (any thoughts on that?).
The current version of the collection smart contract (
nft-collection.fc
) works withseqno
.Problems may arise if the NFT developer wants to deploy a large collection (e.g. 10,000 NFTs). It will be necessary to get the current
seqno
each time to send a request to the collection contract, waiting for the previous NFT deployment completion. A similar problem occurs withwallet-v3
, which is why it is not recommended for sending a large number of transactions.Solution: develop a collection contract based on the
highload-wallet