-
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 #176 from casper-ecosystem/Updating-milestones-status
Updating milestones status
- Loading branch information
Showing
20 changed files
with
133 additions
and
25 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
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 |
---|---|---|
@@ -1,6 +1,6 @@ | ||
--- | ||
Milestone: "M1", | ||
Status: "Completed", | ||
Status: "Complete", | ||
--- | ||
<!--lang:en--> | ||
### Description | ||
|
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 |
---|---|---|
@@ -1,6 +1,6 @@ | ||
--- | ||
Milestone: "M2", | ||
Status: "Completed", | ||
Status: "Complete", | ||
--- | ||
<!--lang:en--> | ||
### Description | ||
|
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 |
---|---|---|
@@ -1,6 +1,6 @@ | ||
--- | ||
Milestone: "M1", | ||
Status: "In Progress", | ||
Status: "Completed", | ||
--- | ||
<!--lang:en--> | ||
### Description | ||
|
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: "M2", | ||
Status: "In Progress", | ||
--- | ||
<!--lang:en--> | ||
### Description | ||
|
||
Integration with the Metacask Marketplace where Helix markets would enable the direct purchase of Casks via other cryptocurrencies by acting as a payments processor - p2p payments. This type of integration can be potentially extended to any other Casper Network marketplace. | ||
Example of use case Flow: | ||
Marketplace transaction C2C (customer to customer) payments. Marketplace would enable the customers to pay for secondary trades. Customer A sells NFT on the Casper Network and is willing to accept ETH or USCD (on the Ethereum Network) as payment. Customer B buys this NFT using ETH that he has. In order for this to occur they would be onboarded on Helix if they chose this payment flow. | ||
Upon execution the funds of user B would flow into the Metacask account and Metacask would send the NFT to User B and Payment to user A. | ||
|
||
Deliverables: | ||
|
||
- Creation of a wallet stack for Metacasks users | ||
- payment API between Metacask and Helix | ||
▪ first part of API User registration | ||
▪ second API Payment instructions | ||
- Open sourcing the API SDK making it generally available for any Casper Network marketplace to connect to Helix Markets | ||
- Integration with the Metacask UI/UX payment flow | ||
|
||
### Acceptance Criteria | ||
Metacask users can pay for Casks using their Helix wallets in different crypto currencies. | ||
|
||
|
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 |
---|---|---|
@@ -1,6 +1,6 @@ | ||
--- | ||
Milestone: "M1", | ||
Status: "In Review", | ||
Status: "Completed", | ||
--- | ||
<!--lang:en--> | ||
### Description | ||
|
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 |
---|---|---|
@@ -1,6 +1,6 @@ | ||
--- | ||
Milestone: "M2", | ||
Status: "In Review", | ||
Status: "Completed", | ||
--- | ||
<!--lang:en--> | ||
### Description | ||
|
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 |
---|---|---|
@@ -1,6 +1,6 @@ | ||
--- | ||
Milestone: "M1", | ||
Status: "In Review", | ||
Status: "Completed", | ||
--- | ||
<!--lang:en--> | ||
### Description | ||
|
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 |
---|---|---|
@@ -1,6 +1,6 @@ | ||
--- | ||
Milestone: "M2", | ||
Status: "In Progress", | ||
Status: "In Review", | ||
--- | ||
<!--lang:en--> | ||
### Description | ||
|
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
--- | ||
Milestone: "M2", | ||
Status: "Not Started", | ||
--- | ||
<!--lang:en--> | ||
### Description | ||
|
||
* Develop and test the smart contracts related to the GDP module. | ||
* Develop and test the smart contracts related to the carbon emissions module. | ||
* Conduct thorough testing of the smart contracts on the test environment. Smart Contracts Breakup: | ||
* Smart Contract 1: Mutual agreements, contracts , and other document generation and verification for GDP module. | ||
* Smart Contract 2: Manage eco-labels for product batches in the SCM/PLM module. | ||
* Smart Contract 3: Handle emission reports, validation certificates and traceability in the carbon emissions module | ||
|
||
### Acceptance Criteria | ||
|
||
▪ Smart contracts developed and tested successfully for both GDP disclosures and carbon | ||
launchpad modules | ||
▪ Fetching records of Reports, Eco-labels, Contracts and Certificates for verification and | ||
validations at GDP properly. | ||
▪ Testing confirms the smart contracts' accuracy and functionality. | ||
▪ KPI: Successful implementation and testing of the smart contracts on Casper Testnet. | ||
▪ Contribution to Casper: Provide a working integration of smart contracts with the Casper | ||
network. | ||
|
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,22 @@ | ||
--- | ||
Milestone: "M3", | ||
Status: "Not Started", | ||
--- | ||
<!--lang:en--> | ||
### Description | ||
|
||
Implement login and wallet changes to support smart contract functionalities. | ||
Integrate the backend layer of the web and tablet applications with the Casper network's SDK | ||
integration. | ||
Implement frontend changes to accommodate the wallet integration and different user roles. | ||
Test and ensure smooth workflows between the backend and frontend layers. | ||
Logical changes: Adding more standards GHG and ISO 14064 | ||
|
||
### Acceptance Criteria | ||
|
||
▪ Successful integration of the backend layer with the Casper network's SDK wallet integration. | ||
▪ Frontend changes implemented and functioning properly for the web and tablet applications. | ||
▪ Testing confirms seamless workflows between the backend and frontend layers. | ||
▪ KPI: Seamless integration of backend and frontend with the Casper network's wallet. | ||
▪ Contribution to Casper: Provide a fully integrated application with Casper network's wallet functionality | ||
|
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,20 @@ | ||
--- | ||
Milestone: "M4", | ||
Status: "Not Started", | ||
--- | ||
<!--lang:en--> | ||
### Description | ||
|
||
Launch the beta version of the GDP module backend with Casper integration. | ||
Integrate the GDP and end-to-end modules with the Casper network. | ||
Test workflows and functionalities | ||
|
||
### Acceptance Criteria | ||
|
||
▪ Successful launch of the beta version of the GDP module backend integrated with Casper. | ||
▪ Integration of the GDP and end-to-end modules(Launchpad) with the Casper network. | ||
▪ Thorough testing validates the workflows and functionalities. | ||
▪ KPI: Successful beta version launch and comprehensive testing results. | ||
▪ Contribution to Casper: Provide a functional beta version of the integrated modules with Casper. | ||
|
||
|
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,16 @@ | ||
--- | ||
Milestone: "M5", | ||
Status: "Not Started", | ||
--- | ||
<!--lang:en--> | ||
### Description | ||
|
||
Release the fully functional end-to-end version with Casper integration. | ||
Conduct final testing to ensure all workflows and functionalities are working as expected | ||
|
||
### Acceptance Criteria | ||
|
||
▪ Successful release of the fully functional end-to-end version integrated with Casper. | ||
▪ Final testing confirms the stability and correctness of all workflows and functionalities. | ||
▪ KPI: Successful full release and positive final testing results. | ||
▪ Contribution to Casper: Provide a stable and fully integrated application leveraging Casper's capabilities. |