From cd7c51fa49f908d510478bb8bbda03e42b33ddab Mon Sep 17 00:00:00 2001 From: Fuling Date: Mon, 25 Jan 2021 21:11:53 +0800 Subject: [PATCH 01/12] Create starry_network.md --- applications/starry_network.md | 112 +++++++++++++++++++++++++++++++++ 1 file changed, 112 insertions(+) create mode 100644 applications/starry_network.md diff --git a/applications/starry_network.md b/applications/starry_network.md new file mode 100644 index 00000000000..c95c30afb67 --- /dev/null +++ b/applications/starry_network.md @@ -0,0 +1,112 @@ +# Open Grant Proposal + +> This document is referenced in the terms and conditions and therefore needs to contain all the required information. Don't remove any of the mandatory parts presented in bold letters or as headlines! See the [Open Grants Program Process](https://github.com/w3f/Open-Grants-Program/blob/master/README_2.md) on how to submit a proposal. + +> This page is also available in [Chinese (中文)](./application-template-cn.md). + +* **Project Name:** Name of your project (e.g. DuoSwap Module) +* **Team Name:** Legal name of your team (e.g. Duo) +* **Payment Address:** BTC or Ethereum (DAI) payment address. We don't accept payments for the program in other currencies at this stage. (e.g. 123mp123...) + +*The above combination of your GitHub account submitting the application and payment address will be your unique identifier during the program. Please keep them safe.* + +## Project Overview :page_facing_up: +If this application in response to an RFP then please indicate this on the first line of this section. + +### Overview + +Please provide the following: + * A brief description of the project. + * An indication of how you will integrate this project into Substrate / Polkadot / Kusama. + * An indication of why your team is interested in creating this project. + +### Project Details +We expect the teams to already have a solid idea about the project's expected final state. + +Therefore, we ask the teams to submit (where relevant): +* Mockups/designs of any UI components +* API specifications of the core functionality +* An overview of the technology stack to be used +* Documentation of core components, protocols, architecture etc. to be deployed +* PoC/MVP or other relevant prior work or research on the topic + +### Ecosystem Fit +Are there any other projects similar to yours? If so, how is your project different? + +## Team :busts_in_silhouette: + +### Team members +* Name of team leader +* Names of team members + +### Contact +* **Contact Name:** Full name of the contact person (e.g. John Brown) +* **Contact Email:** Contact email (e.g. john@duo.com) +* Website + +### Legal Structure +* **Registered Address:** Address of your registered legal entity, if available. Please keep it on one line. (e.g. High Street 1, London LK1 234, UK) +* **Registered Legal Entity:** Name of your registered legal entity, if available. (e.g. Duo Ltd.) + +### Team's experience +Please describe the team's relevant experience. If the project involves development work, then we'd appreciated if you can single out a few interesting code commits made by team members on their past projects. For research-related grants, references to past publications and projects in a related domain are helpful. + +### Team Code Repos +* https://github.com/ +* https://github.com/ + +### Team LinkedIn Profiles +* https://www.linkedin.com/ +* https://www.linkedin.com/ + +## Development Roadmap :nut_and_bolt: + +This section should break out the development roadmap into a number of milestones. Since the milestones will appear in the grant contract, it helps to describe the functionality we should expect, plus how we can check that such functionality exists in the product. Whenever milestones are delivered, we refer to the contract to ensure that everything has been delivered as expected. + +Below we provide an **example roadmap**. In the descriptions it should be clear how the project is related to Substrate and/or Polkadot. We recommend that the scope of the work can fit within a 3 month period and that teams structure their roadmap as 1 month = 1 milestone. + +For each milestone: +* Please be sure to include a specification of your software. Treat it as a contract - the level of detail must be enough to later verify that the software meets the specification. +To assist you in defining it, we created a document with examples for some grant categories [here](../src/grant_guidelines_per_category.md). +* Please include total amount of funding requested per milestone. +* Please note that we require documentation (e.g. tutorials, API specifications, architecture details) in each milestone. This ensures that the code can be widely used by the community. +* Please provide a test suite, comprising unit and integration tests, along with a guide on how to run these. +* Please commit to providing a dockerfiles for the delivery of your project. +* Please indicate the milestone duration, as well as number of Full-Time Employees working on each milestone, and include the number of days along with their cost per day. +* Deliverables 0a-0d are mandatory and should not be removed, unless you explicitly specify a reason within the PR's `Additional Notes` section (e.g. Milestone X is research oriented and as such there is no code to test) + +### Overview +* **Total Estimated Duration:** Duration of the whole project (e.g. 2 months) +* **Full-time equivalent (FTE):** Workload of an employed person ([see](https://en.wikipedia.org/wiki/Full-time_equivalent)) (e.g. 2 FTE) +* **Total Costs:** Amount of Payment in BTC or DAI for the whole project. The total amount of funding needs to be below $30k for initial grants and $100k for follow-up grants at the time of submission. (e.g. 0.80 BTC) + +### Milestone 1 Example — Implement Substrate Modules +* **Estimated Duration:** 1 month +* **FTE:** 1 +* **Costs:** 0.75 BTC + +| Number | Deliverable | Specification | +| ------------- | ------------- | ------------- | +| 0a. | License | Apache 2.0 / MIT / Unlicense | +| 0b. | Documentation | We will provide both inline documentation of the code and a basic tutorial that explains how a user can (for example) spin up one of our Substrate nodes. Once the node is up, it will be possible to send test transactions that will show how the new functionality works. | +| 0c. | Testing Guide | The code will have unit-test coverage (min. 70%) to ensure functionality and robustness. In the guide we will describe how to run these tests | +| 0d. | Article/Tutorial | We will write an article or tutorial that explains the work done as part of the grant. +| 1. | Substrate module: X | We will create a Substrate module that will... (Please list the functionality that will be coded for the first milestone) | +| 2. | Substrate module: Y | We will create a Substrate module that will... | +| 3. | Substrate module: Z | We will create a Substrate module that will... | +| 4. | Substrate chain | Modules X, Y & Z of our custom chain will interact in such a way... (Please describe the deliverable here as detailed as possible) | +| 5. | Docker | We will provide a dockerfile to demonstrate the full functionality of our chain | + +### Milestone 2 Example — Additional features +... + +## Future Plans +Please include the team's long-term plans and intentions. + +## Additional Information :heavy_plus_sign: +Any additional information that you think is relevant to this application that hasn't already been included. + +Possible additional information to include: +* What work has been done so far? +* Are there are any teams who have already contributed (financially) to the project? +* Have you applied for other grants so far? From 4c0c4ff3f6595868cda7fd741c231cd163069aba Mon Sep 17 00:00:00 2001 From: Fuling Date: Mon, 25 Jan 2021 21:13:17 +0800 Subject: [PATCH 02/12] Rename starry_network.md to Starry_Network.md --- applications/{starry_network.md => Starry_Network.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename applications/{starry_network.md => Starry_Network.md} (100%) diff --git a/applications/starry_network.md b/applications/Starry_Network.md similarity index 100% rename from applications/starry_network.md rename to applications/Starry_Network.md From 20f1c9b32e19e60cb229b5d4e9aba60033862102 Mon Sep 17 00:00:00 2001 From: Fuling Date: Sun, 31 Jan 2021 13:05:50 +0800 Subject: [PATCH 03/12] Update Starry_Network.md --- applications/Starry_Network.md | 136 +++++++++++++++------------------ 1 file changed, 61 insertions(+), 75 deletions(-) diff --git a/applications/Starry_Network.md b/applications/Starry_Network.md index c95c30afb67..f98868dc0f5 100644 --- a/applications/Starry_Network.md +++ b/applications/Starry_Network.md @@ -1,112 +1,98 @@ # Open Grant Proposal -> This document is referenced in the terms and conditions and therefore needs to contain all the required information. Don't remove any of the mandatory parts presented in bold letters or as headlines! See the [Open Grants Program Process](https://github.com/w3f/Open-Grants-Program/blob/master/README_2.md) on how to submit a proposal. +* **Project Name:** Starry Protocol +* **Proposer:** [Starry Network](https://github.com/Starry-Network) +* **Payment Address:** 0xe29DE8c6088d241647e6456F8b4755a3D0f7c8B1 -> This page is also available in [Chinese (中文)](./application-template-cn.md). +## Project Overview :page_facing_up: +### Overview -* **Project Name:** Name of your project (e.g. DuoSwap Module) -* **Team Name:** Legal name of your team (e.g. Duo) -* **Payment Address:** BTC or Ethereum (DAI) payment address. We don't accept payments for the program in other currencies at this stage. (e.g. 123mp123...) +It is well known that most NFTs are traded either directly or by auction, and the single NFT limit the flexibility of NFTs in some ways. -*The above combination of your GitHub account submitting the application and payment address will be your unique identifier during the program. Please keep them safe.* +Splittable NFT will bring more possibilities for NFT ecosystem. For example, buying SubNFTs on bonding curve will allow for better pricing of works, while NFTs that are otherwise very expensive can be collected by more people, and will also have applications in rare tickets, rare music works on sale, etc. -## Project Overview :page_facing_up: -If this application in response to an RFP then please indicate this on the first line of this section. +Starry is developing a substrate-based NFT ecosystem with support for creating single/multiple NFT, splitting NFTs and buying SubNFTs -### Overview +### Project Details +The Starry Protocol contains four parts: Pallet_NFT, Pallet_SubNFT, Pallet_EX, Frontend -Please provide the following: - * A brief description of the project. - * An indication of how you will integrate this project into Substrate / Polkadot / Kusama. - * An indication of why your team is interested in creating this project. +#### Architecture -### Project Details -We expect the teams to already have a solid idea about the project's expected final state. -Therefore, we ask the teams to submit (where relevant): -* Mockups/designs of any UI components -* API specifications of the core functionality -* An overview of the technology stack to be used -* Documentation of core components, protocols, architecture etc. to be deployed -* PoC/MVP or other relevant prior work or research on the topic -### Ecosystem Fit -Are there any other projects similar to yours? If so, how is your project different? +![](https://github.com/Starry-Network/frontend_mvp/blob/main/public/images/architecture.png?raw=true) + + + +**Pallet_NFT** + +Creates, destroys, transfers NFT. modifies existing Pallet-NFT so that they can create multiple NFT + +**Pallet_SubNFT** + +Splitting single NFT into SubNFTs and recovering SubNFTs into single NFT + +**Pallet_EX** + +exchange NFT (including buying SubNFTs with bonding curve/one price) and send royalties generated by each transaction to the creator + +**FrontEnd** + +Interaction with users. Here is a [demo](https://friendly-mclean-d455eb.netlify.app/) ## Team :busts_in_silhouette: ### Team members -* Name of team leader -* Names of team members +* Poria - Full-stack Developer ### Contact -* **Contact Name:** Full name of the contact person (e.g. John Brown) -* **Contact Email:** Contact email (e.g. john@duo.com) -* Website +* **Contact Name:** Poria Cattus +* **Contact Email:** fulingcat@gmail.com +* Starry.network (WIP) ### Legal Structure -* **Registered Address:** Address of your registered legal entity, if available. Please keep it on one line. (e.g. High Street 1, London LK1 234, UK) -* **Registered Legal Entity:** Name of your registered legal entity, if available. (e.g. Duo Ltd.) +* No Legal Entity ### Team's experience -Please describe the team's relevant experience. If the project involves development work, then we'd appreciated if you can single out a few interesting code commits made by team members on their past projects. For research-related grants, references to past publications and projects in a related domain are helpful. +**Poria** -### Team Code Repos -* https://github.com/ -* https://github.com/ +- Full-stack Developer +- Expertise in using JS, PHP, Python, Rust +- Have written blockchain with DAG structure in JS -### Team LinkedIn Profiles -* https://www.linkedin.com/ -* https://www.linkedin.com/ +### Team Code Repos +* https://github.com/Starry-Network +* https://github.com/Starry-Network/frontend_mvp ## Development Roadmap :nut_and_bolt: -This section should break out the development roadmap into a number of milestones. Since the milestones will appear in the grant contract, it helps to describe the functionality we should expect, plus how we can check that such functionality exists in the product. Whenever milestones are delivered, we refer to the contract to ensure that everything has been delivered as expected. - -Below we provide an **example roadmap**. In the descriptions it should be clear how the project is related to Substrate and/or Polkadot. We recommend that the scope of the work can fit within a 3 month period and that teams structure their roadmap as 1 month = 1 milestone. - -For each milestone: -* Please be sure to include a specification of your software. Treat it as a contract - the level of detail must be enough to later verify that the software meets the specification. -To assist you in defining it, we created a document with examples for some grant categories [here](../src/grant_guidelines_per_category.md). -* Please include total amount of funding requested per milestone. -* Please note that we require documentation (e.g. tutorials, API specifications, architecture details) in each milestone. This ensures that the code can be widely used by the community. -* Please provide a test suite, comprising unit and integration tests, along with a guide on how to run these. -* Please commit to providing a dockerfiles for the delivery of your project. -* Please indicate the milestone duration, as well as number of Full-Time Employees working on each milestone, and include the number of days along with their cost per day. -* Deliverables 0a-0d are mandatory and should not be removed, unless you explicitly specify a reason within the PR's `Additional Notes` section (e.g. Milestone X is research oriented and as such there is no code to test) - ### Overview -* **Total Estimated Duration:** Duration of the whole project (e.g. 2 months) -* **Full-time equivalent (FTE):** Workload of an employed person ([see](https://en.wikipedia.org/wiki/Full-time_equivalent)) (e.g. 2 FTE) -* **Total Costs:** Amount of Payment in BTC or DAI for the whole project. The total amount of funding needs to be below $30k for initial grants and $100k for follow-up grants at the time of submission. (e.g. 0.80 BTC) +* **Total Estimated Duration:** 2 months +* **Full-time equivalent (FTE):** 1 +* **Total Costs:** 14000 DAI ### Milestone 1 Example — Implement Substrate Modules -* **Estimated Duration:** 1 month +* **Estimated Duration:** 2 months * **FTE:** 1 -* **Costs:** 0.75 BTC +* **Costs:** 14000 DAI | Number | Deliverable | Specification | | ------------- | ------------- | ------------- | -| 0a. | License | Apache 2.0 / MIT / Unlicense | -| 0b. | Documentation | We will provide both inline documentation of the code and a basic tutorial that explains how a user can (for example) spin up one of our Substrate nodes. Once the node is up, it will be possible to send test transactions that will show how the new functionality works. | -| 0c. | Testing Guide | The code will have unit-test coverage (min. 70%) to ensure functionality and robustness. In the guide we will describe how to run these tests | -| 0d. | Article/Tutorial | We will write an article or tutorial that explains the work done as part of the grant. -| 1. | Substrate module: X | We will create a Substrate module that will... (Please list the functionality that will be coded for the first milestone) | -| 2. | Substrate module: Y | We will create a Substrate module that will... | -| 3. | Substrate module: Z | We will create a Substrate module that will... | -| 4. | Substrate chain | Modules X, Y & Z of our custom chain will interact in such a way... (Please describe the deliverable here as detailed as possible) | +| 0a. | License | Apache License 2.0 | +| 0b. | Documentation | Documents containing the description of whole architecture design for Starry | +| 0c. | Testing Guide | Provide a full test suite and guide for NFT. The code will have unit-test coverage (min. 70%) to ensure functionality and robustness. | +| 0d. | Article/Tutorial | Write an article or tutorial that explains the work done as part of the grant on medium. +| 1a. | Node Repo | Complete the deployment of the basic public chain | +| 2a. | Pallet_NFT | Complete the development of pallet_nft, realize the single/multiple NFT create, transfer and burn mechanism +| 2b. | Pallet_SubNFT | Complete the development of pallet_subNFT, relize the split, transfer, burn and recover mechanism| +| 2c. | Pallet_EX | Complete the development of pallet_ex, relize the bonding curve and one price mechanism| +| 3. | Front End | Complete the development of the basic interactive page in React, the demo is [demo](https://friendly-mclean-d455eb.netlify.app/)| | 5. | Docker | We will provide a dockerfile to demonstrate the full functionality of our chain | -### Milestone 2 Example — Additional features -... ## Future Plans -Please include the team's long-term plans and intentions. - -## Additional Information :heavy_plus_sign: -Any additional information that you think is relevant to this application that hasn't already been included. - -Possible additional information to include: -* What work has been done so far? -* Are there are any teams who have already contributed (financially) to the project? -* Have you applied for other grants so far? +- Implementing auction functions (English auction, Dutch auction). +- Add comments, favorites and data analysis to Starry to improve the Starry ecosystem. +- Simplify the usage process and make NFT more friendly to newcomers. +- Implementing cross-chain transmission NFT. +- Lead the community to hold online exhibitions and comment on good NFT works, using tokens to promote these beneficial behaviors. From 24852480bd505bc2f58f1e0046429079b8d3c138 Mon Sep 17 00:00:00 2001 From: Fuling Date: Sun, 31 Jan 2021 15:46:49 +0800 Subject: [PATCH 04/12] update Ecosystem Fit --- applications/Starry_Network.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/applications/Starry_Network.md b/applications/Starry_Network.md index f98868dc0f5..074a747887e 100644 --- a/applications/Starry_Network.md +++ b/applications/Starry_Network.md @@ -16,6 +16,15 @@ Starry is developing a substrate-based NFT ecosystem with support for creating s ### Project Details The Starry Protocol contains four parts: Pallet_NFT, Pallet_SubNFT, Pallet_EX, Frontend +### Ecosystem Fit +What is the difference between SubNFT and Erc-1155? + +erc-1155's multiple NFT is Semi-fungible tokens, these tokens use same token_id. + +SubNFT splits single NFT into different NFTs, each SubNFT has its own token_id. As a result, subNFT is even rarer and suitable as a collector's item. + +For example, we can use Semi-fungible tokens to create general admission tickets for a concert, and then use SubNFT to create commemorative tickets. + #### Architecture From e980a3a00c1a1e3f6219ae922a00ce7a0465d18e Mon Sep 17 00:00:00 2001 From: Fuling Date: Fri, 5 Feb 2021 10:25:30 +0800 Subject: [PATCH 05/12] update overview --- applications/Starry_Network.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/applications/Starry_Network.md b/applications/Starry_Network.md index 074a747887e..bfa66b91d94 100644 --- a/applications/Starry_Network.md +++ b/applications/Starry_Network.md @@ -11,7 +11,7 @@ It is well known that most NFTs are traded either directly or by auction, and th Splittable NFT will bring more possibilities for NFT ecosystem. For example, buying SubNFTs on bonding curve will allow for better pricing of works, while NFTs that are otherwise very expensive can be collected by more people, and will also have applications in rare tickets, rare music works on sale, etc. -Starry is developing a substrate-based NFT ecosystem with support for creating single/multiple NFT, splitting NFTs and buying SubNFTs +Starry is developing an NFT Wrapper and can split an NFT into some sub nft or fungible token or split a set of NFTs into fungible tokens. ### Project Details The Starry Protocol contains four parts: Pallet_NFT, Pallet_SubNFT, Pallet_EX, Frontend From 2fa018d019ec1406b622220b8ea6d2135a6fe3db Mon Sep 17 00:00:00 2001 From: Fuling Date: Fri, 5 Feb 2021 10:26:26 +0800 Subject: [PATCH 06/12] update architecture --- applications/Starry_Network.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/applications/Starry_Network.md b/applications/Starry_Network.md index bfa66b91d94..dd9f82a907e 100644 --- a/applications/Starry_Network.md +++ b/applications/Starry_Network.md @@ -39,7 +39,7 @@ Creates, destroys, transfers NFT. modifies existing Pallet-NFT so that they can **Pallet_SubNFT** -Splitting single NFT into SubNFTs and recovering SubNFTs into single NFT +An NFT Wrapper to split NFTs into SubNFTs or fungible tokens, or a set of NFTs into fungible tokens **Pallet_EX** From 6b30682e015af04e8be391d8aea655c1c5f7c73d Mon Sep 17 00:00:00 2001 From: Fuling Date: Fri, 5 Feb 2021 10:29:39 +0800 Subject: [PATCH 07/12] remove ecosystem fit and add additional Information --- applications/Starry_Network.md | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/applications/Starry_Network.md b/applications/Starry_Network.md index dd9f82a907e..5e8024c4153 100644 --- a/applications/Starry_Network.md +++ b/applications/Starry_Network.md @@ -16,14 +16,6 @@ Starry is developing an NFT Wrapper and can split an NFT into some sub nft or fu ### Project Details The Starry Protocol contains four parts: Pallet_NFT, Pallet_SubNFT, Pallet_EX, Frontend -### Ecosystem Fit -What is the difference between SubNFT and Erc-1155? - -erc-1155's multiple NFT is Semi-fungible tokens, these tokens use same token_id. - -SubNFT splits single NFT into different NFTs, each SubNFT has its own token_id. As a result, subNFT is even rarer and suitable as a collector's item. - -For example, we can use Semi-fungible tokens to create general admission tickets for a concert, and then use SubNFT to create commemorative tickets. #### Architecture @@ -105,3 +97,9 @@ Interaction with users. Here is a [demo](https://friendly-mclean-d455eb.netlify - Simplify the usage process and make NFT more friendly to newcomers. - Implementing cross-chain transmission NFT. - Lead the community to hold online exhibitions and comment on good NFT works, using tokens to promote these beneficial behaviors. + +## Additional Information :heavy_plus_sign: + +- What is the difference between SubNFT and Erc-721? + +subNFT is also erc-721 token. From dca327d12b450baa89c3cea03e24e0360f579eb3 Mon Sep 17 00:00:00 2001 From: Fuling Date: Fri, 5 Feb 2021 10:32:50 +0800 Subject: [PATCH 08/12] update overview --- applications/Starry_Network.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/applications/Starry_Network.md b/applications/Starry_Network.md index 5e8024c4153..325488813e6 100644 --- a/applications/Starry_Network.md +++ b/applications/Starry_Network.md @@ -9,7 +9,7 @@ It is well known that most NFTs are traded either directly or by auction, and the single NFT limit the flexibility of NFTs in some ways. -Splittable NFT will bring more possibilities for NFT ecosystem. For example, buying SubNFTs on bonding curve will allow for better pricing of works, while NFTs that are otherwise very expensive can be collected by more people, and will also have applications in rare tickets, rare music works on sale, etc. +Splittable NFT will bring liquidity and more possibilities for NFT ecosystem. For example, buying SubNFTs on bonding curve will allow for better pricing of works, while NFTs that are otherwise very expensive can be collected by more people, and will also have applications in rare tickets, rare music works on sale, etc. Starry is developing an NFT Wrapper and can split an NFT into some sub nft or fungible token or split a set of NFTs into fungible tokens. @@ -100,6 +100,6 @@ Interaction with users. Here is a [demo](https://friendly-mclean-d455eb.netlify ## Additional Information :heavy_plus_sign: -- What is the difference between SubNFT and Erc-721? +What is the difference between SubNFT and Erc-721? subNFT is also erc-721 token. From 55b57b25472923027755cb5f37a1e2ccbf61e961 Mon Sep 17 00:00:00 2001 From: Fuling Date: Fri, 5 Feb 2021 20:17:01 +0800 Subject: [PATCH 09/12] Update Starry_Network.md --- applications/Starry_Network.md | 36 +++++++++++++++++++++------------- 1 file changed, 22 insertions(+), 14 deletions(-) diff --git a/applications/Starry_Network.md b/applications/Starry_Network.md index 325488813e6..b55ae0c859f 100644 --- a/applications/Starry_Network.md +++ b/applications/Starry_Network.md @@ -9,29 +9,26 @@ It is well known that most NFTs are traded either directly or by auction, and the single NFT limit the flexibility of NFTs in some ways. -Splittable NFT will bring liquidity and more possibilities for NFT ecosystem. For example, buying SubNFTs on bonding curve will allow for better pricing of works, while NFTs that are otherwise very expensive can be collected by more people, and will also have applications in rare tickets, rare music works on sale, etc. +Splittable NFT will bring liquidity, lower barriers to entry and more possibilities to NFT ecosystem. For example, buying SubNFTs on bonding curve will allow for better pricing of works, while NFTs that are otherwise very expensive can be collected by more people, it is also possible to purchase a group of NFT tokens and contribute to the management of this group of NFTs. -Starry is developing an NFT Wrapper and can split an NFT into some sub nft or fungible token or split a set of NFTs into fungible tokens. +Starry provides some solutions for splittable NFTs, such as: splitting Single NFT into some SubNFTs, splitting Single NFT into some fungible tokens, and splitting a group of NFTs into some fungible tokens and managing them using dao. ### Project Details The Starry Protocol contains four parts: Pallet_NFT, Pallet_SubNFT, Pallet_EX, Frontend - #### Architecture -![](https://github.com/Starry-Network/frontend_mvp/blob/main/public/images/architecture.png?raw=true) - - +![](https://github.com/Starry-Network/frontend_mvp/raw/main/public/images/architecture.png) -**Pallet_NFT** +**Pallet_SubNFT** -Creates, destroys, transfers NFT. modifies existing Pallet-NFT so that they can create multiple NFT +An NFT Wrapper to split NFTs into SubNFTs or fungible tokens, or a set of NFTs into fungible tokens( without DAO) -**Pallet_SubNFT** +**Pallet_NFTDAO** -An NFT Wrapper to split NFTs into SubNFTs or fungible tokens, or a set of NFTs into fungible tokens +Split a set of NFTs into fungible tokens and manage the NFTs in a DAO way, such as adding more NFTs or selling NFTs **Pallet_EX** @@ -84,11 +81,12 @@ Interaction with users. Here is a [demo](https://friendly-mclean-d455eb.netlify | 0c. | Testing Guide | Provide a full test suite and guide for NFT. The code will have unit-test coverage (min. 70%) to ensure functionality and robustness. | | 0d. | Article/Tutorial | Write an article or tutorial that explains the work done as part of the grant on medium. | 1a. | Node Repo | Complete the deployment of the basic public chain | -| 2a. | Pallet_NFT | Complete the development of pallet_nft, realize the single/multiple NFT create, transfer and burn mechanism -| 2b. | Pallet_SubNFT | Complete the development of pallet_subNFT, relize the split, transfer, burn and recover mechanism| +| 2a. | Pallet_SubNFT | Complete the development of pallet_subNFT, relize the split, transfer, burn and recover mechanism| +| 2b. | Pallet_NFTDAO | Complete the development of Pallet_NFTDAO, relize the split NFTs, and dao mechanism| | 2c. | Pallet_EX | Complete the development of pallet_ex, relize the bonding curve and one price mechanism| | 3. | Front End | Complete the development of the basic interactive page in React, the demo is [demo](https://friendly-mclean-d455eb.netlify.app/)| | 5. | Docker | We will provide a dockerfile to demonstrate the full functionality of our chain | +| 6. | PSP | Add a Polkadot Standards Proposal about Splittable NFT | ## Future Plans @@ -100,6 +98,16 @@ Interaction with users. Here is a [demo](https://friendly-mclean-d455eb.netlify ## Additional Information :heavy_plus_sign: -What is the difference between SubNFT and Erc-721? +- What is the difference between SubNFT and Erc-1155? + + erc-1155's multiple NFT is Semi-fungible tokens, these tokens use same token_id. + + SubNFT splits single NFT into different NFTs, each SubNFT has its own token_id. As a result, subNFT is even rarer and suitable as a collector's item. + + For example, we can use Semi-fungible tokens to create general admission tickets for a concert, and then use SubNFT to create commemorative tickets. + + + +- What is the difference between SubNFT and Erc-721? -subNFT is also erc-721 token. + subNFT is also erc-721 token From 683e327013afe819b1bdc0fb418bb6e2bba52360 Mon Sep 17 00:00:00 2001 From: Fuling Date: Tue, 9 Feb 2021 17:35:57 +0800 Subject: [PATCH 10/12] add nft dao architecture image and reduce price --- applications/Starry_Network.md | 20 ++++++++++++-------- 1 file changed, 12 insertions(+), 8 deletions(-) diff --git a/applications/Starry_Network.md b/applications/Starry_Network.md index b55ae0c859f..cf7966e883f 100644 --- a/applications/Starry_Network.md +++ b/applications/Starry_Network.md @@ -22,17 +22,21 @@ The Starry Protocol contains four parts: Pallet_NFT, Pallet_SubNFT, Pallet_EX, F ![](https://github.com/Starry-Network/frontend_mvp/raw/main/public/images/architecture.png) + + +![](https://github.com/Starry-Network/frontend_mvp/raw/main/public/images/nft_dao.png) + **Pallet_SubNFT** -An NFT Wrapper to split NFTs into SubNFTs or fungible tokens, or a set of NFTs into fungible tokens( without DAO) +An NFT Wrapper to split NFTs into SubNFTs or fungible tokens, or a set of NFTs into fungible tokens( without DAO). Here is [demo page](https://friendly-mclean-d455eb.netlify.app/splitNFT). **Pallet_NFTDAO** -Split a set of NFTs into fungible tokens and manage the NFTs in a DAO way, such as adding more NFTs or selling NFTs +Split a set of NFTs into fungible tokens and manage the NFTs in a DAO way, such as adding more NFTs or selling NFTs. Here is [demo page](https://friendly-mclean-d455eb.netlify.app/dao/0). **Pallet_EX** -exchange NFT (including buying SubNFTs with bonding curve/one price) and send royalties generated by each transaction to the creator +exchange NFT (including buying SubNFTs with bonding curve/one price) and send royalties generated by each transaction to the creator. Here is [demo page](https://friendly-mclean-d455eb.netlify.app/nft/1). **FrontEnd** @@ -67,24 +71,24 @@ Interaction with users. Here is a [demo](https://friendly-mclean-d455eb.netlify ### Overview * **Total Estimated Duration:** 2 months * **Full-time equivalent (FTE):** 1 -* **Total Costs:** 14000 DAI +* **Total Costs:** 12000 DAI ### Milestone 1 Example — Implement Substrate Modules * **Estimated Duration:** 2 months * **FTE:** 1 -* **Costs:** 14000 DAI +* **Costs:** 12000 DAI | Number | Deliverable | Specification | | ------------- | ------------- | ------------- | | 0a. | License | Apache License 2.0 | | 0b. | Documentation | Documents containing the description of whole architecture design for Starry | | 0c. | Testing Guide | Provide a full test suite and guide for NFT. The code will have unit-test coverage (min. 70%) to ensure functionality and robustness. | -| 0d. | Article/Tutorial | Write an article or tutorial that explains the work done as part of the grant on medium. -| 1a. | Node Repo | Complete the deployment of the basic public chain | +| 0d. | Article/Tutorial | Write an article or tutorial that explains the work done as part of the grant on medium. | +| 1a. | Node Repo | Complete the deployment of the basic public chain | | 2a. | Pallet_SubNFT | Complete the development of pallet_subNFT, relize the split, transfer, burn and recover mechanism| | 2b. | Pallet_NFTDAO | Complete the development of Pallet_NFTDAO, relize the split NFTs, and dao mechanism| | 2c. | Pallet_EX | Complete the development of pallet_ex, relize the bonding curve and one price mechanism| -| 3. | Front End | Complete the development of the basic interactive page in React, the demo is [demo](https://friendly-mclean-d455eb.netlify.app/)| +| 3. | Front End | Complete the development of the basic interactive page in React, the demo is [demo](https://friendly-mclean-d455eb.netlify.app/)| | 5. | Docker | We will provide a dockerfile to demonstrate the full functionality of our chain | | 6. | PSP | Add a Polkadot Standards Proposal about Splittable NFT | From 7bb4bc939a5b07646b8cdaa30c90bb651c568538 Mon Sep 17 00:00:00 2001 From: Fuling Date: Thu, 11 Feb 2021 18:18:52 +0800 Subject: [PATCH 11/12] Added user story about NFT DAO, update demo link --- applications/Starry_Network.md | 32 ++++++++++++++++++++++---------- 1 file changed, 22 insertions(+), 10 deletions(-) diff --git a/applications/Starry_Network.md b/applications/Starry_Network.md index cf7966e883f..bf4e28c530b 100644 --- a/applications/Starry_Network.md +++ b/applications/Starry_Network.md @@ -28,19 +28,19 @@ The Starry Protocol contains four parts: Pallet_NFT, Pallet_SubNFT, Pallet_EX, F **Pallet_SubNFT** -An NFT Wrapper to split NFTs into SubNFTs or fungible tokens, or a set of NFTs into fungible tokens( without DAO). Here is [demo page](https://friendly-mclean-d455eb.netlify.app/splitNFT). +An NFT Wrapper to split NFTs into SubNFTs or fungible tokens, or a set of NFTs into fungible tokens( without DAO). Here is [demo page](https://friendly-mclean-d455eb.netlify.app/#/splitNFT). **Pallet_NFTDAO** -Split a set of NFTs into fungible tokens and manage the NFTs in a DAO way, such as adding more NFTs or selling NFTs. Here is [demo page](https://friendly-mclean-d455eb.netlify.app/dao/0). +Split a set of NFTs into fungible tokens and manage the NFTs in a DAO way, such as adding more NFTs or selling NFTs. Here is [demo page](https://friendly-mclean-d455eb.netlify.app/#/dao/0). **Pallet_EX** -exchange NFT (including buying SubNFTs with bonding curve/one price) and send royalties generated by each transaction to the creator. Here is [demo page](https://friendly-mclean-d455eb.netlify.app/nft/1). +exchange NFT (including buying SubNFTs with bonding curve/one price) and send royalties generated by each transaction to the creator. Here is [demo page](https://friendly-mclean-d455eb.netlify.app/#/nft/1). **FrontEnd** -Interaction with users. Here is a [demo](https://friendly-mclean-d455eb.netlify.app/) +Interaction with users. Here is a [demo](https://friendly-mclean-d455eb.netlify.app/#/) ## Team :busts_in_silhouette: @@ -69,14 +69,14 @@ Interaction with users. Here is a [demo](https://friendly-mclean-d455eb.netlify ## Development Roadmap :nut_and_bolt: ### Overview -* **Total Estimated Duration:** 2 months +* **Total Estimated Duration:** 2.5 months * **Full-time equivalent (FTE):** 1 * **Total Costs:** 12000 DAI ### Milestone 1 Example — Implement Substrate Modules -* **Estimated Duration:** 2 months +* **Estimated Duration:** 2.5 months * **FTE:** 1 -* **Costs:** 12000 DAI +* **Costs:** 10000 DAI | Number | Deliverable | Specification | | ------------- | ------------- | ------------- | @@ -88,13 +88,14 @@ Interaction with users. Here is a [demo](https://friendly-mclean-d455eb.netlify | 2a. | Pallet_SubNFT | Complete the development of pallet_subNFT, relize the split, transfer, burn and recover mechanism| | 2b. | Pallet_NFTDAO | Complete the development of Pallet_NFTDAO, relize the split NFTs, and dao mechanism| | 2c. | Pallet_EX | Complete the development of pallet_ex, relize the bonding curve and one price mechanism| -| 3. | Front End | Complete the development of the basic interactive page in React, the demo is [demo](https://friendly-mclean-d455eb.netlify.app/)| +| 3. | Front End | Complete the development of the basic interactive page in React, the demo is [demo](https://friendly-mclean-d455eb.netlify.app/#/) | | 5. | Docker | We will provide a dockerfile to demonstrate the full functionality of our chain | | 6. | PSP | Add a Polkadot Standards Proposal about Splittable NFT | ## Future Plans - Implementing auction functions (English auction, Dutch auction). +- Adding auctions to NFT DAO. - Add comments, favorites and data analysis to Starry to improve the Starry ecosystem. - Simplify the usage process and make NFT more friendly to newcomers. - Implementing cross-chain transmission NFT. @@ -110,8 +111,19 @@ Interaction with users. Here is a [demo](https://friendly-mclean-d455eb.netlify For example, we can use Semi-fungible tokens to create general admission tickets for a concert, and then use SubNFT to create commemorative tickets. - - - What is the difference between SubNFT and Erc-721? subNFT is also erc-721 token + +- Perhaps you may be confused with how nft dao works, here is an example to explain it: + + Alice created the token named DOGE with a set of NFTs related to the Doge meme, but she did not want to manage this set of NFTs herself, so Alice created the Doge NFTS DAO. + + Bob was very happy with Doge and created NFT related to Doge, at this time he saw Doge NFTS DAO, so he thought it would be a great thing to put his work into this DAO, so he launched a proposal with this NFT and hoped to get 2000 DOGE in return. + + Charlie likes Doge-related NFTs and holds many DOGE. One day, Charlie saw an NFT that he thought would be helpful for the appreciation of DOGE, so he bought it on Starry and then initiated a proposal in DAO to add the NFT and hoped to get 1500 DOGE to make up for the loss (of course he could have done without the 1500 DOGE). + + Dave was an active participant in the Doge NFTS DAO and when he looked at the proposals he saw Bob and Charlie's proposals and thought they were great proposals, so Dave used a certain DOGE to agree to both proposals. + + Since most people agreed with Bob and Charlie's proposal, the proposed NFTs were added to the NFTs managed by the DAO and the corresponding DOGEs were minted for Bob and Charlie. + From ff064dc9c6d4601e33e52f6f2df4349f5c6618cb Mon Sep 17 00:00:00 2001 From: Fuling Date: Thu, 11 Feb 2021 18:48:29 +0800 Subject: [PATCH 12/12] reduce from 12000 DAI to 10000 DAI --- applications/Starry_Network.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/applications/Starry_Network.md b/applications/Starry_Network.md index bf4e28c530b..e44ac7b822b 100644 --- a/applications/Starry_Network.md +++ b/applications/Starry_Network.md @@ -71,7 +71,7 @@ Interaction with users. Here is a [demo](https://friendly-mclean-d455eb.netlify ### Overview * **Total Estimated Duration:** 2.5 months * **Full-time equivalent (FTE):** 1 -* **Total Costs:** 12000 DAI +* **Total Costs:** 10000 DAI ### Milestone 1 Example — Implement Substrate Modules * **Estimated Duration:** 2.5 months