Application: Æternity NFT Standard and Implementation
Application Status
Status: Postponed on 09.08.2021, Approved on the 31.05.2021, Postponed on the 28.04.2021
Last updated: 09.08.2021
Submitted by Henning Diedrich, [email protected] on the 07.04.2021
Team: Plenity Anstalt
Approved Budget (in h): –
Used Budget (in h): –
Planned Delivery: 31 July 2021
Specify the funding category
Open Source Development
Application Title
Æternity NFT standard
In extension or completion of ÆX 12
Applicant
Plenity Anstalt
Arjan van Eersel
Value Application
Æternity should asap have a powerful, working NFT standard.
The outcome of the project will be a working, tested and documented NFT code library.
It will benefit Æternity to become a more popular platform in the current NFT boom, which will grow – possibly multiply – the number of developers in the Æternity community and the total funds being spent on Æternity applications.
Definition of Terms
An NFT standard code in Sophia, coded by experienced blockchain developers, posted with tests, examples and documentation to the Æternity/ÆXs repository.
The standard may be fully compliant with Ethereum ERC-721 if this is achievable without detrimental consequences, i.e. no loss of possible additional functionality provided by Æternity over Ethereum.
The standard will be tested in a real-world use case to be launched in 2021. The use of this standard will be publicized together with the launch of that application.
Ideally the standard would be joined with the existing ÆX 12 effort but it will be developed unhampered politics and might receive its own number if that is more practical.
Status Quo
- · Team is assembled,
- · specification work has started and
- · forensics about the status of the current ÆX 12 work to avoid repetition.
Required Work
- · Specification of desired functionality
- · Prototype development
- · Test framework development
- · Internal Tests
- · Documentation
- · Public Tests
- · Publication
Estimate
Time Budget
| Task | Person Hours |
|---|---|
| Overhead / Grant Application | 10 |
| Ongoing Dev Team Communication / Meetings | 50 |
| Specification drafting and finalization | 30 |
| Prototype development | 360 |
| Test framework development | 120 |
| Internal Tests, Debugging | 50 |
| Documentation | 40 |
| Public Test Coordination | 25 |
| Publication | 10 |
| Presentation | 20 |
| Maintenance / Fixes / Communication 1 year | 120 |
| Total | 835 hours |
Timeline
| Specification | 19 April 2021 |
|---|---|
| Prototype development | 24 May |
| Test framework development | 31 May |
| Internal Tests | 14 June |
| Documentation | 28 June |
| Public Tests | 26 July |
| Official Public Release | 30 July |
Known Limitations
none
Outlook
The project should be owned, improved and maintained by the Æternity developer community.
It should ideally stabilize and not see too many and not to deep changes.
Advertisement for the standard will be through its first real-world use that will happen in parallel.
At public launch, we will record a dev-level explanation video and provide a press release for the Æternity web site if wanted.
License
The work will be published under GPL.
Maintenance
We will provide bug fixes for at least one year. The scope of functionality should ideally not change as the code is to be a reference for a standard.
