Skip to content

Commit

Permalink
Update AgriDot.md
Browse files Browse the repository at this point in the history
  • Loading branch information
@kacena123
kacena123 authored Sep 10, 2024
1 parent 19b18cc commit 969a6f2
Showing 1 changed file with 8 additions and 8 deletions.
16 changes: 8 additions & 8 deletions applications/AgriDot.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -176,14 +176,14 @@ We have created Figma mockups of how would this Web2 to Web3 migration look. The
| **0c.** | Testing and Testing Guide | We will provide unit tests for core application functionality. Guide on how to launch these tests will be mentioned in the README.md |
| **0d.** | Docker | We will provide a docker file that will let you try all the implemented functionality mentioned in the milestone description. |
| 0e. | Article | We will provide a summary article that will mention all the innovations brought during the development of AgriDot. This article will be published on [Medium](https://medium.com/). |
| 1.a | Fields as NFTs (Private) | We will implement functionality that allows farmers to mint their fields as NFTs in a secure, hashed way so only AgriDot will be able to decode them and display them to farmers who own them. |
| 1.b | Fields as NFTs (Public) | We will implement functionality that allows farmers to mint their fields in a public way, so any NFT explorer will be able to display them. These fields will then be able to be used with "4. Crop origin proofs" allowing farmers to create a proof of crop origin that will be linked to their public field. |
| 1.c | See the weather for your NFT fields | We will implement functionality that lets you query the coordinates of your NFT fields and display weather for the upcoming period |
| 2.a | Pests as NFTs | We will implement Pest functionality. Pests will be minted to a unified collection, with coordination of the Field where it appeared (Coordinate will be private (Hashed)), farmers will only know, that a certain Pest appeared X km away from their field (They will be able to set how far they wish to monitor pests) |
| 2.b | Donation system for Pest reporters | We will implement a donation system for pest reporters. Farmers that actively report Pests and are useful to the community can receive donations from Farmers who are willing to thank them for this information (Potentially saving their crops & giving them the ability to prepare for Pest arrival well ahead) |
| 3.a | Guides as NFTs | We will implement guides to be mintable as NFTs into the unified collection. Guides allow farmers to share their knowledge with other farmers (They can range from DIY guides to crop-growing or animal caretaking guides). |
| 3.b | Rating and donation system for Guides | We will implement functionality that allows farmers to provide guide rating by small donation to Farmer who created the Guide. The application will display the amount of "Likes"(Donations) and a report button (So malicious guides can be removed by administrators). This functionality requires a database, however only for 2 anonymous details (Concrete guide NFT ID & amount of times, that farmers donated (Not saving who (which address donated). The database will only increase like a counter once the donation is finalized in the block also). |
| 4. | Crop origin proofs | We will implement a feature that allows farmers to mint NFTs of crops, that were cultivated on field that farmer minted. Farmer will then be able to use these NFTs as proof of crop origin. The application will generate a QR code for NFT explorer that will contain details about the crop and its origin field (If the field was minted as Public). |
| 1.a | Fields as NFTs (Private) | We will implement functionality that allows farmers to mint their fields as NFTs (via NFTs pallet) in a secure, hashed way (in-app hashed by AgriDot key phrase (each NFT will be checked for the correspondation between signed wallet address and owner of NFT before being decoded and displayed (as additional protection step))) so only AgriDot will be able to decode them and display them to farmers who own them. |
| 1.b | Fields as NFTs (Public) | We will implement functionality that allows farmers to mint their fields (via NFTs pallet) in a public way, so any NFT explorer will be able to display them (NFTs will have a standard format (name, image, metadata(containing field coordinates) )). These fields will then be able to be used with "4. Crop origin proofs" allowing farmers to create a proof of crop origin that will be linked to their public field. |
| 1.c | See the weather for your NFT fields | We will implement functionality that lets you query the coordinates of your NFT fields and display weather for the upcoming period (This feature will use Kodadot uniquery package for creating queries that will be used with Subsquid indexer. Weather for farmer's NFTs will be queried from OpenWeatherMap open-source API (or else if found better)) |
| 2.a | Pests as NFTs | We will implement Pest functionality. Pests will be minted to a unified collection (via NFTs pallet), with coordination of the Field where it appeared (Coordinate will be private (Hashed in-app by AgriDot key phrase)), farmers will only know, that a certain Pest appeared X km away from their field (They will be able to set how far they wish to monitor pests) |
| 2.b | Donation system for Pest reporters | We will implement a donation system for pest reporters. Farmers that actively report Pests and are useful to the community can receive donations from Farmers who are willing to thank them for this information (Potentially saving their crops & giving them the ability to prepare for Pest arrival well ahead). This feature will use a standard transfer pallet. |
| 3.a | Guides as NFTs | We will implement guides to be mintable as NFTs into the unified collection (via NFTs pallet). Guides allow farmers to share their knowledge with other farmers (They can range from DIY guides to crop-growing or animal caretaking guides). |
| 3.b | Rating and donation system for Guides | We will implement functionality that allows farmers to provide guide rating by small donation to Farmer who created the Guide. The application will display the amount of "Likes"(Donations) and a report button (So malicious guides can be removed by administrators). This functionality requires a database, however only for 2 anonymous details (Concrete guide NFT ID & amount of times, that farmers donated (Not saving who (which address donated). The database will only increase like a counter once the donation is finalized in the block also). This feature will use a standard transfer pallet. |
| 4. | Crop origin proofs | We will implement a feature that allows farmers to mint NFTs of crops (via NFTs pallet), that were cultivated on field that farmer minted. Farmer will then be able to use these NFTs as proof of crop origin. The application will generate a QR code for NFT explorer that will contain details about the crop and its origin field (If the field was minted as Public). |
| 5.a | Comprehensive documentation I | We will provide comprehensive documentation for developers - on how to start the application and different functions overview (Via GitHub pages) |
| 5.b | Comprehensive documentation II | We will provide comprehensive documentation for users - on how to create a Polkadot wallet, how to use the application, and a basic application overview (Via Github pages) |

Expand Down

0 comments on commit 969a6f2

Please sign in to comment.