From c41252f104a6106411ea66b40ba9c6a38ef682be Mon Sep 17 00:00:00 2001 From: LuukDAO <59537248+LuukDAO@users.noreply.github.com> Date: Mon, 21 Aug 2023 16:09:24 +0200 Subject: [PATCH 01/16] Add files via upload --- applications/application-template (1).md | 212 +++++++++++++++++++++++ 1 file changed, 212 insertions(+) create mode 100644 applications/application-template (1).md diff --git a/applications/application-template (1).md b/applications/application-template (1).md new file mode 100644 index 00000000..7a6fdb4c --- /dev/null +++ b/applications/application-template (1).md @@ -0,0 +1,212 @@ +# EOS Network Foundation Grant Proposal + +> 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. +> +> See the [Grant Framework Process](https://github.com/eosnetworkfoundation/grant-framework#grant-process-for-new-proposals) on how to submit a proposal. +> +> Please do not remove any of the mandatory lines that start with **bold labels** or as headlines! Your application will be rejected! +> +> Please do not remove the bolding of labels (such as **Bold Label:** ) as it is needed by the automated parsers - that includes the bolding on lines starting with a bullet as part of a list. +> +> Please note that this application will be **automatically parsed**. Please only put the data required in the fields following the bolded labels. +> +> Deleting lines that start with **Bold Labels:** will cause your grant to be rejected! Please fill this out carefully if you want to be approved! +> +> All "comment" lines starting with a `>` (such as this one and the ones above and below) should be removed. + +- **Project Name:** Name of your project (e.g. Anchor Wallet) +- **Team Name:** Legal name of your team (e.g. Greymass, Inc.) +- **EOS Payment Address:** EOS payment address +- **[Level](https://github.com/eosnetworkfoundation/grant-framework#grant-levels):** 1, 2 or 3 +- **Pomelo Grant(s):** List URL(s) to Pomelo grants for your team (or list N/A for non-applicable) +- **Project is Open-Source:** Yes/No +- **Project was part of Token sale:** Yes/No +- **Repository where Project resides:** https://github.com// +> Please only answer Yes or No to the Open-Source or Token sale questions. Do not explain more on that line. You may delete this line and all lines that begin with `>` from your application. + +## Contact + +- **Contact Name:** Full name of the contact person in your team +- **Contact Email:** myemail@mycompany.com +- **Website:** https://yourwebsite.com + +> ⚠️ *The combination of your GitHub account submitting the application and the EOS account address above will be your unique identifier during the program. Please keep them safe.* + +## Project Overview + +> If this is an application for a follow-up grant (the continuation of an earlier, successful ENF grant), please provide name and/or pull request of said grant on the first line of this section. + +### Overview + +> Please provide the following: + +- **Name:** If the name of your project is not descriptive, a tag line (one sentence summary). +- **Brief Description:** A brief description of your project. +- **Relationship to EOS Network / Antelope:** An indication of how your project relates to / integrates into the EOS Network or Antelope software. +- **Reason for Interest:** 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): + +- Mock-ups/designs of any UI components +- Data models of the core functionality +- 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 + +### Ecosystem Fit + +> Help us locate your project in the EOS Network 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 (chain/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 EOS Network / Antelope ecosystem? + - If so, how is your project different? + - If not, are there similar projects in related ecosystems? + +## Team + +### Team members + +- **Team Leader:** Name of team leader +- Name of team member 1 +- Name of team member 2 +- Name of team member 3, etc. + +### Legal Structure +- **Registered Legal Entity:** Name of your registered legal entity. (e.g. Greymass, Inc.) +- **Registered Address:** Address of your registered legal entity. Please keep it in a single line. (e.g. 123 Main Street, London LK1 234, UK) + +### Team 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. For research-related grants, references to past publications and projects in a related domain are helpful. If you applied for a Pomelo grant in the past, please be sure you listed them in the section above and mention them in detail in this section. + +> If anyone on your team has applied for a grant at the EOS Network Foundation previously, please list the name of the project and legal entity here. + +### Team Org Repos + +- https://github.com/ +- 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. + +### Team Member Repos + +- https://github.com/ +- https://github.com/ + +### Team LinkedIn Profiles (if available) + +- https://www.linkedin.com/in/ +- https://www.linkedin.com/in/ + +## Development Status + +> 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/eosnetworkfoundation/grant-framework/tree/main/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 EOS Network Foundation, +- previous interface iterations, such as mock-ups and wireframes. + +## Development Roadmap + +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/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 the EOS ecosystem. We _recommend_ that teams structure their roadmap as 1 milestone ≈ 1 month. + +For each milestone, + +- make sure to include a specification of your software. _Treat it as a contract_; the level of detail must be enough to later verify that the software meets the specification. +- include the amount of funding requested _per milestone_. +- include documentation (tutorials, API specifications, architecture diagrams, whatever is appropriate) in each milestone. This ensures that the code can be widely used by the community. +- provide a test suite, comprising unit and integration tests, along with a guide on how to set up and run them. +- commit to providing Dockerfiles for the delivery of your project. +- indicate milestone duration as well as number of full-time employees working on each milestone. +- **Deliverables 0a-0c are mandatory for all milestones**, and deliverable 0e at least for the last one. If you do not intend to deliver one of these, please state a reason in its specification (e.g. Milestone X is research oriented and as such there is no code to test). + +> :zap: If any of your deliverables is based on someone 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.** + +### Milestone Summary + +> Note: the numbers in the three lines below are examples. Please replace with your own calculations! Then delete this instruction line. +> You **must** keep these three Milestone Summary lines below for your grant to be approved. The Total Cost should add up to the costs +> of all of your Milestones. Please **DO NOT** remove the three lines below. If you do, your grant will be rejected or delayed while you fix it. +- **Total Estimated Duration:** 2 months +- **Full-Time Equivalent (FTE):** 2 FTE +- **Total Costs:** 12,000 USD + +> Please note that this application is automatically parsed.
+> For the above fields, please only put the answer on that line. If you want to add more information, please put it below these instructions.
+> Please remember to delete all lines that start with `>` as they are just instructions and not needed in the application submission.
+> +> Notes on above fields: +> - Total Estimated Duration: Duration of the whole project (example: 2 months or 7 weeks) +> - Full-Time Equivalent (FTE): This is the average number of full-time employees working on the project throughout its duration (see [Wikipedia](https://en.wikipedia.org/wiki/Full-time_equivalent), example: 2 FTE or possibly 2.5 FTE as it is an average) +> - Total Costs: This should be the requested amount in USD for the whole project (example 12,000 USD). Note that the acceptance criteria and additional benefits vary depending on the [level](../README.md#grant-levels) of funding requested. This and the costs for each milestone need to be provided in USD; if the grant is paid out in EOS, the amount will be calculated according to the exchange rate at the time of payment. + +### Milestone 1 Example — Implement EOS Application + +- **Estimated duration:** 1 month +- **FTE:** 2 +- **Costs:** 8,000 USD + +| ID | Deliverable | Specification | +| ----- | ----------- | ------------- | +| 0a. | License | MIT / Apache 2.0 / GPLv3 / 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 EOS nodes and send test transactions, which will show how the new functionality works. | +| 0c. | Testing Guide | Core functions will be fully covered by 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. | Application interface to Antelope | We will create an integration layer ... (Please list the functionality that will be implemented for the first milestone) | +| 2. | Front-End / User Interface | We will create a UI that connects to ... | +| 3. | Caching layer | We will create a caching layer ... | +| 4. | API interface to our app | We will create an API that ... | + + + +### Milestone 2 Example — Additional features + +- **Estimated Duration:** 1 month +- **FTE:** 2 +- **Costs:** 4,000 USD + +| ID | Deliverable | Specification | +| ----- | ----------- | ------------- | +| 0a. | License | MIT / Apache 2.0 / GPLv3 / 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 EOS nodes and send test transactions, which will show how the new functionality works. | +| 0c. | Testing Guide | Core functions will be fully covered by 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. | Performance Enhancements | We will create performance enhancements to ... (Please list the functionality that will be implemented for the first milestone) | +| 2. | Added UI functionality | We will add UI functionality to... | +| 3. | Add 3rd Party API integration | We will add 3rd party integration to ... | + + +... Add more milestones as above as needed ... + + +## 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. + + +## Additional Information + +**How did you hear about the Grants Program?** EOS Network 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 4767fbec3b5da40370292d30ad0498cfe2eb0df7 Mon Sep 17 00:00:00 2001 From: LuukDAO <59537248+LuukDAO@users.noreply.github.com> Date: Mon, 21 Aug 2023 16:10:06 +0200 Subject: [PATCH 02/16] Delete application-template (1).md --- applications/application-template (1).md | 212 ----------------------- 1 file changed, 212 deletions(-) delete mode 100644 applications/application-template (1).md diff --git a/applications/application-template (1).md b/applications/application-template (1).md deleted file mode 100644 index 7a6fdb4c..00000000 --- a/applications/application-template (1).md +++ /dev/null @@ -1,212 +0,0 @@ -# EOS Network Foundation Grant Proposal - -> 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. -> -> See the [Grant Framework Process](https://github.com/eosnetworkfoundation/grant-framework#grant-process-for-new-proposals) on how to submit a proposal. -> -> Please do not remove any of the mandatory lines that start with **bold labels** or as headlines! Your application will be rejected! -> -> Please do not remove the bolding of labels (such as **Bold Label:** ) as it is needed by the automated parsers - that includes the bolding on lines starting with a bullet as part of a list. -> -> Please note that this application will be **automatically parsed**. Please only put the data required in the fields following the bolded labels. -> -> Deleting lines that start with **Bold Labels:** will cause your grant to be rejected! Please fill this out carefully if you want to be approved! -> -> All "comment" lines starting with a `>` (such as this one and the ones above and below) should be removed. - -- **Project Name:** Name of your project (e.g. Anchor Wallet) -- **Team Name:** Legal name of your team (e.g. Greymass, Inc.) -- **EOS Payment Address:** EOS payment address -- **[Level](https://github.com/eosnetworkfoundation/grant-framework#grant-levels):** 1, 2 or 3 -- **Pomelo Grant(s):** List URL(s) to Pomelo grants for your team (or list N/A for non-applicable) -- **Project is Open-Source:** Yes/No -- **Project was part of Token sale:** Yes/No -- **Repository where Project resides:** https://github.com// -> Please only answer Yes or No to the Open-Source or Token sale questions. Do not explain more on that line. You may delete this line and all lines that begin with `>` from your application. - -## Contact - -- **Contact Name:** Full name of the contact person in your team -- **Contact Email:** myemail@mycompany.com -- **Website:** https://yourwebsite.com - -> ⚠️ *The combination of your GitHub account submitting the application and the EOS account address above will be your unique identifier during the program. Please keep them safe.* - -## Project Overview - -> If this is an application for a follow-up grant (the continuation of an earlier, successful ENF grant), please provide name and/or pull request of said grant on the first line of this section. - -### Overview - -> Please provide the following: - -- **Name:** If the name of your project is not descriptive, a tag line (one sentence summary). -- **Brief Description:** A brief description of your project. -- **Relationship to EOS Network / Antelope:** An indication of how your project relates to / integrates into the EOS Network or Antelope software. -- **Reason for Interest:** 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): - -- Mock-ups/designs of any UI components -- Data models of the core functionality -- 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 - -### Ecosystem Fit - -> Help us locate your project in the EOS Network 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 (chain/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 EOS Network / Antelope ecosystem? - - If so, how is your project different? - - If not, are there similar projects in related ecosystems? - -## Team - -### Team members - -- **Team Leader:** Name of team leader -- Name of team member 1 -- Name of team member 2 -- Name of team member 3, etc. - -### Legal Structure -- **Registered Legal Entity:** Name of your registered legal entity. (e.g. Greymass, Inc.) -- **Registered Address:** Address of your registered legal entity. Please keep it in a single line. (e.g. 123 Main Street, London LK1 234, UK) - -### Team 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. For research-related grants, references to past publications and projects in a related domain are helpful. If you applied for a Pomelo grant in the past, please be sure you listed them in the section above and mention them in detail in this section. - -> If anyone on your team has applied for a grant at the EOS Network Foundation previously, please list the name of the project and legal entity here. - -### Team Org Repos - -- https://github.com/ -- 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. - -### Team Member Repos - -- https://github.com/ -- https://github.com/ - -### Team LinkedIn Profiles (if available) - -- https://www.linkedin.com/in/ -- https://www.linkedin.com/in/ - -## Development Status - -> 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/eosnetworkfoundation/grant-framework/tree/main/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 EOS Network Foundation, -- previous interface iterations, such as mock-ups and wireframes. - -## Development Roadmap - -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/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 the EOS ecosystem. We _recommend_ that teams structure their roadmap as 1 milestone ≈ 1 month. - -For each milestone, - -- make sure to include a specification of your software. _Treat it as a contract_; the level of detail must be enough to later verify that the software meets the specification. -- include the amount of funding requested _per milestone_. -- include documentation (tutorials, API specifications, architecture diagrams, whatever is appropriate) in each milestone. This ensures that the code can be widely used by the community. -- provide a test suite, comprising unit and integration tests, along with a guide on how to set up and run them. -- commit to providing Dockerfiles for the delivery of your project. -- indicate milestone duration as well as number of full-time employees working on each milestone. -- **Deliverables 0a-0c are mandatory for all milestones**, and deliverable 0e at least for the last one. If you do not intend to deliver one of these, please state a reason in its specification (e.g. Milestone X is research oriented and as such there is no code to test). - -> :zap: If any of your deliverables is based on someone 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.** - -### Milestone Summary - -> Note: the numbers in the three lines below are examples. Please replace with your own calculations! Then delete this instruction line. -> You **must** keep these three Milestone Summary lines below for your grant to be approved. The Total Cost should add up to the costs -> of all of your Milestones. Please **DO NOT** remove the three lines below. If you do, your grant will be rejected or delayed while you fix it. -- **Total Estimated Duration:** 2 months -- **Full-Time Equivalent (FTE):** 2 FTE -- **Total Costs:** 12,000 USD - -> Please note that this application is automatically parsed.
-> For the above fields, please only put the answer on that line. If you want to add more information, please put it below these instructions.
-> Please remember to delete all lines that start with `>` as they are just instructions and not needed in the application submission.
-> -> Notes on above fields: -> - Total Estimated Duration: Duration of the whole project (example: 2 months or 7 weeks) -> - Full-Time Equivalent (FTE): This is the average number of full-time employees working on the project throughout its duration (see [Wikipedia](https://en.wikipedia.org/wiki/Full-time_equivalent), example: 2 FTE or possibly 2.5 FTE as it is an average) -> - Total Costs: This should be the requested amount in USD for the whole project (example 12,000 USD). Note that the acceptance criteria and additional benefits vary depending on the [level](../README.md#grant-levels) of funding requested. This and the costs for each milestone need to be provided in USD; if the grant is paid out in EOS, the amount will be calculated according to the exchange rate at the time of payment. - -### Milestone 1 Example — Implement EOS Application - -- **Estimated duration:** 1 month -- **FTE:** 2 -- **Costs:** 8,000 USD - -| ID | Deliverable | Specification | -| ----- | ----------- | ------------- | -| 0a. | License | MIT / Apache 2.0 / GPLv3 / 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 EOS nodes and send test transactions, which will show how the new functionality works. | -| 0c. | Testing Guide | Core functions will be fully covered by 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. | Application interface to Antelope | We will create an integration layer ... (Please list the functionality that will be implemented for the first milestone) | -| 2. | Front-End / User Interface | We will create a UI that connects to ... | -| 3. | Caching layer | We will create a caching layer ... | -| 4. | API interface to our app | We will create an API that ... | - - - -### Milestone 2 Example — Additional features - -- **Estimated Duration:** 1 month -- **FTE:** 2 -- **Costs:** 4,000 USD - -| ID | Deliverable | Specification | -| ----- | ----------- | ------------- | -| 0a. | License | MIT / Apache 2.0 / GPLv3 / 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 EOS nodes and send test transactions, which will show how the new functionality works. | -| 0c. | Testing Guide | Core functions will be fully covered by 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. | Performance Enhancements | We will create performance enhancements to ... (Please list the functionality that will be implemented for the first milestone) | -| 2. | Added UI functionality | We will add UI functionality to... | -| 3. | Add 3rd Party API integration | We will add 3rd party integration to ... | - - -... Add more milestones as above as needed ... - - -## 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. - - -## Additional Information - -**How did you hear about the Grants Program?** EOS Network 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 a18e9a9064167b3ec8c217598d72284b54218b6d Mon Sep 17 00:00:00 2001 From: LuukDAO <59537248+LuukDAO@users.noreply.github.com> Date: Mon, 21 Aug 2023 16:10:59 +0200 Subject: [PATCH 03/16] Add files via upload --- applications/EOSHub.md | 212 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 212 insertions(+) create mode 100644 applications/EOSHub.md diff --git a/applications/EOSHub.md b/applications/EOSHub.md new file mode 100644 index 00000000..7a6fdb4c --- /dev/null +++ b/applications/EOSHub.md @@ -0,0 +1,212 @@ +# EOS Network Foundation Grant Proposal + +> 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. +> +> See the [Grant Framework Process](https://github.com/eosnetworkfoundation/grant-framework#grant-process-for-new-proposals) on how to submit a proposal. +> +> Please do not remove any of the mandatory lines that start with **bold labels** or as headlines! Your application will be rejected! +> +> Please do not remove the bolding of labels (such as **Bold Label:** ) as it is needed by the automated parsers - that includes the bolding on lines starting with a bullet as part of a list. +> +> Please note that this application will be **automatically parsed**. Please only put the data required in the fields following the bolded labels. +> +> Deleting lines that start with **Bold Labels:** will cause your grant to be rejected! Please fill this out carefully if you want to be approved! +> +> All "comment" lines starting with a `>` (such as this one and the ones above and below) should be removed. + +- **Project Name:** Name of your project (e.g. Anchor Wallet) +- **Team Name:** Legal name of your team (e.g. Greymass, Inc.) +- **EOS Payment Address:** EOS payment address +- **[Level](https://github.com/eosnetworkfoundation/grant-framework#grant-levels):** 1, 2 or 3 +- **Pomelo Grant(s):** List URL(s) to Pomelo grants for your team (or list N/A for non-applicable) +- **Project is Open-Source:** Yes/No +- **Project was part of Token sale:** Yes/No +- **Repository where Project resides:** https://github.com// +> Please only answer Yes or No to the Open-Source or Token sale questions. Do not explain more on that line. You may delete this line and all lines that begin with `>` from your application. + +## Contact + +- **Contact Name:** Full name of the contact person in your team +- **Contact Email:** myemail@mycompany.com +- **Website:** https://yourwebsite.com + +> ⚠️ *The combination of your GitHub account submitting the application and the EOS account address above will be your unique identifier during the program. Please keep them safe.* + +## Project Overview + +> If this is an application for a follow-up grant (the continuation of an earlier, successful ENF grant), please provide name and/or pull request of said grant on the first line of this section. + +### Overview + +> Please provide the following: + +- **Name:** If the name of your project is not descriptive, a tag line (one sentence summary). +- **Brief Description:** A brief description of your project. +- **Relationship to EOS Network / Antelope:** An indication of how your project relates to / integrates into the EOS Network or Antelope software. +- **Reason for Interest:** 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): + +- Mock-ups/designs of any UI components +- Data models of the core functionality +- 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 + +### Ecosystem Fit + +> Help us locate your project in the EOS Network 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 (chain/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 EOS Network / Antelope ecosystem? + - If so, how is your project different? + - If not, are there similar projects in related ecosystems? + +## Team + +### Team members + +- **Team Leader:** Name of team leader +- Name of team member 1 +- Name of team member 2 +- Name of team member 3, etc. + +### Legal Structure +- **Registered Legal Entity:** Name of your registered legal entity. (e.g. Greymass, Inc.) +- **Registered Address:** Address of your registered legal entity. Please keep it in a single line. (e.g. 123 Main Street, London LK1 234, UK) + +### Team 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. For research-related grants, references to past publications and projects in a related domain are helpful. If you applied for a Pomelo grant in the past, please be sure you listed them in the section above and mention them in detail in this section. + +> If anyone on your team has applied for a grant at the EOS Network Foundation previously, please list the name of the project and legal entity here. + +### Team Org Repos + +- https://github.com/ +- 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. + +### Team Member Repos + +- https://github.com/ +- https://github.com/ + +### Team LinkedIn Profiles (if available) + +- https://www.linkedin.com/in/ +- https://www.linkedin.com/in/ + +## Development Status + +> 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/eosnetworkfoundation/grant-framework/tree/main/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 EOS Network Foundation, +- previous interface iterations, such as mock-ups and wireframes. + +## Development Roadmap + +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/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 the EOS ecosystem. We _recommend_ that teams structure their roadmap as 1 milestone ≈ 1 month. + +For each milestone, + +- make sure to include a specification of your software. _Treat it as a contract_; the level of detail must be enough to later verify that the software meets the specification. +- include the amount of funding requested _per milestone_. +- include documentation (tutorials, API specifications, architecture diagrams, whatever is appropriate) in each milestone. This ensures that the code can be widely used by the community. +- provide a test suite, comprising unit and integration tests, along with a guide on how to set up and run them. +- commit to providing Dockerfiles for the delivery of your project. +- indicate milestone duration as well as number of full-time employees working on each milestone. +- **Deliverables 0a-0c are mandatory for all milestones**, and deliverable 0e at least for the last one. If you do not intend to deliver one of these, please state a reason in its specification (e.g. Milestone X is research oriented and as such there is no code to test). + +> :zap: If any of your deliverables is based on someone 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.** + +### Milestone Summary + +> Note: the numbers in the three lines below are examples. Please replace with your own calculations! Then delete this instruction line. +> You **must** keep these three Milestone Summary lines below for your grant to be approved. The Total Cost should add up to the costs +> of all of your Milestones. Please **DO NOT** remove the three lines below. If you do, your grant will be rejected or delayed while you fix it. +- **Total Estimated Duration:** 2 months +- **Full-Time Equivalent (FTE):** 2 FTE +- **Total Costs:** 12,000 USD + +> Please note that this application is automatically parsed.
+> For the above fields, please only put the answer on that line. If you want to add more information, please put it below these instructions.
+> Please remember to delete all lines that start with `>` as they are just instructions and not needed in the application submission.
+> +> Notes on above fields: +> - Total Estimated Duration: Duration of the whole project (example: 2 months or 7 weeks) +> - Full-Time Equivalent (FTE): This is the average number of full-time employees working on the project throughout its duration (see [Wikipedia](https://en.wikipedia.org/wiki/Full-time_equivalent), example: 2 FTE or possibly 2.5 FTE as it is an average) +> - Total Costs: This should be the requested amount in USD for the whole project (example 12,000 USD). Note that the acceptance criteria and additional benefits vary depending on the [level](../README.md#grant-levels) of funding requested. This and the costs for each milestone need to be provided in USD; if the grant is paid out in EOS, the amount will be calculated according to the exchange rate at the time of payment. + +### Milestone 1 Example — Implement EOS Application + +- **Estimated duration:** 1 month +- **FTE:** 2 +- **Costs:** 8,000 USD + +| ID | Deliverable | Specification | +| ----- | ----------- | ------------- | +| 0a. | License | MIT / Apache 2.0 / GPLv3 / 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 EOS nodes and send test transactions, which will show how the new functionality works. | +| 0c. | Testing Guide | Core functions will be fully covered by 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. | Application interface to Antelope | We will create an integration layer ... (Please list the functionality that will be implemented for the first milestone) | +| 2. | Front-End / User Interface | We will create a UI that connects to ... | +| 3. | Caching layer | We will create a caching layer ... | +| 4. | API interface to our app | We will create an API that ... | + + + +### Milestone 2 Example — Additional features + +- **Estimated Duration:** 1 month +- **FTE:** 2 +- **Costs:** 4,000 USD + +| ID | Deliverable | Specification | +| ----- | ----------- | ------------- | +| 0a. | License | MIT / Apache 2.0 / GPLv3 / 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 EOS nodes and send test transactions, which will show how the new functionality works. | +| 0c. | Testing Guide | Core functions will be fully covered by 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. | Performance Enhancements | We will create performance enhancements to ... (Please list the functionality that will be implemented for the first milestone) | +| 2. | Added UI functionality | We will add UI functionality to... | +| 3. | Add 3rd Party API integration | We will add 3rd party integration to ... | + + +... Add more milestones as above as needed ... + + +## 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. + + +## Additional Information + +**How did you hear about the Grants Program?** EOS Network 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 623b41a81825cfbf5f443f0ed68f19ec4ccedf32 Mon Sep 17 00:00:00 2001 From: LuukDAO <59537248+LuukDAO@users.noreply.github.com> Date: Mon, 21 Aug 2023 16:13:06 +0200 Subject: [PATCH 04/16] Update EOSHub.md --- applications/EOSHub.md | 16 ++-------------- 1 file changed, 2 insertions(+), 14 deletions(-) diff --git a/applications/EOSHub.md b/applications/EOSHub.md index 7a6fdb4c..39afde4d 100644 --- a/applications/EOSHub.md +++ b/applications/EOSHub.md @@ -1,18 +1,6 @@ -# EOS Network Foundation Grant Proposal +# EOS Hub Grant Proposal + -> 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. -> -> See the [Grant Framework Process](https://github.com/eosnetworkfoundation/grant-framework#grant-process-for-new-proposals) on how to submit a proposal. -> -> Please do not remove any of the mandatory lines that start with **bold labels** or as headlines! Your application will be rejected! -> -> Please do not remove the bolding of labels (such as **Bold Label:** ) as it is needed by the automated parsers - that includes the bolding on lines starting with a bullet as part of a list. -> -> Please note that this application will be **automatically parsed**. Please only put the data required in the fields following the bolded labels. -> -> Deleting lines that start with **Bold Labels:** will cause your grant to be rejected! Please fill this out carefully if you want to be approved! -> -> All "comment" lines starting with a `>` (such as this one and the ones above and below) should be removed. - **Project Name:** Name of your project (e.g. Anchor Wallet) - **Team Name:** Legal name of your team (e.g. Greymass, Inc.) From 34ae219fe87fa3e313e57f0e60134ca5c0a9834c Mon Sep 17 00:00:00 2001 From: LuukDAO <59537248+LuukDAO@users.noreply.github.com> Date: Mon, 21 Aug 2023 16:15:49 +0200 Subject: [PATCH 05/16] Update EOSHub.md --- applications/EOSHub.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/applications/EOSHub.md b/applications/EOSHub.md index 39afde4d..985652fc 100644 --- a/applications/EOSHub.md +++ b/applications/EOSHub.md @@ -2,15 +2,15 @@ -- **Project Name:** Name of your project (e.g. Anchor Wallet) -- **Team Name:** Legal name of your team (e.g. Greymass, Inc.) -- **EOS Payment Address:** EOS payment address -- **[Level](https://github.com/eosnetworkfoundation/grant-framework#grant-levels):** 1, 2 or 3 -- **Pomelo Grant(s):** List URL(s) to Pomelo grants for your team (or list N/A for non-applicable) -- **Project is Open-Source:** Yes/No -- **Project was part of Token sale:** Yes/No -- **Repository where Project resides:** https://github.com// -> Please only answer Yes or No to the Open-Source or Token sale questions. Do not explain more on that line. You may delete this line and all lines that begin with `>` from your application. +- **Project Name:** EOS Hub +- **Team Name:** Kolektivo Labs +- **EOS Payment Address:** primeratings +- **[Level](https://github.com/eosnetworkfoundation/grant-framework#grant-levels):** 2 +- **Pomelo Grant(s):** https://pomelo.io/grants/eosdashboard +- **Project is Open-Source:** Yes +- **Project was part of Token sale:** No +- **Repository where Project resides:** N.A + ## Contact From ade7b5fd4d580110f6763ecba0334ccef877d39c Mon Sep 17 00:00:00 2001 From: LuukDAO <59537248+LuukDAO@users.noreply.github.com> Date: Mon, 21 Aug 2023 16:18:05 +0200 Subject: [PATCH 06/16] Update EOSHub.md --- applications/EOSHub.md | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/applications/EOSHub.md b/applications/EOSHub.md index 985652fc..154cbc0d 100644 --- a/applications/EOSHub.md +++ b/applications/EOSHub.md @@ -14,19 +14,18 @@ ## Contact -- **Contact Name:** Full name of the contact person in your team -- **Contact Email:** myemail@mycompany.com -- **Website:** https://yourwebsite.com +- **Contact Name:**Luuk Weber +- **Contact Email:** luuk@prime.xyz +- **Website:** [https://yourwebsite.com](https://www.prime.xyz/eosdashboard) + -> ⚠️ *The combination of your GitHub account submitting the application and the EOS account address above will be your unique identifier during the program. Please keep them safe.* ## Project Overview -> If this is an application for a follow-up grant (the continuation of an earlier, successful ENF grant), please provide name and/or pull request of said grant on the first line of this section. + ### Overview -> Please provide the following: - **Name:** If the name of your project is not descriptive, a tag line (one sentence summary). - **Brief Description:** A brief description of your project. From 3fe25c6e2a87f42e62453e7feed71a6e959f224f Mon Sep 17 00:00:00 2001 From: LuukDAO <59537248+LuukDAO@users.noreply.github.com> Date: Mon, 21 Aug 2023 16:22:50 +0200 Subject: [PATCH 07/16] Update EOSHub.md --- applications/EOSHub.md | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/applications/EOSHub.md b/applications/EOSHub.md index 154cbc0d..defc10b8 100644 --- a/applications/EOSHub.md +++ b/applications/EOSHub.md @@ -14,13 +14,24 @@ ## Contact -- **Contact Name:**Luuk Weber +- **Contact Name:** Luuk Weber - **Contact Email:** luuk@prime.xyz - **Website:** [https://yourwebsite.com](https://www.prime.xyz/eosdashboard) ## Project Overview +Our team has already successfully created and launched an EOS ecosystem dashboard in collaboration with Kolektivo Labs and Hypha DAO, which is live and provides a detailed and easy-to-navigate overview of 10+ different EOS & EOS EVM projects. + +After the successful development of the EOS ecosystem dashboard and Pomelo grant participation - we intend to expand the Dashboard into a full fledge EOS Hub. The EOS Ecosystem hub is a standalone platform with it’s own brand and socials that will provide a deepdive on all projects on EOS and EOS EVM, create ecosystem reports and EOS guides. The EOS Hub will provide all EOS stakeholders with a comprehensive overview of the ecosystem projects status and quality. Which helps with curation, grant allocation, partnerships and exploration. + +The EOS hub is free to use and projects reviewed do not have to pay a fee of any kind. EOS native analysts can get involved to help create reports that will shape up the hub - this not only enhances the quality of the hub but also helps EOS native contributors grow. EOS native analysts will be rewarded once a report has been reviewed. All insights will be put together in an EOS Ecosystem Report - an easy-to-digest and highly visual report that can be utilized by existing and potential EOS ecosystem members to get a snapshot of all initiatives and potential of the EOS Network. This comprehensive approach will ensure that we continue to provide valuable resources for the EOS ecosystem. + +An extensive DeFi and DAO infrastructure map which will highlight existing tools and ecosystem initiatives, and identify missing pieces which can help prioritize EOS Ecosystem development. +An overview of the top EOS native projects - This will help existing and potential EOS ecosystem members to better understand project quality to guide their contributions. + + +Looking ahead, we see great potential in establishing an EOS DAO Ecosystem Acceleration program that will leverage our collective network, services, and technology to greatly accelerate DAO and DeFi growth on EOS. Our project will focus on creating the ecosystem insights required to run an effective acceleration program and prioritize product deployment. From 5f2e091562d8fe6607e01b299cae57f34cc78df6 Mon Sep 17 00:00:00 2001 From: LuukDAO <59537248+LuukDAO@users.noreply.github.com> Date: Mon, 21 Aug 2023 17:37:24 +0200 Subject: [PATCH 08/16] Update EOSHub.md --- applications/EOSHub.md | 51 +++++++++++++++++++----------------------- 1 file changed, 23 insertions(+), 28 deletions(-) diff --git a/applications/EOSHub.md b/applications/EOSHub.md index defc10b8..5e4cc97b 100644 --- a/applications/EOSHub.md +++ b/applications/EOSHub.md @@ -21,51 +21,46 @@ ## Project Overview -Our team has already successfully created and launched an EOS ecosystem dashboard in collaboration with Kolektivo Labs and Hypha DAO, which is live and provides a detailed and easy-to-navigate overview of 10+ different EOS & EOS EVM projects. -After the successful development of the EOS ecosystem dashboard and Pomelo grant participation - we intend to expand the Dashboard into a full fledge EOS Hub. The EOS Ecosystem hub is a standalone platform with it’s own brand and socials that will provide a deepdive on all projects on EOS and EOS EVM, create ecosystem reports and EOS guides. The EOS Hub will provide all EOS stakeholders with a comprehensive overview of the ecosystem projects status and quality. Which helps with curation, grant allocation, partnerships and exploration. -The EOS hub is free to use and projects reviewed do not have to pay a fee of any kind. EOS native analysts can get involved to help create reports that will shape up the hub - this not only enhances the quality of the hub but also helps EOS native contributors grow. EOS native analysts will be rewarded once a report has been reviewed. All insights will be put together in an EOS Ecosystem Report - an easy-to-digest and highly visual report that can be utilized by existing and potential EOS ecosystem members to get a snapshot of all initiatives and potential of the EOS Network. This comprehensive approach will ensure that we continue to provide valuable resources for the EOS ecosystem. -An extensive DeFi and DAO infrastructure map which will highlight existing tools and ecosystem initiatives, and identify missing pieces which can help prioritize EOS Ecosystem development. -An overview of the top EOS native projects - This will help existing and potential EOS ecosystem members to better understand project quality to guide their contributions. +### Overview -Looking ahead, we see great potential in establishing an EOS DAO Ecosystem Acceleration program that will leverage our collective network, services, and technology to greatly accelerate DAO and DeFi growth on EOS. Our project will focus on creating the ecosystem insights required to run an effective acceleration program and prioritize product deployment. +- **Name:** EOS Hub +- **Brief Description:** The EOS Hub is a platform designed to enhance the EOS ecosystem by providing a comprehensive and up-to-date resource for EOS and EOS EVM projects. +- **Relationship to EOS Network / Antelope:** The EOS Hub will provide all EOS stakeholders with a comprehensive overview of the ecosystem projects' status and quality. EOS Hub will foster community engagement, streamline EOS ecosystem insights, and offer tools to accelerate DAO and DeFi growth on EOS. +- **Reason for Interest:** As the EOS ecosystem grows, there's a need for a unified platform where projects, developers, and stakeholders can come together. The EOS Hub aims to be that central point of reference, providing a comprehensive overview of EOS projects, tools, and initiatives. +### Project Details +Our team has already successfully created and launched an EOS ecosystem dashboard in collaboration with Kolektivo Labs and Hypha DAO, which is live and provides a detailed and easy-to-navigate overview of 10+ different EOS & EOS EVM projects. -### Overview +After the successful development of the EOS ecosystem dashboard and Pomelo grant participation - we intend to expand the Dashboard into a full fledge EOS Hub. The EOS Ecosystem hub is a standalone platform with it’s own brand and socials that will provide a deepdive on all projects on EOS and EOS EVM, create ecosystem reports and EOS guides. The EOS Hub will provide all EOS stakeholders with a comprehensive overview of the ecosystem projects status and quality. Which helps with curation, grant allocation, partnerships and exploration. +The EOS hub is free to use and projects reviewed do not have to pay a fee of any kind. EOS native analysts can get involved to help create reports that will shape up the hub - this not only enhances the quality of the hub but also helps EOS native contributors grow. EOS native analysts will be rewarded once a report has been reviewed. All insights will be put together in an EOS Ecosystem Report - an easy-to-digest and highly visual report that can be utilized by existing and potential EOS ecosystem members to get a snapshot of all initiatives and potential of the EOS Network. This comprehensive approach will ensure we continue providing valuable resources for the EOS ecosystem. -- **Name:** If the name of your project is not descriptive, a tag line (one sentence summary). -- **Brief Description:** A brief description of your project. -- **Relationship to EOS Network / Antelope:** An indication of how your project relates to / integrates into the EOS Network or Antelope software. -- **Reason for Interest:** An indication of why your team is interested in creating this project. +An extensive DeFi and DAO infrastructure map which will highlight existing tools and ecosystem initiatives, and identify missing pieces which can help prioritize EOS Ecosystem development. +An overview of the top EOS native projects - This will help existing and potential EOS ecosystem members to better understand project quality to guide their contributions. -### Project Details +Eos Hub will also be providing a detailed and easy-to-navigate overview of different EOS & EOS EVM projects. It's designed to improve ecosystem growth and coordination. The Hub API will provide easy and reliable access to all EOS data, including project Ratings and sub-category scores. -> 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): +Looking ahead, we see great potential in establishing an EOS DAO Ecosystem Acceleration program that will leverage our collective network, services, and technology to accelerate DAO and DeFi growth on EOS greatly. Our project will focus on creating the ecosystem insights required to run an effective acceleration program and prioritize product deployment. -- Mock-ups/designs of any UI components -- Data models of the core functionality -- 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 ### Ecosystem Fit -> Help us locate your project in the EOS Network landscape and what problems it tries to solve by answering each of these questions: +Our primary target audience includes EOS blockchain developers, Decentralized Autonomous Organizations (DAOs), dApp developers, EOS wallet users, and participants within the EOS ecosystem. + +Our project serves to address several essential needs within the EOS DAO Ecosystem: + +**Ecosystem Mapping**: By creating a comprehensive ecosystem assessment, we aim to provide a clear, detailed map of the EOS DAO Ecosystem. This would be beneficial to all participants in the ecosystem, helping them better understand the environment and identify opportunities and challenges. + +**Guided Resource Allocation**: The Ecosystem Report will serve as a critical foundation for directing EOS Network resources more effectively. This can help maximize the impact of these resources, promoting growth and innovation within the EOS DAO Ecosystem. + +**Enhanced Understanding**: This project will enhance the understanding of the DAO landscape on the EOS network, supporting its development and maturity. This knowledge could be instrumental for new and existing DAOs, developers, users, and other stakeholders. -- Where and how does your project fit into the ecosystem? -- Who is your target audience (chain/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 EOS Network / Antelope ecosystem? - - If so, how is your project different? - - If not, are there similar projects in related ecosystems? +It appears that there are no direct equivalents to the EOS hub within the EOS and Antelope ecosystem. This makes the project unique and potentially very valuable to the EOS community, as it provides a comprehensive overview of EOS & EOS EVM projects in a way that no other project currently does. The EOS hub shares similarities with a few projects in the broader crypto ecosystem. Baserank is a crowdsourced platform that evaluates the risk of crypto assets based on ratings from various sources. Lastly, Messari is a data aggregator that provides information and ratings on various cryptocurrencies based on their fundamental and technical aspects. ## Team From 4967a732133051e4b090b96472e01125cb484aa7 Mon Sep 17 00:00:00 2001 From: LuukDAO <59537248+LuukDAO@users.noreply.github.com> Date: Mon, 21 Aug 2023 17:42:42 +0200 Subject: [PATCH 09/16] Update EOSHub.md --- applications/EOSHub.md | 60 ++++++++++++++++++++++++++---------------- 1 file changed, 37 insertions(+), 23 deletions(-) diff --git a/applications/EOSHub.md b/applications/EOSHub.md index 5e4cc97b..0c2c2b7d 100644 --- a/applications/EOSHub.md +++ b/applications/EOSHub.md @@ -60,54 +60,68 @@ Our project serves to address several essential needs within the EOS DAO Ecosyst **Enhanced Understanding**: This project will enhance the understanding of the DAO landscape on the EOS network, supporting its development and maturity. This knowledge could be instrumental for new and existing DAOs, developers, users, and other stakeholders. -It appears that there are no direct equivalents to the EOS hub within the EOS and Antelope ecosystem. This makes the project unique and potentially very valuable to the EOS community, as it provides a comprehensive overview of EOS & EOS EVM projects in a way that no other project currently does. The EOS hub shares similarities with a few projects in the broader crypto ecosystem. Baserank is a crowdsourced platform that evaluates the risk of crypto assets based on ratings from various sources. Lastly, Messari is a data aggregator that provides information and ratings on various cryptocurrencies based on their fundamental and technical aspects. +There are no direct equivalents to the EOS hub within the EOS and Antelope ecosystem. This makes the project unique and potentially very valuable to the EOS community, as it provides a comprehensive overview of EOS & EOS EVM projects in a way that no other project currently does. The EOS hub shares similarities with a few projects in the broader crypto ecosystem. Baserank is a crowdsourced platform that evaluates the risk of crypto assets based on ratings from various sources. Lastly, Messari is a data aggregator that provides information and ratings on various cryptocurrencies based on their fundamental and technical aspects. ## Team ### Team members -- **Team Leader:** Name of team leader -- Name of team member 1 -- Name of team member 2 -- Name of team member 3, etc. +- **Team Leader:** Luuk Weber, Project Manager +-Enrique Badaracco, Digital Designer +- Jash Mirpuri, Senior Analyst ### Legal Structure -- **Registered Legal Entity:** Name of your registered legal entity. (e.g. Greymass, Inc.) -- **Registered Address:** Address of your registered legal entity. Please keep it in a single line. (e.g. 123 Main Street, London LK1 234, UK) +- **Registered Legal Entity:** Prime Development Foundation +- **Registered Address:** President Romule Betancourt Boulevard + ### Team 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. For research-related grants, references to past publications and projects in a related domain are helpful. If you applied for a Pomelo grant in the past, please be sure you listed them in the section above and mention them in detail in this section. +**Luuk Weber** + +Luuk Weber's professional experience showcases his strong background in Web 3, fund management, and entrepreneurship. His involvement in Web 3 is evident through roles such as a Strategist at PrimeDAO, where he contributed to the systemic advancement of DAO tooling. He was also an investment associate at Cycber Capital where he specialized in DeFi, Stablecoins, DAOs, and Tokenomics. Luuk also has experience in fund management at Icoinic Capital, where he managed the DeFi Fund. With all the experience that Luuk developed he decided to start Kolektivo Labs, a Web3 Venture Studio. + +**Enrique Badaracco +** +Enrique began his career in 2017 as an IT Operator, working in various roles that focused on IT Operations and technical support. In 2020, Enrique made a shift in his career by moving into the field of design within the Web 3 space. He took on the role of Digital Designer at Kolektivo Labs in the Netherlands, where he honed his skills in creative ideation, graphic design, web design, and branding. + +**Jash Mirpuri +** +Jash Mirpuri, after obtaining his master's degree in Financial Economics, embarked on his professional journey as an Analyst in portfolio management, where he spent a year and a month honing his skills. Following this experience, he transitioned into Investment Banking, serving as a Junior Analyst in Rotterdam, Zuid-Holland, Netherlands, for five months. This role allowed him to further develop his analytical abilities within the financial sector. Later, Jash made a significant career move by entering the Web 3 space. -> If anyone on your team has applied for a grant at the EOS Network Foundation previously, please list the name of the project and legal entity here. +This team has worked on varios projects in the passed, including building out PrimeDAO and Kolektivo, and supporting Balancer, dHedge, and Celo. **** ### Team Org Repos -- https://github.com/ -- https://github.com// -- https://github.com// +- https://github.com/PrimeDAO +- https://github.com/Kolektivo + > 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. ### Team Member Repos -- https://github.com/ -- https://github.com/ - +- N.A ### Team LinkedIn Profiles (if available) -- https://www.linkedin.com/in/ -- https://www.linkedin.com/in/ +- https://www.linkedin.com/in/luukweber/ +- https://www.linkedin.com/in/enriquebadaracco/ +- https://www.linkedin.com/in/jaswant-mirpuri-1b67211b7/ ## Development Status -> 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/eosnetworkfoundation/grant-framework/tree/main/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 EOS Network Foundation, -- previous interface iterations, such as mock-ups and wireframes. +- ttps://forum.gnosis.io/t/draft-should-gnosisdao-fund-gnosis-chain-ecosystem-analysis-and-dashboard/5975 +- https://twitter.com/HyphaDAO/status/1673662474237648898?s=20 +- https://mautic.hypha.earth/email/preview/49 +- https://blog.refidao.com/refi-deep-dive-refi-rate-athon/ +- https://medium.com/primedao/the-primerating-metaverse-rate-a-thon-is-coming-8d7af84d3a8b +- https://medium.com/primedao/research-on-demand-by-prime-rating-b96873d79b7c?source=user_profile---------14---------------------------- +- https://medium.com/primedao/prime-rating-season-two-is-coming-f691ddc37b84?source=user_profile---------27---------------------------- +- https://medium.com/primedao/new-prime-rating-web-app-goes-live-with-over-125-reports-from-20-raters-8cf4e302d0e5?source=user_profile---------37---------------------------- +- https://medium.com/primedao/new-prime-rating-web-app-goes-live-with-over-125-reports-from-20-raters-8cf4e302d0e5?source=user_profile---------37---------------------------- +- https://medium.com/primedao/game-on-introducing-prime-rating-season-one-65476aa0fc6d?source=user_profile---------39---------------------------- + ## Development Roadmap From 86e8d00cbc09803bf1ee443de869b9372056435d Mon Sep 17 00:00:00 2001 From: LuukDAO <59537248+LuukDAO@users.noreply.github.com> Date: Mon, 21 Aug 2023 17:44:45 +0200 Subject: [PATCH 10/16] Update EOSHub.md --- applications/EOSHub.md | 36 ++++++++++++++++++------------------ 1 file changed, 18 insertions(+), 18 deletions(-) diff --git a/applications/EOSHub.md b/applications/EOSHub.md index 0c2c2b7d..3aa015bb 100644 --- a/applications/EOSHub.md +++ b/applications/EOSHub.md @@ -81,15 +81,15 @@ There are no direct equivalents to the EOS hub within the EOS and Antelope ecosy Luuk Weber's professional experience showcases his strong background in Web 3, fund management, and entrepreneurship. His involvement in Web 3 is evident through roles such as a Strategist at PrimeDAO, where he contributed to the systemic advancement of DAO tooling. He was also an investment associate at Cycber Capital where he specialized in DeFi, Stablecoins, DAOs, and Tokenomics. Luuk also has experience in fund management at Icoinic Capital, where he managed the DeFi Fund. With all the experience that Luuk developed he decided to start Kolektivo Labs, a Web3 Venture Studio. -**Enrique Badaracco -** +**Enrique Badaracco ** + Enrique began his career in 2017 as an IT Operator, working in various roles that focused on IT Operations and technical support. In 2020, Enrique made a shift in his career by moving into the field of design within the Web 3 space. He took on the role of Digital Designer at Kolektivo Labs in the Netherlands, where he honed his skills in creative ideation, graphic design, web design, and branding. -**Jash Mirpuri -** +**Jash Mirpuri** + Jash Mirpuri, after obtaining his master's degree in Financial Economics, embarked on his professional journey as an Analyst in portfolio management, where he spent a year and a month honing his skills. Following this experience, he transitioned into Investment Banking, serving as a Junior Analyst in Rotterdam, Zuid-Holland, Netherlands, for five months. This role allowed him to further develop his analytical abilities within the financial sector. Later, Jash made a significant career move by entering the Web 3 space. -This team has worked on varios projects in the passed, including building out PrimeDAO and Kolektivo, and supporting Balancer, dHedge, and Celo. **** +This team has worked on varios projects in the passed, including building out PrimeDAO and Kolektivo, and supporting Balancer, dHedge, and Celo. ### Team Org Repos @@ -97,12 +97,13 @@ This team has worked on varios projects in the passed, including building out Pr - https://github.com/Kolektivo -> 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. + ### Team Member Repos - N.A -### Team LinkedIn Profiles (if available) + +### Team LinkedIn Profiles - https://www.linkedin.com/in/luukweber/ - https://www.linkedin.com/in/enriquebadaracco/ @@ -125,21 +126,20 @@ This team has worked on varios projects in the passed, including building out Pr ## Development Roadmap -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/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. +Over the course of 4 months, with the dedicated effort of 3 full-time equivalents (FTEs), and a total budget of 35,000 USD, we plan to accomplish significant milestones that will enhance the EOS ecosystem. + +We will kick off our project by building upon our existing work where we have already assessed 15 projects on EOS using our proven methodology, these can be seen here. This forms the foundation of our first milestone, where we will develop a comprehensive DeFi and DAO infrastructure map for the EOS ecosystem. This map will highlight existing tools and initiatives and identify gaps that can inform future EOS Ecosystem spending. + +Moving into the second milestone, we will enhance the EOS Dashboard by adding new features and improving its user interface. We will also expand the scope of the dashboard by adding new EOS and EOS EVM projects. To engage the community and generate a wealth of project reports, we will host an EOS Rate-a-thon, a community initiative that rewards participants for their contributions. In the third milestone, we will continue to refine the EOS Dashboard with updates and the addition of more new EOS and EOS EVM projects. To maintain community engagement and continue the momentum of report generation, we will host another EOS Rate-a-thon. + +Finally, in the fourth milestone, we will consolidate all the insights gathered over the course of the project into a comprehensive yet easy-to-digest EOS Ecosystem Report. This highly visual report will serve as a valuable tool for both existing and potential EOS ecosystem members, providing a snapshot of all initiatives and the untapped potential of the EOS Network. Through these milestones, we aim to significantly enhance the EOS ecosystem by providing a comprehensive and up-to-date resource for EOS and EOS EVM projects, fostering community engagement, and delivering a valuable EOS Ecosystem Report. -Below we provide an **example roadmap**. In the descriptions, it should be clear how your project is related to the EOS ecosystem. We _recommend_ that teams structure their roadmap as 1 milestone ≈ 1 month. -For each milestone, +- Total Estimated Duration: 4 months +- Full-Time Equivalent (FTE): 3 FTE +- Total Costs: 35,000 USD -- make sure to include a specification of your software. _Treat it as a contract_; the level of detail must be enough to later verify that the software meets the specification. -- include the amount of funding requested _per milestone_. -- include documentation (tutorials, API specifications, architecture diagrams, whatever is appropriate) in each milestone. This ensures that the code can be widely used by the community. -- provide a test suite, comprising unit and integration tests, along with a guide on how to set up and run them. -- commit to providing Dockerfiles for the delivery of your project. -- indicate milestone duration as well as number of full-time employees working on each milestone. -- **Deliverables 0a-0c are mandatory for all milestones**, and deliverable 0e at least for the last one. If you do not intend to deliver one of these, please state a reason in its specification (e.g. Milestone X is research oriented and as such there is no code to test). -> :zap: If any of your deliverables is based on someone 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.** ### Milestone Summary From 1b0cfda7b028a68d2150f3dffa2dbaaca90bca6a Mon Sep 17 00:00:00 2001 From: LuukDAO <59537248+LuukDAO@users.noreply.github.com> Date: Mon, 21 Aug 2023 17:51:07 +0200 Subject: [PATCH 11/16] Update EOSHub.md --- applications/EOSHub.md | 56 +++++++++++++++--------------------------- 1 file changed, 20 insertions(+), 36 deletions(-) diff --git a/applications/EOSHub.md b/applications/EOSHub.md index 3aa015bb..a5fb62e5 100644 --- a/applications/EOSHub.md +++ b/applications/EOSHub.md @@ -126,56 +126,40 @@ This team has worked on varios projects in the passed, including building out Pr ## Development Roadmap -Over the course of 4 months, with the dedicated effort of 3 full-time equivalents (FTEs), and a total budget of 35,000 USD, we plan to accomplish significant milestones that will enhance the EOS ecosystem. - -We will kick off our project by building upon our existing work where we have already assessed 15 projects on EOS using our proven methodology, these can be seen here. This forms the foundation of our first milestone, where we will develop a comprehensive DeFi and DAO infrastructure map for the EOS ecosystem. This map will highlight existing tools and initiatives and identify gaps that can inform future EOS Ecosystem spending. - -Moving into the second milestone, we will enhance the EOS Dashboard by adding new features and improving its user interface. We will also expand the scope of the dashboard by adding new EOS and EOS EVM projects. To engage the community and generate a wealth of project reports, we will host an EOS Rate-a-thon, a community initiative that rewards participants for their contributions. In the third milestone, we will continue to refine the EOS Dashboard with updates and the addition of more new EOS and EOS EVM projects. To maintain community engagement and continue the momentum of report generation, we will host another EOS Rate-a-thon. - -Finally, in the fourth milestone, we will consolidate all the insights gathered over the course of the project into a comprehensive yet easy-to-digest EOS Ecosystem Report. This highly visual report will serve as a valuable tool for both existing and potential EOS ecosystem members, providing a snapshot of all initiatives and the untapped potential of the EOS Network. Through these milestones, we aim to significantly enhance the EOS ecosystem by providing a comprehensive and up-to-date resource for EOS and EOS EVM projects, fostering community engagement, and delivering a valuable EOS Ecosystem Report. +### Milestone Summary -- Total Estimated Duration: 4 months -- Full-Time Equivalent (FTE): 3 FTE -- Total Costs: 35,000 USD +- **Total Estimated Duration:** 4 months +- **Full-Time Equivalent (FTE):** 3 FTE +- **Total Costs:** 35,000 USD +Over the course of 4 months, with the dedicated effort of 3 full-time equivalents (FTEs), and a total budget of 35,000 USD, we plan to accomplish significant milestones that will enhance the EOS ecosystem. We will kick off our project by building upon our existing work where we have already assessed 15 projects on EOS using our proven methodology, these can be seen here. This forms the foundation of our first milestone, where we will develop a comprehensive DeFi and DAO infrastructure map for the EOS ecosystem. This map will highlight existing tools and initiatives and identify gaps that can inform future EOS Ecosystem spending. -### Milestone Summary +Moving into the second milestone, we will enhance the EOS Dashboard by adding new features and improving its user interface. We will also expand the scope of the dashboard by adding new EOS and EOS EVM projects. In the third milestone, we will host an EOS Rate-a-thon, a community initiative that rewards participants for their contributions. -> Note: the numbers in the three lines below are examples. Please replace with your own calculations! Then delete this instruction line. -> You **must** keep these three Milestone Summary lines below for your grant to be approved. The Total Cost should add up to the costs -> of all of your Milestones. Please **DO NOT** remove the three lines below. If you do, your grant will be rejected or delayed while you fix it. -- **Total Estimated Duration:** 2 months -- **Full-Time Equivalent (FTE):** 2 FTE -- **Total Costs:** 12,000 USD +Finally, in the fourth milestone, we will consolidate all the insights gathered over the course of the project into a comprehensive yet easy-to-digest EOS Ecosystem Report. This highly visual report will serve as a valuable tool for both existing and potential EOS ecosystem members, providing a snapshot of all initiatives and the untapped potential of the EOS Network. Through these milestones, we aim to significantly enhance the EOS ecosystem by providing a comprehensive and up-to-date resource for EOS and EOS EVM projects, fostering community engagement, and delivering a valuable EOS Ecosystem Report. -> Please note that this application is automatically parsed.
-> For the above fields, please only put the answer on that line. If you want to add more information, please put it below these instructions.
-> Please remember to delete all lines that start with `>` as they are just instructions and not needed in the application submission.
-> -> Notes on above fields: -> - Total Estimated Duration: Duration of the whole project (example: 2 months or 7 weeks) -> - Full-Time Equivalent (FTE): This is the average number of full-time employees working on the project throughout its duration (see [Wikipedia](https://en.wikipedia.org/wiki/Full-time_equivalent), example: 2 FTE or possibly 2.5 FTE as it is an average) -> - Total Costs: This should be the requested amount in USD for the whole project (example 12,000 USD). Note that the acceptance criteria and additional benefits vary depending on the [level](../README.md#grant-levels) of funding requested. This and the costs for each milestone need to be provided in USD; if the grant is paid out in EOS, the amount will be calculated according to the exchange rate at the time of payment. -### Milestone 1 Example — Implement EOS Application +### Milestone 1 Example — Deployment of EOS Hub - **Estimated duration:** 1 month - **FTE:** 2 -- **Costs:** 8,000 USD +- **Costs:** 12,500 USD | ID | Deliverable | Specification | | ----- | ----------- | ------------- | -| 0a. | License | MIT / Apache 2.0 / GPLv3 / 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 EOS nodes and send test transactions, which will show how the new functionality works. | -| 0c. | Testing Guide | Core functions will be fully covered by 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. | Application interface to Antelope | We will create an integration layer ... (Please list the functionality that will be implemented for the first milestone) | -| 2. | Front-End / User Interface | We will create a UI that connects to ... | -| 3. | Caching layer | We will create a caching layer ... | -| 4. | API interface to our app | We will create an API that ... | +| 0a. | License | MIT | +| 0b. | Documentation | Comprehensive documentation will be provided, detailing the architecture, functionalities, and features of the EOS Hub. This will serve as a guide for developers and users to understand the platform's workings and its significance in the EOS ecosystem. | +| 0c. | Testing Guide | +A detailed guide will be made available, outlining the steps and procedures to test all functionalities of the EOS Hub. This ensures that the platform remains robust and reliable, meeting the standards set for its operation. | +| 0d. | Docker | N.A | +| 0e. | Article | +An article will be published introducing the EOS Hub, its features, and its significance to the EOS ecosystem. This will serve as a public announcement and overview of the platform's capabilities. ] +| 1. | Application interface to Antelope | N.A | +| 2. | Front-End / User Interface | The user interface of the EOS Hub will be deployed, designed to offer a responsive and intuitive user experience. This frontend will serve as the primary interaction point for users, ensuring they can navigate and access the platform's features with ease.| +| 3. | Caching layer | N.A | +| 4. | API interface to our app | We will create an API that allows third-party applications to interact with the EOS Dashboard. | From bef36c65b7389a08ce06f4de73d9ed2dd9c29e73 Mon Sep 17 00:00:00 2001 From: LuukDAO <59537248+LuukDAO@users.noreply.github.com> Date: Mon, 21 Aug 2023 17:52:47 +0200 Subject: [PATCH 12/16] Update EOSHub.md --- applications/EOSHub.md | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/applications/EOSHub.md b/applications/EOSHub.md index a5fb62e5..9180bd74 100644 --- a/applications/EOSHub.md +++ b/applications/EOSHub.md @@ -81,7 +81,7 @@ There are no direct equivalents to the EOS hub within the EOS and Antelope ecosy Luuk Weber's professional experience showcases his strong background in Web 3, fund management, and entrepreneurship. His involvement in Web 3 is evident through roles such as a Strategist at PrimeDAO, where he contributed to the systemic advancement of DAO tooling. He was also an investment associate at Cycber Capital where he specialized in DeFi, Stablecoins, DAOs, and Tokenomics. Luuk also has experience in fund management at Icoinic Capital, where he managed the DeFi Fund. With all the experience that Luuk developed he decided to start Kolektivo Labs, a Web3 Venture Studio. -**Enrique Badaracco ** +**Enrique Badaracco** Enrique began his career in 2017 as an IT Operator, working in various roles that focused on IT Operations and technical support. In 2020, Enrique made a shift in his career by moving into the field of design within the Web 3 space. He took on the role of Digital Designer at Kolektivo Labs in the Netherlands, where he honed his skills in creative ideation, graphic design, web design, and branding. @@ -150,14 +150,12 @@ Finally, in the fourth milestone, we will consolidate all the insights gathered | ID | Deliverable | Specification | | ----- | ----------- | ------------- | | 0a. | License | MIT | -| 0b. | Documentation | Comprehensive documentation will be provided, detailing the architecture, functionalities, and features of the EOS Hub. This will serve as a guide for developers and users to understand the platform's workings and its significance in the EOS ecosystem. | -| 0c. | Testing Guide | -A detailed guide will be made available, outlining the steps and procedures to test all functionalities of the EOS Hub. This ensures that the platform remains robust and reliable, meeting the standards set for its operation. | +| 0b. | Documentation | Documenation will serve as a guide for developers and users to understand the platform's workings and its significance in the EOS ecosystem. | +| 0c. | Testing Guide | The testing guide ensures that the platform remains robust and reliable, meeting the standards set for its operation. | | 0d. | Docker | N.A | -| 0e. | Article | -An article will be published introducing the EOS Hub, its features, and its significance to the EOS ecosystem. This will serve as a public announcement and overview of the platform's capabilities. ] +| 0e. | Article | An article will be published introducing the EOS Hub, its features, and its significance to the EOS ecosystem. This will serve as a public announcement and overview of the platform's capabilities. ] | 1. | Application interface to Antelope | N.A | -| 2. | Front-End / User Interface | The user interface of the EOS Hub will be deployed, designed to offer a responsive and intuitive user experience. This frontend will serve as the primary interaction point for users, ensuring they can navigate and access the platform's features with ease.| +| 2. | Front-End / User Interface | The user interface of the EOS Hub will be deployed, designed to offer a responsive and intuitive user experience.| | 3. | Caching layer | N.A | | 4. | API interface to our app | We will create an API that allows third-party applications to interact with the EOS Dashboard. | From 717106818f9ee9d5e2b04fa2128ac0d7db30888a Mon Sep 17 00:00:00 2001 From: LuukDAO <59537248+LuukDAO@users.noreply.github.com> Date: Mon, 21 Aug 2023 21:57:34 +0200 Subject: [PATCH 13/16] Update EOSHub.md --- applications/EOSHub.md | 70 +++++++++++++++++++++++++++++++++--------- 1 file changed, 56 insertions(+), 14 deletions(-) diff --git a/applications/EOSHub.md b/applications/EOSHub.md index 9180bd74..504e3e1b 100644 --- a/applications/EOSHub.md +++ b/applications/EOSHub.md @@ -141,7 +141,7 @@ Moving into the second milestone, we will enhance the EOS Dashboard by adding ne Finally, in the fourth milestone, we will consolidate all the insights gathered over the course of the project into a comprehensive yet easy-to-digest EOS Ecosystem Report. This highly visual report will serve as a valuable tool for both existing and potential EOS ecosystem members, providing a snapshot of all initiatives and the untapped potential of the EOS Network. Through these milestones, we aim to significantly enhance the EOS ecosystem by providing a comprehensive and up-to-date resource for EOS and EOS EVM projects, fostering community engagement, and delivering a valuable EOS Ecosystem Report. -### Milestone 1 Example — Deployment of EOS Hub +### Milestone 1 — Deployment of EOS Hub - **Estimated duration:** 1 month - **FTE:** 2 @@ -161,25 +161,67 @@ Finally, in the fourth milestone, we will consolidate all the insights gathered -### Milestone 2 Example — Additional features +### Milestone 2 — EOS Hub growth through additional projects and maintenance -- **Estimated Duration:** 1 month -- **FTE:** 2 -- **Costs:** 4,000 USD + +- **Estimated duration:** 1 month +- **FTE:** 3 +- **Costs:** 5,000 USD | ID | Deliverable | Specification | | ----- | ----------- | ------------- | -| 0a. | License | MIT / Apache 2.0 / GPLv3 / 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 EOS nodes and send test transactions, which will show how the new functionality works. | -| 0c. | Testing Guide | Core functions will be fully covered by 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. | Performance Enhancements | We will create performance enhancements to ... (Please list the functionality that will be implemented for the first milestone) | -| 2. | Added UI functionality | We will add UI functionality to... | -| 3. | Add 3rd Party API integration | We will add 3rd party integration to ... | +| 0a. | License | MIT | +| 0b. | Documentation | We will enhance the EOS Hub by adding new features and improving its user interface. We will also add new EOS and EOS EVM projects to the dashboard. | +| 0c. | Testing Guide | A detailed guide will be made available, outlining the steps and procedures to test all functionalities of the EOS Hub. | +| 0d. | Docker | N.A | +| 0e. | Article | An article will be published introducing the new projects and new features ] +| 1. | Application interface to Antelope | N.A | +| 2. | Front-End / User Interface | This frontend updates will serve as the primary interaction point for users, ensuring they can navigate and access the platform's features with ease.| +| 3. | Caching layer | N.A | +| 4. | API interface to our app | We will create an API that allows third-party applications to interact with the EOS Dashboard. | + + +### Milestone 3 — EOS Rate-a-thon + + +- **Estimated duration:** 1 month +- **FTE:** 3 +- **Costs:** 12,500 USD + +| ID | Deliverable | Specification | +| ----- | ----------- | ------------- | +| 0a. | License | MIT | +| 0b. | Documentation | We will also host an EOS Rate-a-thon to continue engaging the community and producing more project reports. Participants will be rewarded for their contributions. | +| 0c. | Testing Guide | Validate the updates made to the EOS Hub and the written content of the rate-a-thon | +| 0d. | Docker | N.A | +| 0e. | Article | We will publish an article summarizing the outcomes of the EOS Rate-a-thon. ] +| 1. | Application interface to Antelope | N.A | +| 2. | Front-End / User Interface | The user interface will be updated with the results of the rate-a-thon as well as the analysts| +| 3. | Caching layer | N.A | +| 4. | API interface to our app | We will create an API that allows third-party applications to interact with the EOS Dashboard. | + + +### Milestone 4 Example — EOS Ecosystem Report Compilation + + +- **Estimated duration:** 1 month +- **FTE:** 3 +- **Costs:** 5,000 USD + +| ID | Deliverable | Specification | +| ----- | ----------- | ------------- | +| 0a. | License | MIT | +| 0b. | Documentation | Consolidate all insights into a comprehensive yet easy-to-digest EOS Ecosystem Report. | +| 0c. | Testing Guide | N.A | +| 0d. | Docker | N.A | +| 0e. | Article | We will publish an article summarizing the report as well as displaying our findings. ] +| 1. | Application interface to Antelope | N.A | +| 2. | Front-End / User Interface | The user interface of the EOS Hub will be deployed, designed to offer a responsive and intuitive user experience.| +| 3. | Caching layer | N.A | +| 4. | API interface to our app | We will create an API that allows third-party applications to interact with the EOS Dashboard. | + -... Add more milestones as above as needed ... ## Future Plans From 12322fdd4295b5591203dbed21338e2649b3335f Mon Sep 17 00:00:00 2001 From: LuukDAO <59537248+LuukDAO@users.noreply.github.com> Date: Mon, 21 Aug 2023 21:59:08 +0200 Subject: [PATCH 14/16] Update EOSHub.md --- applications/EOSHub.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/applications/EOSHub.md b/applications/EOSHub.md index 504e3e1b..e6e43d06 100644 --- a/applications/EOSHub.md +++ b/applications/EOSHub.md @@ -144,7 +144,7 @@ Finally, in the fourth milestone, we will consolidate all the insights gathered ### Milestone 1 — Deployment of EOS Hub - **Estimated duration:** 1 month -- **FTE:** 2 +- **FTE:** 3 - **Costs:** 12,500 USD | ID | Deliverable | Specification | @@ -153,7 +153,7 @@ Finally, in the fourth milestone, we will consolidate all the insights gathered | 0b. | Documentation | Documenation will serve as a guide for developers and users to understand the platform's workings and its significance in the EOS ecosystem. | | 0c. | Testing Guide | The testing guide ensures that the platform remains robust and reliable, meeting the standards set for its operation. | | 0d. | Docker | N.A | -| 0e. | Article | An article will be published introducing the EOS Hub, its features, and its significance to the EOS ecosystem. This will serve as a public announcement and overview of the platform's capabilities. ] +| 0e. | Article | An article will be published introducing the EOS Hub, its features, and its significance to the EOS ecosystem. This will serve as a public announcement and overview of the platform's capabilities. | | 1. | Application interface to Antelope | N.A | | 2. | Front-End / User Interface | The user interface of the EOS Hub will be deployed, designed to offer a responsive and intuitive user experience.| | 3. | Caching layer | N.A | @@ -174,7 +174,7 @@ Finally, in the fourth milestone, we will consolidate all the insights gathered | 0b. | Documentation | We will enhance the EOS Hub by adding new features and improving its user interface. We will also add new EOS and EOS EVM projects to the dashboard. | | 0c. | Testing Guide | A detailed guide will be made available, outlining the steps and procedures to test all functionalities of the EOS Hub. | | 0d. | Docker | N.A | -| 0e. | Article | An article will be published introducing the new projects and new features ] +| 0e. | Article | An article will be published introducing the new projects and new features. | | 1. | Application interface to Antelope | N.A | | 2. | Front-End / User Interface | This frontend updates will serve as the primary interaction point for users, ensuring they can navigate and access the platform's features with ease.| | 3. | Caching layer | N.A | @@ -194,7 +194,7 @@ Finally, in the fourth milestone, we will consolidate all the insights gathered | 0b. | Documentation | We will also host an EOS Rate-a-thon to continue engaging the community and producing more project reports. Participants will be rewarded for their contributions. | | 0c. | Testing Guide | Validate the updates made to the EOS Hub and the written content of the rate-a-thon | | 0d. | Docker | N.A | -| 0e. | Article | We will publish an article summarizing the outcomes of the EOS Rate-a-thon. ] +| 0e. | Article | We will publish an article summarizing the outcomes of the EOS Rate-a-thon. | | 1. | Application interface to Antelope | N.A | | 2. | Front-End / User Interface | The user interface will be updated with the results of the rate-a-thon as well as the analysts| | 3. | Caching layer | N.A | @@ -214,7 +214,7 @@ Finally, in the fourth milestone, we will consolidate all the insights gathered | 0b. | Documentation | Consolidate all insights into a comprehensive yet easy-to-digest EOS Ecosystem Report. | | 0c. | Testing Guide | N.A | | 0d. | Docker | N.A | -| 0e. | Article | We will publish an article summarizing the report as well as displaying our findings. ] +| 0e. | Article | We will publish an article summarizing the report as well as displaying our findings. | | 1. | Application interface to Antelope | N.A | | 2. | Front-End / User Interface | The user interface of the EOS Hub will be deployed, designed to offer a responsive and intuitive user experience.| | 3. | Caching layer | N.A | @@ -229,7 +229,7 @@ Finally, in the fourth milestone, we will consolidate all the insights gathered > 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. +- the team's long-term plans and intentions about it. ## Additional Information @@ -239,5 +239,5 @@ Finally, in the fourth milestone, we will consolidate all the insights gathered > 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. +- If any other teams have already contributed (financially) to the project. - Previous grants you may have applied for. From e529738287357908f039fad0485ddc3b345654cf Mon Sep 17 00:00:00 2001 From: LuukDAO <59537248+LuukDAO@users.noreply.github.com> Date: Mon, 21 Aug 2023 22:00:22 +0200 Subject: [PATCH 15/16] Update EOSHub.md --- applications/EOSHub.md | 11 ++--------- 1 file changed, 2 insertions(+), 9 deletions(-) diff --git a/applications/EOSHub.md b/applications/EOSHub.md index e6e43d06..6b0dd545 100644 --- a/applications/EOSHub.md +++ b/applications/EOSHub.md @@ -226,18 +226,11 @@ Finally, in the fourth milestone, we will consolidate all the insights gathered ## 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 about it. +After the completion of these milestones, we plan to continue to scale the EOS Hub even further. Our goal is to add more projects and provide monthly updates to ensure the dashboard remains a valuable and up-to-date resource for the EOS. Based on the outputs of the EOS DAO Ecosystem Map, an EOS DAO Acceleration Program will be made. To support the Resource Coordination and Execution of the Program, several products may be deployed to the EOS EVM, such as a Launch Pad and a Balancer Friendly Fork which will provide the required tools to enhance DAO growth and liquidity onto EOS. ## Additional Information -**How did you hear about the Grants Program?** EOS Network Foundation Website / Medium / Twitter / Element / Announcement by another team / personal recommendation / etc. +**How did you hear about the Grants Program?** Through our partners HyphaDAO -> 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 any other teams have already contributed (financially) to the project. -- Previous grants you may have applied for. From 193cb877e5c95b208856e161496a03e406869a28 Mon Sep 17 00:00:00 2001 From: LuukDAO <59537248+LuukDAO@users.noreply.github.com> Date: Mon, 21 Aug 2023 22:01:06 +0200 Subject: [PATCH 16/16] Update EOSHub.md --- applications/EOSHub.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/applications/EOSHub.md b/applications/EOSHub.md index 6b0dd545..8d3fefd9 100644 --- a/applications/EOSHub.md +++ b/applications/EOSHub.md @@ -1,4 +1,4 @@ -# EOS Hub Grant Proposal +# EOS Network Foundation Grant Proposal