As we discussed on #3 , we should specify the running entity of AINFTFactory.
So far, AINFTFactory is used for cloning ERC721 or creating new AINFT721. After cloning or creating, the AINFTFactory contract doesn't need, which seems to be redundant.
After a few conversation, we decided that the structure of factory should be changed. Following are the alternatives:
-
We(AI Network) deploy AINFTFactory contract and provide public only its contract address and functions(cloneERC721, createAINFT721). In this case, the factory deployer should get fees.
-
Just let anybody deploy the AINFTFactory. Then the AINFTFactory just works as an adapter for deploying AINFT721 contract. In this case, AINFTFactory contact might not need to be existing.
As we discussed on #3 , we should specify the running entity of AINFTFactory.
So far, AINFTFactory is used for cloning ERC721 or creating new AINFT721. After cloning or creating, the AINFTFactory contract doesn't need, which seems to be redundant.
After a few conversation, we decided that the structure of factory should be changed. Following are the alternatives:
We(AI Network) deploy
AINFTFactorycontract and provide public only its contract address and functions(cloneERC721,createAINFT721). In this case, the factory deployer should get fees.Just let anybody deploy the AINFTFactory. Then the AINFTFactory just works as an adapter for deploying AINFT721 contract. In this case, AINFTFactory contact might not need to be existing.