From e4ab2f00de6059faeb07148e8a9e6e4e002b046d Mon Sep 17 00:00:00 2001 From: Oleksandra Burmenska Date: Mon, 1 May 2023 19:43:53 +0200 Subject: [PATCH 01/34] DAOsign application MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Create a DAOsign application file  --- applications/DAOsign | 172 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 172 insertions(+) create mode 100644 applications/DAOsign diff --git a/applications/DAOsign b/applications/DAOsign new file mode 100644 index 00000000000..57087dad840 --- /dev/null +++ b/applications/DAOsign @@ -0,0 +1,172 @@ +# Name of your Project + +> This document will be part of the terms and conditions of your agreement and therefore needs to contain all the required information about the project. Don't remove any of the mandatory parts presented in bold letters or as headlines (except for the title)! Lines starting with a `>` (such as this one) should be removed. Please use markdown instead of HTML (e.g. `![](image.png)` instead of ``). +> +> See the [Grants Program Process](https://github.com/w3f/Grants-Program/#pencil-process) on how to submit a proposal. +- **Team Name:** Legal name of your team (e.g. Duo) +- **Payment Address:** In the case of fiat payment, please share your bank account privately with grants@web3.foundation via your contact email (see below) and enter the date when you shared the information with us (e.g. Fiat 24.12.1971, 11:59) here. Otherwise, provide the BTC, Ethereum (USDC/DAI) or Polkadot/Kusama (USDT) payment address. Please also specify the currency. (e.g. 0x8920... (DAI)) +- **[Level](https://github.com/w3f/Grants-Program/tree/master#level_slider-levels):** 1, 2 or 3 + +> :exclamation: *The combination of your GitHub account submitting the application and the payment address above will be your unique identifier during the program. Please keep them safe.* +## Project Overview :page_facing_up: + +If this application is in response to an RFP, please indicate this on the first line of this section. + +If this is an application for a follow-up grant (the continuation of an earlier, successful W3F grant), please provide name and/or pull request of said grant on the first line of this section. + +### Overview + +Please provide the following: + +- If the name of your project is not descriptive, a tag line (one sentence summary). +- A brief description of your project. +- An indication of how your project relates to / integrates 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 your project's expected final state. Therefore, we ask the teams to submit (where relevant): + +- Mockups/designs of any UI components +- Data models / 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 +- What your project is _not_ or will _not_ provide or implement + - This is a place for you to manage expectations and to clarify any limitations that might not be obvious + + +Things that shouldn’t be part of the application (see also our [FAQ](../docs/faq.md)): +- The (future) tokenomics of your project +- For non-infrastructure projects—deployment and hosting costs, maintenance or audits +- Business-oriented activities (marketing, business planning), events or outreach + +### Ecosystem Fit + +Help us locate your project in the Polkadot/Substrate/Kusama landscape and what problems it tries to solve by answering each of these questions: + +- Where and how does your project fit into the ecosystem? +- Who is your target audience (parachain/dapp/wallet/UI developers, designers, your own user base, some dapp's userbase, yourself)? +- What need(s) does your project meet? +- Are there any other projects similar to yours in the Substrate / Polkadot / Kusama ecosystem? + - If so, how is your project different? + - If not, are there similar projects in related ecosystems? + +## Team :busts_in_silhouette: + +### Team members + +- Name of team leader +- Names of team members + +### Contact + +- **Contact Name:** Full name of the contact person in your team +- **Contact Email:** Contact email (e.g. john@duo.com) +- **Website:** Your website + +### Legal Structure + +- **Registered Address:** Address of your registered legal entity, if available. Please keep it in a single 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 your project involves development work, we would appreciate it if you singled out a few interesting projects or contributions made by team members in the past. + +If anyone on your team has applied for a grant at the Web3 Foundation previously, please list the name of the project and legal entity here. + +### Team Code Repos + +- https://github.com// +- https://github.com// + +Please also provide the GitHub accounts of all team members. If they contain no activity, references to projects hosted elsewhere or live are also fine. + +- https://github.com/ +- https://github.com/ + +### Team LinkedIn Profiles (if available) + +- https://www.linkedin.com/ +- https://www.linkedin.com/ + + +## Development Status :open_book: + +If you've already started implementing your project or it is part of a larger repository, please provide a link and a description of the code here. In any case, please provide some documentation on the research and other work you have conducted before applying. This could be: + +- links to improvement proposals or [RFPs](https://github.com/w3f/Grants-Program/tree/master/docs/RFPs) (requests for proposal), +- academic publications relevant to the problem, +- links to your research diary, blog posts, articles, forum discussions or open GitHub issues, +- references to conversations you might have had related to this project with anyone from the Web3 Foundation, +- previous interface iterations, such as mock-ups and wireframes. + +## Development Roadmap :nut_and_bolt: + +This section should break the development roadmap down into milestones and deliverables. To assist you in defining it, we have created a document with examples for some grant categories [here](../docs/Support%20Docs/grant_guidelines_per_category.md). Since these will be part of the agreement, it helps to describe _the functionality we should expect in as much detail as possible_, plus how we can verify and test that functionality. Whenever milestones are delivered, we refer to this document to ensure that everything has been delivered as expected. + +Below we provide an **example roadmap**. In the descriptions, it should be clear how your project is related to Substrate, Kusama or Polkadot. We _recommend_ that teams structure their roadmap as 1 milestone ≈ 1 month. + +> :exclamation: If any of your deliverables is based on somebody else's work, make sure you work and publish _under the terms of the license_ of the respective project and that you **highlight this fact in your milestone documentation** and in the source code if applicable! **Teams that submit others' work without attributing it will be immediately terminated.** + +### Overview + +- **Total Estimated Duration:** Duration of the whole project (e.g. 2 months) +- **Full-Time Equivalent (FTE):** Average number of full-time employees working on the project throughout its duration (see [Wikipedia](https://en.wikipedia.org/wiki/Full-time_equivalent), e.g. 2 FTE) +- **Total Costs:** Requested amount in USD for the whole project (e.g. 12,000 USD). Note that the acceptance criteria and additional benefits vary depending on the [level](../README.md#level_slider-levels) of funding requested. This and the costs for each milestone need to be provided in USD; if the grant is paid out in Bitcoin, the amount will be calculated according to the exchange rate at the time of payment. + +### Milestone 1 Example — Basic functionality + +- **Estimated duration:** 1 month +- **FTE:** 1,5 +- **Costs:** 8,000 USD + +> :exclamation: **The default deliverables 0a-0d below are mandatory for all milestones**, and deliverable 0e at least for the last one. + +| Number | Deliverable | Specification | +| -----: | ----------- | ------------- | +| **0a.** | License | Apache 2.0 / GPLv3 / 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 and send test transactions, which will show how the new functionality works. | +| **0c.** | Testing and Testing Guide | Core functions will be fully covered by comprehensive unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. | +| **0d.** | Docker | We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone. | +| 0e. | Article | We will publish an **article**/workshop that explains [...] (what was done/achieved as part of the grant). (Content, language and medium should reflect your target audience described above.) | +| 1. | Substrate module: X | We will create a Substrate module that will... (Please list the functionality that will be implemented for the first milestone. You can refer to details provided in previous sections.) | +| 2. | Substrate module: Y | The Y Substrate module will... | +| 3. | Substrate module: Z | The Z Substrate module 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. | Library: ABC | We will deliver a JS library that will implement the functionality described under "ABC Library" | +| 6. | Smart contracts: ... | We will deliver a set of ink! smart contracts that will... + + +### Milestone 2 Example — Additional features + +- **Estimated Duration:** 1 month +- **FTE:** 1,5 +- **Costs:** 8,000 USD + +... + + +## Future Plans + +Please include here + +- how you intend to use, enhance, promote and support your project in the short term, and +- the team's long-term plans and intentions in relation to it. + +## Referral Program (optional) :moneybag: + +You can find more information about the program [here](../README.md#moneybag-referral-program). +- **Referrer:** Name of the Polkadot Ambassador or GitHub account of the Web3 Foundation grantee +- **Payment Address:** BTC, Ethereum (USDC/DAI) or Polkadot/Kusama (USDT) payment address. Please also specify the currency. (e.g. 0x8920... (DAI)) + +## Additional Information :heavy_plus_sign: + +**How did you hear about the Grants Program?** Web3 Foundation Website / Medium / Twitter / Element / Announcement by another team / personal recommendation / etc. + +Here you can also add any additional information that you think is relevant to this application but isn't part of it already, such as: + +- Work you have already done. +- If there are any other teams who have already contributed (financially) to the project. +- Previous grants you may have applied for. From 0ef446054025c4d186eb34c94e018e87eeefa6fe Mon Sep 17 00:00:00 2001 From: Oleksandra Burmenska Date: Tue, 9 May 2023 15:49:05 +0200 Subject: [PATCH 02/34] Delete DAOsign --- applications/DAOsign | 172 ------------------------------------------- 1 file changed, 172 deletions(-) delete mode 100644 applications/DAOsign diff --git a/applications/DAOsign b/applications/DAOsign deleted file mode 100644 index 57087dad840..00000000000 --- a/applications/DAOsign +++ /dev/null @@ -1,172 +0,0 @@ -# Name of your Project - -> This document will be part of the terms and conditions of your agreement and therefore needs to contain all the required information about the project. Don't remove any of the mandatory parts presented in bold letters or as headlines (except for the title)! Lines starting with a `>` (such as this one) should be removed. Please use markdown instead of HTML (e.g. `![](image.png)` instead of ``). -> -> See the [Grants Program Process](https://github.com/w3f/Grants-Program/#pencil-process) on how to submit a proposal. -- **Team Name:** Legal name of your team (e.g. Duo) -- **Payment Address:** In the case of fiat payment, please share your bank account privately with grants@web3.foundation via your contact email (see below) and enter the date when you shared the information with us (e.g. Fiat 24.12.1971, 11:59) here. Otherwise, provide the BTC, Ethereum (USDC/DAI) or Polkadot/Kusama (USDT) payment address. Please also specify the currency. (e.g. 0x8920... (DAI)) -- **[Level](https://github.com/w3f/Grants-Program/tree/master#level_slider-levels):** 1, 2 or 3 - -> :exclamation: *The combination of your GitHub account submitting the application and the payment address above will be your unique identifier during the program. Please keep them safe.* -## Project Overview :page_facing_up: - -If this application is in response to an RFP, please indicate this on the first line of this section. - -If this is an application for a follow-up grant (the continuation of an earlier, successful W3F grant), please provide name and/or pull request of said grant on the first line of this section. - -### Overview - -Please provide the following: - -- If the name of your project is not descriptive, a tag line (one sentence summary). -- A brief description of your project. -- An indication of how your project relates to / integrates 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 your project's expected final state. Therefore, we ask the teams to submit (where relevant): - -- Mockups/designs of any UI components -- Data models / 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 -- What your project is _not_ or will _not_ provide or implement - - This is a place for you to manage expectations and to clarify any limitations that might not be obvious - - -Things that shouldn’t be part of the application (see also our [FAQ](../docs/faq.md)): -- The (future) tokenomics of your project -- For non-infrastructure projects—deployment and hosting costs, maintenance or audits -- Business-oriented activities (marketing, business planning), events or outreach - -### Ecosystem Fit - -Help us locate your project in the Polkadot/Substrate/Kusama landscape and what problems it tries to solve by answering each of these questions: - -- Where and how does your project fit into the ecosystem? -- Who is your target audience (parachain/dapp/wallet/UI developers, designers, your own user base, some dapp's userbase, yourself)? -- What need(s) does your project meet? -- Are there any other projects similar to yours in the Substrate / Polkadot / Kusama ecosystem? - - If so, how is your project different? - - If not, are there similar projects in related ecosystems? - -## Team :busts_in_silhouette: - -### Team members - -- Name of team leader -- Names of team members - -### Contact - -- **Contact Name:** Full name of the contact person in your team -- **Contact Email:** Contact email (e.g. john@duo.com) -- **Website:** Your website - -### Legal Structure - -- **Registered Address:** Address of your registered legal entity, if available. Please keep it in a single 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 your project involves development work, we would appreciate it if you singled out a few interesting projects or contributions made by team members in the past. - -If anyone on your team has applied for a grant at the Web3 Foundation previously, please list the name of the project and legal entity here. - -### Team Code Repos - -- https://github.com// -- https://github.com// - -Please also provide the GitHub accounts of all team members. If they contain no activity, references to projects hosted elsewhere or live are also fine. - -- https://github.com/ -- https://github.com/ - -### Team LinkedIn Profiles (if available) - -- https://www.linkedin.com/ -- https://www.linkedin.com/ - - -## Development Status :open_book: - -If you've already started implementing your project or it is part of a larger repository, please provide a link and a description of the code here. In any case, please provide some documentation on the research and other work you have conducted before applying. This could be: - -- links to improvement proposals or [RFPs](https://github.com/w3f/Grants-Program/tree/master/docs/RFPs) (requests for proposal), -- academic publications relevant to the problem, -- links to your research diary, blog posts, articles, forum discussions or open GitHub issues, -- references to conversations you might have had related to this project with anyone from the Web3 Foundation, -- previous interface iterations, such as mock-ups and wireframes. - -## Development Roadmap :nut_and_bolt: - -This section should break the development roadmap down into milestones and deliverables. To assist you in defining it, we have created a document with examples for some grant categories [here](../docs/Support%20Docs/grant_guidelines_per_category.md). Since these will be part of the agreement, it helps to describe _the functionality we should expect in as much detail as possible_, plus how we can verify and test that functionality. Whenever milestones are delivered, we refer to this document to ensure that everything has been delivered as expected. - -Below we provide an **example roadmap**. In the descriptions, it should be clear how your project is related to Substrate, Kusama or Polkadot. We _recommend_ that teams structure their roadmap as 1 milestone ≈ 1 month. - -> :exclamation: If any of your deliverables is based on somebody else's work, make sure you work and publish _under the terms of the license_ of the respective project and that you **highlight this fact in your milestone documentation** and in the source code if applicable! **Teams that submit others' work without attributing it will be immediately terminated.** - -### Overview - -- **Total Estimated Duration:** Duration of the whole project (e.g. 2 months) -- **Full-Time Equivalent (FTE):** Average number of full-time employees working on the project throughout its duration (see [Wikipedia](https://en.wikipedia.org/wiki/Full-time_equivalent), e.g. 2 FTE) -- **Total Costs:** Requested amount in USD for the whole project (e.g. 12,000 USD). Note that the acceptance criteria and additional benefits vary depending on the [level](../README.md#level_slider-levels) of funding requested. This and the costs for each milestone need to be provided in USD; if the grant is paid out in Bitcoin, the amount will be calculated according to the exchange rate at the time of payment. - -### Milestone 1 Example — Basic functionality - -- **Estimated duration:** 1 month -- **FTE:** 1,5 -- **Costs:** 8,000 USD - -> :exclamation: **The default deliverables 0a-0d below are mandatory for all milestones**, and deliverable 0e at least for the last one. - -| Number | Deliverable | Specification | -| -----: | ----------- | ------------- | -| **0a.** | License | Apache 2.0 / GPLv3 / 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 and send test transactions, which will show how the new functionality works. | -| **0c.** | Testing and Testing Guide | Core functions will be fully covered by comprehensive unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. | -| **0d.** | Docker | We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone. | -| 0e. | Article | We will publish an **article**/workshop that explains [...] (what was done/achieved as part of the grant). (Content, language and medium should reflect your target audience described above.) | -| 1. | Substrate module: X | We will create a Substrate module that will... (Please list the functionality that will be implemented for the first milestone. You can refer to details provided in previous sections.) | -| 2. | Substrate module: Y | The Y Substrate module will... | -| 3. | Substrate module: Z | The Z Substrate module 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. | Library: ABC | We will deliver a JS library that will implement the functionality described under "ABC Library" | -| 6. | Smart contracts: ... | We will deliver a set of ink! smart contracts that will... - - -### Milestone 2 Example — Additional features - -- **Estimated Duration:** 1 month -- **FTE:** 1,5 -- **Costs:** 8,000 USD - -... - - -## Future Plans - -Please include here - -- how you intend to use, enhance, promote and support your project in the short term, and -- the team's long-term plans and intentions in relation to it. - -## Referral Program (optional) :moneybag: - -You can find more information about the program [here](../README.md#moneybag-referral-program). -- **Referrer:** Name of the Polkadot Ambassador or GitHub account of the Web3 Foundation grantee -- **Payment Address:** BTC, Ethereum (USDC/DAI) or Polkadot/Kusama (USDT) payment address. Please also specify the currency. (e.g. 0x8920... (DAI)) - -## Additional Information :heavy_plus_sign: - -**How did you hear about the Grants Program?** Web3 Foundation Website / Medium / Twitter / Element / Announcement by another team / personal recommendation / etc. - -Here you can also add any additional information that you think is relevant to this application but isn't part of it already, such as: - -- Work you have already done. -- If there are any other teams who have already contributed (financially) to the project. -- Previous grants you may have applied for. From 6a41dbdfb92e51d54f27a70f253dbf18c43589dc Mon Sep 17 00:00:00 2001 From: Oleksandra Burmenska Date: Tue, 9 May 2023 16:34:19 +0200 Subject: [PATCH 03/34] Create DAOsign.md Project description update --- applications/DAOsign.md | 167 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 167 insertions(+) create mode 100644 applications/DAOsign.md diff --git a/applications/DAOsign.md b/applications/DAOsign.md new file mode 100644 index 00000000000..dd57f9392a6 --- /dev/null +++ b/applications/DAOsign.md @@ -0,0 +1,167 @@ +# DAOsign + + +> See the [Grants Program Process](https://github.com/w3f/Grants-Program/#pencil-process) on how to submit a proposal. +- **Team Name:** DAOsign +- **Payment Address:** cidt.eth +- **[Level](https://github.com/w3f/Grants-Program/tree/master#level_slider-levels):** 2 + +> :exclamation: *The combination of your GitHub account submitting the application and the payment address above will be your unique identifier during the program. Please keep them safe.* +## Project Overview :page_facing_up: + + +### Overview + +DAOsign is a decentralized platform for agreements and policies with publicly verifiable and authorized cryptographic proofs and Governance Automation, designed for DAOs. +Traditional methods of signing agreements, such as paper-based systems or legacy e-signatures, are prone to fraud and lack transparency, and offer no solution for verification of the signer's identity or signer’s authority to execute the agreement. Instead these systems rely on costly legal proceedings for enforce agreements. + +DAOsign provides publicly verifiable cryptographic proofs; secure, transparent and automated processing of complex Agreements and Policies. + +Furthermore, DAOsign provides robust Governance and Policy Builder platform to provide governance, workflow automation and controls for organization policies and procedures. +### Project Details + +We expect the teams to already have a solid idea about your project's expected final state. Therefore, we ask the teams to submit (where relevant): + +- Mockups/designs of any UI components +- Data models / 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 +- What your project is _not_ or will _not_ provide or implement + - This is a place for you to manage expectations and to clarify any limitations that might not be obvious + + +Things that shouldn’t be part of the application (see also our [FAQ](../docs/faq.md)): +- The (future) tokenomics of your project +- For non-infrastructure projects—deployment and hosting costs, maintenance or audits +- Business-oriented activities (marketing, business planning), events or outreach + +### Ecosystem Fit + +Help us locate your project in the Polkadot/Substrate/Kusama landscape and what problems it tries to solve by answering each of these questions: + +- Where and how does your project fit into the ecosystem? +- Who is your target audience (parachain/dapp/wallet/UI developers, designers, your own user base, some dapp's userbase, yourself)? +- What need(s) does your project meet? +- Are there any other projects similar to yours in the Substrate / Polkadot / Kusama ecosystem? + - If so, how is your project different? + - If not, are there similar projects in related ecosystems? + +## Team :busts_in_silhouette: + +### Team members + +- Name of team leader +- Names of team members + +### Contact + +- **Contact Name:** Full name of the contact person in your team +- **Contact Email:** Contact email (e.g. john@duo.com) +- **Website:** Your website + +### Legal Structure + +- **Registered Address:** Address of your registered legal entity, if available. Please keep it in a single 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 your project involves development work, we would appreciate it if you singled out a few interesting projects or contributions made by team members in the past. + +If anyone on your team has applied for a grant at the Web3 Foundation previously, please list the name of the project and legal entity here. + +### Team Code Repos + +- https://github.com// +- https://github.com// + +Please also provide the GitHub accounts of all team members. If they contain no activity, references to projects hosted elsewhere or live are also fine. + +- https://github.com/ +- https://github.com/ + +### Team LinkedIn Profiles (if available) + +- https://www.linkedin.com/ +- https://www.linkedin.com/ + + +## Development Status :open_book: + +If you've already started implementing your project or it is part of a larger repository, please provide a link and a description of the code here. In any case, please provide some documentation on the research and other work you have conducted before applying. This could be: + +- links to improvement proposals or [RFPs](https://github.com/w3f/Grants-Program/tree/master/docs/RFPs) (requests for proposal), +- academic publications relevant to the problem, +- links to your research diary, blog posts, articles, forum discussions or open GitHub issues, +- references to conversations you might have had related to this project with anyone from the Web3 Foundation, +- previous interface iterations, such as mock-ups and wireframes. + +## Development Roadmap :nut_and_bolt: + +This section should break the development roadmap down into milestones and deliverables. To assist you in defining it, we have created a document with examples for some grant categories [here](../docs/Support%20Docs/grant_guidelines_per_category.md). Since these will be part of the agreement, it helps to describe _the functionality we should expect in as much detail as possible_, plus how we can verify and test that functionality. Whenever milestones are delivered, we refer to this document to ensure that everything has been delivered as expected. + +Below we provide an **example roadmap**. In the descriptions, it should be clear how your project is related to Substrate, Kusama or Polkadot. We _recommend_ that teams structure their roadmap as 1 milestone ≈ 1 month. + +> :exclamation: If any of your deliverables is based on somebody else's work, make sure you work and publish _under the terms of the license_ of the respective project and that you **highlight this fact in your milestone documentation** and in the source code if applicable! **Teams that submit others' work without attributing it will be immediately terminated.** + +### Overview + +- **Total Estimated Duration:** Duration of the whole project (e.g. 2 months) +- **Full-Time Equivalent (FTE):** Average number of full-time employees working on the project throughout its duration (see [Wikipedia](https://en.wikipedia.org/wiki/Full-time_equivalent), e.g. 2 FTE) +- **Total Costs:** Requested amount in USD for the whole project (e.g. 12,000 USD). Note that the acceptance criteria and additional benefits vary depending on the [level](../README.md#level_slider-levels) of funding requested. This and the costs for each milestone need to be provided in USD; if the grant is paid out in Bitcoin, the amount will be calculated according to the exchange rate at the time of payment. + +### Milestone 1 Example — Basic functionality + +- **Estimated duration:** 1 month +- **FTE:** 1,5 +- **Costs:** 8,000 USD + +> :exclamation: **The default deliverables 0a-0d below are mandatory for all milestones**, and deliverable 0e at least for the last one. + +| Number | Deliverable | Specification | +| -----: | ----------- | ------------- | +| **0a.** | License | Apache 2.0 / GPLv3 / 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 and send test transactions, which will show how the new functionality works. | +| **0c.** | Testing and Testing Guide | Core functions will be fully covered by comprehensive unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. | +| **0d.** | Docker | We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone. | +| 0e. | Article | We will publish an **article**/workshop that explains [...] (what was done/achieved as part of the grant). (Content, language and medium should reflect your target audience described above.) | +| 1. | Substrate module: X | We will create a Substrate module that will... (Please list the functionality that will be implemented for the first milestone. You can refer to details provided in previous sections.) | +| 2. | Substrate module: Y | The Y Substrate module will... | +| 3. | Substrate module: Z | The Z Substrate module 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. | Library: ABC | We will deliver a JS library that will implement the functionality described under "ABC Library" | +| 6. | Smart contracts: ... | We will deliver a set of ink! smart contracts that will... + + +### Milestone 2 Example — Additional features + +- **Estimated Duration:** 1 month +- **FTE:** 1,5 +- **Costs:** 8,000 USD + +... + + +## Future Plans + +Please include here + +- how you intend to use, enhance, promote and support your project in the short term, and +- the team's long-term plans and intentions in relation to it. + +## Referral Program (optional) :moneybag: + +You can find more information about the program [here](../README.md#moneybag-referral-program). +- **Referrer:** Name of the Polkadot Ambassador or GitHub account of the Web3 Foundation grantee +- **Payment Address:** BTC, Ethereum (USDC/DAI) or Polkadot/Kusama (USDT) payment address. Please also specify the currency. (e.g. 0x8920... (DAI)) + +## Additional Information :heavy_plus_sign: + +**How did you hear about the Grants Program?** Web3 Foundation Website / Medium / Twitter / Element / Announcement by another team / personal recommendation / etc. + +Here you can also add any additional information that you think is relevant to this application but isn't part of it already, such as: + +- Work you have already done. +- If there are any other teams who have already contributed (financially) to the project. +- Previous grants you may have applied for. From 9f311da98821afcf168f4a8d0c129ee849b92063 Mon Sep 17 00:00:00 2001 From: Oleksandra Burmenska Date: Tue, 9 May 2023 17:50:15 +0200 Subject: [PATCH 04/34] Update DAOsign.md Adding an information about project purpose --- applications/DAOsign.md | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/applications/DAOsign.md b/applications/DAOsign.md index dd57f9392a6..1a75b9aa4ab 100644 --- a/applications/DAOsign.md +++ b/applications/DAOsign.md @@ -38,32 +38,32 @@ Things that shouldn’t be part of the application (see also our [FAQ](../docs/f ### Ecosystem Fit -Help us locate your project in the Polkadot/Substrate/Kusama landscape and what problems it tries to solve by answering each of these questions: +DAOsign fit the Governance category and since, Polkadot and Kusama are designed to be community-driven networks that allow for decentralized governance. DAOsign can fit into this ecosystem by providing a platform for DAOs to manage their decision-making processes in a decentralized manner. +Our target audience is not only DAOs, but also all the companies, who have a need to deal with the agreement/policies management including the use case for managing Grants, that was presented to you during our introdution call. +Competitors analysis can be found here: https://docsend.com/view/sbexkxn5su3ahdg8 . Particularly in Substrate / Polkadot / Kusama ecosystems we are not aware about any tools, that provide exactly the same functionality. -- Where and how does your project fit into the ecosystem? -- Who is your target audience (parachain/dapp/wallet/UI developers, designers, your own user base, some dapp's userbase, yourself)? -- What need(s) does your project meet? -- Are there any other projects similar to yours in the Substrate / Polkadot / Kusama ecosystem? - - If so, how is your project different? - - If not, are there similar projects in related ecosystems? ## Team :busts_in_silhouette: ### Team members -- Name of team leader -- Names of team members +- Team Leader, Founder: Eugene Fine https://github.com/ConsiderItDone, +- Solution Architect: Ramil Amerzyanov https://github.com/ramilexe +- Blockchain / Tech lead: Misha Kushka https://github.com/kushkamisha +- Director of Buisiness development and Partnerships: Oleksandra Burmenska github.com/burmenska + + ### Contact -- **Contact Name:** Full name of the contact person in your team -- **Contact Email:** Contact email (e.g. john@duo.com) -- **Website:** Your website +- **Contact Name:** Eugene Fine +- **Contact Email:** eugene@daosign.org +- **Website:** daosign.org ### Legal Structure -- **Registered Address:** Address of your registered legal entity, if available. Please keep it in a single 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.) +- **Registered Address:** ILLINOIS LIMITED LIABILITY CORPORATION, US +- **Registered Legal Entity:** DAOSIGN, LLC ### Team's experience From 9780b4064631bce6d2cf0724b88945f52d236bfc Mon Sep 17 00:00:00 2001 From: Oleksandra Burmenska Date: Wed, 10 May 2023 14:14:40 +0200 Subject: [PATCH 05/34] Update DAOsign.md Add info about team members --- applications/DAOsign.md | 49 ++++++++++++++++++++++++++++++++--------- 1 file changed, 38 insertions(+), 11 deletions(-) diff --git a/applications/DAOsign.md b/applications/DAOsign.md index 1a75b9aa4ab..90b67c579be 100644 --- a/applications/DAOsign.md +++ b/applications/DAOsign.md @@ -66,25 +66,52 @@ Competitors analysis can be found here: https://docsend.com/view/sbexkxn5su3ahdg - **Registered Legal Entity:** DAOSIGN, LLC ### Team's experience - -Please describe the team's relevant experience. If your project involves development work, we would appreciate it if you singled out a few interesting projects or contributions made by team members in the past. - -If anyone on your team has applied for a grant at the Web3 Foundation previously, please list the name of the project and legal entity here. +**Eugene Fine:** CEO, Founder +Background: +Over 20 years of building, scaling, and managing technology organizations. Past experience: +- CTO for https://www.explorersurgical.com +- tech leadership contribution to https://bird.coach +- tech advisor and facilitator for polywrap.io +to name a few. +Also, Eugene is a founder at consideritdone.tech and daosign.org + +**Ramil Amerzyanov:** Solution Architect, CTO +Background: +12+ years in building complex enterprize solutions (all SDLC aspects), including 7+ years in Blockchain industry. +Past projects include: +- contribution to Ethereum standards development +- tech leadership for https://docsend.com/view/fjrvjtyzgm7wgrkj projects + +**Oleksandra Burmenska:** Director of Business Development and Partnerships +Background: +Engineering, MBA, and Psychology diplomas. Over a decade of experience in IT: development and managerial positions, last five years focused on the Blockchain industry. +Experience with enterprises and startup companies, scaling teams, and building blockchain products. +Previous blockchain projects include: +- successfully managed ICOs during 2017-2019 (example: Õpet – Medium ) +- contribution to Polywrap, NEAR, Axelar, GnosisSafe, Avalanche ecosystems +- contribution to nodle.com ecosystem: managing the block explorer development (before it moved to Subscan), leading the Landslide - Avalanche subnet development,etc. + +**Misha Kushka**: Tech Lead and Blockchain Developer +Background: 6+ years of professional experience as a developer, 4+ years of professional experience in the Blockchain field, 4+ years experience as a lead ### Team Code Repos -- https://github.com// -- https://github.com// +- https://github.com/ConsiderItDone +- https://github.com/DAOsign Please also provide the GitHub accounts of all team members. If they contain no activity, references to projects hosted elsewhere or live are also fine. -- https://github.com/ -- https://github.com/ +- [Eugene Fine](https://github.com/ConsiderItDone) +- [Ramil Amerzyanov](https://github.com/ramilexe) +- [Oleksandra Burmenska](https://github.com/Burmenska) +- [Misha Kushka](https://github.com/kushkamisha) ### Team LinkedIn Profiles (if available) -- https://www.linkedin.com/ -- https://www.linkedin.com/ +- [Eugene Fine](https://www.linkedin.com/in/eugenefine/) +- [Ramil Amerzyanov](https://www.linkedin.com/in/ramil-amerzyanov/) +- [Oleksandra Burmenska](https://www.linkedin.com/in/oleksandra-burmenska/) +- [Misha Kushka](https://www.linkedin.com/in/mkushka/) ## Development Status :open_book: @@ -94,7 +121,7 @@ If you've already started implementing your project or it is part of a larger re - links to improvement proposals or [RFPs](https://github.com/w3f/Grants-Program/tree/master/docs/RFPs) (requests for proposal), - academic publications relevant to the problem, - links to your research diary, blog posts, articles, forum discussions or open GitHub issues, -- references to conversations you might have had related to this project with anyone from the Web3 Foundation, +- references to conversations you might have had related to t his project with anyone from the Web3 Foundation, - previous interface iterations, such as mock-ups and wireframes. ## Development Roadmap :nut_and_bolt: From 2460677de044784046156948027ef5d27c3be4c3 Mon Sep 17 00:00:00 2001 From: Oleksandra Burmenska Date: Wed, 10 May 2023 14:59:33 +0200 Subject: [PATCH 06/34] Update DAOsign.md Adding milestone details --- applications/DAOsign.md | 54 ++++++++++++----------------------------- 1 file changed, 15 insertions(+), 39 deletions(-) diff --git a/applications/DAOsign.md b/applications/DAOsign.md index 90b67c579be..e9e4dcb5d8b 100644 --- a/applications/DAOsign.md +++ b/applications/DAOsign.md @@ -50,7 +50,7 @@ Competitors analysis can be found here: https://docsend.com/view/sbexkxn5su3ahdg - Team Leader, Founder: Eugene Fine https://github.com/ConsiderItDone, - Solution Architect: Ramil Amerzyanov https://github.com/ramilexe - Blockchain / Tech lead: Misha Kushka https://github.com/kushkamisha -- Director of Buisiness development and Partnerships: Oleksandra Burmenska github.com/burmenska +- Director of Buisiness development and Partnerships: Oleksandra Burmenska https://github.com/burmenska @@ -116,60 +116,36 @@ Please also provide the GitHub accounts of all team members. If they contain no ## Development Status :open_book: -If you've already started implementing your project or it is part of a larger repository, please provide a link and a description of the code here. In any case, please provide some documentation on the research and other work you have conducted before applying. This could be: - -- links to improvement proposals or [RFPs](https://github.com/w3f/Grants-Program/tree/master/docs/RFPs) (requests for proposal), -- academic publications relevant to the problem, -- links to your research diary, blog posts, articles, forum discussions or open GitHub issues, -- references to conversations you might have had related to t his project with anyone from the Web3 Foundation, -- previous interface iterations, such as mock-ups and wireframes. +We are currently working on a tech demo (kind of a pre-beta version) and non-blockchain version of DAOsign is available here: https://testnet.daosign.org ## Development Roadmap :nut_and_bolt: -This section should break the development roadmap down into milestones and deliverables. To assist you in defining it, we have created a document with examples for some grant categories [here](../docs/Support%20Docs/grant_guidelines_per_category.md). Since these will be part of the agreement, it helps to describe _the functionality we should expect in as much detail as possible_, plus how we can verify and test that functionality. Whenever milestones are delivered, we refer to this document to ensure that everything has been delivered as expected. - -Below we provide an **example roadmap**. In the descriptions, it should be clear how your project is related to Substrate, Kusama or Polkadot. We _recommend_ that teams structure their roadmap as 1 milestone ≈ 1 month. - -> :exclamation: If any of your deliverables is based on somebody else's work, make sure you work and publish _under the terms of the license_ of the respective project and that you **highlight this fact in your milestone documentation** and in the source code if applicable! **Teams that submit others' work without attributing it will be immediately terminated.** - -### Overview - -- **Total Estimated Duration:** Duration of the whole project (e.g. 2 months) -- **Full-Time Equivalent (FTE):** Average number of full-time employees working on the project throughout its duration (see [Wikipedia](https://en.wikipedia.org/wiki/Full-time_equivalent), e.g. 2 FTE) -- **Total Costs:** Requested amount in USD for the whole project (e.g. 12,000 USD). Note that the acceptance criteria and additional benefits vary depending on the [level](../README.md#level_slider-levels) of funding requested. This and the costs for each milestone need to be provided in USD; if the grant is paid out in Bitcoin, the amount will be calculated according to the exchange rate at the time of payment. +**Overview** -### Milestone 1 Example — Basic functionality +Total Estimated Duration: 2 months +Full-Time Equivalent (FTE): 2 FTE +Total Costs: 30,000 EUR -- **Estimated duration:** 1 month -- **FTE:** 1,5 -- **Costs:** 8,000 USD - -> :exclamation: **The default deliverables 0a-0d below are mandatory for all milestones**, and deliverable 0e at least for the last one. +Milestone 1 - TestNet MVP +Total Costs: 20,000 EUR +Milestone 2 - MainNet MVP +Total Costs: 10,000 EUR | Number | Deliverable | Specification | | -----: | ----------- | ------------- | -| **0a.** | License | Apache 2.0 / GPLv3 / 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 and send test transactions, which will show how the new functionality works. | +| **0a.** | License | TBD | +| **0b.** | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how a user can upload/generate the agreement, add signers/observers and complete the signature process with storing signature proofs either in test or mainnet, which will show how the new functionality works. | | **0c.** | Testing and Testing Guide | Core functions will be fully covered by comprehensive unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. | | **0d.** | Docker | We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone. | -| 0e. | Article | We will publish an **article**/workshop that explains [...] (what was done/achieved as part of the grant). (Content, language and medium should reflect your target audience described above.) | -| 1. | Substrate module: X | We will create a Substrate module that will... (Please list the functionality that will be implemented for the first milestone. You can refer to details provided in previous sections.) | -| 2. | Substrate module: Y | The Y Substrate module will... | +| 0e. | Article | We will publish an **article** that explains how does DAOsign users can create agreements and store them in Polkadot test- or mainnet. It will be published in our Medium, Linkedin, Twitter and Discord channels. Apart of that, we will regularly publish grant development status on our social media. +| 1. | Polkadot integration: testnet | We will create a testnet integration with Polkadot | +| 2. | Polkadot integration: mainnet | We will create a mainnet integration with Polkadot | | 3. | Substrate module: Z | The Z Substrate module 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. | Library: ABC | We will deliver a JS library that will implement the functionality described under "ABC Library" | | 6. | Smart contracts: ... | We will deliver a set of ink! smart contracts that will... -### Milestone 2 Example — Additional features - -- **Estimated Duration:** 1 month -- **FTE:** 1,5 -- **Costs:** 8,000 USD - -... - - ## Future Plans Please include here From f86961db883ff6e054ceb77a4313ad405611d1c9 Mon Sep 17 00:00:00 2001 From: Oleksandra Burmenska Date: Sat, 27 May 2023 16:27:50 +0200 Subject: [PATCH 07/34] Update DAOsign.md Polkadot address update --- applications/DAOsign.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/applications/DAOsign.md b/applications/DAOsign.md index e9e4dcb5d8b..b928ee2b914 100644 --- a/applications/DAOsign.md +++ b/applications/DAOsign.md @@ -3,7 +3,7 @@ > See the [Grants Program Process](https://github.com/w3f/Grants-Program/#pencil-process) on how to submit a proposal. - **Team Name:** DAOsign -- **Payment Address:** cidt.eth +- **Payment Address:** 13s3c37rwrZfa8WQcZPdqE1zi1hGAguf2TWfWMr8f5aLBrg - **[Level](https://github.com/w3f/Grants-Program/tree/master#level_slider-levels):** 2 > :exclamation: *The combination of your GitHub account submitting the application and the payment address above will be your unique identifier during the program. Please keep them safe.* From cb965f47b828a4642c54c92ed4a6cc37330fb378 Mon Sep 17 00:00:00 2001 From: Oleksandra Burmenska Date: Sat, 27 May 2023 16:28:15 +0200 Subject: [PATCH 08/34] Update DAOsign.md --- applications/DAOsign.md | 1 - 1 file changed, 1 deletion(-) diff --git a/applications/DAOsign.md b/applications/DAOsign.md index b928ee2b914..35c1e5e9779 100644 --- a/applications/DAOsign.md +++ b/applications/DAOsign.md @@ -6,7 +6,6 @@ - **Payment Address:** 13s3c37rwrZfa8WQcZPdqE1zi1hGAguf2TWfWMr8f5aLBrg - **[Level](https://github.com/w3f/Grants-Program/tree/master#level_slider-levels):** 2 -> :exclamation: *The combination of your GitHub account submitting the application and the payment address above will be your unique identifier during the program. Please keep them safe.* ## Project Overview :page_facing_up: From 082bd5388e87678b5d82ac1da5da0c0019b32e42 Mon Sep 17 00:00:00 2001 From: Oleksandra Burmenska Date: Sat, 27 May 2023 16:29:01 +0200 Subject: [PATCH 09/34] Update DAOsign.md --- applications/DAOsign.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/applications/DAOsign.md b/applications/DAOsign.md index 35c1e5e9779..2d64029ff55 100644 --- a/applications/DAOsign.md +++ b/applications/DAOsign.md @@ -139,10 +139,7 @@ Total Costs: 10,000 EUR | 0e. | Article | We will publish an **article** that explains how does DAOsign users can create agreements and store them in Polkadot test- or mainnet. It will be published in our Medium, Linkedin, Twitter and Discord channels. Apart of that, we will regularly publish grant development status on our social media. | 1. | Polkadot integration: testnet | We will create a testnet integration with Polkadot | | 2. | Polkadot integration: mainnet | We will create a mainnet integration with Polkadot | -| 3. | Substrate module: Z | The Z Substrate module 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. | Library: ABC | We will deliver a JS library that will implement the functionality described under "ABC Library" | -| 6. | Smart contracts: ... | We will deliver a set of ink! smart contracts that will... + ## Future Plans From ec31d4fb4c361223000b3ccb7d0e5ec3ac2913ba Mon Sep 17 00:00:00 2001 From: Oleksandra Burmenska Date: Sat, 27 May 2023 16:57:03 +0200 Subject: [PATCH 10/34] Update DAOsign.md --- applications/DAOsign.md | 19 ++++++------------- 1 file changed, 6 insertions(+), 13 deletions(-) diff --git a/applications/DAOsign.md b/applications/DAOsign.md index 2d64029ff55..6db55f93c2e 100644 --- a/applications/DAOsign.md +++ b/applications/DAOsign.md @@ -18,23 +18,16 @@ DAOsign provides publicly verifiable cryptographic proofs; secure, transparent a Furthermore, DAOsign provides robust Governance and Policy Builder platform to provide governance, workflow automation and controls for organization policies and procedures. ### Project Details +A project goal is to implement signature proofs storing in Polkadot blockchain. +Deliveries include DAOsign platform with an ability to: +- create, edit and generate agreements/policies using ChatGPT 3.5 +- add and remove signators of different levels of anonymity +- allow signing the documents with further storing of signature proofs in Polkadot blockchain. +Core components: -We expect the teams to already have a solid idea about your project's expected final state. Therefore, we ask the teams to submit (where relevant): -- Mockups/designs of any UI components -- Data models / 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 -- What your project is _not_ or will _not_ provide or implement - - This is a place for you to manage expectations and to clarify any limitations that might not be obvious -Things that shouldn’t be part of the application (see also our [FAQ](../docs/faq.md)): -- The (future) tokenomics of your project -- For non-infrastructure projects—deployment and hosting costs, maintenance or audits -- Business-oriented activities (marketing, business planning), events or outreach - ### Ecosystem Fit DAOsign fit the Governance category and since, Polkadot and Kusama are designed to be community-driven networks that allow for decentralized governance. DAOsign can fit into this ecosystem by providing a platform for DAOs to manage their decision-making processes in a decentralized manner. From 6982b32e2d0362941118db59b6d389f1bd3e37a3 Mon Sep 17 00:00:00 2001 From: Oleksandra Burmenska Date: Sat, 27 May 2023 17:10:47 +0200 Subject: [PATCH 11/34] Update DAOsign.md Project description details --- applications/DAOsign.md | 16 ++++++---------- 1 file changed, 6 insertions(+), 10 deletions(-) diff --git a/applications/DAOsign.md b/applications/DAOsign.md index 6db55f93c2e..bff20d513b0 100644 --- a/applications/DAOsign.md +++ b/applications/DAOsign.md @@ -24,7 +24,7 @@ Deliveries include DAOsign platform with an ability to: - add and remove signators of different levels of anonymity - allow signing the documents with further storing of signature proofs in Polkadot blockchain. Core components: - +Screenshot 2023-05-27 at 16 51 43 @@ -137,14 +137,14 @@ Total Costs: 10,000 EUR ## Future Plans -Please include here +Our team plans to contribute to the Polkadot ecosystem through: -- how you intend to use, enhance, promote and support your project in the short term, and -- the team's long-term plans and intentions in relation to it. +Announcing Early Adopters Program and working closely with DAOs to help them integrate DAOsign. +Enhance our tutorials and supplementary materials to better support users and developers. ## Referral Program (optional) :moneybag: -You can find more information about the program [here](../README.md#moneybag-referral-program). + - **Referrer:** Name of the Polkadot Ambassador or GitHub account of the Web3 Foundation grantee - **Payment Address:** BTC, Ethereum (USDC/DAI) or Polkadot/Kusama (USDT) payment address. Please also specify the currency. (e.g. 0x8920... (DAI)) @@ -152,8 +152,4 @@ You can find more information about the program [here](../README.md#moneybag-ref **How did you hear about the Grants Program?** Web3 Foundation Website / Medium / Twitter / Element / Announcement by another team / personal recommendation / etc. -Here you can also add any additional information that you think is relevant to this application but isn't part of it already, such as: - -- Work you have already done. -- If there are any other teams who have already contributed (financially) to the project. -- Previous grants you may have applied for. +By recommendation of Richard Casey from Parity. From 01640f346fe3e4edf3f2875be03acf26520d821d Mon Sep 17 00:00:00 2001 From: Oleksandra Burmenska Date: Sun, 28 May 2023 23:37:02 +0200 Subject: [PATCH 12/34] Update DAOsign.md Update the roadmap --- applications/DAOsign.md | 43 ++++++++++++++++++++++++++++------------- 1 file changed, 30 insertions(+), 13 deletions(-) diff --git a/applications/DAOsign.md b/applications/DAOsign.md index bff20d513b0..5fc70eca4ec 100644 --- a/applications/DAOsign.md +++ b/applications/DAOsign.md @@ -18,15 +18,20 @@ DAOsign provides publicly verifiable cryptographic proofs; secure, transparent a Furthermore, DAOsign provides robust Governance and Policy Builder platform to provide governance, workflow automation and controls for organization policies and procedures. ### Project Details -A project goal is to implement signature proofs storing in Polkadot blockchain. +A project goal is to store Agreements Proofs on Polkadot chain using Ink! smart contracts. +Proofs are implemented in EIP-712 standard and signed using user’s EVM private key. We are supporting this standard in Ink! smart contract to be able to verify signature. +Also, we are implementing EIP-2771 standard to allow Agreement Signers gas-free delegation to publish proof on-chain. + Deliveries include DAOsign platform with an ability to: - create, edit and generate agreements/policies using ChatGPT 3.5 -- add and remove signators of different levels of anonymity -- allow signing the documents with further storing of signature proofs in Polkadot blockchain. -Core components: +- add and remove signers/observers of different levels of anonymity +- allow signing the documents with further storing of signature proofs on Polkadot blockchain. +Core DAOsign components: Screenshot 2023-05-27 at 16 51 43 +Technical design: +Screenshot 2023-05-28 at 23 30 53 ### Ecosystem Fit @@ -115,13 +120,11 @@ We are currently working on a tech demo (kind of a pre-beta version) and non-blo **Overview** Total Estimated Duration: 2 months -Full-Time Equivalent (FTE): 2 FTE -Total Costs: 30,000 EUR +Full-Time Equivalent (FTE): 4 FTE +Total Costs: 48,100 EUR -Milestone 1 - TestNet MVP -Total Costs: 20,000 EUR -Milestone 2 - MainNet MVP -Total Costs: 10,000 EUR +Milestone 1 - Smartcontracts +Total Costs: 40,300 EUR | Number | Deliverable | Specification | | -----: | ----------- | ------------- | @@ -130,8 +133,21 @@ Total Costs: 10,000 EUR | **0c.** | Testing and Testing Guide | Core functions will be fully covered by comprehensive unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. | | **0d.** | Docker | We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone. | | 0e. | Article | We will publish an **article** that explains how does DAOsign users can create agreements and store them in Polkadot test- or mainnet. It will be published in our Medium, Linkedin, Twitter and Discord channels. Apart of that, we will regularly publish grant development status on our social media. -| 1. | Polkadot integration: testnet | We will create a testnet integration with Polkadot | -| 2. | Polkadot integration: mainnet | We will create a mainnet integration with Polkadot | +| 1. | Smart Contracts | Agreement Contract | +| 2. | Smart Contracts | EIP712 standard implementation on Ink! | +| 3. | Smart Contracts | EIP2771 standard implementation on Ink! | +| 4. | Smart Contracts | Delegate call using EIP2771 | + + + +Milestone 2 - Application integration +Total Costs: 7,800 EUR + +| Number | Deliverable | Specification | +| -----: | ----------- | ------------- | +| **0a.** | License | TBD | +| 1. | Application Integration| Application Private Key Management | +| 2. | Application Integration | DAOsign app integration | @@ -141,6 +157,7 @@ Our team plans to contribute to the Polkadot ecosystem through: Announcing Early Adopters Program and working closely with DAOs to help them integrate DAOsign. Enhance our tutorials and supplementary materials to better support users and developers. +Expanding DAOsign functionality according to the roadmap. ## Referral Program (optional) :moneybag: @@ -150,6 +167,6 @@ Enhance our tutorials and supplementary materials to better support users and de ## Additional Information :heavy_plus_sign: -**How did you hear about the Grants Program?** Web3 Foundation Website / Medium / Twitter / Element / Announcement by another team / personal recommendation / etc. +**How did you hear about the Grants Program?** Web3 Foundation Website / Medium / Twitter / Element / Announcement by another team / **personal recommendation **/ etc. By recommendation of Richard Casey from Parity. From 941c3a454cd44618807816715f01883346901ba0 Mon Sep 17 00:00:00 2001 From: Oleksandra Burmenska Date: Sun, 28 May 2023 23:38:50 +0200 Subject: [PATCH 13/34] Update DAOsign.md --- applications/DAOsign.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/applications/DAOsign.md b/applications/DAOsign.md index 5fc70eca4ec..b7c32133a1e 100644 --- a/applications/DAOsign.md +++ b/applications/DAOsign.md @@ -22,10 +22,12 @@ A project goal is to store Agreements Proofs on Polkadot chain using Ink! smart Proofs are implemented in EIP-712 standard and signed using user’s EVM private key. We are supporting this standard in Ink! smart contract to be able to verify signature. Also, we are implementing EIP-2771 standard to allow Agreement Signers gas-free delegation to publish proof on-chain. + Deliveries include DAOsign platform with an ability to: - create, edit and generate agreements/policies using ChatGPT 3.5 -- add and remove signers/observers of different levels of anonymity +- add and remove signers and observers of different levels of anonymity - allow signing the documents with further storing of signature proofs on Polkadot blockchain. + Core DAOsign components: Screenshot 2023-05-27 at 16 51 43 @@ -159,11 +161,7 @@ Announcing Early Adopters Program and working closely with DAOs to help them int Enhance our tutorials and supplementary materials to better support users and developers. Expanding DAOsign functionality according to the roadmap. -## Referral Program (optional) :moneybag: - -- **Referrer:** Name of the Polkadot Ambassador or GitHub account of the Web3 Foundation grantee -- **Payment Address:** BTC, Ethereum (USDC/DAI) or Polkadot/Kusama (USDT) payment address. Please also specify the currency. (e.g. 0x8920... (DAI)) ## Additional Information :heavy_plus_sign: From ae046d8cfab3ffd005e92bb3ca82655c7fe1974e Mon Sep 17 00:00:00 2001 From: Oleksandra Burmenska Date: Sun, 28 May 2023 23:39:21 +0200 Subject: [PATCH 14/34] Update DAOsign.md --- applications/DAOsign.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/applications/DAOsign.md b/applications/DAOsign.md index b7c32133a1e..fbb4723f361 100644 --- a/applications/DAOsign.md +++ b/applications/DAOsign.md @@ -19,8 +19,6 @@ DAOsign provides publicly verifiable cryptographic proofs; secure, transparent a Furthermore, DAOsign provides robust Governance and Policy Builder platform to provide governance, workflow automation and controls for organization policies and procedures. ### Project Details A project goal is to store Agreements Proofs on Polkadot chain using Ink! smart contracts. -Proofs are implemented in EIP-712 standard and signed using user’s EVM private key. We are supporting this standard in Ink! smart contract to be able to verify signature. -Also, we are implementing EIP-2771 standard to allow Agreement Signers gas-free delegation to publish proof on-chain. Deliveries include DAOsign platform with an ability to: @@ -28,10 +26,13 @@ Deliveries include DAOsign platform with an ability to: - add and remove signers and observers of different levels of anonymity - allow signing the documents with further storing of signature proofs on Polkadot blockchain. -Core DAOsign components: +**Core DAOsign components: ** + Screenshot 2023-05-27 at 16 51 43 -Technical design: +**Technical design:** +Proofs are implemented in EIP-712 standard and signed using user’s EVM private key. We are supporting this standard in Ink! smart contract to be able to verify signature. +Also, we are implementing EIP-2771 standard to allow Agreement Signers gas-free delegation to publish proof on-chain. Screenshot 2023-05-28 at 23 30 53 From d3431480aa15f8cf0a7e403cad5520731f9d49bc Mon Sep 17 00:00:00 2001 From: Oleksandra Burmenska Date: Sun, 28 May 2023 23:39:42 +0200 Subject: [PATCH 15/34] Update DAOsign.md --- applications/DAOsign.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/applications/DAOsign.md b/applications/DAOsign.md index fbb4723f361..d584dcf5342 100644 --- a/applications/DAOsign.md +++ b/applications/DAOsign.md @@ -26,11 +26,12 @@ Deliveries include DAOsign platform with an ability to: - add and remove signers and observers of different levels of anonymity - allow signing the documents with further storing of signature proofs on Polkadot blockchain. -**Core DAOsign components: ** +**Core DAOsign components:** Screenshot 2023-05-27 at 16 51 43 **Technical design:** + Proofs are implemented in EIP-712 standard and signed using user’s EVM private key. We are supporting this standard in Ink! smart contract to be able to verify signature. Also, we are implementing EIP-2771 standard to allow Agreement Signers gas-free delegation to publish proof on-chain. From 57a4e21b548297da99a5466d3690fc10ecbe68f5 Mon Sep 17 00:00:00 2001 From: Oleksandra Burmenska Date: Sun, 28 May 2023 23:43:27 +0200 Subject: [PATCH 16/34] Update DAOsign.md --- applications/DAOsign.md | 18 +++++++++++------- 1 file changed, 11 insertions(+), 7 deletions(-) diff --git a/applications/DAOsign.md b/applications/DAOsign.md index d584dcf5342..d4450ccde02 100644 --- a/applications/DAOsign.md +++ b/applications/DAOsign.md @@ -26,10 +26,12 @@ Deliveries include DAOsign platform with an ability to: - add and remove signers and observers of different levels of anonymity - allow signing the documents with further storing of signature proofs on Polkadot blockchain. + **Core DAOsign components:** Screenshot 2023-05-27 at 16 51 43 + **Technical design:** Proofs are implemented in EIP-712 standard and signed using user’s EVM private key. We are supporting this standard in Ink! smart contract to be able to verify signature. @@ -125,14 +127,14 @@ We are currently working on a tech demo (kind of a pre-beta version) and non-blo Total Estimated Duration: 2 months Full-Time Equivalent (FTE): 4 FTE -Total Costs: 48,100 EUR +Total Costs: 48,100 USD -Milestone 1 - Smartcontracts -Total Costs: 40,300 EUR +Milestone 1 - Smartcontracts. +Total Costs: 40,300 USD | Number | Deliverable | Specification | | -----: | ----------- | ------------- | -| **0a.** | License | TBD | +| **0a.** | License | Open Source | | **0b.** | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how a user can upload/generate the agreement, add signers/observers and complete the signature process with storing signature proofs either in test or mainnet, which will show how the new functionality works. | | **0c.** | Testing and Testing Guide | Core functions will be fully covered by comprehensive unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. | | **0d.** | Docker | We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone. | @@ -144,8 +146,10 @@ Total Costs: 40,300 EUR -Milestone 2 - Application integration -Total Costs: 7,800 EUR + +Milestone 2 - Application integration. +Total Costs: 7,800 USD + | Number | Deliverable | Specification | | -----: | ----------- | ------------- | @@ -167,6 +171,6 @@ Expanding DAOsign functionality according to the roadmap. ## Additional Information :heavy_plus_sign: -**How did you hear about the Grants Program?** Web3 Foundation Website / Medium / Twitter / Element / Announcement by another team / **personal recommendation **/ etc. +**How did you hear about the Grants Program?** By recommendation of Richard Casey from Parity. From 3d17647f990f87b75826dc07e76b1e342cb0c14e Mon Sep 17 00:00:00 2001 From: Oleksandra Burmenska Date: Mon, 29 May 2023 15:30:09 +0200 Subject: [PATCH 17/34] Update DAOsign.md Final iteration with Ramil. --- applications/DAOsign.md | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-) diff --git a/applications/DAOsign.md b/applications/DAOsign.md index d4450ccde02..d35767d1f7a 100644 --- a/applications/DAOsign.md +++ b/applications/DAOsign.md @@ -22,7 +22,7 @@ A project goal is to store Agreements Proofs on Polkadot chain using Ink! smart Deliveries include DAOsign platform with an ability to: -- create, edit and generate agreements/policies using ChatGPT 3.5 +- create agreements including generating using ChatGPT - add and remove signers and observers of different levels of anonymity - allow signing the documents with further storing of signature proofs on Polkadot blockchain. @@ -37,6 +37,10 @@ Deliveries include DAOsign platform with an ability to: Proofs are implemented in EIP-712 standard and signed using user’s EVM private key. We are supporting this standard in Ink! smart contract to be able to verify signature. Also, we are implementing EIP-2771 standard to allow Agreement Signers gas-free delegation to publish proof on-chain. +Detailed storyboard can be found here: https://consideritdone.storiesonboard.com/m/PUCLDvQC4kKwoRJ8kbm3MA . + +Architectural diagram: + Screenshot 2023-05-28 at 23 30 53 ### Ecosystem Fit @@ -126,7 +130,7 @@ We are currently working on a tech demo (kind of a pre-beta version) and non-blo **Overview** Total Estimated Duration: 2 months -Full-Time Equivalent (FTE): 4 FTE +Full-Time Equivalent (FTE): 2 FTE per month Total Costs: 48,100 USD Milestone 1 - Smartcontracts. @@ -134,11 +138,10 @@ Total Costs: 40,300 USD | Number | Deliverable | Specification | | -----: | ----------- | ------------- | -| **0a.** | License | Open Source | -| **0b.** | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how a user can upload/generate the agreement, add signers/observers and complete the signature process with storing signature proofs either in test or mainnet, which will show how the new functionality works. | -| **0c.** | Testing and Testing Guide | Core functions will be fully covered by comprehensive unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. | -| **0d.** | Docker | We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone. | -| 0e. | Article | We will publish an **article** that explains how does DAOsign users can create agreements and store them in Polkadot test- or mainnet. It will be published in our Medium, Linkedin, Twitter and Discord channels. Apart of that, we will regularly publish grant development status on our social media. +| 0a. | License | Open Source | +| 0b. | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how a user can upload/generate the agreement, add signers/observers and complete the signature process with storing signature proofs either in test or mainnet, which will show how the new functionality works. | +| 0c. | Testing and Testing Guide | Core functions will be fully covered by comprehensive unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. | +| 0d. | Article | We will publish an **article** that explains how does DAOsign users can create agreements and store them in Polkadot test- or mainnet. It will be published in our Medium, Linkedin, Twitter and Discord channels. Apart of that, we will regularly publish grant development status on our social media. | 1. | Smart Contracts | Agreement Contract | | 2. | Smart Contracts | EIP712 standard implementation on Ink! | | 3. | Smart Contracts | EIP2771 standard implementation on Ink! | From 7e95d9591997411565ec633272f91dd223727934 Mon Sep 17 00:00:00 2001 From: Oleksandra Burmenska Date: Mon, 29 May 2023 15:32:05 +0200 Subject: [PATCH 18/34] Update DAOsign.md --- applications/DAOsign.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/applications/DAOsign.md b/applications/DAOsign.md index d35767d1f7a..3b7fa79f3cc 100644 --- a/applications/DAOsign.md +++ b/applications/DAOsign.md @@ -1,7 +1,5 @@ # DAOsign - -> See the [Grants Program Process](https://github.com/w3f/Grants-Program/#pencil-process) on how to submit a proposal. - **Team Name:** DAOsign - **Payment Address:** 13s3c37rwrZfa8WQcZPdqE1zi1hGAguf2TWfWMr8f5aLBrg - **[Level](https://github.com/w3f/Grants-Program/tree/master#level_slider-levels):** 2 From e3e7e77562f46efdebfc429b5d3991a8a4cae0a5 Mon Sep 17 00:00:00 2001 From: Oleksandra Burmenska Date: Thu, 15 Jun 2023 22:27:05 +0200 Subject: [PATCH 19/34] Update DAOsign.md provide the requested information --- applications/DAOsign.md | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/applications/DAOsign.md b/applications/DAOsign.md index 3b7fa79f3cc..8f6e50c4926 100644 --- a/applications/DAOsign.md +++ b/applications/DAOsign.md @@ -2,7 +2,7 @@ - **Team Name:** DAOsign - **Payment Address:** 13s3c37rwrZfa8WQcZPdqE1zi1hGAguf2TWfWMr8f5aLBrg -- **[Level](https://github.com/w3f/Grants-Program/tree/master#level_slider-levels):** 2 +- **[Level](https://github.com/w3f/Grants-Program/tree/master#level_slider-levels):** 3 ## Project Overview :page_facing_up: @@ -32,8 +32,10 @@ Deliveries include DAOsign platform with an ability to: **Technical design:** -Proofs are implemented in EIP-712 standard and signed using user’s EVM private key. We are supporting this standard in Ink! smart contract to be able to verify signature. -Also, we are implementing EIP-2771 standard to allow Agreement Signers gas-free delegation to publish proof on-chain. +Proofs are implemented in the EIP-712 standard and adjusted to !ink ecosystem. Signed using user’s !ink private key. We are supporting this standard in Ink! smart contract to be able to verify the signature. Also, we are implementing an adjusted EIP-2771 standard to allow Agreement Signers gas-free delegation to publish proof on-chain.712 standard will be used for for proofs, adaptation means that user data is converted to a binary bit; we use its hash (serialization vs deserialization) +And 271 standard - to securely send the proof and receive it. +So that EVM standards will be adapted to !ink ecosystem requirements. + Detailed storyboard can be found here: https://consideritdone.storiesonboard.com/m/PUCLDvQC4kKwoRJ8kbm3MA . @@ -136,10 +138,11 @@ Total Costs: 40,300 USD | Number | Deliverable | Specification | | -----: | ----------- | ------------- | -| 0a. | License | Open Source | +| 0a. | License | Open Source, TBD | | 0b. | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how a user can upload/generate the agreement, add signers/observers and complete the signature process with storing signature proofs either in test or mainnet, which will show how the new functionality works. | | 0c. | Testing and Testing Guide | Core functions will be fully covered by comprehensive unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. | -| 0d. | Article | We will publish an **article** that explains how does DAOsign users can create agreements and store them in Polkadot test- or mainnet. It will be published in our Medium, Linkedin, Twitter and Discord channels. Apart of that, we will regularly publish grant development status on our social media. +| 0d. | Delivery format | We will provide a website that will include the agreement creation, modification and signing functionality for users with further proofs storing on Polkadot chain. +| 0e. | Article | We will publish an **article** that explains how does DAOsign users can create agreements and store them in Polkadot test- or mainnet. It will be published in our Medium, Linkedin, Twitter and Discord channels. Apart of that, we will regularly publish grant development status on our social media. | 1. | Smart Contracts | Agreement Contract | | 2. | Smart Contracts | EIP712 standard implementation on Ink! | | 3. | Smart Contracts | EIP2771 standard implementation on Ink! | From 6c92b8f34bedff5f84046689fcbd3786e4764622 Mon Sep 17 00:00:00 2001 From: Oleksandra Burmenska Date: Wed, 5 Jul 2023 23:38:35 +0200 Subject: [PATCH 20/34] Update DAOsign.md minor updates to the application: - license info - reusing brush-contracts info included --- applications/DAOsign.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/applications/DAOsign.md b/applications/DAOsign.md index 8f6e50c4926..516ccc4d624 100644 --- a/applications/DAOsign.md +++ b/applications/DAOsign.md @@ -138,13 +138,13 @@ Total Costs: 40,300 USD | Number | Deliverable | Specification | | -----: | ----------- | ------------- | -| 0a. | License | Open Source, TBD | +| 0a. | License | most likely there will be Apache 2.0 | | 0b. | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how a user can upload/generate the agreement, add signers/observers and complete the signature process with storing signature proofs either in test or mainnet, which will show how the new functionality works. | | 0c. | Testing and Testing Guide | Core functions will be fully covered by comprehensive unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. | | 0d. | Delivery format | We will provide a website that will include the agreement creation, modification and signing functionality for users with further proofs storing on Polkadot chain. | 0e. | Article | We will publish an **article** that explains how does DAOsign users can create agreements and store them in Polkadot test- or mainnet. It will be published in our Medium, Linkedin, Twitter and Discord channels. Apart of that, we will regularly publish grant development status on our social media. | 1. | Smart Contracts | Agreement Contract | -| 2. | Smart Contracts | EIP712 standard implementation on Ink! | +| 2. | Smart Contracts | EIP712 standard implementation on Ink! reusing https://github.com/Brushfam/openbrush-contracts| | 3. | Smart Contracts | EIP2771 standard implementation on Ink! | | 4. | Smart Contracts | Delegate call using EIP2771 | From e5f5c20758ec46dee3fce91834d7f99f26176c3c Mon Sep 17 00:00:00 2001 From: Oleksandra Burmenska Date: Sun, 9 Jul 2023 17:10:16 +0200 Subject: [PATCH 21/34] Update DAOsign.md Updated a license information and added an example of the smart contracts --- applications/DAOsign.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/applications/DAOsign.md b/applications/DAOsign.md index 516ccc4d624..1f026082992 100644 --- a/applications/DAOsign.md +++ b/applications/DAOsign.md @@ -35,6 +35,9 @@ Deliveries include DAOsign platform with an ability to: Proofs are implemented in the EIP-712 standard and adjusted to !ink ecosystem. Signed using user’s !ink private key. We are supporting this standard in Ink! smart contract to be able to verify the signature. Also, we are implementing an adjusted EIP-2771 standard to allow Agreement Signers gas-free delegation to publish proof on-chain.712 standard will be used for for proofs, adaptation means that user data is converted to a binary bit; we use its hash (serialization vs deserialization) And 271 standard - to securely send the proof and receive it. So that EVM standards will be adapted to !ink ecosystem requirements. +Example (interfaces) of the smart contracts can be found here https://github.com/DAOsign/daosign-smart-contracts (Solidity version). + + Detailed storyboard can be found here: https://consideritdone.storiesonboard.com/m/PUCLDvQC4kKwoRJ8kbm3MA . @@ -138,7 +141,7 @@ Total Costs: 40,300 USD | Number | Deliverable | Specification | | -----: | ----------- | ------------- | -| 0a. | License | most likely there will be Apache 2.0 | +| 0a. | License | Apache 2.0 | | 0b. | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how a user can upload/generate the agreement, add signers/observers and complete the signature process with storing signature proofs either in test or mainnet, which will show how the new functionality works. | | 0c. | Testing and Testing Guide | Core functions will be fully covered by comprehensive unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. | | 0d. | Delivery format | We will provide a website that will include the agreement creation, modification and signing functionality for users with further proofs storing on Polkadot chain. From 13c0d8587eacdff2b80efdc580777eb09eb7039e Mon Sep 17 00:00:00 2001 From: ramil Date: Thu, 13 Jul 2023 04:41:01 +0300 Subject: [PATCH 22/34] update --- applications/DAOsign.md | 60 +++++++++++++++++++++-------------------- 1 file changed, 31 insertions(+), 29 deletions(-) diff --git a/applications/DAOsign.md b/applications/DAOsign.md index 1f026082992..2cd9d0e59ae 100644 --- a/applications/DAOsign.md +++ b/applications/DAOsign.md @@ -130,50 +130,52 @@ We are currently working on a tech demo (kind of a pre-beta version) and non-blo ## Development Roadmap :nut_and_bolt: -**Overview** +## Overview -Total Estimated Duration: 2 months -Full-Time Equivalent (FTE): 2 FTE per month -Total Costs: 48,100 USD +* **Total Estimated Duration:** 2 months +* **Full-Time Equivalent (FTE):** 2 FTE +* **Total Costs:** 48,100 USD -Milestone 1 - Smartcontracts. -Total Costs: 40,300 USD +### Milestone 1 - Smart Contract Development -| Number | Deliverable | Specification | -| -----: | ----------- | ------------- | -| 0a. | License | Apache 2.0 | -| 0b. | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how a user can upload/generate the agreement, add signers/observers and complete the signature process with storing signature proofs either in test or mainnet, which will show how the new functionality works. | -| 0c. | Testing and Testing Guide | Core functions will be fully covered by comprehensive unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. | -| 0d. | Delivery format | We will provide a website that will include the agreement creation, modification and signing functionality for users with further proofs storing on Polkadot chain. -| 0e. | Article | We will publish an **article** that explains how does DAOsign users can create agreements and store them in Polkadot test- or mainnet. It will be published in our Medium, Linkedin, Twitter and Discord channels. Apart of that, we will regularly publish grant development status on our social media. -| 1. | Smart Contracts | Agreement Contract | -| 2. | Smart Contracts | EIP712 standard implementation on Ink! reusing https://github.com/Brushfam/openbrush-contracts| -| 3. | Smart Contracts | EIP2771 standard implementation on Ink! | -| 4. | Smart Contracts | Delegate call using EIP2771 | +* **Estimated Duration:** 6 weeks +* **FTE:** 2 +* **Costs:** 40,300 USD +| Number | Deliverable | Specification | +|-------:|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0a. | License | Apache 2.0 | +| 0b. | Documentation | We will provide both inline documentation of the code and a basic tutorial that explains how a user can use DAOsign Smart Contract developed in ink! for proof verification. | +| 0c. | Testing and Testing Guide | Core functions will be fully covered by comprehensive unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. | +| 0d. | Docker | We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone. | +| 0e. | Article | We will publish an **article** that explains what was done as part of the grant. And we will publish a series of articles that explains how DAOsign works from a high-level perspective. The content of the articles will be consistent with the functions at this stage. | +| 1. | Smart Contracts | DAOsign Smart Contract repo that includes following components: Agreement Contract, EIP712/EIP2771 standard implementation on Ink!. These smart contracts can be deployed to any substrate chain with ink! pallet. | | +| 2. | Gas Relayer | Off-chain component for transaction relaying | -Milestone 2 - Application integration. -Total Costs: 7,800 USD +### Milestone 2 - DAOsign Application integration +* **Estimated Duration:** 2 weeks +* **FTE:** 2 +* **Costs:** 7,800 USD -| Number | Deliverable | Specification | -| -----: | ----------- | ------------- | -| **0a.** | License | TBD | -| 1. | Application Integration| Application Private Key Management | -| 2. | Application Integration | DAOsign app integration | +| Number | Deliverable | Specification | +|-------:|---------------------------------|---------------------------------------------------------------------------------------------------------| +| 0a. | License | Apache 2.0 | +| 0b. | Documentation | We will provide both inline documentation of the code and a basic tutorial that explains how a user can | +| 0c. | Testing Guide | Core functions will be fully covered by unit tests to ensure functionality and robustness. | +| 1. | DAOsign Ink! JS SDK | We will publish a npm/yarn package with the logic how to interact with Smart Contract from JS | +| 2. | DAOsign Application Integration | Integrate DAOsign application using SDK | -## Future Plans -Our team plans to contribute to the Polkadot ecosystem through: +## Future Plans -Announcing Early Adopters Program and working closely with DAOs to help them integrate DAOsign. -Enhance our tutorials and supplementary materials to better support users and developers. -Expanding DAOsign functionality according to the roadmap. +After the `ink!` version of the DAOsign protocol stack is fully tested, we would like to implement a `pallet` version for Polkadot ecosystems. Anyone who is integrating it can communicate with other ecosystems conveniently. +Add support for multi-chain proof verification using [XCM](https://wiki.polkadot.network/docs/learn-xcm) and [IBC](https://ibcprotocol.org/) protocols. ## Additional Information :heavy_plus_sign: From 43440840946420256744c4267f75b9aaa4b80195 Mon Sep 17 00:00:00 2001 From: ramil Date: Sun, 16 Jul 2023 02:34:42 +0300 Subject: [PATCH 23/34] correct name of the pallet --- applications/DAOsign.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/applications/DAOsign.md b/applications/DAOsign.md index 2cd9d0e59ae..1f5cd481d90 100644 --- a/applications/DAOsign.md +++ b/applications/DAOsign.md @@ -150,7 +150,7 @@ We are currently working on a tech demo (kind of a pre-beta version) and non-blo | 0c. | Testing and Testing Guide | Core functions will be fully covered by comprehensive unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. | | 0d. | Docker | We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone. | | 0e. | Article | We will publish an **article** that explains what was done as part of the grant. And we will publish a series of articles that explains how DAOsign works from a high-level perspective. The content of the articles will be consistent with the functions at this stage. | -| 1. | Smart Contracts | DAOsign Smart Contract repo that includes following components: Agreement Contract, EIP712/EIP2771 standard implementation on Ink!. These smart contracts can be deployed to any substrate chain with ink! pallet. | | +| 1. | Smart Contracts | DAOsign Smart Contract repo that includes following components: Agreement Contract, EIP712/EIP2771 standard implementation on Ink!. These smart contracts can be deployed to any substrate chain with contracts-pallet. | | | 2. | Gas Relayer | Off-chain component for transaction relaying | From cd4e9490d24ef99090ff7041271cda9a8c783c60 Mon Sep 17 00:00:00 2001 From: ramil Date: Tue, 18 Jul 2023 13:01:25 +0300 Subject: [PATCH 24/34] update deliverables to deploy to Astar testnet fix typos --- applications/DAOsign.md | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/applications/DAOsign.md b/applications/DAOsign.md index 1f5cd481d90..0429e4b8df8 100644 --- a/applications/DAOsign.md +++ b/applications/DAOsign.md @@ -22,7 +22,7 @@ A project goal is to store Agreements Proofs on Polkadot chain using Ink! smart Deliveries include DAOsign platform with an ability to: - create agreements including generating using ChatGPT - add and remove signers and observers of different levels of anonymity -- allow signing the documents with further storing of signature proofs on Polkadot blockchain. +- allow signing the documents with further storing of signature proofs on Astar testnet blockchain. **Core DAOsign components:** @@ -32,14 +32,15 @@ Deliveries include DAOsign platform with an ability to: **Technical design:** -Proofs are implemented in the EIP-712 standard and adjusted to !ink ecosystem. Signed using user’s !ink private key. We are supporting this standard in Ink! smart contract to be able to verify the signature. Also, we are implementing an adjusted EIP-2771 standard to allow Agreement Signers gas-free delegation to publish proof on-chain.712 standard will be used for for proofs, adaptation means that user data is converted to a binary bit; we use its hash (serialization vs deserialization) -And 271 standard - to securely send the proof and receive it. -So that EVM standards will be adapted to !ink ecosystem requirements. +Proofs are implemented in the EIP-712 standard and adjusted to ink! ecosystem. Proofs digned using user’s EVM private key. +We are supporting this standard in Ink! smart contract to be able to verify the signature in ink! smart contract. +Also, we are implementing an adjusted EIP-2771 standard to allow Agreement Signers gas-free delegation to publish proof on-chain. +EIP-712 standard will be used for proofs, adaptation means that user data is converted to a binary bit; we use its hash (serialization vs deserialization) +And EIP-2771 standard - to securely send the proof and receive it. +So that EVM standards will be adapted to ink! ecosystem requirements. Example (interfaces) of the smart contracts can be found here https://github.com/DAOsign/daosign-smart-contracts (Solidity version). - - Detailed storyboard can be found here: https://consideritdone.storiesonboard.com/m/PUCLDvQC4kKwoRJ8kbm3MA . Architectural diagram: From 978bdf3eb5d73773fd18b65e245e79239460bdbb Mon Sep 17 00:00:00 2001 From: ramil Date: Tue, 18 Jul 2023 14:18:45 +0300 Subject: [PATCH 25/34] update m2 deliverables --- applications/DAOsign.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/applications/DAOsign.md b/applications/DAOsign.md index 0429e4b8df8..16220e4e8c7 100644 --- a/applications/DAOsign.md +++ b/applications/DAOsign.md @@ -162,13 +162,13 @@ We are currently working on a tech demo (kind of a pre-beta version) and non-blo * **Costs:** 7,800 USD -| Number | Deliverable | Specification | -|-------:|---------------------------------|---------------------------------------------------------------------------------------------------------| -| 0a. | License | Apache 2.0 | -| 0b. | Documentation | We will provide both inline documentation of the code and a basic tutorial that explains how a user can | -| 0c. | Testing Guide | Core functions will be fully covered by unit tests to ensure functionality and robustness. | -| 1. | DAOsign Ink! JS SDK | We will publish a npm/yarn package with the logic how to interact with Smart Contract from JS | -| 2. | DAOsign Application Integration | Integrate DAOsign application using SDK | +| Number | Deliverable | Specification | +|-------:|---------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0a. | License | Apache 2.0 | +| 0b. | Documentation | We will provide both inline documentation of the code and a basic tutorial that explains how a user can | +| 0c. | Testing Guide | Core functions will be fully covered by unit tests to ensure functionality and robustness. | +| 1. | DAOsign Ink! JS SDK | We will publish a npm/yarn package with the logic how to interact with Smart Contract from JS | +| 2. | DAOsign Application Integration | Integrate DAOsign application using SDK. DAOsign application will be open sourced as well. DAOsign is written using ReactJS on frontend and Typescript on backend | From 31167fda79bd1db855b90334f21f21d6e0de7d7d Mon Sep 17 00:00:00 2001 From: Oleksandra Burmenska Date: Thu, 27 Jul 2023 10:53:13 +0300 Subject: [PATCH 26/34] Update DAOsign.md updated a registered address --- applications/DAOsign.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/applications/DAOsign.md b/applications/DAOsign.md index 16220e4e8c7..8b0a99874ce 100644 --- a/applications/DAOsign.md +++ b/applications/DAOsign.md @@ -73,7 +73,7 @@ Competitors analysis can be found here: https://docsend.com/view/sbexkxn5su3ahdg ### Legal Structure -- **Registered Address:** ILLINOIS LIMITED LIABILITY CORPORATION, US +- **Registered Address:** 2468 Brian Dr. Northbrook, IL 60062 - **Registered Legal Entity:** DAOSIGN, LLC ### Team's experience From 59cf84a6bb1f92278fee52bce88ca63a1665b8b7 Mon Sep 17 00:00:00 2001 From: Ramil Amerzyanov Date: Thu, 27 Jul 2023 21:17:59 +0300 Subject: [PATCH 27/34] Update applications/DAOsign.md Co-authored-by: S E R A Y A --- applications/DAOsign.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/applications/DAOsign.md b/applications/DAOsign.md index 8b0a99874ce..55736d540d9 100644 --- a/applications/DAOsign.md +++ b/applications/DAOsign.md @@ -168,7 +168,7 @@ We are currently working on a tech demo (kind of a pre-beta version) and non-blo | 0b. | Documentation | We will provide both inline documentation of the code and a basic tutorial that explains how a user can | | 0c. | Testing Guide | Core functions will be fully covered by unit tests to ensure functionality and robustness. | | 1. | DAOsign Ink! JS SDK | We will publish a npm/yarn package with the logic how to interact with Smart Contract from JS | -| 2. | DAOsign Application Integration | Integrate DAOsign application using SDK. DAOsign application will be open sourced as well. DAOsign is written using ReactJS on frontend and Typescript on backend | +| 2. | DAOsign Application Integration | Integrate DAOsign application using SDK. DAOsign application (which is not part of this grant) will be open sourced as well. DAOsign is written using ReactJS on frontend and Typescript on backend | From f9d5adba8cfb359fc49e0bbf014fb90f60622d83 Mon Sep 17 00:00:00 2001 From: ramil Date: Thu, 27 Jul 2023 22:12:03 +0300 Subject: [PATCH 28/34] add UI design --- applications/DAOsign.md | 40 +++++++++++++++++++++++++++++++--------- 1 file changed, 31 insertions(+), 9 deletions(-) diff --git a/applications/DAOsign.md b/applications/DAOsign.md index 55736d540d9..ad1f497a203 100644 --- a/applications/DAOsign.md +++ b/applications/DAOsign.md @@ -15,6 +15,7 @@ Traditional methods of signing agreements, such as paper-based systems or legacy DAOsign provides publicly verifiable cryptographic proofs; secure, transparent and automated processing of complex Agreements and Policies. Furthermore, DAOsign provides robust Governance and Policy Builder platform to provide governance, workflow automation and controls for organization policies and procedures. + ### Project Details A project goal is to store Agreements Proofs on Polkadot chain using Ink! smart contracts. @@ -25,12 +26,12 @@ Deliveries include DAOsign platform with an ability to: - allow signing the documents with further storing of signature proofs on Astar testnet blockchain. -**Core DAOsign components:** +**Core DAOsign components** Screenshot 2023-05-27 at 16 51 43 -**Technical design:** +**Technical design** Proofs are implemented in the EIP-712 standard and adjusted to ink! ecosystem. Proofs digned using user’s EVM private key. We are supporting this standard in Ink! smart contract to be able to verify the signature in ink! smart contract. @@ -43,10 +44,31 @@ Example (interfaces) of the smart contracts can be found here https://github.com Detailed storyboard can be found here: https://consideritdone.storiesonboard.com/m/PUCLDvQC4kKwoRJ8kbm3MA . -Architectural diagram: +**Architectural diagram** Screenshot 2023-05-28 at 23 30 53 +Agreement Proof entity represent 3 proofs: +* Proof of signature +* Proof of authority +* Proof of agreement + +**UI Design** + +In Milestone 2 we have a frontend delivery. Here list of wireframes/designs with comments: + + +1. Adding toggle to allow store Agreement Proof on-chain (toggle above Sign Agreement button) +![Store proofs 0](https://github.com/w3f/Grants-Program/assets/1008882/40f89bfa-50fc-4944-8a64-af84337b713a) + +2. Enable that toggle and select Parity network from dropdown + +![Store proofs 1](https://github.com/w3f/Grants-Program/assets/1008882/87894c58-bc30-4e48-b74b-3eabfcad2779) + +3. After user click `Sign Agreement` and execute transaction, we show `On-chain Proof` transaction hash on Information panel +![Store proofs 6](https://github.com/w3f/Grants-Program/assets/1008882/88dfed66-5f88-4658-88b4-8a6198060de9) + + ### Ecosystem Fit DAOsign fit the Governance category and since, Polkadot and Kusama are designed to be community-driven networks that allow for decentralized governance. DAOsign can fit into this ecosystem by providing a platform for DAOs to manage their decision-making processes in a decentralized manner. @@ -162,12 +184,12 @@ We are currently working on a tech demo (kind of a pre-beta version) and non-blo * **Costs:** 7,800 USD -| Number | Deliverable | Specification | -|-------:|---------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 0a. | License | Apache 2.0 | -| 0b. | Documentation | We will provide both inline documentation of the code and a basic tutorial that explains how a user can | -| 0c. | Testing Guide | Core functions will be fully covered by unit tests to ensure functionality and robustness. | -| 1. | DAOsign Ink! JS SDK | We will publish a npm/yarn package with the logic how to interact with Smart Contract from JS | +| Number | Deliverable | Specification | +|-------:|---------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0a. | License | Apache 2.0 | +| 0b. | Documentation | We will provide both inline documentation of the code and a basic tutorial that explains how a user can | +| 0c. | Testing Guide | Core functions will be fully covered by unit tests to ensure functionality and robustness. | +| 1. | DAOsign Ink! JS SDK | We will publish a npm/yarn package with the logic how to interact with Smart Contract from JS | | 2. | DAOsign Application Integration | Integrate DAOsign application using SDK. DAOsign application (which is not part of this grant) will be open sourced as well. DAOsign is written using ReactJS on frontend and Typescript on backend | From 0a5ab6a79c304cad58e49fbc50d6821250b006ad Mon Sep 17 00:00:00 2001 From: ramil Date: Thu, 27 Jul 2023 22:32:42 +0300 Subject: [PATCH 29/34] add link to Proof technical design --- applications/DAOsign.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/applications/DAOsign.md b/applications/DAOsign.md index ad1f497a203..f9fd2cf4b21 100644 --- a/applications/DAOsign.md +++ b/applications/DAOsign.md @@ -53,6 +53,8 @@ Agreement Proof entity represent 3 proofs: * Proof of authority * Proof of agreement +The detailed Proof Technical Design is [here](https://github.com/w3f/Grants-Program/files/12183424/Proofs.Technical.Design.-.DAOSign.pdf) + **UI Design** In Milestone 2 we have a frontend delivery. Here list of wireframes/designs with comments: From 7c62fc5191248d04f80f1b594ec647b73a85acf5 Mon Sep 17 00:00:00 2001 From: ramil Date: Thu, 10 Aug 2023 18:49:06 +0300 Subject: [PATCH 30/34] * added description for Off-chain Relayer * realign milestones cost --- applications/DAOsign.md | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/applications/DAOsign.md b/applications/DAOsign.md index f9fd2cf4b21..c4247a75ae8 100644 --- a/applications/DAOsign.md +++ b/applications/DAOsign.md @@ -44,6 +44,15 @@ Example (interfaces) of the smart contracts can be found here https://github.com Detailed storyboard can be found here: https://consideritdone.storiesonboard.com/m/PUCLDvQC4kKwoRJ8kbm3MA . +**Off-chain Relayer** + +Relayer is an off-chain component that accepts transaction (with EIP-712 signature from Metamask) from user, +signs it and sends to the network. This app will be developed using following technology stack: + +* Typescript/NodeJS +* express.js +* polkadot.js + **Architectural diagram** Screenshot 2023-05-28 at 23 30 53 @@ -165,7 +174,7 @@ We are currently working on a tech demo (kind of a pre-beta version) and non-blo * **Estimated Duration:** 6 weeks * **FTE:** 2 -* **Costs:** 40,300 USD +* **Costs:** 36,075 USD | Number | Deliverable | Specification | @@ -183,7 +192,7 @@ We are currently working on a tech demo (kind of a pre-beta version) and non-blo * **Estimated Duration:** 2 weeks * **FTE:** 2 -* **Costs:** 7,800 USD +* **Costs:** 12,025 USD | Number | Deliverable | Specification | From e1a426f2d2fac50d932eaba93740196218893dd8 Mon Sep 17 00:00:00 2001 From: ramil Date: Thu, 10 Aug 2023 20:53:04 +0300 Subject: [PATCH 31/34] updated seq diagram --- applications/DAOsign.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/applications/DAOsign.md b/applications/DAOsign.md index c4247a75ae8..0a414e02920 100644 --- a/applications/DAOsign.md +++ b/applications/DAOsign.md @@ -55,7 +55,15 @@ signs it and sends to the network. This app will be developed using following te **Architectural diagram** -Screenshot 2023-05-28 at 23 30 53 +![DAOsign_ Storing proofs using Ink!](https://github.com/Burmenska/Grants-Program/assets/1008882/297093a0-200a-4f78-babb-04ad6314fb35) + +**Definitions**: +* **Creator**: Author of agreement, define agreement content, signers +* **Signer**: Participant (Signer) of the agreement. Signs and sends transactions to a Relay +* **Relayer**: Receives signed requests off-chain from Signers and pays gas to turn it into a valid transaction that goes through a Trusted Forwarder +* **Trusted Forwarder**: A contract trusted by the Recipient to correctly verify signatures before forwarding the request from Signers +* **AgreementProof**: A contract that holds metadata and proofs for agreement.er + Agreement Proof entity represent 3 proofs: * Proof of signature From bca204eba970a12fed3aa91a862408943d25329d Mon Sep 17 00:00:00 2001 From: Ramil Amerzyanov Date: Fri, 11 Aug 2023 11:56:05 +0300 Subject: [PATCH 32/34] Update applications/DAOsign.md Co-authored-by: S E R A Y A --- applications/DAOsign.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/applications/DAOsign.md b/applications/DAOsign.md index 0a414e02920..04ad925fe2f 100644 --- a/applications/DAOsign.md +++ b/applications/DAOsign.md @@ -21,7 +21,7 @@ A project goal is to store Agreements Proofs on Polkadot chain using Ink! smart Deliveries include DAOsign platform with an ability to: -- create agreements including generating using ChatGPT +- create agreements including generating using ChatGPT (already implemented on our platform, currently available on our [testnet](https://testnet.daosign.org/) - add and remove signers and observers of different levels of anonymity - allow signing the documents with further storing of signature proofs on Astar testnet blockchain. From 49500aed878ad4e27c6c2a65b4def98ca5dfa398 Mon Sep 17 00:00:00 2001 From: ramil Date: Thu, 17 Aug 2023 18:34:47 +0300 Subject: [PATCH 33/34] add docker to m2 --- applications/DAOsign.md | 1 + 1 file changed, 1 insertion(+) diff --git a/applications/DAOsign.md b/applications/DAOsign.md index 04ad925fe2f..05e3708a145 100644 --- a/applications/DAOsign.md +++ b/applications/DAOsign.md @@ -208,6 +208,7 @@ We are currently working on a tech demo (kind of a pre-beta version) and non-blo | 0a. | License | Apache 2.0 | | 0b. | Documentation | We will provide both inline documentation of the code and a basic tutorial that explains how a user can | | 0c. | Testing Guide | Core functions will be fully covered by unit tests to ensure functionality and robustness. | +| 0d. | Docker | Dockerfile(s) provided in Milestone 1 will be used to test all the functionality delivered with this milestone. | | 1. | DAOsign Ink! JS SDK | We will publish a npm/yarn package with the logic how to interact with Smart Contract from JS | | 2. | DAOsign Application Integration | Integrate DAOsign application using SDK. DAOsign application (which is not part of this grant) will be open sourced as well. DAOsign is written using ReactJS on frontend and Typescript on backend | From cd0bd68a27817f30e0039900fb00ab87591513d5 Mon Sep 17 00:00:00 2001 From: ramil Date: Tue, 29 Aug 2023 02:29:07 +0300 Subject: [PATCH 34/34] added relayer as a separate milestone 3 --- applications/DAOsign.md | 21 ++++++++++++++++++--- 1 file changed, 18 insertions(+), 3 deletions(-) diff --git a/applications/DAOsign.md b/applications/DAOsign.md index 05e3708a145..6410e337604 100644 --- a/applications/DAOsign.md +++ b/applications/DAOsign.md @@ -180,9 +180,9 @@ We are currently working on a tech demo (kind of a pre-beta version) and non-blo ### Milestone 1 - Smart Contract Development -* **Estimated Duration:** 6 weeks +* **Estimated Duration:** 4 weeks * **FTE:** 2 -* **Costs:** 36,075 USD +* **Costs:** 24,050 USD | Number | Deliverable | Specification | @@ -193,7 +193,6 @@ We are currently working on a tech demo (kind of a pre-beta version) and non-blo | 0d. | Docker | We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone. | | 0e. | Article | We will publish an **article** that explains what was done as part of the grant. And we will publish a series of articles that explains how DAOsign works from a high-level perspective. The content of the articles will be consistent with the functions at this stage. | | 1. | Smart Contracts | DAOsign Smart Contract repo that includes following components: Agreement Contract, EIP712/EIP2771 standard implementation on Ink!. These smart contracts can be deployed to any substrate chain with contracts-pallet. | | -| 2. | Gas Relayer | Off-chain component for transaction relaying | ### Milestone 2 - DAOsign Application integration @@ -213,6 +212,22 @@ We are currently working on a tech demo (kind of a pre-beta version) and non-blo | 2. | DAOsign Application Integration | Integrate DAOsign application using SDK. DAOsign application (which is not part of this grant) will be open sourced as well. DAOsign is written using ReactJS on frontend and Typescript on backend | +### Milestone 3 - Relayer Development + +* **Estimated Duration:** 2 weeks +* **FTE:** 2 +* **Costs:** 12,025 USD + + +| Number | Deliverable | Specification | +|-------:|---------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| 0a. | License | Apache 2.0 | +| 0b. | Documentation | We will provide both inline documentation of the code and a basic tutorial that explains how a user can run Relayer and broadcast transactions | +| 0c. | Testing Guide | Core functions will be fully covered by unit tests to ensure functionality and robustness. | +| 0d. | Docker | We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone. | +| 1. | Gas Relayer | Off-chain component for relaying transactions. Will be developed on Typescript/NodeJS using polkadot.js library | + + ## Future Plans