AINFT contract template

[jakepyo]

feat: AINFT contract template structure implementation

• AINFT721.sol, AINFT721Upgradeable.sol
• Support upgradeable contract(apply UUPS pattern)
  • proxy contract is AINFT721Upgradeable.sol, the example logic contract is AINFT721LogicV2.sol.
• Update metadata scheme is on proxy contract - IAINFT.sol interface

deploy

• deploy proxy and logic contract

test

• If I've missed something to test, feel free to comment or mention

[minho-comcom-ai]

should emit BatchMetadataUpdate(start, end) with counter's help?

[jakepyo]

I considered it before. However the setBaseURI() call occurs after the someone calls updateTokenURI(), the baseURI could be ignored when calling tokenURI(). I will leave it behind, with remaining TODO comment

[minho-comcom-ai]

MetadataUpdate / BatchMetadataUpdate is for the NFT marketplaces or other 3rd parties, so I think this should be emitted on here.
If not, we don't have to implement the ERC-4906 at first.

[jakepyo]

Most of ERC721 contracts set the baseURI in initialization phase and no implementation for setBaseURI(). In the perspective of structuring the base template, setBaseURI() don't need to be necessary. However, the versioning of metadata is important concept of template and it'd better to put ERC4906 inside the template.

As a alternative way, I'm trying to add pre-condition check of setBaseURI(): if the number of having been called updateTokenURI() is equal or more than once, setBaseURI() cannot be executed. In this case, the BatchMetadataUpdate can be added.

What do you think of this way?