Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Who runs the AINFTFactory contract? #6

Open
jakepyo opened this issue Apr 14, 2023 · 0 comments
Open

Who runs the AINFTFactory contract? #6

jakepyo opened this issue Apr 14, 2023 · 0 comments

Comments

@jakepyo
Copy link
Contributor

jakepyo commented Apr 14, 2023

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:

  1. 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.

  2. 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant