Application Status
Status: Approved on the 23.03.2023, submitted on the 17.02.2023
Last updated: 17.02.2023
Submited by: Marco
Team: Marco
Approved Budget (in h):
Used Budget (in h):
Planned Delivery of Phase 1 (Scope Definition): ~4-6 weeks after start
Planned Delivery of Phase 2 (Smart Contract Development): ~4-6 weeks after scope definition is finished
Planned Delivery of Phase 3 (Frontend, hosted via gh-pages): ~4-6 weeks after contract development is finished
Specify the funding category
- Open Source Development
- Community Growth
Application Title
Wrapping AENS names into AEX-141 NFTs to allow batch transfers, batch updates and batch trades
Applicant
- Marco
Value Application
- Provide a way for the community to better manage their AENS names
- Enable batch-actions for AENS names
- Allow strangers to extend AENS names and get rewarded for that
Definition of Terms
Wrapping AENS names into NFTs will make it easy to perform batch-actions on the names and enable new use cases. NFT trading is also highly anticipated and is another topic to tackle in that regards.
Status Quo
- No batch actions (updates, transfers) for AENS names are possible
- No trading of AENS names possible (yet)
- There is another ongoing grant which I am not sure about the exact status: [Active] Distributed otc domain name trading system
- This proposal here differs a lot from the other approach because trading would be enabled via a regular NFT marketplace where the wrapped AENS names could be exchanged
- Users still suffer from name expiration as they fail to consistently track name expiration
Required Work
1. Scope Definition
Although I have already a quite clear picture in my head this phase is very important to make sure I am developing the solution in the best way possible to serve the needs of various members in the community. It is a very good chance for everybody to get involved and drive the solution into the right direction
Tasks:
- Create different diagrams to discuss and define a clear scope
- Topics to cover for the big picture:
- Wrap AENS names into AEX-141 NFTs
- Allow batch-actions (updates, transfers) on AENS names wrapped in the NFT
- Provide a way for anybody to perform those updates and get rewarded for doing so
- Consider an AENS DAO with its own AEX-9 token to handle changes on various parameters which might be defined in some contracts (e.g. a certain percentage of the update rewards could be moved into the DAO and distributed based on decisions taken by the DAO)
- Iterate on the scope & diagrams based on public discussion with community
General design decision to take:
- Should contracts be deployed in a way they could be upgraded later on to enable new features like e.g. the reward mechanism and the AENS DAO
Deliverables:
- Different diagrams that define a clear scope for phase 2+3
2. Smart Contract Development & Deployment
Tasks:
- Analyse how many batch-actions can be performed on AENS names to prevent out of gas issues and possibly limit the amount of AENS names to be wrapped into a single NFT
- Development (incl. tests) of Smart Contracts required to cover the defined scoped
- Deployment of the contracts
- Documentation of contracts & deployment(s)
Deliverables:
- Sophia Smart Contracts with test coverage
3. Frontend
Deliverables:
- A frontend that does not rely on a custom backend (mainly using hosted mdw) and allows to interact with all entrypoints of the developed smart contracts.
Estimate
1. Scope Definition
- Delivery: ~4-6 weeks after starting to work on it
- Working hours: ~80-120
2. Smart Contract Development
- Working hours: ~100-150 (can vary depending on the scope defined in phase 1)
- The better the scope definition, the faster the development can be
3. Frontend
- Working hours: ~100-150 (can vary depending on the scope defined in phase 1)
Known Limitations
- I already provided a request to make the wrapping of AENS names more convenient here:
I would ignore this limitation for the moment and later on apply for another smaller grant to update all components once this feature is implemented and activated on testnet and mainnet.
Outlook
- Publication of a detailed blog article
- Live presentation for the community
- Make the NFTs tradable
- NFT marketplace
- NFT auction platform
- …
Publishment
- Research and development will be published free of any proprietary license (open-source, open-access)
- GitHub Repo: marc0olo/aens-nfts · GitHub
Maintainance
- I confirm that my research and code will be maintained with bug fixing free of charge for one year after publishing it.
- Disclaimer: I cannot give any ETA for bugfixes as this will always depend on my availability. I will guarantee to fix problems as soon as possible.
- This does not include new updates & features. If e.g. the mentioned limitation is fixed, I will apply for a follow up grant that allows me to update the services accordingly.