-
Notifications
You must be signed in to change notification settings - Fork 13
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #169 from casper-ecosystem/chore-update-milestone-…
…status Update milestone status
- Loading branch information
Showing
8 changed files
with
99 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
--- | ||
Milestone: "M1", | ||
Status: "In progress", | ||
--- | ||
<!--lang:en--> | ||
## Description | ||
|
||
### Traceability blockchain initialization | ||
|
||
Basically, the data structure to be saved must be developed, the agronomic variables must be well defined, and our current application must be adapted to be able to collect them. Finally, these data must be uploaded to the blockchain in the form of metadata (NFT) which will serve to see its traceability. The estimated time is about 10 weeks (however, we depend on third-party data), in case of delay we will mock data. | ||
|
||
|
||
### Acceptance Criteria | ||
|
||
- Understand the entire Casper Network development environment and know all of its key elements (there should be training to achieve this). | ||
- Be able to generate an NFT with images and metadata via API (create a script to do this). | ||
- Be able to verify online that an NFT has been generated with an image and metadata with client agronomic data (even if it's fake for development purposes). | ||
- Have a script that queries this NFT via API. | ||
- Have a node implemented to be able to perform all these interactions. | ||
|
||
|
||
### Progress Update | ||
|
||
**Reporting Week: 01.12.2023 - Current** | ||
- Progressing to plan |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
--- | ||
Milestone: "M2", | ||
Status: "To Do", | ||
--- | ||
<!--lang:en--> | ||
## Description | ||
|
||
### Non-Deforestation NFT generation | ||
|
||
A system of interaction between the generation of NFTs from the previous point must be designed. Achieving functionalities such as expiring an NFT and creating an NFT from two specific NFTs. Here, there will be a lot of work managing wallets and NFTs to make the flow easy for the end client. The final objective is to have an automatic representation on the blockchain of a certification process that is done manually every 3-6 months. This process can maintain the certificate, improve it, or expire it. The NFTs (with their rarity) will have to exemplify the same. | ||
|
||
|
||
### Acceptance Criteria | ||
|
||
- Deliver a detailed flow of how the generation and creation of NFTs will go (with approximate usage metrics). | ||
- Create a function (script) that creates an NFT from two NFTs via an API. | ||
- Create a function (script) that proposes an expiration date for this NFT when it is created, at which point it will be destroyed (if auto-deprecation is not possible) | ||
- These NFTs must contain a satellite image of the crop location with basic information (to be specified) about its traceability (a design should be made to show it as a card or sticker). | ||
|
||
### Progress Update | ||
|
||
**Reporting Week: 15.04.2024 - 31.06.2024** | ||
- To Do |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
--- | ||
Milestone: "M3", | ||
Status: "To Do", | ||
--- | ||
<!--lang:en--> | ||
## Description | ||
|
||
### User Flow deployment | ||
|
||
In this final phase, the only thing left will be the integration of the functionalities into a common frontend (a web app). Here, the user will have to interact with their wallet to access their NFTs. Also, all the necessary user documentation for the use of this new tool will have to be generated. Finally, the initial user training will need to be set-up (250-500 Alpha users). | ||
|
||
|
||
### Acceptance Criteria | ||
|
||
- Have initial NFTs generated (one for each user activated at the time of the milestone). | ||
- Have a demo user with each of the possible NFTs (depending on their rarity and their traceability) to be able to make product demonstrations and marketing. | ||
- Have prepared a joint marketing campaign with Casper to disseminate the communication of this project when it comes to market. | ||
- Have the technical documentation generated and linked to the web app so that the user can know and understand the flow transparently at all times. | ||
- App integrated in Layers (layers.hemav.com). You can see traceability of the coffee and certificate of non deforestation, with code or QR. | ||
- As an extra point, there could be an acceptance criterion which is to perform a demo of the happy path process to Casper. | ||
|
||
|
||
### Progress Update | ||
|
||
**Reporting Week: 31.06.2024 - 03.11.2024** | ||
- To Do |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters