-
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 #182 from casper-ecosystem/wkly-grant-upd-09feb
Update grant milestones
- Loading branch information
Showing
23 changed files
with
364 additions
and
25 deletions.
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
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,43 @@ | ||
--- | ||
Grant-Number: "", | ||
Name: "Casper Unity SDK", | ||
Service-Provider: "", | ||
Status: "In progress", | ||
Grant-Link: "", | ||
Website: "", | ||
Grant-Size: "Medium", | ||
Total-Milestones: "9", | ||
Current-Milestone: "M1", | ||
M1: "09.01.2024","In progress", | ||
M2: "01.30.2024","To Do", | ||
M3: "13.02.2024","To Do", | ||
M4: "27.02.2024","To Do", | ||
M5: "12.03.2024","To Do", | ||
M6: "TBC","To Do", | ||
M7: "TBC","To Do", | ||
M8: "22.04.2025","To Do", | ||
M9: "22.04.2025","To Do", | ||
Twitter: "", | ||
Public-Project-Chat: "", | ||
Casper-PM: "https://github.com/devendran-m", | ||
Project-GitHub-Repo: "", | ||
--- | ||
<!--lang:en--> | ||
The objective of this grant is; | ||
|
||
Casper SDK for Unity should be released as an assetpackage(.assetpackage),published in UnityAsset Store,and full yopen-sourced-code available on GitHub. | ||
|
||
Solution must be self-contained,with no additional backend,third-party libraries,except those explicitly mentioned in the contract document. | ||
|
||
All major platforms needs to be supported,i.e. Desktop-Windows,macOS Browser Mobile-Android,iOS. | ||
<!--lang:es--] | ||
<!--lang:de--] | ||
<!--lang:fr--] | ||
<!--lang:pl--] | ||
<!--lang:uk--] | ||
[!--lang:*--> |
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,28 @@ | ||
--- | ||
Milestone: "M1", | ||
Status: "In progress", | ||
--- | ||
<!--lang:en--> | ||
### Description | ||
|
||
Milestone 1 - Windows version development and testing. | ||
|
||
Developers integrate the SDK into their code and interact with basic contracts such as (CEP-18, CEP-78, etc.) | ||
|
||
|
||
### Acceptance Criteria | ||
The criteria mentioned above should be met. | ||
- Developers integrate the SDK into their code. | ||
- The game login is achieved through an iframe that opens, using a wallet supported by Casper as the standard. | ||
- The Casper balance and public key are displayed within the game. | ||
- The user's CEP-18 tokens and CEP-78 NFTs are visible. | ||
- A basic CEP-78 NFT is utilized within the game, and the transaction resulting from the operation can be viewed on testnet.cspr.live. The communication established with the contract is examined. | ||
- Ownership of the NFT is verified within the wallet after the transaction is completed. | ||
|
||
|
||
### Progress Update | ||
|
||
**Reporting Period: 06.12.2023 - 09.02.2024** | ||
- Milestone completion trailing behind | ||
- Demo completed on 9th Feb 2024 | ||
- Revised ETC is on or before 16th Feb 2024 |
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,29 @@ | ||
--- | ||
Milestone: "M2", | ||
Status: "To Do", | ||
--- | ||
<!--lang:en--> | ||
### Description | ||
|
||
Milestone 2 - iOS version development and testing. | ||
|
||
Developers integrate the SDK into their code and interact with basic contracts such as (CEP-18, CEP-78, etc.) | ||
|
||
|
||
### Acceptance Criteria | ||
|
||
The criteria mentioned above should be met. | ||
- Developers integrate the SDK into their code. | ||
- The game login is initiated using Casper Dash or Casper Wallet(beta in mobile). | ||
- The Casper balance and public key are displayed within the game. | ||
- The user's CEP-18 tokens and CEP-78 NFTs are visible. | ||
- A basic CEP-78 NFT is utilized within the game, and the transaction resulting from the | ||
operation can be viewed on testnet.cspr.live. The communication established with the contract is examined. | ||
- Ownership of the NFT is verified within the wallet after the transaction is completed. | ||
|
||
|
||
### Progress Update | ||
|
||
**Reporting Period: ** | ||
- 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,28 @@ | ||
--- | ||
Milestone: "M3", | ||
Status: "To Do", | ||
--- | ||
<!--lang:en--> | ||
### Description | ||
|
||
Milestone 3 - Android version development and testing. | ||
|
||
### Scope | ||
Developers integrate the SDK into their code and interact with basic contracts such as (CEP-18, CEP-78, etc.) | ||
|
||
### Acceptance Criteria | ||
|
||
The criteria mentioned above should be met. | ||
- Developers integrate the SDK into their code. | ||
- The game login is initiated using Casper Dash or Casper Wallet(beta in mobile). | ||
- The Casper balance and public key are displayed within the game. | ||
- The user's CEP-18 tokens and CEP-78 NFTs are visible. | ||
- A basic CEP-78 NFT is utilized within the game, and the transaction resulting from the | ||
operation can be viewed on testnet.cspr.live. The communication established with the contract is examined. | ||
- Ownership of the NFT is verified within the wallet after the transaction is completed. | ||
|
||
|
||
### Progress Update | ||
|
||
**Reporting Period: ** | ||
- 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,28 @@ | ||
--- | ||
Milestone: "M4", | ||
Status: "To Do", | ||
--- | ||
<!--lang:en--> | ||
### Description | ||
|
||
Milestone 4 - Browser version development and testing. | ||
|
||
### Scope | ||
Developers integrate the SDK into their code and interact with basic contracts such as (CEP-18, CEP-78, etc.) | ||
|
||
### Acceptance Criteria | ||
|
||
The criteria mentioned above should be met. | ||
- Developers integrate the SDK into their code. | ||
- The game login is initiated using standard web wallets. | ||
- The Casper balance and public key are displayed within the game. | ||
- The user's CEP-18 tokens and CEP-78 NFTs are visible. | ||
- A basic CEP-78 NFT is utilized within the game, and the transaction resulting from the | ||
operation can be viewed on testnet.cspr.live. The communication established with the contract is examined. | ||
- Ownership of the NFT is verified within the wallet after the transaction is completed. | ||
|
||
|
||
### Progress Update | ||
|
||
**Reporting Period: ** | ||
- 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,27 @@ | ||
--- | ||
Milestone: "M5", | ||
Status: "To Do", | ||
--- | ||
<!--lang:en--> | ||
### Description | ||
|
||
Milestone 5 - macOS version development and testing. | ||
|
||
### Scope | ||
Developers integrate the SDK into their code and interact with basic contracts such as (CEP-18, CEP-78, etc.). | ||
|
||
### Acceptance Criteria | ||
|
||
The criteria mentioned above should be met. | ||
- Developers integrate the SDK into their code. | ||
- The game login is achieved through an iframe that opens, using a wallet supported by Casper as the standard. | ||
- The Casper balance and public key are displayed within the game. | ||
- The user's CEP-18 tokens and CEP-78 NFTs are visible. | ||
- A basic CEP-78 NFT is utilized within the game, and the transaction resulting from the | ||
operation can be viewed on testnet.cspr.live. The communication established with the contract is examined. | ||
- Ownership of the NFT is verified within the wallet after the transaction is completed. | ||
|
||
### Progress Update | ||
|
||
**Reporting Period: ** | ||
- 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,24 @@ | ||
--- | ||
Milestone: "M6", | ||
Status: "To Do", | ||
--- | ||
<!--lang:en--> | ||
### Description | ||
|
||
Milstone 6 - Web3auth Integration development and testing. | ||
|
||
### Scope | ||
The user implements the SDK and logs into the application using the Web3 Auth standard. | ||
|
||
### Acceptance Criteria | ||
|
||
The criteria mentioned above should be met. | ||
- The Web3 Auth Unity SDK comes pre-integrated into our SDK for seamless implementation. ● The login option is triggered through Web3 Auth. | ||
- The login option is triggered through a social platform supported by Web3 Auth. | ||
- The user's Web3 identity is created, and the login process is executed. | ||
|
||
|
||
### Progress Update | ||
|
||
**Reporting Period: ** | ||
- 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,29 @@ | ||
--- | ||
Milestone: "M7", | ||
Status: "To Do", | ||
--- | ||
<!--lang:en--> | ||
### Description | ||
|
||
Milestone 7 - Prefab asset pack development and testing. | ||
|
||
### Scope | ||
Assets complete with a foundational user interface designed for quick setup and testing of the aforementioned capabilities. | ||
|
||
This should not only be a showcase of the delivered SDK but also serve as a Unity game example where blockchain functionality operates seamlessly "under the hood", utilizing the integrated capabilities of the delivered SDK. | ||
|
||
This milestone delivers a prefab asset pack that is Unity compatible. | ||
|
||
|
||
### Acceptance Criteria | ||
|
||
The criteria mentioned above should be met. | ||
- The game developer opens a game project on Unity. | ||
- Downloads and imports the prefab asset pack to the game project. | ||
- Uses the assets in the pack in the project. | ||
|
||
|
||
### Progress Update | ||
|
||
**Reporting Period: ** | ||
- 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: "M8", | ||
Status: "To Do", | ||
--- | ||
<!--lang:en--> | ||
### Description | ||
|
||
Milestone 8 - Integration to Casper .Net SDKs. | ||
|
||
### Scope | ||
- Support and maintenance of the SDKs post-deployment, bug fixing, version improvements (on demand). | ||
- Fundamentally, the integrated functions will work in conjunction with Casper .Net SDKs. | ||
|
||
|
||
### Acceptance Criteria | ||
|
||
The criteria mentioned above should be met. | ||
- All developed methods are added to the SDK with comprehensive documentation. | ||
- Once the SDK development is complete and the source code is accessible, interaction with Casper .NET SDKs is established through fundamental methods. | ||
- The integrated SDK triggers our SDK methods, and tests are completed. | ||
|
||
|
||
### Progress Update | ||
|
||
**Reporting Period: ** | ||
- 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,29 @@ | ||
--- | ||
Milestone: "M9", | ||
Status: "To Do", | ||
--- | ||
<!--lang:en--> | ||
### Description | ||
|
||
Milestone 9 - Integration to Inventuna No-Code Platform. | ||
|
||
### Scope | ||
- Support and maintenance of the SDKs post-deployment, bug fixing, version improvements (on demand). | ||
- Tracking all operations returned by the SDK and utilizing custom contracts can be monitored through a no-code tool. | ||
|
||
|
||
### Acceptance Criteria | ||
|
||
The criteria mentioned above should be met. | ||
- The user wallet used for the SDK is connected to the no-code tool. | ||
- The accuracy of fundamental assets owned by the wallet at that moment, such as CSPR balance, CEP-78 NFT collection and NFTs, CEP-18 assets, is verified. | ||
- Raffles are created using the raffles contract in the No Code tool. Users participate in the raffles, and the NFTs they win are transferred to their wallets for use within the game. | ||
- Timeable and mergable NFTs are created within the No Code tool, and these are utilized within the Unity SDK. | ||
- Loot boxes are created in the No Code tool, and their utilization is enabled within the Unity SDK. | ||
- All other standard functions are tested in the No Code tool, and their reflections on the Unity SDK wallet are verified. | ||
|
||
|
||
### Progress Update | ||
|
||
**Reporting Period: ** | ||
- 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
Oops, something went wrong.