From 43935fde1be6e4c448be58bd96970062b489c174 Mon Sep 17 00:00:00 2001 From: DefiboxTeam Date: Wed, 16 Nov 2022 15:48:02 +0800 Subject: [PATCH 001/170] Defibox_vault.md --- applications/Defibox_vault.md | 106 ++++++++++++++++++++++++++++++++++ 1 file changed, 106 insertions(+) create mode 100644 applications/Defibox_vault.md diff --git a/applications/Defibox_vault.md b/applications/Defibox_vault.md new file mode 100644 index 00000000..511f1e78 --- /dev/null +++ b/applications/Defibox_vault.md @@ -0,0 +1,106 @@ +# EOS Network Foundation Grant Proposal + +- **Project Name:** Vault Protocol +- **Team Name:** Defibox +- **EOS Payment Address:** liquid.defi +- **[Level](https://github.com/eosnetworkfoundation/grant-framework#grant-levels):** 3 +- **Pomelo Grant(s):** https://pomelo.io/grants/vault +- **Project is Open-Source:** No +- **Project was part of Token sale:** No +- **Repository where Project resides:** NA +> 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:** Raven +- **Contact Email:** raven@defibox.io +- **Website:** https://eos.defibox.io/vault + +> ⚠️ *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:** Vault, a decentralized single-token staking protocol +- **Brief Description:** The Vault protocol is the first single-token lossless yield protocol launched by Defibox. Users can earn corresponding token income by depositing tokens. The assets can be flexibly deposited and withdrawn with open and transparent on chain data. Valut income mainly comes from Defibox protocol income, Yield+ rewards, BP income, REX income, etc. At the same time, in order to improve the utility, the protocol will issue a standard EOS token called sToken, which represents a deposit certificate. sToken can be used in multiple DeFi protocols to obtain more benefits. +- **Relationship to EOSIO:** a public use that provides a variety of staking strategies to EOS users and project teams for more yields. Code will be open source after running safely for 1 year. This will contribute to EOSIO repository. +- **Reason for Interest:** It provides a variety of staking strategies to EOS users and project teams for more yields. It will brings TVL and income to Defibox team while giving benefits to participants. Ecosystem Boost: attract inactive EOS tokens which will prosper ecosystem + +### Project Details +https://eos.defibox.io/vault +https://bloks.io/account/vault.defi +Everything is on the website and contract + +### Ecosystem Fit + +> Help us locate your project in the EOSIO landscape and what problems it tries to solve by answering each of these questions: + +- Where and how does your project fit into the ecosystem? Users can earn corresponding token income by depositing tokens. The assets can be flexibly deposited and withdrawn with open and transparent on chain data. Valut income mainly comes from Defibox protocol income, Yield+ rewards, BP income, REX income, etc. At the same time, in order to improve the utility, the protocol will issue a standard EOS token called sToken, which represents a deposit certificate. sToken can be used in multiple DeFi protocols to obtain more benefits. +- Who is your target audience (chain/dapp/wallet/UI developers, designers, your own user base, some dapp's userbase, yourself)? EOS users including any dapp user and project teams +- What need(s) does your project meet? For generating yield and income when holding EOS +- Are there any other projects similar to yours in the EOSIO ecosystem? Yes, BSS from Defibox + - If so, how is your project different? Vault is widely supporting all the users on EOS while BSS is only available for Defibox users who have BOX tokens. + - If not, are there similar projects in related ecosystems? + +## Team + +### Team members + +- **Team Leader:** Eason + + +### Legal Structure +- **Registered Legal Entity:** METABOXTECHNOLOGYPTE.LTD. +- **Registered Address:** 160 ROBINSONROAD #14-04 SINGAPORE (068914) + +### 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. +Defibox team is a full-time team that covers front-end, back-end, contract, operations, testing, and business on EOS, WAX and BSC. We have developed Swap, USN, Lending and many other DeFi protocols on EOS. We have been the leading DeFi on EOS in terms of TVL and running safely over 2 years. Besides this, we also co-developed major projects like Yield+ portal, etc. + +> 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/DefiboxTeam/luckybox +https://github.com/DefiboxTeam/Defibox-document +https://github.com/DefiboxTeam/DefiboxTeam + + +> 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. + + +## Development Status +https://eos.defibox.io/vault +https://bloks.io/account/vault.defi +https://twitter.com/DefiboxOfficial/status/1589907995919781888 + + +### Milestone Summary + +- **Total Estimated Duration:** 3 months +- **Full-Time Equivalent (FTE):** 5 FTE +- **Total Costs:** 12,000 USD + + + +Full launch as milestone reached, 80,000 USD for total cost in which 24,000 USD for security audit fees (already paid) and 56,000 USD for development cost. + + +## Future Plans + +Promote the project with big prize event +Fully support sEOS (vault asset) in all our DeFi protocol + + +## Additional Information + +**How did you hear about the Grants Program?** EOS Network Foundation Website + +**About open source** Open source available when full amount of grant received From 5b4b797ac742bbe0218b7854ddf94950199b15f1 Mon Sep 17 00:00:00 2001 From: DefiboxTeam Date: Wed, 16 Nov 2022 16:07:22 +0800 Subject: [PATCH 002/170] Update Defibox_vault.md --- applications/Defibox_vault.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/applications/Defibox_vault.md b/applications/Defibox_vault.md index 511f1e78..97669c42 100644 --- a/applications/Defibox_vault.md +++ b/applications/Defibox_vault.md @@ -68,7 +68,6 @@ Defibox team is a full-time team that covers front-end, back-end, contract, oper ### Team Org Repos -https://github.com/DefiboxTeam/luckybox https://github.com/DefiboxTeam/Defibox-document https://github.com/DefiboxTeam/DefiboxTeam @@ -79,6 +78,7 @@ https://github.com/DefiboxTeam/DefiboxTeam ## Development Status https://eos.defibox.io/vault https://bloks.io/account/vault.defi +https://bloks.io/account/stoken.defi  https://twitter.com/DefiboxOfficial/status/1589907995919781888 @@ -86,9 +86,7 @@ https://twitter.com/DefiboxOfficial/status/1589907995919781888 - **Total Estimated Duration:** 3 months - **Full-Time Equivalent (FTE):** 5 FTE -- **Total Costs:** 12,000 USD - - +- **Total Costs:** 80,000 USD Full launch as milestone reached, 80,000 USD for total cost in which 24,000 USD for security audit fees (already paid) and 56,000 USD for development cost. From 59693315506c5fdda7be17ec1c213dfc875f213b Mon Sep 17 00:00:00 2001 From: DefiboxTeam Date: Wed, 16 Nov 2022 16:08:08 +0800 Subject: [PATCH 003/170] Update Defibox_vault.md --- applications/Defibox_vault.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/applications/Defibox_vault.md b/applications/Defibox_vault.md index 97669c42..85943a85 100644 --- a/applications/Defibox_vault.md +++ b/applications/Defibox_vault.md @@ -77,8 +77,11 @@ https://github.com/DefiboxTeam/DefiboxTeam ## Development Status https://eos.defibox.io/vault + https://bloks.io/account/vault.defi + https://bloks.io/account/stoken.defi  + https://twitter.com/DefiboxOfficial/status/1589907995919781888 From 5a0a22d04bd2ad446e2ba3b089528328008d2771 Mon Sep 17 00:00:00 2001 From: DefiboxTeam Date: Wed, 16 Nov 2022 16:09:39 +0800 Subject: [PATCH 004/170] Update Defibox_vault.md --- applications/Defibox_vault.md | 20 ++++++++++++++------ 1 file changed, 14 insertions(+), 6 deletions(-) diff --git a/applications/Defibox_vault.md b/applications/Defibox_vault.md index 85943a85..b610879d 100644 --- a/applications/Defibox_vault.md +++ b/applications/Defibox_vault.md @@ -40,12 +40,20 @@ Everything is on the website and contract > Help us locate your project in the EOSIO landscape and what problems it tries to solve by answering each of these questions: -- Where and how does your project fit into the ecosystem? Users can earn corresponding token income by depositing tokens. The assets can be flexibly deposited and withdrawn with open and transparent on chain data. Valut income mainly comes from Defibox protocol income, Yield+ rewards, BP income, REX income, etc. At the same time, in order to improve the utility, the protocol will issue a standard EOS token called sToken, which represents a deposit certificate. sToken can be used in multiple DeFi protocols to obtain more benefits. -- Who is your target audience (chain/dapp/wallet/UI developers, designers, your own user base, some dapp's userbase, yourself)? EOS users including any dapp user and project teams -- What need(s) does your project meet? For generating yield and income when holding EOS -- Are there any other projects similar to yours in the EOSIO ecosystem? Yes, BSS from Defibox - - If so, how is your project different? Vault is widely supporting all the users on EOS while BSS is only available for Defibox users who have BOX tokens. - - If not, are there similar projects in related ecosystems? +- Where and how does your project fit into the ecosystem? +Users can earn corresponding token income by depositing tokens. The assets can be flexibly deposited and withdrawn with open and transparent on chain data. Valut income mainly comes from Defibox protocol income, Yield+ rewards, BP income, REX income, etc. At the same time, in order to improve the utility, the protocol will issue a standard EOS token called sToken, which represents a deposit certificate. sToken can be used in multiple DeFi protocols to obtain more benefits. + +- Who is your target audience (chain/dapp/wallet/UI developers, designers, your own user base, some dapp's userbase, yourself)? +EOS users including any dapp user and project teams + +- What need(s) does your project meet? +For generating yield and income when holding EOS + +- Are there any other projects similar to yours in the EOSIO ecosystem? +Yes, BSS from Defibox + + - If so, how is your project different? +Vault is widely supporting all the users on EOS while BSS is only available for Defibox users who have BOX tokens. ## Team From e8c38da5e3205f35eb0729d8de7e2e626ac30c53 Mon Sep 17 00:00:00 2001 From: DefiboxTeam Date: Thu, 17 Nov 2022 14:20:27 +0800 Subject: [PATCH 005/170] Update Defibox_vault.md --- applications/Defibox_vault.md | 83 +++++++++++++++++++++++++++++++++-- 1 file changed, 80 insertions(+), 3 deletions(-) diff --git a/applications/Defibox_vault.md b/applications/Defibox_vault.md index b610879d..6dab1e22 100644 --- a/applications/Defibox_vault.md +++ b/applications/Defibox_vault.md @@ -28,12 +28,13 @@ - **Name:** Vault, a decentralized single-token staking protocol - **Brief Description:** The Vault protocol is the first single-token lossless yield protocol launched by Defibox. Users can earn corresponding token income by depositing tokens. The assets can be flexibly deposited and withdrawn with open and transparent on chain data. Valut income mainly comes from Defibox protocol income, Yield+ rewards, BP income, REX income, etc. At the same time, in order to improve the utility, the protocol will issue a standard EOS token called sToken, which represents a deposit certificate. sToken can be used in multiple DeFi protocols to obtain more benefits. -- **Relationship to EOSIO:** a public use that provides a variety of staking strategies to EOS users and project teams for more yields. Code will be open source after running safely for 1 year. This will contribute to EOSIO repository. +- **Relationship to EOSIO:** a public use that provides a variety of staking strategies to EOS users and project teams for more yields. Code will be open source for contribution to EOSIO repository. - **Reason for Interest:** It provides a variety of staking strategies to EOS users and project teams for more yields. It will brings TVL and income to Defibox team while giving benefits to participants. Ecosystem Boost: attract inactive EOS tokens which will prosper ecosystem ### Project Details https://eos.defibox.io/vault https://bloks.io/account/vault.defi +https://bloks.io/account/stoken.defi  Everything is on the website and contract ### Ecosystem Fit @@ -76,8 +77,7 @@ Defibox team is a full-time team that covers front-end, back-end, contract, oper ### Team Org Repos -https://github.com/DefiboxTeam/Defibox-document -https://github.com/DefiboxTeam/DefiboxTeam +https://github.com/defiboxswap > 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. @@ -113,3 +113,80 @@ Fully support sEOS (vault asset) in all our DeFi protocol **How did you hear about the Grants Program?** EOS Network Foundation Website **About open source** Open source available when full amount of grant received + + +**Chinese Translation** + +- **项目名称：** 金库协议 (Vault) +- **团队名称：** Defibox +- **EOS支付地址：** liquid.defi +- **等级：** 3 +- **Pomelo资助：** https://pomelo.io/grants/vault +- **项目是开源的：** 否 +- **项目是代币销售的一部分：** 否 +- **项目资源库：** 不适用 + +**联系人** +- **联系人姓名：** Raven +- **联系邮箱：** raven@defibox.io +- **网站：** https://eos.defibox.io/vault + +**项目概况** +**概述** +- **名称：金库协议** + +- **简介：** Vault协议是Defibox推出的第一个单代币无损收益协议。用户可以通过存入代币获得相应的代币收益。资产可灵活存取，链上数据公开透明。 Valut收益主要来自Defibox协议收益、Yield+奖励、BP收益、REX收益等。同时，为了提高效用，协议会发行一个标准的EOS代币sToken，代表存单。 sToken 可以在多种 DeFi 协议中使用以获得更多收益。 +- **与EOSIO的关系：** 一种公共设施，为 EOS用户和项目团队提供各种质押策略以获得更多收益，并提供开源，这将有助于EOSIO代码资源库。 +- **感兴趣的原因：** 它为 EOS 用户和项目团队提供了多种质押策略以获得更多收益。它将为 Defibox 团队带来锁仓量和收入，同时让参与者受益。生态系统提升：吸引不活跃的EOS代币，这将繁荣生态系统。 + +- **项目详情** +-https://eos.defibox.io/vault +-https://bloks.io/account/vault.defi +-https://bloks.io/account/stoken.defi + + +**生态系统** +- **您的项目在哪里以及如何融入生态系统？** +-用户可以通过存入代币获得相应的代币收益。资产可灵活存取，链上数据公开透明。 Valut收益主要来自Defibox协议收益、Yield+奖励、BP收益、REX收益等。同时，为了提高效用，协议会发行一个标准的EOS代币sToken，代表存单。 sToken可以在多种DeFi协议中使用以获得更多收益。 + +- **谁是你的目标受众（链/dapp/钱包/UI 开发人员、设计师、你自己的用户群、一些 dapp 的用户群、你自己）？** +-EOS 用户，包括任何dapp用户和项目团队 + +- **您的项目满足什么需求？** +-持有EOS用于产生收益和收入 + +- **在EOSIO生态系统中还有其他类似的项目吗？** +-有，类似项目有Defibox的BSS + +- **如果是这样，您的项目有何不同？** +-Vault广泛支持EOS上的所有用户，而BSS仅适用于拥有BOX代币的Defibox用户。 + +**团队** +- **团队成员：** 12 +- **团队负责人：** Eason + +**法律结构** +- **注册法律实体：** METABOXTECHNOLOGYPTE.LTD. +- **注册地址：** 160 ROBINSONROAD #14-04 SINGAPORE (068914) + +**团队经验** +-Defibox是一只涵盖EOS、WAX、BSC上前端、后端、合约、运营、测试、商务的专业团队。我们在EOS上开发了Swap、USN、Lending 和许多其他 DeFi 协议。就锁仓量而言，我们一直是EOS上领先的DeFi，并且安全运行了 2 年多。 除此之外，我们还共同开发了Yield+等重大项目。 + +**团队组织** +-https://github.com/defiboxswap + + +**里程碑总结** +- **总预计持续时间：**3 个月 +- **全职当量 (FTE)：**5 FTE +- **总成本：** 80,000 美元，其中 24,000 美元用于安全审计费用，56,000 美元用于开发成本。 + + +**未来的计划** +-高额奖金活动宣传项目，在我们所有的 DeFi 协议中完全支持 sEOS（金库资产） + +**附加信息** + +**您是如何得知赠款计划的？：** EOS网络基金会网站 + +**关于开源：** 收到全额资助后即可开源 From cec8c0cf277d445850aeb08c0085aba2ed0ece80 Mon Sep 17 00:00:00 2001 From: DefiboxTeam Date: Mon, 21 Nov 2022 16:37:42 +0800 Subject: [PATCH 006/170] Update Defibox_vault.md --- applications/Defibox_vault.md | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/applications/Defibox_vault.md b/applications/Defibox_vault.md index 6dab1e22..9fac51fd 100644 --- a/applications/Defibox_vault.md +++ b/applications/Defibox_vault.md @@ -99,7 +99,11 @@ https://twitter.com/DefiboxOfficial/status/1589907995919781888 - **Full-Time Equivalent (FTE):** 5 FTE - **Total Costs:** 80,000 USD -Full launch as milestone reached, 80,000 USD for total cost in which 24,000 USD for security audit fees (already paid) and 56,000 USD for development cost. +- **Deliverables:** +A. Developer documentation: Provide open developer documentation on how to use & integrate Defibox Vault open-source protocol. +B. User tutorials: Provide video & explainers articles for users on how to use Defibox Vault protocol & sTokens. + +Full launch as milestone reached, 80,000 USD for total cost in which 24,000 USD for security audit fees and 56,000 USD for development cost. ## Future Plans @@ -112,7 +116,7 @@ Fully support sEOS (vault asset) in all our DeFi protocol **How did you hear about the Grants Program?** EOS Network Foundation Website -**About open source** Open source available when full amount of grant received +**Open source** Source code made available upon completion of ENF grant **Chinese Translation** @@ -180,7 +184,9 @@ Fully support sEOS (vault asset) in all our DeFi protocol - **总预计持续时间：**3 个月 - **全职当量 (FTE)：**5 FTE - **总成本：** 80,000 美元，其中 24,000 美元用于安全审计费用，56,000 美元用于开发成本。 - +- **可交付成果：** +A. 开发者文档：提供关于如何使用和集成 Defibox Vault 开源协议的开放式开发者文档。 +B. 用户教程：为用户提供有关如何使用 Defibox Vault 协议和 sTokens 的视频和解释文章。 **未来的计划** -高额奖金活动宣传项目，在我们所有的 DeFi 协议中完全支持 sEOS（金库资产） From ec0af045ee500bb92cd7164ecd4d20dbac1f9485 Mon Sep 17 00:00:00 2001 From: DefiboxTeam Date: Wed, 23 Nov 2022 16:37:35 +0800 Subject: [PATCH 007/170] Update Defibox_vault.md --- applications/Defibox_vault.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/applications/Defibox_vault.md b/applications/Defibox_vault.md index 9fac51fd..f9062825 100644 --- a/applications/Defibox_vault.md +++ b/applications/Defibox_vault.md @@ -116,8 +116,10 @@ Fully support sEOS (vault asset) in all our DeFi protocol **How did you hear about the Grants Program?** EOS Network Foundation Website -**Open source** Source code made available upon completion of ENF grant +**Launch Data** 3,000,000 EOS TVL within 53 hours since launch, at the moment, it is 3,400,000 EOS. +![image](https://user-images.githubusercontent.com/93515916/203501096-b20bcd1d-95cc-4aeb-ba46-6a69dfbc0a44.png) +**Open source** Source code made available upon completion of ENF grant **Chinese Translation** @@ -195,4 +197,8 @@ B. 用户教程：为用户提供有关如何使用 Defibox Vault 协议和 sTok **您是如何得知赠款计划的？：** EOS网络基金会网站 +**上线数据** 上线53小时内获得3,000,000 EOS 锁仓量，目前锁仓量约为3,400,000 EOS。 +![image](https://user-images.githubusercontent.com/93515916/203501634-7ee79252-dff3-48dd-96f7-b941d58bea66.png) + + **关于开源：** 收到全额资助后即可开源 From 9e892de1a94e658bad2a0bf364f4cfd599507086 Mon Sep 17 00:00:00 2001 From: DefiboxTeam Date: Wed, 23 Nov 2022 16:41:33 +0800 Subject: [PATCH 008/170] Update Defibox_vault.md --- applications/Defibox_vault.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/applications/Defibox_vault.md b/applications/Defibox_vault.md index f9062825..6b938f59 100644 --- a/applications/Defibox_vault.md +++ b/applications/Defibox_vault.md @@ -119,7 +119,13 @@ Fully support sEOS (vault asset) in all our DeFi protocol **Launch Data** 3,000,000 EOS TVL within 53 hours since launch, at the moment, it is 3,400,000 EOS. ![image](https://user-images.githubusercontent.com/93515916/203501096-b20bcd1d-95cc-4aeb-ba46-6a69dfbc0a44.png) -**Open source** Source code made available upon completion of ENF grant + + +***Open source: Source code made available upon completion of ENF grant*** + +------------------------------------------------------------------------------------------------------------------------------ + + **Chinese Translation** @@ -201,4 +207,4 @@ B. 用户教程：为用户提供有关如何使用 Defibox Vault 协议和 sTok ![image](https://user-images.githubusercontent.com/93515916/203501634-7ee79252-dff3-48dd-96f7-b941d58bea66.png) -**关于开源：** 收到全额资助后即可开源 +***关于开源：收到全额资助后即可开源*** From 458e8d463cee70bef3bdd2367f993135d3fcc834 Mon Sep 17 00:00:00 2001 From: DefiboxTeam Date: Thu, 24 Nov 2022 16:05:59 +0800 Subject: [PATCH 009/170] Update Defibox_vault.md --- applications/Defibox_vault.md | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/applications/Defibox_vault.md b/applications/Defibox_vault.md index 6b938f59..6fc3d0d7 100644 --- a/applications/Defibox_vault.md +++ b/applications/Defibox_vault.md @@ -100,8 +100,12 @@ https://twitter.com/DefiboxOfficial/status/1589907995919781888 - **Total Costs:** 80,000 USD - **Deliverables:** -A. Developer documentation: Provide open developer documentation on how to use & integrate Defibox Vault open-source protocol. -B. User tutorials: Provide video & explainers articles for users on how to use Defibox Vault protocol & sTokens. +Staking yield system template that includes: +Protocol design +Smart contract development +User documentation +Technical documentation + Full launch as milestone reached, 80,000 USD for total cost in which 24,000 USD for security audit fees and 56,000 USD for development cost. @@ -193,8 +197,11 @@ Fully support sEOS (vault asset) in all our DeFi protocol - **全职当量 (FTE)：**5 FTE - **总成本：** 80,000 美元，其中 24,000 美元用于安全审计费用，56,000 美元用于开发成本。 - **可交付成果：** -A. 开发者文档：提供关于如何使用和集成 Defibox Vault 开源协议的开放式开发者文档。 -B. 用户教程：为用户提供有关如何使用 Defibox Vault 协议和 sTokens 的视频和解释文章。 +质押收益系统模板，包括： +协议设计 +智能合约开发 +用户文档 +技术文档 **未来的计划** -高额奖金活动宣传项目，在我们所有的 DeFi 协议中完全支持 sEOS（金库资产） From 97440bcd9fa72b1cfce5abc78878f7896bb81187 Mon Sep 17 00:00:00 2001 From: DefiboxTeam Date: Fri, 25 Nov 2022 16:50:42 +0800 Subject: [PATCH 010/170] Update Defibox_vault.md --- applications/Defibox_vault.md | 29 +++++++++++++++++++---------- 1 file changed, 19 insertions(+), 10 deletions(-) diff --git a/applications/Defibox_vault.md b/applications/Defibox_vault.md index 6fc3d0d7..218f206a 100644 --- a/applications/Defibox_vault.md +++ b/applications/Defibox_vault.md @@ -5,7 +5,7 @@ - **EOS Payment Address:** liquid.defi - **[Level](https://github.com/eosnetworkfoundation/grant-framework#grant-levels):** 3 - **Pomelo Grant(s):** https://pomelo.io/grants/vault -- **Project is Open-Source:** No +- **Project is Open-Source:** Yes - **Project was part of Token sale:** No - **Repository where Project resides:** NA > 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. @@ -27,7 +27,7 @@ > Please provide the following: - **Name:** Vault, a decentralized single-token staking protocol -- **Brief Description:** The Vault protocol is the first single-token lossless yield protocol launched by Defibox. Users can earn corresponding token income by depositing tokens. The assets can be flexibly deposited and withdrawn with open and transparent on chain data. Valut income mainly comes from Defibox protocol income, Yield+ rewards, BP income, REX income, etc. At the same time, in order to improve the utility, the protocol will issue a standard EOS token called sToken, which represents a deposit certificate. sToken can be used in multiple DeFi protocols to obtain more benefits. +- **Brief Description:** The Vault protocol is the first single-token lossless yield protocol launched by Defibox. Users can earn corresponding token income by depositing tokens. The assets can be flexibly deposited and withdrawn with open and transparent on chain data. Vault income mainly comes from Defibox protocol income, Yield+ rewards, BP income, REX income, etc. At the same time, in order to improve the utility, the protocol will issue a standard EOS token called sToken, which represents a deposit certificate. sToken can be used in multiple DeFi protocols to obtain more benefits. - **Relationship to EOSIO:** a public use that provides a variety of staking strategies to EOS users and project teams for more yields. Code will be open source for contribution to EOSIO repository. - **Reason for Interest:** It provides a variety of staking strategies to EOS users and project teams for more yields. It will brings TVL and income to Defibox team while giving benefits to participants. Ecosystem Boost: attract inactive EOS tokens which will prosper ecosystem @@ -42,7 +42,7 @@ Everything is on the website and contract > Help us locate your project in the EOSIO landscape and what problems it tries to solve by answering each of these questions: - Where and how does your project fit into the ecosystem? -Users can earn corresponding token income by depositing tokens. The assets can be flexibly deposited and withdrawn with open and transparent on chain data. Valut income mainly comes from Defibox protocol income, Yield+ rewards, BP income, REX income, etc. At the same time, in order to improve the utility, the protocol will issue a standard EOS token called sToken, which represents a deposit certificate. sToken can be used in multiple DeFi protocols to obtain more benefits. +Users can earn corresponding token income by depositing tokens. The assets can be flexibly deposited and withdrawn with open and transparent on chain data. Vault income mainly comes from Defibox protocol income, Yield+ rewards, BP income, REX income, etc. At the same time, in order to improve the utility, the protocol will issue a standard EOS token called sToken, which represents a deposit certificate. sToken can be used in multiple DeFi protocols to obtain more benefits. - Who is your target audience (chain/dapp/wallet/UI developers, designers, your own user base, some dapp's userbase, yourself)? EOS users including any dapp user and project teams @@ -90,8 +90,9 @@ https://bloks.io/account/vault.defi https://bloks.io/account/stoken.defi  -https://twitter.com/DefiboxOfficial/status/1589907995919781888 +https://twitter.com/DefiboxOfficial/status/1593966063334871042 +Reaching 3 million EOS TVL in 53 hours ### Milestone Summary @@ -105,6 +106,8 @@ Protocol design Smart contract development User documentation Technical documentation +Unit tests +User test instructions Full launch as milestone reached, 80,000 USD for total cost in which 24,000 USD for security audit fees and 56,000 USD for development cost. @@ -112,7 +115,7 @@ Full launch as milestone reached, 80,000 USD for total cost in which 24,000 USD ## Future Plans -Promote the project with big prize event +Promote the project with big prize event: https://eos.defibox.io/lottery Fully support sEOS (vault asset) in all our DeFi protocol @@ -125,7 +128,7 @@ Fully support sEOS (vault asset) in all our DeFi protocol -***Open source: Source code made available upon completion of ENF grant*** +***Open source: Source code made available to ENF and later to the public upon ENF request*** ------------------------------------------------------------------------------------------------------------------------------ @@ -138,7 +141,7 @@ Fully support sEOS (vault asset) in all our DeFi protocol - **EOS支付地址：** liquid.defi - **等级：** 3 - **Pomelo资助：** https://pomelo.io/grants/vault -- **项目是开源的：** 否 +- **项目是开源的：** 是 - **项目是代币销售的一部分：** 否 - **项目资源库：** 不适用 @@ -151,7 +154,7 @@ Fully support sEOS (vault asset) in all our DeFi protocol **概述** - **名称：金库协议** -- **简介：** Vault协议是Defibox推出的第一个单代币无损收益协议。用户可以通过存入代币获得相应的代币收益。资产可灵活存取，链上数据公开透明。 Valut收益主要来自Defibox协议收益、Yield+奖励、BP收益、REX收益等。同时，为了提高效用，协议会发行一个标准的EOS代币sToken，代表存单。 sToken 可以在多种 DeFi 协议中使用以获得更多收益。 +- **简介：** Vault协议是Defibox推出的第一个单代币无损收益协议。用户可以通过存入代币获得相应的代币收益。资产可灵活存取，链上数据公开透明。 Vault收益主要来自Defibox协议收益、Yield+奖励、BP收益、REX收益等。同时，为了提高效用，协议会发行一个标准的EOS代币sToken，代表存单。 sToken 可以在多种 DeFi 协议中使用以获得更多收益。 - **与EOSIO的关系：** 一种公共设施，为 EOS用户和项目团队提供各种质押策略以获得更多收益，并提供开源，这将有助于EOSIO代码资源库。 - **感兴趣的原因：** 它为 EOS 用户和项目团队提供了多种质押策略以获得更多收益。它将为 Defibox 团队带来锁仓量和收入，同时让参与者受益。生态系统提升：吸引不活跃的EOS代币，这将繁荣生态系统。 @@ -159,6 +162,8 @@ Fully support sEOS (vault asset) in all our DeFi protocol -https://eos.defibox.io/vault -https://bloks.io/account/vault.defi -https://bloks.io/account/stoken.defi +https://twitter.com/DefiboxOfficial/status/1593966063334871042 +上线53小时内获得3,000,000 EOS 锁仓量 **生态系统** @@ -202,9 +207,13 @@ Fully support sEOS (vault asset) in all our DeFi protocol 智能合约开发 用户文档 技术文档 +单元测试 +用户测试说明 + **未来的计划** --高额奖金活动宣传项目，在我们所有的 DeFi 协议中完全支持 sEOS（金库资产） +-高额奖金活动宣传项目：https://eos.defibox.io/lottery +在我们所有的 DeFi 协议中完全支持 sEOS（金库资产） **附加信息** @@ -214,4 +223,4 @@ Fully support sEOS (vault asset) in all our DeFi protocol ![image](https://user-images.githubusercontent.com/93515916/203501634-7ee79252-dff3-48dd-96f7-b941d58bea66.png) -***关于开源：收到全额资助后即可开源*** +***关于开源：对ENF开源并随后根据ENF的要求对社区开源*** From 2e1bed09bc0b1051332fe1e5137509ae16e62ec0 Mon Sep 17 00:00:00 2001 From: DefiboxTeam Date: Fri, 25 Nov 2022 16:59:43 +0800 Subject: [PATCH 011/170] Update Defibox_vault.md --- applications/Defibox_vault.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/applications/Defibox_vault.md b/applications/Defibox_vault.md index 218f206a..2bb066be 100644 --- a/applications/Defibox_vault.md +++ b/applications/Defibox_vault.md @@ -58,7 +58,7 @@ Vault is widely supporting all the users on EOS while BSS is only available for ## Team -### Team members +### Team members：16 - **Team Leader:** Eason @@ -127,7 +127,7 @@ Fully support sEOS (vault asset) in all our DeFi protocol ![image](https://user-images.githubusercontent.com/93515916/203501096-b20bcd1d-95cc-4aeb-ba46-6a69dfbc0a44.png) - +***Audit by Certik:** https://www.certik.com/projects/defibox ***Open source: Source code made available to ENF and later to the public upon ENF request*** ------------------------------------------------------------------------------------------------------------------------------ @@ -183,7 +183,7 @@ https://twitter.com/DefiboxOfficial/status/1593966063334871042 -Vault广泛支持EOS上的所有用户，而BSS仅适用于拥有BOX代币的Defibox用户。 **团队** -- **团队成员：** 12 +- **团队成员：** 16 - **团队负责人：** Eason **法律结构** @@ -222,5 +222,5 @@ https://twitter.com/DefiboxOfficial/status/1593966063334871042 **上线数据** 上线53小时内获得3,000,000 EOS 锁仓量，目前锁仓量约为3,400,000 EOS。 ![image](https://user-images.githubusercontent.com/93515916/203501634-7ee79252-dff3-48dd-96f7-b941d58bea66.png) - +***Certik审计：*** https://www.certik.com/projects/defibox ***关于开源：对ENF开源并随后根据ENF的要求对社区开源*** From d8b21ba5e1e8024a9c713ee18fedfd8716bb4ed2 Mon Sep 17 00:00:00 2001 From: Evm_nams_service <118707458+evmns@users.noreply.github.com> Date: Mon, 28 Nov 2022 16:32:16 +0800 Subject: [PATCH 012/170] Create EVMNS.md --- applications/EVMNS.md | 231 ++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 231 insertions(+) create mode 100644 applications/EVMNS.md diff --git a/applications/EVMNS.md b/applications/EVMNS.md new file mode 100644 index 00000000..72e5e881 --- /dev/null +++ b/applications/EVMNS.md @@ -0,0 +1,231 @@ + +# EOS Network Foundation Grant Proposal +- **Project Name:** EVMNS (EVM Name Service) +- **Team Name: **EVMNS Labs +- **EOS Payment Address:** evmnsdomains +- **Level: **3 +- ** Pomelo Grant(s): **N/A +- **Project is Open-Source:** Yes +- **Project was part of Token sale:** No +- **Repository where Project resides:** https://github.com/evmns/EVMNS + +# Contact +**Contact Name:** Harry Davis +**Contact Email:** evmns_manager@outloook.com +**Website:** N/A + +# Project Overview +**EVMNS (EVM Name Service) is a distributed, open and extensible multi-chain DID domain naming system built on EVM and EOS,** relying on the high performance, security and reliability of EOS to better and seamlessly connect people, information, assets, dApps, etc. in the WEB3 world. +EVMNS domains use the ERC721 protocol standard with .evm as the domain suffix, such as abc.evm, 123.evm, jack.evm, etc., to map human-readable and easy-to-remember names with all kinds of content at the same time, including but not limited to EVM addresses, EOS addresses, other cryptocurrency addresses, content hashes, URLs, and metadata. +#### Overview +- **Name:** EVMNS (EVM Name Service) +- **Brief Description:** A distributed, open and extensible multi-chain DID domain naming system built on EVM and EOS +- **Relationship to EOSIO:** EVMNS's multi-chain layout will bring more new users to EOS and EVM, because it helps users of other chains to know and understand EOS and EVM, and to enjoy the unique advantages of EOS (industry-leading block speed, high TPS and low transaction cost), and help EOS to expand its positive influence in the WEB3 world. +- **Reason for Interest:** WEB3 trend is developing rapidly, a set of DID domain naming system with perfect function, multi-chain layout and good user experience is the "identity infrastructure" of WEB3 application, and it can be confirmed that DID is like an avatar, which is the basic and essential element and the identity of WEB3 world. For more information, see our research **< Why DID is needed\>** in Additional Information at the end of this article. + +#### Project Details + +- **Mock-ups/designs of any UI components** +We will build the official website, including project introduction, domain registry and management, and explanatory documents, etc., to provide users with a complete one-stop experience. +- **Implementation Overview** + EVMNS has two principal components. **Registry and Resolvers.** +![](https://github.com/evmns/evm_name_service/blob/main/registry.png?raw=true ) + - EVMNS Registry +The EVMNS registry is a smart contract that maintains a list of all domains and subdomains and stores three critical pieces of information about each domain: the owner of the domain, the resolver for the domain, and the caching time-to-live for all records under the domain. +The owner of a name can be an external account (a user) or a smart contract. A registrar is a smart contract that owns a top-level domain and distributes subdomains of that domain to users according to the rules in the contract. +The domain owner in the EVMNS registry is capable of: +1.Set the resolver and TTL for the domain; +2.Transfer ownership of the domain to another address; +3.Change the ownership of subdomains; +The EVMNS registry exists simply to map domains to the resolver responsible for resolving that domain. + + - Resolvers +The resolver is responsible for converting domains to addresses. Any smart contract that meets the criteria related to resolvers can be used as a resolver program in EVMNS. +Each record type (EVM address, content hash, etc.) defines one or more methods that the resolver must implement in order to provide such records. Adding a new record type does not require changes to the EVMNS registry or to existing resolvers. +Resolving a domain in EVMNS requires two steps: the first step is to ask the registry which resolver is responsible for the domain; the second step is to query that resolver for the result. +Let's say we want to find the EVM address pointed by "abc.evm". First, we ask the registry which resolver is responsible for resolving "abc.evm"; then, we ask that resolver for the address of "abc.evm". + + - About Namehash +Resource constraints in smart contracts make it inefficient to interact directly with readable names, so EVMNS uses only fixed length 256-bit cryptographic hashes. In order to generate hashes from names while still retaining their hierarchical nature, EVMNS uses an algorithm called Namehash, which is used only to represent names within EVMNS. +Namehash is a recursive process that generates a unique hash for any valid name. Starting from the Namehash of any name (e.g., the Namehash of "abc.evm"), one can derive the Namehash of any subname (e.g., the Namehash of "ab. abc.evm"), and the derivation process does not require knowledge of or processing of the readable original name "abc.evm". It is this feature that allows EVMNS to be a hierarchical system without having to deal with readable text strings internally. +Before using Namehash for hashing, the name first needs to be normalized with the help of the UTS-46 standard to ensure that the letters in the name are case-insensitive and to prohibit the use of invalid characters. Any hashing and resolving of names must first be normalized to ensure that all users get consistency of EVMNS. + +#### Ecosystem Fit +- **Where and how does your project fit into the ecosystem?** +EOS has integrated short domain name function in the main chain since its launch, and naturally supports user-defined account name, which is the first to achieve a good experience of human readability and easy to remember, **It would be a great pity if this advantage is not continued on EVM,** As we know, EVMNS, as a DID domain naming system, can fulfill the requirement well and help EVM to better continue the convenience and efficiency of EOS. +Considering the better integration of EVM and EOS users, EOS mainnet users will have the privilege to register EVM domains (5-digit and above length domains) at a special price, **which not only fills the gap in the EOS ecological DID domain system, but also further helps the growth of EOS user scale** (more new users will create EOS accounts in order to get the privilege to register EVM domain at a special price. In addition, it also helps EOS users to have the same experience of EOS account name on EVM, and EOS users can also create their own decentralized super business cards, personal decentralized WEB3 homepage/website. It's a multi-benefit! +What's more, EVMNS will also provides free technical support to holders of existing short names on the EOS mainnet to assist them in issuing corresponding DID domain service agreements in the EVM, such as assisting holder of short name‘eos’to issue domain contract with the suffix .eos on EVM, contributing to the ecological prosperity of EOS and the EVM together. +- **Who is your target audience ?** +Our users are positioned as WEB3 ecological users, corresponding to blockchains including but not limited to EOS, EVM, ETH, BSC, etc. +- **What need(s) does your project meet?** +**One identity accessible to multiple blockchains. **There is no doubt that we are moving towards a multi-chain future, where each WEB3 user travels through different blockchains and dApps, having and managing multiple identities, multiple usernames, multiple sets of identity information, full of tedium and inconvenience and lacking a good experience. +With EVMNS, you can ensure that one universal identity remains intact, not only for all applications, but for all blockchains. You will only have to manage one set of identities, such as your profile, Email, Twitter, Telegram, ETH address, EOS address, EVM address, etc. How wonderful it will be to be able to sync to all chains with one edit. +EVMNS will also meet these needs: human readable and memorable WEB3 usernames, a more user-friendly experience in WEB3 world, decentralized super business cards, and personal decentralized WEB3 homepage/website. For more information, see our research **< Why DID is needed>** in Additional Information at the end of this article. +- **Are there any other projects similar to yours in the EOSIO ecosystem?** +There are no other projects on EOS and EVM ecosystem that are similar to EVMNS for now. +But there are similar DID projects in other blockchains, such as ENS on ETH, SPACE ID on BSC, Bonfida on Solana, EVNS on Evmos, PNS on Polka, and cross-chain DID service‘.bit’, etc. The DID domain naming service protocol has become one of the basic projects on every blockchain, showing a blossoming market. See our research **< DID Market Analysis> **in Additional Information at the end of this article for more details on the market. +Compared to other DID domain projects, EVMNS has a special feature. Benefited from EOS's industry-leading transaction speeds (0.5 seconds), high TPS and low transaction costs, users will have an unparalleled experience when using EVMNS. They will be able to confirm the successful modification of their identity information in seconds, without worrying about block congestion or the cost of interacting with the chain, and will be able to enjoy the WEB3 world more smoothly, which will be an important advantage of EVMNS. + +# Team +#### Team members +- **Team Leader: Harry Davis** +- Allen Harris +- Frank Lee + +#### Legal Structure +- **Registered Legal Entity:** Jump Dream PTE. LTD. +- **Registered Address:** 5001 Beach Road#07-37, Golden Mile Complex, Singapore 199588 + +#### Team Experience +The core members of EVMNS Labs are the first ecological participants of EOS, who experienced and witnessed the launch of EOS and are still deeply involved in the ecological construction. +Team members have participated in several medium to large scale EOS projects before and after, and also developed ENS (Ethereum Name Service) related domain Exchange, domain bulk registry protocol, etc. We are not only EOS loyalists, but also ENS heavy players, with good understanding of DID domain naming system. + +# Development Roadmap +#### Milestone Summary +- Estimated project development duration: 12 weeks +- Full Time Equivalent Employees (FTE): 6 +- Total cost: $195,000 + +#### Milestone 1 - Requirements Analysis and official website +- Estimated project development duration: 2 weeks +- Full Time Equivalent Employees (FTE): 2 +- Total cost: $20,000 + +| ID | Deliverable |Specification| +| ------------ | ------------ | ------------ | +| 0a. |License | MIT License | +| 0b. | Documentation | Provide and update documentation for this milestone in the form of instruction files and examples in the repository, provide guidance in the Readme file, and more in-depth guidance in our articles. | +| 0c. | Testing Guide | The functions of this milestone can be tested by running the unit tests we provide, and guidance on how to run these tests is provided in the Readme file. | +| 0d. | Docker | Use Docker to start a container that runs a local nodevm instance where specific users and contracts are deployed for developer testing. This ensures that developers have the same environment when using EVMNS. | +| 1 | Demand Analysis | Unpacking requirements, developing business process diagrams, planning business modules, standardizing development documentation and testing processes, etc. | +| 2 | Release official website | Including project introduction, Roadmap and other content. | + + +#### Milestone 2 - Smart Contracts + +- Estimated project development duration: 4 weeks +- Full Time Equivalent Employees (FTE): 5 +- Total cost: $100,000 + +| ID | Deliverable |Specification| +| ------------ | ------------ | ------------ | +| 0a. | License | MIT License | +| 0b. | Documentation | Provide and update documentation for this milestone in the form of instruction files and examples in the repository, provide guidance in the Readme file, and more in-depth guidance in our articles. | +| 0c. | Testing Guide | The functions of this milestone can be tested by running the unit tests we provide, and guidance on how to run these tests is provided in the Readme file. | +| 0d. | Docker | Use Docker to start a container that runs a local nodevm instance where specific users and contracts are deployed for developer testing. This ensures that developers have the same environment when using EVMNS. | +| 1 | Core Contracts | At the core of EVMNS is a smart contract that maintains a list of all domains and sub-domains and stores three key pieces of information about each domain: the owner of the domain, the resolver of the domain, and the cached time to live (i.e., TTL) for all records under the domain. | +| 2 | Domain registrar | EVMNS allows domain owners to manage all their domains, including sub-domain registrations. We will provide standard domain registration contracts and interfaces, allowing all compliant contracts to access and renew, transfer and other operations for domains. | +| 3 | Root Node Management | Completing the design of the root node, EVMNS will lock the control of the root node so that the root owner cannot influence the ownership of the .evm domain and set the root node to be held jointly by the community in a multi-signature contract, guaranteeing all the power of the user. | +| 4 | Domain Resolver | Resolvers are responsible for the actual process of translating names into addresses. Any contract that implements the relevant standards may act as a resolver in EVMNS. | + +#### Milestone 3 - Key Systems and Components +- Estimated project development duration: 3 weeks +- Full Time Equivalent Employees (FTE): 3 +- Total cost: $45,000 + +| ID | Deliverable |Specification| +| ------------ | ------------ | ------------ | +| 0a. | License | MIT License | +| 0b. | Documentation | Provide and update documentation for this milestone in the form of instruction files and examples in the repository, provide guidance in the Readme file, and more in-depth guidance in our articles. | +| 0c. | Testing Guide | The functions of this milestone can be tested by running the unit tests we provide, and guidance on how to run these tests is provided in the Readme file. | +| 0d. | Docker | Use Docker to start a container that runs a local nodevm instance where specific users and contracts are deployed for developer testing. This ensures that developers have the same environment when using EVMNS. | +| 1 | Domain Manager | The Domain Manager in EVMNS is a domain management contract that allows domain owners to manage the domains they own, change names in the registry and transfer ownership to anyone else. | +| 2 | Reverse resolver | The reverse resolver in EVMNS provides the ability to declare reverse records for use in configuring records as a convenient feature most commonly used as a way to specify address specification names. | +| 3 | Metadata Storage Management System | Store the domain metadata independently in the metadata management system and access the corresponding metadata through api. | +| 4 | Domain Management System | Build EVMNS domain management system to realize administrators capability of financial review, daily log maintenance review, emergency management, etc. for EVMNS. | + +#### Milestone 4 - In-depth testing +- Estimated project development duration: 2 weeks +- Full Time Equivalent Employees (FTE): 2 +- Total cost: $20,000 + +| ID | Deliverable |Specification| +| ------------ | ------------ | ------------ | +| 0a. | License | MIT License | +| 0b. | Documentation | Provide and update documentation for this milestone in the form of instruction files and examples in the repository, provide guidance in the Readme file, and more in-depth guidance in our articles. | +| 0c. | Testing Guide | The functions of this milestone can be tested by running the unit tests we provide, and guidance on how to run these tests is provided in the Readme file. | +| 0d. | Docker | Use Docker to start a container that runs a local nodevm instance where specific users and contracts are deployed for developer testing. This ensures that developers have the same environment when using EVMNS. | +| 1 | In-depth test | Automated unit tests with 100% coverage and multiple rounds of functional testing are completed internally to ensure functionality and robustness. | +| 2 | dApp Development Documentation | Establish a perfect dApp development documentation system to meet and support the quick access of dApp developers. | + +#### Milestone 5 - Deployment Test Network +- Estimated project development duration: 1 week +- Full Time Equivalent Employees (FTE): 2 +- Total cost: $10,000 + +| ID | Deliverable |Specification| +| ------------ | ------------ | ------------ | +| 0a. | License | MIT License | +| 0b. | Documentation | Provide and update documentation for this milestone in the form of instruction files and examples in the repository, provide guidance in the Readme file, and more in-depth guidance in our articles. | +| 0c. | Testing Guide | The functions of this milestone can be tested by running the unit tests we provide, and guidance on how to run these tests is provided in the Readme file. | +| 0d. | Docker | Use Docker to start a container that runs a local nodevm instance where specific users and contracts are deployed for developer testing. This ensures that developers have the same environment when using EVMNS. | +| 1 | New version of the official website | Including project introduction, domain registration and management, instruction documents, etc. | +| 2 | Deployment of test networks | Deploy the test environment and conduct public testing to further ensure the smooth launch and security of the system | + + +#### Multi-Chain Ecology +Multi-chain ecology is the focus of the second phase of development, and we will prioritize the completion of the first phase of development (the above five milestones) to maximize the assurance that EVMNS can be launched and run stably at the first time after the official launch of EVM. +Therefore, the development content, duration and cost of the multi-chain ecology will be separately defined before the launch of the second phase. + +# Future Plans +- We will build EVMNS DAO, realize community management, and promote the implementation of decentralized operation and R&D of EVMNS. +- Register WEB2 domain with .evm suffix with DNS operators for domain resolution and binding services for traditional browsers so that users can directly access websites/personal homepages corresponding to .evm domain in Chrome, Edge and other browsers to achieve good interoperability between WEB3 and WEB2. +- Develop EOS plug-ins and browser plug-ins belonging to EVMNS to help users manage their EVMNS domains more easily through plug-ins, quick access, collection management of EVMNS domains of other users, etc. + +# Additional Information +#### How did you hear about the Grants Program? +We learned of the program by following announcements on ENF’s Twitter and other channels. + +#### Some of our research +- **What is DID** +DID is the abbreviation of‘Decentralized Identity’, which is a kind of digital identity without a centralized institution as the final guarantee, and is an extension and expansion in WEB 3 of the concept of "user portrait" in WEB2. +The final form of DID development may be that each user has a unique network-wide identity, and multiple local identities for segmented scenarios. Users remember and identify DIDs through domains, manage DIDs and interact with applications through wallets, and integrate different credentials and local identities on multiple chains through wallets. + +- **Why DID is needed** + - Human readable and easy to remember WEB3 username +Although each of us has a unique ID number, in our daily life, we generally use 'name' as an identifier of one's identity (although there will be renames) because it is easier for daily communication. +The world of WEB3 has the same problem: while people currently interact primarily based on wallet addresses, no one wants to remember that long string of characters. If the digital identity of WEB3 needs a 'name', then what EVMNS is doing is hoping to be that 'name'. + + - A more user-friendly WEB3 experience +In WEB2 world, digital identity is platform-centered, and different products within the same group are connected through an account system. For example, Tencent's mailbox, games and finance can all use the same account; Google, Facebook and other top Internet enterprises also have their own account systems. Although this kind of identity system is easy to build, its disadvantages have been widely known: the accounts between platforms do not interoperate with each other, and users have no way to control their own identity data. +In WEB3 world, user interaction is mainly based on wallet address, so a series of activities related to the address constitute the most native decentralized digital identity DID of WEB3, and it can be naturally interoperable between different dApp applications without barriers. In this way, users can quickly find their acquaintance and friends when they enter new applications and games, without having to re-add them back by themselves like in WEB2 world. +Imagine a peer-to-peer chat where you can find the desired contact by simply searching for xxx. evm instead of an 18-digit irregular address starting with 0x. What a wonderful experience, and each EVM domain is unique so you don't have to worry about matching the wrong person. +Moreover, by using a DID name to connect to various cryptocurrency addresses, you can receive cryptocurrency payments from others through that domain name without having to copy and paste long addresses. + + - Decentralized Super Business Card +Each DID domain is a unique NFT, and the owner is free to set the content they wish to map or record, in addition to the common EVM wallet address, other cryptocurrency addresses, but also avatars/pictures, Email, Website, profile, Twitter/Telegram accounts and other content, no one can tamper or delete the information, the user has full control of his or her identity information. A DID may seem like a simple domain name, but it contains unlimited content, and** is a super business card for the WEB3 world.** + + - Personal decentralized WEB3 homepage/website +EVMNS allows users to create personal decentralized homepages/websites and upload them to the Interplanetary File System (IPFS), a global network of storage protocols that allow computers around the world to store and share data in a peer-to-peer fashion. +In short, EVMNS and IPFS can help users to establish personal homepages/blogs and websites, with functions similar to the combination of RSS feeds + WEB3 Medium. **Users will have full ownership, including domain name, content and data,** completely avoiding the possibility of being deleted by registrars/data operators. + + - WEB3 Infrastructure +DID is also known as the "identity infrastructure" of WEB3 applications. As discussed above, it is basically determined that DID and avatar are the basic and essential elements of WEB3, being the identity of the WEB3 world. + +- **DID Market Analysis** + - ENS (Ethereum Name Service) +ENS was launched on May 4, 2017 by Alex Van de Sande and Nick Johnson of the ETH Foundation. In November 2021, ENS issued its own governance token and launched an airdrop. At the same time, ENS established the ENS DAO to enable community governance, where token holders will participate in the management of the assets, as well as voting on DAO proposals and co-voting on the use of the vault. +Earlier in the interview Vitalik said, "**The Ethereum Domain Name Service ENS is by far the most successful non-financial ETH application,** which can basically be compared to a decentralized phone book." +As of November 27, 2022, the** total amount of ENS domain registration reached 2.79 million** and the number of Ethereum addresses holding ENS domains reached 609,000. Since November 2021, the number of monthly ENS registrations has shown explosive growth, reaching a peak of 437,000 monthly registrations in September 2022. +![](https://github.com/evmns/evm_name_service/blob/main/t2.png?raw=true ) +###### Data source dune.com/makoto/ens +**Total registration revenue of ENS domains has exceeded $60 million,** of which nearly $50 million has been realized so far in 2022 alone. **Total secondary market transactions have reached 112.39K ETH and $197 million.** +![](https://github.com/evmns/evm_name_service/blob/main/t3.png?raw=true ) +###### Data source NFTGO.io +Whether it is the registration scale, transaction scale, or the number of holder’s addresses, ENS is far ahead of similar projects, occupying the absolute leading position and having the strongest community consensus. +The following is the partial sales of historical. +paradigm.eth, 420ETH +000.eth, 300ETH +Opensea.eth, 99.89ETH +Nike.eth, 60ETH +Samsung.eth, 60ETH + - SPACE ID (BNB Chain Name Service) +SPACE ID is a decentralized domain naming service protocol developed based on BNB Chain, officially launched in August 2022, with .bnb as the domain suffix, essentially the same as ENS, and dedicated to building a common name service network that seamlessly connects people, information, assets and applications across the blockchain. And by allowing users to bind their identities across multiple chains, communities can build their own domain naming services through SPACE ID's network. To date, more than 40 applications have announced that they have enabled integration of the SPACE ID protocol. +A seed round of funding led by Binance Labs was completed on September 2nd, 2022 for an undisclosed amount. +As of November 27, 2022, SPACE ID domain name total registrations reached 304,000, the total number of holders’ addresses reached 98,700, and the total registration revenue was 14,700 BNB, USD 4.42 million (1 BNB = USD 300). The total secondary market transaction size was about 22,000 BNB, 6.60 million USD. +![](https://github.com/evmns/evm_name_service/blob/main/t4.png?raw=true ) +###### Data source dune.com/spaceid/spaceid +At present, WEB3 domain services like ENS and SPACE ID are also BNS on Binance, Bonfida on Solana, EVNS on Evmos, PNS on Polka, and cross-chain DID service‘.bit’, etc. The DID domain naming service protocol has become one of the basic items of every blockchain, showing a blossoming market state. + + + From b8344591356142229aae3912d0a3c492df17d033 Mon Sep 17 00:00:00 2001 From: Evm_nams_service <118707458+evmns@users.noreply.github.com> Date: Mon, 28 Nov 2022 16:36:38 +0800 Subject: [PATCH 013/170] Update EVMNS.md --- applications/EVMNS.md | 38 ++++++++++++++++++++------------------ 1 file changed, 20 insertions(+), 18 deletions(-) diff --git a/applications/EVMNS.md b/applications/EVMNS.md index 72e5e881..d0583644 100644 --- a/applications/EVMNS.md +++ b/applications/EVMNS.md @@ -1,29 +1,31 @@ # EOS Network Foundation Grant Proposal - **Project Name:** EVMNS (EVM Name Service) -- **Team Name: **EVMNS Labs +- **Team Name:** EVMNS Labs - **EOS Payment Address:** evmnsdomains -- **Level: **3 -- ** Pomelo Grant(s): **N/A +- **Level:** 3 +- ** Pomelo Grant(s):** N/A - **Project is Open-Source:** Yes - **Project was part of Token sale:** No - **Repository where Project resides:** https://github.com/evmns/EVMNS # Contact **Contact Name:** Harry Davis + **Contact Email:** evmns_manager@outloook.com + **Website:** N/A # Project Overview **EVMNS (EVM Name Service) is a distributed, open and extensible multi-chain DID domain naming system built on EVM and EOS,** relying on the high performance, security and reliability of EOS to better and seamlessly connect people, information, assets, dApps, etc. in the WEB3 world. EVMNS domains use the ERC721 protocol standard with .evm as the domain suffix, such as abc.evm, 123.evm, jack.evm, etc., to map human-readable and easy-to-remember names with all kinds of content at the same time, including but not limited to EVM addresses, EOS addresses, other cryptocurrency addresses, content hashes, URLs, and metadata. -#### Overview +### Overview - **Name:** EVMNS (EVM Name Service) - **Brief Description:** A distributed, open and extensible multi-chain DID domain naming system built on EVM and EOS - **Relationship to EOSIO:** EVMNS's multi-chain layout will bring more new users to EOS and EVM, because it helps users of other chains to know and understand EOS and EVM, and to enjoy the unique advantages of EOS (industry-leading block speed, high TPS and low transaction cost), and help EOS to expand its positive influence in the WEB3 world. - **Reason for Interest:** WEB3 trend is developing rapidly, a set of DID domain naming system with perfect function, multi-chain layout and good user experience is the "identity infrastructure" of WEB3 application, and it can be confirmed that DID is like an avatar, which is the basic and essential element and the identity of WEB3 world. For more information, see our research **< Why DID is needed\>** in Additional Information at the end of this article. -#### Project Details +### Project Details - **Mock-ups/designs of any UI components** We will build the official website, including project introduction, domain registry and management, and explanatory documents, etc., to provide users with a complete one-stop experience. @@ -50,7 +52,7 @@ Resource constraints in smart contracts make it inefficient to interact directly Namehash is a recursive process that generates a unique hash for any valid name. Starting from the Namehash of any name (e.g., the Namehash of "abc.evm"), one can derive the Namehash of any subname (e.g., the Namehash of "ab. abc.evm"), and the derivation process does not require knowledge of or processing of the readable original name "abc.evm". It is this feature that allows EVMNS to be a hierarchical system without having to deal with readable text strings internally. Before using Namehash for hashing, the name first needs to be normalized with the help of the UTS-46 standard to ensure that the letters in the name are case-insensitive and to prohibit the use of invalid characters. Any hashing and resolving of names must first be normalized to ensure that all users get consistency of EVMNS. -#### Ecosystem Fit +### Ecosystem Fit - **Where and how does your project fit into the ecosystem?** EOS has integrated short domain name function in the main chain since its launch, and naturally supports user-defined account name, which is the first to achieve a good experience of human readability and easy to remember, **It would be a great pity if this advantage is not continued on EVM,** As we know, EVMNS, as a DID domain naming system, can fulfill the requirement well and help EVM to better continue the convenience and efficiency of EOS. Considering the better integration of EVM and EOS users, EOS mainnet users will have the privilege to register EVM domains (5-digit and above length domains) at a special price, **which not only fills the gap in the EOS ecological DID domain system, but also further helps the growth of EOS user scale** (more new users will create EOS accounts in order to get the privilege to register EVM domain at a special price. In addition, it also helps EOS users to have the same experience of EOS account name on EVM, and EOS users can also create their own decentralized super business cards, personal decentralized WEB3 homepage/website. It's a multi-benefit! @@ -67,26 +69,26 @@ But there are similar DID projects in other blockchains, such as ENS on ETH, SPA Compared to other DID domain projects, EVMNS has a special feature. Benefited from EOS's industry-leading transaction speeds (0.5 seconds), high TPS and low transaction costs, users will have an unparalleled experience when using EVMNS. They will be able to confirm the successful modification of their identity information in seconds, without worrying about block congestion or the cost of interacting with the chain, and will be able to enjoy the WEB3 world more smoothly, which will be an important advantage of EVMNS. # Team -#### Team members +### Team members - **Team Leader: Harry Davis** - Allen Harris - Frank Lee -#### Legal Structure +### Legal Structure - **Registered Legal Entity:** Jump Dream PTE. LTD. - **Registered Address:** 5001 Beach Road#07-37, Golden Mile Complex, Singapore 199588 -#### Team Experience +### Team Experience The core members of EVMNS Labs are the first ecological participants of EOS, who experienced and witnessed the launch of EOS and are still deeply involved in the ecological construction. Team members have participated in several medium to large scale EOS projects before and after, and also developed ENS (Ethereum Name Service) related domain Exchange, domain bulk registry protocol, etc. We are not only EOS loyalists, but also ENS heavy players, with good understanding of DID domain naming system. # Development Roadmap -#### Milestone Summary +### Milestone Summary - Estimated project development duration: 12 weeks - Full Time Equivalent Employees (FTE): 6 - Total cost: $195,000 -#### Milestone 1 - Requirements Analysis and official website +### Milestone 1 - Requirements Analysis and official website - Estimated project development duration: 2 weeks - Full Time Equivalent Employees (FTE): 2 - Total cost: $20,000 @@ -101,7 +103,7 @@ Team members have participated in several medium to large scale EOS projects bef | 2 | Release official website | Including project introduction, Roadmap and other content. | -#### Milestone 2 - Smart Contracts +### Milestone 2 - Smart Contracts - Estimated project development duration: 4 weeks - Full Time Equivalent Employees (FTE): 5 @@ -118,7 +120,7 @@ Team members have participated in several medium to large scale EOS projects bef | 3 | Root Node Management | Completing the design of the root node, EVMNS will lock the control of the root node so that the root owner cannot influence the ownership of the .evm domain and set the root node to be held jointly by the community in a multi-signature contract, guaranteeing all the power of the user. | | 4 | Domain Resolver | Resolvers are responsible for the actual process of translating names into addresses. Any contract that implements the relevant standards may act as a resolver in EVMNS. | -#### Milestone 3 - Key Systems and Components +### Milestone 3 - Key Systems and Components - Estimated project development duration: 3 weeks - Full Time Equivalent Employees (FTE): 3 - Total cost: $45,000 @@ -134,7 +136,7 @@ Team members have participated in several medium to large scale EOS projects bef | 3 | Metadata Storage Management System | Store the domain metadata independently in the metadata management system and access the corresponding metadata through api. | | 4 | Domain Management System | Build EVMNS domain management system to realize administrators capability of financial review, daily log maintenance review, emergency management, etc. for EVMNS. | -#### Milestone 4 - In-depth testing +### Milestone 4 - In-depth testing - Estimated project development duration: 2 weeks - Full Time Equivalent Employees (FTE): 2 - Total cost: $20,000 @@ -148,7 +150,7 @@ Team members have participated in several medium to large scale EOS projects bef | 1 | In-depth test | Automated unit tests with 100% coverage and multiple rounds of functional testing are completed internally to ensure functionality and robustness. | | 2 | dApp Development Documentation | Establish a perfect dApp development documentation system to meet and support the quick access of dApp developers. | -#### Milestone 5 - Deployment Test Network +### Milestone 5 - Deployment Test Network - Estimated project development duration: 1 week - Full Time Equivalent Employees (FTE): 2 - Total cost: $10,000 @@ -163,7 +165,7 @@ Team members have participated in several medium to large scale EOS projects bef | 2 | Deployment of test networks | Deploy the test environment and conduct public testing to further ensure the smooth launch and security of the system | -#### Multi-Chain Ecology +### Multi-Chain Ecology Multi-chain ecology is the focus of the second phase of development, and we will prioritize the completion of the first phase of development (the above five milestones) to maximize the assurance that EVMNS can be launched and run stably at the first time after the official launch of EVM. Therefore, the development content, duration and cost of the multi-chain ecology will be separately defined before the launch of the second phase. @@ -173,10 +175,10 @@ Therefore, the development content, duration and cost of the multi-chain ecology - Develop EOS plug-ins and browser plug-ins belonging to EVMNS to help users manage their EVMNS domains more easily through plug-ins, quick access, collection management of EVMNS domains of other users, etc. # Additional Information -#### How did you hear about the Grants Program? +### How did you hear about the Grants Program? We learned of the program by following announcements on ENF’s Twitter and other channels. -#### Some of our research +### Some of our research - **What is DID** DID is the abbreviation of‘Decentralized Identity’, which is a kind of digital identity without a centralized institution as the final guarantee, and is an extension and expansion in WEB 3 of the concept of "user portrait" in WEB2. The final form of DID development may be that each user has a unique network-wide identity, and multiple local identities for segmented scenarios. Users remember and identify DIDs through domains, manage DIDs and interact with applications through wallets, and integrate different credentials and local identities on multiple chains through wallets. From 76499d3cba0ce1fac522d8f68f5ac8e2dfe177be Mon Sep 17 00:00:00 2001 From: Evm_nams_service <118707458+evmns@users.noreply.github.com> Date: Mon, 28 Nov 2022 16:36:56 +0800 Subject: [PATCH 014/170] Update EVMNS.md --- applications/EVMNS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/applications/EVMNS.md b/applications/EVMNS.md index d0583644..09456226 100644 --- a/applications/EVMNS.md +++ b/applications/EVMNS.md @@ -4,7 +4,7 @@ - **Team Name:** EVMNS Labs - **EOS Payment Address:** evmnsdomains - **Level:** 3 -- ** Pomelo Grant(s):** N/A +- **Pomelo Grant(s):** N/A - **Project is Open-Source:** Yes - **Project was part of Token sale:** No - **Repository where Project resides:** https://github.com/evmns/EVMNS From 26d327b555e5212ca4a72b8e1bb1a293ea20e309 Mon Sep 17 00:00:00 2001 From: Evm_nams_service <118707458+evmns@users.noreply.github.com> Date: Mon, 28 Nov 2022 16:49:52 +0800 Subject: [PATCH 015/170] Update EVMNS.md --- applications/EVMNS.md | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/applications/EVMNS.md b/applications/EVMNS.md index 09456226..e7ce1a92 100644 --- a/applications/EVMNS.md +++ b/applications/EVMNS.md @@ -27,13 +27,13 @@ EVMNS domains use the ERC721 protocol standard with .evm as the domain suffix, s ### Project Details -- **Mock-ups/designs of any UI components** -We will build the official website, including project introduction, domain registry and management, and explanatory documents, etc., to provide users with a complete one-stop experience. -- **Implementation Overview** - EVMNS has two principal components. **Registry and Resolvers.** +* #### Mock-ups/designs of any UI components + We will build the official website, including project introduction, domain registry and management, and explanatory documents, etc., to provide users with a complete one-stop experience. +* #### Implementation Overview + EVMNS has two principal components. **Registry and Resolvers.** ![](https://github.com/evmns/evm_name_service/blob/main/registry.png?raw=true ) - - EVMNS Registry -The EVMNS registry is a smart contract that maintains a list of all domains and subdomains and stores three critical pieces of information about each domain: the owner of the domain, the resolver for the domain, and the caching time-to-live for all records under the domain. + * #### EVMNS Registry + The EVMNS registry is a smart contract that maintains a list of all domains and subdomains and stores three critical pieces of information about each domain: the owner of the domain, the resolver for the domain, and the caching time-to-live for all records under the domain. The owner of a name can be an external account (a user) or a smart contract. A registrar is a smart contract that owns a top-level domain and distributes subdomains of that domain to users according to the rules in the contract. The domain owner in the EVMNS registry is capable of: 1.Set the resolver and TTL for the domain; @@ -41,14 +41,14 @@ The domain owner in the EVMNS registry is capable of: 3.Change the ownership of subdomains; The EVMNS registry exists simply to map domains to the resolver responsible for resolving that domain. - - Resolvers -The resolver is responsible for converting domains to addresses. Any smart contract that meets the criteria related to resolvers can be used as a resolver program in EVMNS. + * #### Resolvers + The resolver is responsible for converting domains to addresses. Any smart contract that meets the criteria related to resolvers can be used as a resolver program in EVMNS. Each record type (EVM address, content hash, etc.) defines one or more methods that the resolver must implement in order to provide such records. Adding a new record type does not require changes to the EVMNS registry or to existing resolvers. Resolving a domain in EVMNS requires two steps: the first step is to ask the registry which resolver is responsible for the domain; the second step is to query that resolver for the result. Let's say we want to find the EVM address pointed by "abc.evm". First, we ask the registry which resolver is responsible for resolving "abc.evm"; then, we ask that resolver for the address of "abc.evm". - - About Namehash -Resource constraints in smart contracts make it inefficient to interact directly with readable names, so EVMNS uses only fixed length 256-bit cryptographic hashes. In order to generate hashes from names while still retaining their hierarchical nature, EVMNS uses an algorithm called Namehash, which is used only to represent names within EVMNS. + * #### About Namehash + Resource constraints in smart contracts make it inefficient to interact directly with readable names, so EVMNS uses only fixed length 256-bit cryptographic hashes. In order to generate hashes from names while still retaining their hierarchical nature, EVMNS uses an algorithm called Namehash, which is used only to represent names within EVMNS. Namehash is a recursive process that generates a unique hash for any valid name. Starting from the Namehash of any name (e.g., the Namehash of "abc.evm"), one can derive the Namehash of any subname (e.g., the Namehash of "ab. abc.evm"), and the derivation process does not require knowledge of or processing of the readable original name "abc.evm". It is this feature that allows EVMNS to be a hierarchical system without having to deal with readable text strings internally. Before using Namehash for hashing, the name first needs to be normalized with the help of the UTS-46 standard to ensure that the letters in the name are case-insensitive and to prohibit the use of invalid characters. Any hashing and resolving of names must first be normalized to ensure that all users get consistency of EVMNS. From 9c38233c7a302d0b4f033ce68db59f3e8358e26c Mon Sep 17 00:00:00 2001 From: Evm_nams_service <118707458+evmns@users.noreply.github.com> Date: Mon, 28 Nov 2022 18:12:35 +0800 Subject: [PATCH 016/170] Update EVMNS.md --- applications/EVMNS.md | 204 +++++++++++++++++++++++++----------------- 1 file changed, 120 insertions(+), 84 deletions(-) diff --git a/applications/EVMNS.md b/applications/EVMNS.md index e7ce1a92..f378381f 100644 --- a/applications/EVMNS.md +++ b/applications/EVMNS.md @@ -18,6 +18,7 @@ # Project Overview **EVMNS (EVM Name Service) is a distributed, open and extensible multi-chain DID domain naming system built on EVM and EOS,** relying on the high performance, security and reliability of EOS to better and seamlessly connect people, information, assets, dApps, etc. in the WEB3 world. + EVMNS domains use the ERC721 protocol standard with .evm as the domain suffix, such as abc.evm, 123.evm, jack.evm, etc., to map human-readable and easy-to-remember names with all kinds of content at the same time, including but not limited to EVM addresses, EOS addresses, other cryptocurrency addresses, content hashes, URLs, and metadata. ### Overview - **Name:** EVMNS (EVM Name Service) @@ -34,39 +35,52 @@ EVMNS domains use the ERC721 protocol standard with .evm as the domain suffix, s ![](https://github.com/evmns/evm_name_service/blob/main/registry.png?raw=true ) * #### EVMNS Registry The EVMNS registry is a smart contract that maintains a list of all domains and subdomains and stores three critical pieces of information about each domain: the owner of the domain, the resolver for the domain, and the caching time-to-live for all records under the domain. -The owner of a name can be an external account (a user) or a smart contract. A registrar is a smart contract that owns a top-level domain and distributes subdomains of that domain to users according to the rules in the contract. -The domain owner in the EVMNS registry is capable of: -1.Set the resolver and TTL for the domain; -2.Transfer ownership of the domain to another address; + + The owner of a name can be an external account (a user) or a smart contract. A registrar is a smart contract that owns a top-level domain and distributes subdomains of that domain to users according to the rules in the contract. +The domain owner in the EVMNS registry is capable of:
+1.Set the resolver and TTL for the domain;
+2.Transfer ownership of the domain to another address;
3.Change the ownership of subdomains; -The EVMNS registry exists simply to map domains to the resolver responsible for resolving that domain. + + The EVMNS registry exists simply to map domains to the resolver responsible for resolving that domain. * #### Resolvers The resolver is responsible for converting domains to addresses. Any smart contract that meets the criteria related to resolvers can be used as a resolver program in EVMNS. -Each record type (EVM address, content hash, etc.) defines one or more methods that the resolver must implement in order to provide such records. Adding a new record type does not require changes to the EVMNS registry or to existing resolvers. -Resolving a domain in EVMNS requires two steps: the first step is to ask the registry which resolver is responsible for the domain; the second step is to query that resolver for the result. -Let's say we want to find the EVM address pointed by "abc.evm". First, we ask the registry which resolver is responsible for resolving "abc.evm"; then, we ask that resolver for the address of "abc.evm". + + Each record type (EVM address, content hash, etc.) defines one or more methods that the resolver must implement in order to provide such records. Adding a new record type does not require changes to the EVMNS registry or to existing resolvers. + + Resolving a domain in EVMNS requires two steps: the first step is to ask the registry which resolver is responsible for the domain; the second step is to query that resolver for the result. + + Let's say we want to find the EVM address pointed by "abc.evm". First, we ask the registry which resolver is responsible for resolving "abc.evm"; then, we ask that resolver for the address of "abc.evm". * #### About Namehash Resource constraints in smart contracts make it inefficient to interact directly with readable names, so EVMNS uses only fixed length 256-bit cryptographic hashes. In order to generate hashes from names while still retaining their hierarchical nature, EVMNS uses an algorithm called Namehash, which is used only to represent names within EVMNS. -Namehash is a recursive process that generates a unique hash for any valid name. Starting from the Namehash of any name (e.g., the Namehash of "abc.evm"), one can derive the Namehash of any subname (e.g., the Namehash of "ab. abc.evm"), and the derivation process does not require knowledge of or processing of the readable original name "abc.evm". It is this feature that allows EVMNS to be a hierarchical system without having to deal with readable text strings internally. -Before using Namehash for hashing, the name first needs to be normalized with the help of the UTS-46 standard to ensure that the letters in the name are case-insensitive and to prohibit the use of invalid characters. Any hashing and resolving of names must first be normalized to ensure that all users get consistency of EVMNS. + + Namehash is a recursive process that generates a unique hash for any valid name. Starting from the Namehash of any name (e.g., the Namehash of "abc.evm"), one can derive the Namehash of any subname (e.g., the Namehash of "ab. abc.evm"), and the derivation process does not require knowledge of or processing of the readable original name "abc.evm". It is this feature that allows EVMNS to be a hierarchical system without having to deal with readable text strings internally. + + Before using Namehash for hashing, the name first needs to be normalized with the help of the UTS-46 standard to ensure that the letters in the name are case-insensitive and to prohibit the use of invalid characters. Any hashing and resolving of names must first be normalized to ensure that all users get consistency of EVMNS. ### Ecosystem Fit -- **Where and how does your project fit into the ecosystem?** -EOS has integrated short domain name function in the main chain since its launch, and naturally supports user-defined account name, which is the first to achieve a good experience of human readability and easy to remember, **It would be a great pity if this advantage is not continued on EVM,** As we know, EVMNS, as a DID domain naming system, can fulfill the requirement well and help EVM to better continue the convenience and efficiency of EOS. -Considering the better integration of EVM and EOS users, EOS mainnet users will have the privilege to register EVM domains (5-digit and above length domains) at a special price, **which not only fills the gap in the EOS ecological DID domain system, but also further helps the growth of EOS user scale** (more new users will create EOS accounts in order to get the privilege to register EVM domain at a special price. In addition, it also helps EOS users to have the same experience of EOS account name on EVM, and EOS users can also create their own decentralized super business cards, personal decentralized WEB3 homepage/website. It's a multi-benefit! -What's more, EVMNS will also provides free technical support to holders of existing short names on the EOS mainnet to assist them in issuing corresponding DID domain service agreements in the EVM, such as assisting holder of short name‘eos’to issue domain contract with the suffix .eos on EVM, contributing to the ecological prosperity of EOS and the EVM together. -- **Who is your target audience ?** -Our users are positioned as WEB3 ecological users, corresponding to blockchains including but not limited to EOS, EVM, ETH, BSC, etc. -- **What need(s) does your project meet?** -**One identity accessible to multiple blockchains. **There is no doubt that we are moving towards a multi-chain future, where each WEB3 user travels through different blockchains and dApps, having and managing multiple identities, multiple usernames, multiple sets of identity information, full of tedium and inconvenience and lacking a good experience. -With EVMNS, you can ensure that one universal identity remains intact, not only for all applications, but for all blockchains. You will only have to manage one set of identities, such as your profile, Email, Twitter, Telegram, ETH address, EOS address, EVM address, etc. How wonderful it will be to be able to sync to all chains with one edit. -EVMNS will also meet these needs: human readable and memorable WEB3 usernames, a more user-friendly experience in WEB3 world, decentralized super business cards, and personal decentralized WEB3 homepage/website. For more information, see our research **< Why DID is needed>** in Additional Information at the end of this article. -- **Are there any other projects similar to yours in the EOSIO ecosystem?** -There are no other projects on EOS and EVM ecosystem that are similar to EVMNS for now. -But there are similar DID projects in other blockchains, such as ENS on ETH, SPACE ID on BSC, Bonfida on Solana, EVNS on Evmos, PNS on Polka, and cross-chain DID service‘.bit’, etc. The DID domain naming service protocol has become one of the basic projects on every blockchain, showing a blossoming market. See our research **< DID Market Analysis> **in Additional Information at the end of this article for more details on the market. -Compared to other DID domain projects, EVMNS has a special feature. Benefited from EOS's industry-leading transaction speeds (0.5 seconds), high TPS and low transaction costs, users will have an unparalleled experience when using EVMNS. They will be able to confirm the successful modification of their identity information in seconds, without worrying about block congestion or the cost of interacting with the chain, and will be able to enjoy the WEB3 world more smoothly, which will be an important advantage of EVMNS. +* #### Where and how does your project fit into the ecosystem? + EOS has integrated short domain name function in the main chain since its launch, and naturally supports user-defined account name, which is the first to achieve a good experience of human readability and easy to remember, **It would be a great pity if this advantage is not continued on EVM,** As we know, EVMNS, as a DID domain naming system, can fulfill the requirement well and help EVM to better continue the convenience and efficiency of EOS. + + Considering the better integration of EVM and EOS users, EOS mainnet users will have the privilege to register EVM domains (5-digit and above length domains) at a special price, **which not only fills the gap in the EOS ecological DID domain system, but also further helps the growth of EOS user scale** (more new users will create EOS accounts in order to get the privilege to register EVM domain at a special price. In addition, it also helps EOS users to have the same experience of EOS account name on EVM, and EOS users can also create their own decentralized super business cards, personal decentralized WEB3 homepage/website. It's a multi-benefit! + + What's more, EVMNS will also provides free technical support to holders of existing short names on the EOS mainnet to assist them in issuing corresponding DID domain service agreements in the EVM, such as assisting holder of short name‘eos’to issue domain contract with the suffix .eos on EVM, contributing to the ecological prosperity of EOS and the EVM together. +* #### Who is your target audience ? + Our users are positioned as WEB3 ecological users, corresponding to blockchains including but not limited to EOS, EVM, ETH, BSC, etc. +* #### What need(s) does your project meet? + **One identity accessible to multiple blockchains.** There is no doubt that we are moving towards a multi-chain future, where each WEB3 user travels through different blockchains and dApps, having and managing multiple identities, multiple usernames, multiple sets of identity information, full of tedium and inconvenience and lacking a good experience. + + With EVMNS, you can ensure that one universal identity remains intact, not only for all applications, but for all blockchains. You will only have to manage one set of identities, such as your profile, Email, Twitter, Telegram, ETH address, EOS address, EVM address, etc. How wonderful it will be to be able to sync to all chains with one edit. + + EVMNS will also meet these needs: human readable and memorable WEB3 usernames, a more user-friendly experience in WEB3 world, decentralized super business cards, and personal decentralized WEB3 homepage/website. For more information, see our research **< Why DID is needed>** in Additional Information at the end of this article. +* #### Are there any other projects similar to yours in the EOSIO ecosystem? + There are no other projects on EOS and EVM ecosystem that are similar to EVMNS for now. + + But there are similar DID projects in other blockchains, such as ENS on ETH, SPACE ID on BSC, Bonfida on Solana, EVNS on Evmos, PNS on Polka, and cross-chain DID service‘.bit’, etc. The DID domain naming service protocol has become one of the basic projects on every blockchain, showing a blossoming market. See our research **< DID Market Analysis>** in Additional Information at the end of this article for more details on the market. + + Compared to other DID domain projects, EVMNS has a special feature. Benefited from EOS's industry-leading transaction speeds (0.5 seconds), high TPS and low transaction costs, users will have an unparalleled experience when using EVMNS. They will be able to confirm the successful modification of their identity information in seconds, without worrying about block congestion or the cost of interacting with the chain, and will be able to enjoy the WEB3 world more smoothly, which will be an important advantage of EVMNS. # Team ### Team members @@ -80,18 +94,19 @@ Compared to other DID domain projects, EVMNS has a special feature. Benefited fr ### Team Experience The core members of EVMNS Labs are the first ecological participants of EOS, who experienced and witnessed the launch of EOS and are still deeply involved in the ecological construction. + Team members have participated in several medium to large scale EOS projects before and after, and also developed ENS (Ethereum Name Service) related domain Exchange, domain bulk registry protocol, etc. We are not only EOS loyalists, but also ENS heavy players, with good understanding of DID domain naming system. # Development Roadmap ### Milestone Summary -- Estimated project development duration: 12 weeks -- Full Time Equivalent Employees (FTE): 6 -- Total cost: $195,000 +- **Estimated project development duration:** 12 weeks +- **Full Time Equivalent Employees (FTE):** 6 +- **Total cost:** $195,000 ### Milestone 1 - Requirements Analysis and official website -- Estimated project development duration: 2 weeks -- Full Time Equivalent Employees (FTE): 2 -- Total cost: $20,000 +- **Estimated project development duration:** 2 weeks +- **Full Time Equivalent Employees (FTE):** 2 +- **Total cost:** $20,000 | ID | Deliverable |Specification| | ------------ | ------------ | ------------ | @@ -105,9 +120,9 @@ Team members have participated in several medium to large scale EOS projects bef ### Milestone 2 - Smart Contracts -- Estimated project development duration: 4 weeks -- Full Time Equivalent Employees (FTE): 5 -- Total cost: $100,000 +- **Estimated project development duration:** 4 weeks +- **Full Time Equivalent Employees (FTE):** 5 +- **Total cost:** $100,000 | ID | Deliverable |Specification| | ------------ | ------------ | ------------ | @@ -121,9 +136,9 @@ Team members have participated in several medium to large scale EOS projects bef | 4 | Domain Resolver | Resolvers are responsible for the actual process of translating names into addresses. Any contract that implements the relevant standards may act as a resolver in EVMNS. | ### Milestone 3 - Key Systems and Components -- Estimated project development duration: 3 weeks -- Full Time Equivalent Employees (FTE): 3 -- Total cost: $45,000 +- **Estimated project development duration:** 3 weeks +- **Full Time Equivalent Employees (FTE):** 3 +- **Total cost:** $45,000 | ID | Deliverable |Specification| | ------------ | ------------ | ------------ | @@ -137,9 +152,9 @@ Team members have participated in several medium to large scale EOS projects bef | 4 | Domain Management System | Build EVMNS domain management system to realize administrators capability of financial review, daily log maintenance review, emergency management, etc. for EVMNS. | ### Milestone 4 - In-depth testing -- Estimated project development duration: 2 weeks -- Full Time Equivalent Employees (FTE): 2 -- Total cost: $20,000 +- **Estimated project development duration:** 2 weeks +- **Full Time Equivalent Employees (FTE):** 2 +- **Total cost:** $20,000 | ID | Deliverable |Specification| | ------------ | ------------ | ------------ | @@ -151,9 +166,9 @@ Team members have participated in several medium to large scale EOS projects bef | 2 | dApp Development Documentation | Establish a perfect dApp development documentation system to meet and support the quick access of dApp developers. | ### Milestone 5 - Deployment Test Network -- Estimated project development duration: 1 week -- Full Time Equivalent Employees (FTE): 2 -- Total cost: $10,000 +- **Estimated project development duration:** 1 week +- **Full Time Equivalent Employees (FTE):** 2 +- **Total cost:** $10,000 | ID | Deliverable |Specification| | ------------ | ------------ | ------------ | @@ -179,54 +194,75 @@ Therefore, the development content, duration and cost of the multi-chain ecology We learned of the program by following announcements on ENF’s Twitter and other channels. ### Some of our research -- **What is DID** +* #### What is DID DID is the abbreviation of‘Decentralized Identity’, which is a kind of digital identity without a centralized institution as the final guarantee, and is an extension and expansion in WEB 3 of the concept of "user portrait" in WEB2. + The final form of DID development may be that each user has a unique network-wide identity, and multiple local identities for segmented scenarios. Users remember and identify DIDs through domains, manage DIDs and interact with applications through wallets, and integrate different credentials and local identities on multiple chains through wallets. -- **Why DID is needed** - - Human readable and easy to remember WEB3 username -Although each of us has a unique ID number, in our daily life, we generally use 'name' as an identifier of one's identity (although there will be renames) because it is easier for daily communication. -The world of WEB3 has the same problem: while people currently interact primarily based on wallet addresses, no one wants to remember that long string of characters. If the digital identity of WEB3 needs a 'name', then what EVMNS is doing is hoping to be that 'name'. - - - A more user-friendly WEB3 experience -In WEB2 world, digital identity is platform-centered, and different products within the same group are connected through an account system. For example, Tencent's mailbox, games and finance can all use the same account; Google, Facebook and other top Internet enterprises also have their own account systems. Although this kind of identity system is easy to build, its disadvantages have been widely known: the accounts between platforms do not interoperate with each other, and users have no way to control their own identity data. -In WEB3 world, user interaction is mainly based on wallet address, so a series of activities related to the address constitute the most native decentralized digital identity DID of WEB3, and it can be naturally interoperable between different dApp applications without barriers. In this way, users can quickly find their acquaintance and friends when they enter new applications and games, without having to re-add them back by themselves like in WEB2 world. -Imagine a peer-to-peer chat where you can find the desired contact by simply searching for xxx. evm instead of an 18-digit irregular address starting with 0x. What a wonderful experience, and each EVM domain is unique so you don't have to worry about matching the wrong person. -Moreover, by using a DID name to connect to various cryptocurrency addresses, you can receive cryptocurrency payments from others through that domain name without having to copy and paste long addresses. - - - Decentralized Super Business Card -Each DID domain is a unique NFT, and the owner is free to set the content they wish to map or record, in addition to the common EVM wallet address, other cryptocurrency addresses, but also avatars/pictures, Email, Website, profile, Twitter/Telegram accounts and other content, no one can tamper or delete the information, the user has full control of his or her identity information. A DID may seem like a simple domain name, but it contains unlimited content, and** is a super business card for the WEB3 world.** - - - Personal decentralized WEB3 homepage/website -EVMNS allows users to create personal decentralized homepages/websites and upload them to the Interplanetary File System (IPFS), a global network of storage protocols that allow computers around the world to store and share data in a peer-to-peer fashion. -In short, EVMNS and IPFS can help users to establish personal homepages/blogs and websites, with functions similar to the combination of RSS feeds + WEB3 Medium. **Users will have full ownership, including domain name, content and data,** completely avoiding the possibility of being deleted by registrars/data operators. - - - WEB3 Infrastructure -DID is also known as the "identity infrastructure" of WEB3 applications. As discussed above, it is basically determined that DID and avatar are the basic and essential elements of WEB3, being the identity of the WEB3 world. - -- **DID Market Analysis** - - ENS (Ethereum Name Service) -ENS was launched on May 4, 2017 by Alex Van de Sande and Nick Johnson of the ETH Foundation. In November 2021, ENS issued its own governance token and launched an airdrop. At the same time, ENS established the ENS DAO to enable community governance, where token holders will participate in the management of the assets, as well as voting on DAO proposals and co-voting on the use of the vault. -Earlier in the interview Vitalik said, "**The Ethereum Domain Name Service ENS is by far the most successful non-financial ETH application,** which can basically be compared to a decentralized phone book." -As of November 27, 2022, the** total amount of ENS domain registration reached 2.79 million** and the number of Ethereum addresses holding ENS domains reached 609,000. Since November 2021, the number of monthly ENS registrations has shown explosive growth, reaching a peak of 437,000 monthly registrations in September 2022. -![](https://github.com/evmns/evm_name_service/blob/main/t2.png?raw=true ) -###### Data source dune.com/makoto/ens -**Total registration revenue of ENS domains has exceeded $60 million,** of which nearly $50 million has been realized so far in 2022 alone. **Total secondary market transactions have reached 112.39K ETH and $197 million.** +* #### Why DID is needed + * ##### Human readable and easy to remember WEB3 username + Although each of us has a unique ID number, in our daily life, we generally use 'name' as an identifier of one's identity (although there will be renames) because it is easier for daily communication. + + The world of WEB3 has the same problem: while people currently interact primarily based on wallet addresses, no one wants to remember that long string of characters. If the digital identity of WEB3 needs a 'name', then what EVMNS is doing is hoping to be that 'name'. + + * ##### A more user-friendly WEB3 experience + In WEB2 world, digital identity is platform-centered, and different products within the same group are connected through an account system. For example, Tencent's mailbox, games and finance can all use the same account; Google, Facebook and other top Internet enterprises also have their own account systems. Although this kind of identity system is easy to build, its disadvantages have been widely known: the accounts between platforms do not interoperate with each other, and users have no way to control their own identity data. + + In WEB3 world, user interaction is mainly based on wallet address, so a series of activities related to the address constitute the most native decentralized digital identity DID of WEB3, and it can be naturally interoperable between different dApp applications without barriers. In this way, users can quickly find their acquaintance and friends when they enter new applications and games, without having to re-add them back by themselves like in WEB2 world. + + Imagine a peer-to-peer chat where you can find the desired contact by simply searching for xxx. evm instead of an 18-digit irregular address starting with 0x. What a wonderful experience, and each EVM domain is unique so you don't have to worry about matching the wrong person. + + Moreover, by using a DID name to connect to various cryptocurrency addresses, you can receive cryptocurrency payments from others through that domain name without having to copy and paste long addresses. + + * ##### Decentralized Super Business Card + Each DID domain is a unique NFT, and the owner is free to set the content they wish to map or record, in addition to the common EVM wallet address, other cryptocurrency addresses, but also avatars/pictures, Email, Website, profile, Twitter/Telegram accounts and other content, no one can tamper or delete the information, the user has full control of his or her identity information. A DID may seem like a simple domain name, but it contains unlimited content, and** is a super business card for the WEB3 world.** + + * ##### Personal decentralized WEB3 homepage/website + EVMNS allows users to create personal decentralized homepages/websites and upload them to the Interplanetary File System (IPFS), a global network of storage protocols that allow computers around the world to store and share data in a peer-to-peer fashion. + + In short, EVMNS and IPFS can help users to establish personal homepages/blogs and websites, with functions similar to the combination of RSS feeds + WEB3 Medium. **Users will have full ownership, including domain name, content and data,** completely avoiding the possibility of being deleted by registrars/data operators. + + * ##### WEB3 Infrastructure + DID is also known as the "identity infrastructure" of WEB3 applications. As discussed above, it is basically determined that DID and avatar are the basic and essential elements of WEB3, being the identity of the WEB3 world. + +* #### DID Market Analysis + ##### ENS (Ethereum Name Service) + ENS was launched on May 4, 2017 by Alex Van de Sande and Nick Johnson of the ETH Foundation. In November 2021, ENS issued its own governance token and launched an airdrop. At the same time, ENS established the ENS DAO to enable community governance, where token holders will participate in the management of the assets, as well as voting on DAO proposals and co-voting on the use of the vault. + + Earlier in the interview Vitalik said, "**The Ethereum Domain Name Service ENS is by far the most successful non-financial ETH application,** which can basically be compared to a decentralized phone book." + + As of November 27, 2022, **the total amount of ENS domain registration reached 2.79 million** and the number of Ethereum addresses holding ENS domains reached 609,000. Since November 2021, the number of monthly ENS registrations has shown explosive growth, reaching a peak of 437,000 monthly registrations in September 2022. + +
+ +
（Data source dune.com/makoto/ens)
+ +**Total registration revenue of ENS domains has exceeded $60 million,** of which nearly $50 million has been realized so far in 2022 alone. Total secondary market transactions have reached 112.39K ETH and $197 million. + ![](https://github.com/evmns/evm_name_service/blob/main/t3.png?raw=true ) -###### Data source NFTGO.io + +
（Data source NFTGO.io）
Whether it is the registration scale, transaction scale, or the number of holder’s addresses, ENS is far ahead of similar projects, occupying the absolute leading position and having the strongest community consensus. -The following is the partial sales of historical. -paradigm.eth, 420ETH -000.eth, 300ETH -Opensea.eth, 99.89ETH -Nike.eth, 60ETH -Samsung.eth, 60ETH - - SPACE ID (BNB Chain Name Service) -SPACE ID is a decentralized domain naming service protocol developed based on BNB Chain, officially launched in August 2022, with .bnb as the domain suffix, essentially the same as ENS, and dedicated to building a common name service network that seamlessly connects people, information, assets and applications across the blockchain. And by allowing users to bind their identities across multiple chains, communities can build their own domain naming services through SPACE ID's network. To date, more than 40 applications have announced that they have enabled integration of the SPACE ID protocol. -A seed round of funding led by Binance Labs was completed on September 2nd, 2022 for an undisclosed amount. -As of November 27, 2022, SPACE ID domain name total registrations reached 304,000, the total number of holders’ addresses reached 98,700, and the total registration revenue was 14,700 BNB, USD 4.42 million (1 BNB = USD 300). The total secondary market transaction size was about 22,000 BNB, 6.60 million USD. + +The following is the partial sales of historical.
+paradigm.eth, 420ETH
+000.eth, 300ETH
+Opensea.eth, 99.89ETH
+Nike.eth, 60ETH
+Samsung.eth, 60ETH
+ + +##### SPACE ID (BNB Chain Name Service) + SPACE ID is a decentralized domain naming service protocol developed based on BNB Chain, officially launched in August 2022, with .bnb as the domain suffix, essentially the same as ENS, and dedicated to building a common name service network that seamlessly connects people, information, assets and applications across the blockchain. And by allowing users to bind their identities across multiple chains, communities can build their own domain naming services through SPACE ID's network. To date, more than 40 applications have announced that they have enabled integration of the SPACE ID protocol. + +**A seed round of funding led by Binance Labs was completed on September 2nd, 2022 for an undisclosed amount.** + +As of November 27, 2022, SPACE ID domain name total registrations reached 304,000, the total number of holders’ addresses reached 98,700, and **the total registration revenue was 14,700 BNB, USD 4.42 million** (1 BNB = USD 300). The total secondary market transaction size was about 22,000 BNB, 6.60 million USD. + ![](https://github.com/evmns/evm_name_service/blob/main/t4.png?raw=true ) -###### Data source dune.com/spaceid/spaceid + +
（Data source dune.com/spaceid/spaceid）
+ At present, WEB3 domain services like ENS and SPACE ID are also BNS on Binance, Bonfida on Solana, EVNS on Evmos, PNS on Polka, and cross-chain DID service‘.bit’, etc. The DID domain naming service protocol has become one of the basic items of every blockchain, showing a blossoming market state. From ecbf3aadb5b4e3e90c97257ba1629d3f6e4b5b55 Mon Sep 17 00:00:00 2001 From: Evm_nams_service <118707458+evmns@users.noreply.github.com> Date: Tue, 29 Nov 2022 09:18:06 +0800 Subject: [PATCH 017/170] Update EVMNS.md --- applications/EVMNS.md | 1 + 1 file changed, 1 insertion(+) diff --git a/applications/EVMNS.md b/applications/EVMNS.md index f378381f..21662e90 100644 --- a/applications/EVMNS.md +++ b/applications/EVMNS.md @@ -176,6 +176,7 @@ Team members have participated in several medium to large scale EOS projects bef | 0b. | Documentation | Provide and update documentation for this milestone in the form of instruction files and examples in the repository, provide guidance in the Readme file, and more in-depth guidance in our articles. | | 0c. | Testing Guide | The functions of this milestone can be tested by running the unit tests we provide, and guidance on how to run these tests is provided in the Readme file. | | 0d. | Docker | Use Docker to start a container that runs a local nodevm instance where specific users and contracts are deployed for developer testing. This ensures that developers have the same environment when using EVMNS. | +| 0e. | Article| We will publish an English article about the project on medium.com, explaining how smart contracts work and how the project will be used. Also, we will illustrate the goals and outcomes set through the grant.| | 1 | New version of the official website | Including project introduction, domain registration and management, instruction documents, etc. | | 2 | Deployment of test networks | Deploy the test environment and conduct public testing to further ensure the smooth launch and security of the system | From 5371606d732a08602748b1578a4c7c72ac98ae6d Mon Sep 17 00:00:00 2001 From: Evm_nams_service <118707458+evmns@users.noreply.github.com> Date: Tue, 29 Nov 2022 09:35:51 +0800 Subject: [PATCH 018/170] Update EVMNS.md --- applications/EVMNS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/applications/EVMNS.md b/applications/EVMNS.md index 21662e90..44e9e802 100644 --- a/applications/EVMNS.md +++ b/applications/EVMNS.md @@ -12,7 +12,7 @@ # Contact **Contact Name:** Harry Davis -**Contact Email:** evmns_manager@outloook.com +**Contact Email:** evmns_manager@outlook.com **Website:** N/A From f5337e0fbd611e016a6b8bdb219a1d48f7957d2c Mon Sep 17 00:00:00 2001 From: Evm_nams_service <118707458+evmns@users.noreply.github.com> Date: Tue, 29 Nov 2022 10:18:02 +0800 Subject: [PATCH 019/170] Update EVMNS.md --- applications/EVMNS.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/applications/EVMNS.md b/applications/EVMNS.md index 44e9e802..e9ba56f8 100644 --- a/applications/EVMNS.md +++ b/applications/EVMNS.md @@ -23,7 +23,7 @@ EVMNS domains use the ERC721 protocol standard with .evm as the domain suffix, s ### Overview - **Name:** EVMNS (EVM Name Service) - **Brief Description:** A distributed, open and extensible multi-chain DID domain naming system built on EVM and EOS -- **Relationship to EOSIO:** EVMNS's multi-chain layout will bring more new users to EOS and EVM, because it helps users of other chains to know and understand EOS and EVM, and to enjoy the unique advantages of EOS (industry-leading block speed, high TPS and low transaction cost), and help EOS to expand its positive influence in the WEB3 world. +- **Relationship to EOSIO:** EVMNS's multi-chain layout will bring more new users to EOS and EVM, because it helps users of other chains to know and understand EOS and EVM, and to enjoy the unique advantages of EOS (industry-leading transaction speeds, high TPS and low transaction cost), and help EOS to expand its positive influence in the WEB3 world. - **Reason for Interest:** WEB3 trend is developing rapidly, a set of DID domain naming system with perfect function, multi-chain layout and good user experience is the "identity infrastructure" of WEB3 application, and it can be confirmed that DID is like an avatar, which is the basic and essential element and the identity of WEB3 world. For more information, see our research **< Why DID is needed\>** in Additional Information at the end of this article. ### Project Details @@ -64,7 +64,7 @@ The domain owner in the EVMNS registry is capable of:
* #### Where and how does your project fit into the ecosystem? EOS has integrated short domain name function in the main chain since its launch, and naturally supports user-defined account name, which is the first to achieve a good experience of human readability and easy to remember, **It would be a great pity if this advantage is not continued on EVM,** As we know, EVMNS, as a DID domain naming system, can fulfill the requirement well and help EVM to better continue the convenience and efficiency of EOS. - Considering the better integration of EVM and EOS users, EOS mainnet users will have the privilege to register EVM domains (5-digit and above length domains) at a special price, **which not only fills the gap in the EOS ecological DID domain system, but also further helps the growth of EOS user scale** (more new users will create EOS accounts in order to get the privilege to register EVM domain at a special price. In addition, it also helps EOS users to have the same experience of EOS account name on EVM, and EOS users can also create their own decentralized super business cards, personal decentralized WEB3 homepage/website. It's a multi-benefit! + Considering the better integration of EVM and EOS users, EOS mainnet users will have the privilege to register EVM domains (5-digit and above length domains) at a special price, **which not only fills the gap in the EOS ecological DID domain system, but also further helps the growth of EOS user scale** (more new users will create EOS accounts in order to get the privilege to register EVM domain at a special price). In addition, it also helps EOS users to have the same experience of EOS account name on EVM, and EOS users can also create their own decentralized super business cards, personal decentralized WEB3 homepage/website. It's a multi-benefit! What's more, EVMNS will also provides free technical support to holders of existing short names on the EOS mainnet to assist them in issuing corresponding DID domain service agreements in the EVM, such as assisting holder of short name‘eos’to issue domain contract with the suffix .eos on EVM, contributing to the ecological prosperity of EOS and the EVM together. * #### Who is your target audience ? From 5b99ae4d086a0752e05b48375a8b7fb6e01c036f Mon Sep 17 00:00:00 2001 From: Evm_nams_service <118707458+evmns@users.noreply.github.com> Date: Tue, 29 Nov 2022 10:28:53 +0800 Subject: [PATCH 020/170] Update EVMNS.md --- applications/EVMNS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/applications/EVMNS.md b/applications/EVMNS.md index e9ba56f8..109ee319 100644 --- a/applications/EVMNS.md +++ b/applications/EVMNS.md @@ -66,7 +66,7 @@ The domain owner in the EVMNS registry is capable of:
Considering the better integration of EVM and EOS users, EOS mainnet users will have the privilege to register EVM domains (5-digit and above length domains) at a special price, **which not only fills the gap in the EOS ecological DID domain system, but also further helps the growth of EOS user scale** (more new users will create EOS accounts in order to get the privilege to register EVM domain at a special price). In addition, it also helps EOS users to have the same experience of EOS account name on EVM, and EOS users can also create their own decentralized super business cards, personal decentralized WEB3 homepage/website. It's a multi-benefit! - What's more, EVMNS will also provides free technical support to holders of existing short names on the EOS mainnet to assist them in issuing corresponding DID domain service agreements in the EVM, such as assisting holder of short name‘eos’to issue domain contract with the suffix .eos on EVM, contributing to the ecological prosperity of EOS and the EVM together. + What's more, EVMNS will also provides free technical support to holders of existing short names on the EOS mainnet to assist them in issuing corresponding DID domain service agreements in the EVM, such as assisting holder of short name ‘eos’ to issue domain protocol with the suffix .eos on EVM, contributing to the ecological prosperity of EOS and the EVM together. * #### Who is your target audience ? Our users are positioned as WEB3 ecological users, corresponding to blockchains including but not limited to EOS, EVM, ETH, BSC, etc. * #### What need(s) does your project meet? From 707ae24aaf5a51abfb61153ae53099911b216f38 Mon Sep 17 00:00:00 2001 From: Evm_nams_service <118707458+evmns@users.noreply.github.com> Date: Tue, 29 Nov 2022 10:48:58 +0800 Subject: [PATCH 021/170] Update EVMNS.md --- applications/EVMNS.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/applications/EVMNS.md b/applications/EVMNS.md index 109ee319..8297c4d2 100644 --- a/applications/EVMNS.md +++ b/applications/EVMNS.md @@ -196,7 +196,7 @@ We learned of the program by following announcements on ENF’s Twitter and othe ### Some of our research * #### What is DID -DID is the abbreviation of‘Decentralized Identity’, which is a kind of digital identity without a centralized institution as the final guarantee, and is an extension and expansion in WEB 3 of the concept of "user portrait" in WEB2. +DID is the abbreviation of ‘Decentralized Identity’ , which is a kind of digital identity without a centralized institution as the final guarantee, and is an extension and expansion in WEB 3 of the concept of "user portrait" in WEB2. The final form of DID development may be that each user has a unique network-wide identity, and multiple local identities for segmented scenarios. Users remember and identify DIDs through domains, manage DIDs and interact with applications through wallets, and integrate different credentials and local identities on multiple chains through wallets. @@ -216,7 +216,7 @@ The final form of DID development may be that each user has a unique network-wid Moreover, by using a DID name to connect to various cryptocurrency addresses, you can receive cryptocurrency payments from others through that domain name without having to copy and paste long addresses. * ##### Decentralized Super Business Card - Each DID domain is a unique NFT, and the owner is free to set the content they wish to map or record, in addition to the common EVM wallet address, other cryptocurrency addresses, but also avatars/pictures, Email, Website, profile, Twitter/Telegram accounts and other content, no one can tamper or delete the information, the user has full control of his or her identity information. A DID may seem like a simple domain name, but it contains unlimited content, and** is a super business card for the WEB3 world.** + Each DID domain is a unique NFT, and the owner is free to set the content they wish to map or record, in addition to the common EVM wallet address, other cryptocurrency addresses, but also avatars/pictures, Email, Website, profile, Twitter/Telegram accounts and other content, no one can tamper or delete the information, the user has full control of his or her identity information. A DID may seem like a simple domain name, but it contains unlimited content, and **is a super business card for the WEB3 world.** * ##### Personal decentralized WEB3 homepage/website EVMNS allows users to create personal decentralized homepages/websites and upload them to the Interplanetary File System (IPFS), a global network of storage protocols that allow computers around the world to store and share data in a peer-to-peer fashion. From 482d292ee9123485ca6e8fae0d3e9ad035a04ba7 Mon Sep 17 00:00:00 2001 From: Evm_nams_service <118707458+evmns@users.noreply.github.com> Date: Tue, 29 Nov 2022 10:57:12 +0800 Subject: [PATCH 022/170] Update EVMNS.md --- applications/EVMNS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/applications/EVMNS.md b/applications/EVMNS.md index 8297c4d2..fa953cb7 100644 --- a/applications/EVMNS.md +++ b/applications/EVMNS.md @@ -244,7 +244,7 @@ The final form of DID development may be that each user has a unique network-wid
（Data source NFTGO.io）
Whether it is the registration scale, transaction scale, or the number of holder’s addresses, ENS is far ahead of similar projects, occupying the absolute leading position and having the strongest community consensus. - +

The following is the partial sales of historical.
paradigm.eth, 420ETH
000.eth, 300ETH
From a7f22c243fe03f2d17edc489877f28e5cbb3a306 Mon Sep 17 00:00:00 2001 From: Evm_nams_service <118707458+evmns@users.noreply.github.com> Date: Tue, 29 Nov 2022 13:45:56 +0800 Subject: [PATCH 023/170] Update EVMNS.md --- applications/EVMNS.md | 55 +++++++++++++++++-------------------------- 1 file changed, 22 insertions(+), 33 deletions(-) diff --git a/applications/EVMNS.md b/applications/EVMNS.md index fa953cb7..e53037c7 100644 --- a/applications/EVMNS.md +++ b/applications/EVMNS.md @@ -27,39 +27,28 @@ EVMNS domains use the ERC721 protocol standard with .evm as the domain suffix, s - **Reason for Interest:** WEB3 trend is developing rapidly, a set of DID domain naming system with perfect function, multi-chain layout and good user experience is the "identity infrastructure" of WEB3 application, and it can be confirmed that DID is like an avatar, which is the basic and essential element and the identity of WEB3 world. For more information, see our research **< Why DID is needed\>** in Additional Information at the end of this article. ### Project Details - -* #### Mock-ups/designs of any UI components - We will build the official website, including project introduction, domain registry and management, and explanatory documents, etc., to provide users with a complete one-stop experience. -* #### Implementation Overview - EVMNS has two principal components. **Registry and Resolvers.** -![](https://github.com/evmns/evm_name_service/blob/main/registry.png?raw=true ) - * #### EVMNS Registry - The EVMNS registry is a smart contract that maintains a list of all domains and subdomains and stores three critical pieces of information about each domain: the owner of the domain, the resolver for the domain, and the caching time-to-live for all records under the domain. - - The owner of a name can be an external account (a user) or a smart contract. A registrar is a smart contract that owns a top-level domain and distributes subdomains of that domain to users according to the rules in the contract. -The domain owner in the EVMNS registry is capable of:
-1.Set the resolver and TTL for the domain;
-2.Transfer ownership of the domain to another address;
-3.Change the ownership of subdomains; - - The EVMNS registry exists simply to map domains to the resolver responsible for resolving that domain. - - * #### Resolvers - The resolver is responsible for converting domains to addresses. Any smart contract that meets the criteria related to resolvers can be used as a resolver program in EVMNS. - - Each record type (EVM address, content hash, etc.) defines one or more methods that the resolver must implement in order to provide such records. Adding a new record type does not require changes to the EVMNS registry or to existing resolvers. - - Resolving a domain in EVMNS requires two steps: the first step is to ask the registry which resolver is responsible for the domain; the second step is to query that resolver for the result. - - Let's say we want to find the EVM address pointed by "abc.evm". First, we ask the registry which resolver is responsible for resolving "abc.evm"; then, we ask that resolver for the address of "abc.evm". - - * #### About Namehash - Resource constraints in smart contracts make it inefficient to interact directly with readable names, so EVMNS uses only fixed length 256-bit cryptographic hashes. In order to generate hashes from names while still retaining their hierarchical nature, EVMNS uses an algorithm called Namehash, which is used only to represent names within EVMNS. - - Namehash is a recursive process that generates a unique hash for any valid name. Starting from the Namehash of any name (e.g., the Namehash of "abc.evm"), one can derive the Namehash of any subname (e.g., the Namehash of "ab. abc.evm"), and the derivation process does not require knowledge of or processing of the readable original name "abc.evm". It is this feature that allows EVMNS to be a hierarchical system without having to deal with readable text strings internally. - - Before using Namehash for hashing, the name first needs to be normalized with the help of the UTS-46 standard to ensure that the letters in the name are case-insensitive and to prohibit the use of invalid characters. Any hashing and resolving of names must first be normalized to ensure that all users get consistency of EVMNS. - +- **Mock-ups/designs of any UI components**

+ We will build the official website, including project introduction, domain registry and management, and explanatory documents, etc., to provide users with a complete one-stop experience.

+- **Implementation Overview**

+ EVMNS has two principal components. **Registry and Resolvers.**
+ ![](https://github.com/evmns/evm_name_service/blob/main/registry.png?raw=true ) + - **EVMNS Registry**
+ The EVMNS registry is a smart contract that maintains a list of all domains and subdomains and stores three critical pieces of information about each domain: the owner of the domain, the resolver for the domain, and the caching time-to-live for all records under the domain.

+ The owner of a name can be an external account (a user) or a smart contract. A registrar is a smart contract that owns a top-level domain and distributes subdomains of that domain to users according to the rules in the contract.

+ The domain owner in the EVMNS registry is capable of:
+ 1.Set the resolver and TTL for the domain;
+ 2.Transfer ownership of the domain to another address;
+ 3.Change the ownership of subdomains;

+ The EVMNS registry exists simply to map domains to the resolver responsible for resolving that domain.
+ - **Resolvers**
+ The resolver is responsible for converting domains to addresses. Any smart contract that meets the criteria related to resolvers can be used as a resolver program in EVMNS.

+ Each record type (EVM address, content hash, etc.) defines one or more methods that the resolver must implement in order to provide such records. Adding a new record type does not require changes to the EVMNS registry or to existing resolvers.
+ Resolving a domain in EVMNS requires two steps: the first step is to ask the registry which resolver is responsible for the domain; the second step is to query that resolver for the result.

+ Let's say we want to find the EVM address pointed by "abc.evm". First, we ask the registry which resolver is responsible for resolving "abc.evm"; then, we ask that resolver for the address of "abc.evm".
+ - **About Namehash**
+ Resource constraints in smart contracts make it inefficient to interact directly with readable names, so EVMNS uses only fixed length 256-bit cryptographic hashes. In order to generate hashes from names while still retaining their hierarchical nature, EVMNS uses an algorithm called Namehash, which is used only to represent names within EVMNS.

+ Namehash is a recursive process that generates a unique hash for any valid name. Starting from the Namehash of any name (e.g., the Namehash of "abc.evm"), one can derive the Namehash of any subname (e.g., the Namehash of "ab. abc.evm"), and the derivation process does not require knowledge of or processing of the readable original name "abc.evm". It is this feature that allows EVMNS to be a hierarchical system without having to deal with readable text strings internally.

+ Before using Namehash for hashing, the name first needs to be normalized with the help of the UTS-46 standard to ensure that the letters in the name are case-insensitive and to prohibit the use of invalid characters. Any hashing and resolving of names must first be normalized to ensure that all users get consistency of EVMNS.
### Ecosystem Fit * #### Where and how does your project fit into the ecosystem? EOS has integrated short domain name function in the main chain since its launch, and naturally supports user-defined account name, which is the first to achieve a good experience of human readability and easy to remember, **It would be a great pity if this advantage is not continued on EVM,** As we know, EVMNS, as a DID domain naming system, can fulfill the requirement well and help EVM to better continue the convenience and efficiency of EOS. From 51259f2527b34e1ff4a4e2c8e16546be9415b9e2 Mon Sep 17 00:00:00 2001 From: DefiboxTeam Date: Tue, 29 Nov 2022 18:37:01 +0800 Subject: [PATCH 024/170] Update Defibox_vault.md --- applications/Defibox_vault.md | 154 +++++++++++++++++++--------------- 1 file changed, 85 insertions(+), 69 deletions(-) diff --git a/applications/Defibox_vault.md b/applications/Defibox_vault.md index 2bb066be..0a21e3e6 100644 --- a/applications/Defibox_vault.md +++ b/applications/Defibox_vault.md @@ -7,7 +7,7 @@ - **Pomelo Grant(s):** https://pomelo.io/grants/vault - **Project is Open-Source:** Yes - **Project was part of Token sale:** No -- **Repository where Project resides:** NA +- **Repository where Project resides:** https://github.com/DefiboxTeam/DefiboxVault-interface > 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 @@ -18,6 +18,32 @@ > ⚠️ *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.* + +## Open source +Timelines to open source + +- **Stage 1 (Immediately) “Version beta v0.1.0”** +https://github.com/defiboxswap/DefiboxVault-interface + +Includes *.hpp interface + +Prebuilt WASM binaries *.wasm & *.abi (with version control) + +General documentation README.md + +Protocol Design (diagram) + +- **Stage 2 (work to be completed)** + +Protocol Design Definition (translated in English/Korean/Chinese) + +Automated unit tests written with Vert + +- **Stage 3 (re-evaluation 2nd Security Audit from Certik) “Version v1.0.0”** + +All smart contract source code will be made available (*.cpp) + + ## 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. @@ -31,11 +57,6 @@ - **Relationship to EOSIO:** a public use that provides a variety of staking strategies to EOS users and project teams for more yields. Code will be open source for contribution to EOSIO repository. - **Reason for Interest:** It provides a variety of staking strategies to EOS users and project teams for more yields. It will brings TVL and income to Defibox team while giving benefits to participants. Ecosystem Boost: attract inactive EOS tokens which will prosper ecosystem -### Project Details -https://eos.defibox.io/vault -https://bloks.io/account/vault.defi -https://bloks.io/account/stoken.defi  -Everything is on the website and contract ### Ecosystem Fit @@ -83,58 +104,38 @@ https://github.com/defiboxswap > 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. -## Development Status -https://eos.defibox.io/vault - -https://bloks.io/account/vault.defi - -https://bloks.io/account/stoken.defi  - -https://twitter.com/DefiboxOfficial/status/1593966063334871042 - -Reaching 3 million EOS TVL in 53 hours ### Milestone Summary -- **Total Estimated Duration:** 3 months +- **Total Estimated Duration:** 3 months (remaining 3 weeks) - **Full-Time Equivalent (FTE):** 5 FTE - **Total Costs:** 80,000 USD - **Deliverables:** -Staking yield system template that includes: -Protocol design -Smart contract development -User documentation -Technical documentation -Unit tests -User test instructions - - -Full launch as milestone reached, 80,000 USD for total cost in which 24,000 USD for security audit fees and 56,000 USD for development cost. - -## Future Plans - -Promote the project with big prize event: https://eos.defibox.io/lottery -Fully support sEOS (vault asset) in all our DeFi protocol + | Deliverable | Status | Cost | + | ---------- | :-----------: | :-----------: | + | Protocol Design - Diagram | Completed | $3,000 | + | Protocol Design - Definitions (EN/KO/CN) | Not completed | $5,000 | + | SC development (prototype) | Completed | $12,000 | + | SC development (production) | Not completed | $12,000 | + | Developer documentation | Completed | $4,000 | + | User documentation | Not completed | $6,000 | + | Automatic Contracts Tests | Not completed | $14,000 | + | Certik Audit | Completed | $24,000 | + | Total | Not completed | $80,000 | ## Additional Information **How did you hear about the Grants Program?** EOS Network Foundation Website -**Launch Data** 3,000,000 EOS TVL within 53 hours since launch, at the moment, it is 3,400,000 EOS. -![image](https://user-images.githubusercontent.com/93515916/203501096-b20bcd1d-95cc-4aeb-ba46-6a69dfbc0a44.png) - - -***Audit by Certik:** https://www.certik.com/projects/defibox -***Open source: Source code made available to ENF and later to the public upon ENF request*** ------------------------------------------------------------------------------------------------------------------------------ -**Chinese Translation** +# Chinese Translation 中文翻译 - **项目名称：** 金库协议 (Vault) - **团队名称：** Defibox @@ -143,14 +144,39 @@ Fully support sEOS (vault asset) in all our DeFi protocol - **Pomelo资助：** https://pomelo.io/grants/vault - **项目是开源的：** 是 - **项目是代币销售的一部分：** 否 -- **项目资源库：** 不适用 +- **项目资源库：** https://github.com/DefiboxTeam/DefiboxVault-interface -**联系人** +### 联系人 - **联系人姓名：** Raven - **联系邮箱：** raven@defibox.io - **网站：** https://eos.defibox.io/vault -**项目概况** +### 开源 +开源时间表 + +- **第一阶段（立即）“测试版 v0.1.0”** +https://github.com/defiboxswap/DefiboxVault-interface + +包括 *.hpp 界面 + +预构建的 WASM 二进制文件 *.wasm & *.abi（带版本控制） + +通用文档 README.md + +协议设计（示意图） + +- **第二阶段（待完成的工作）** + +协议设计定义（英文/韩文/中文翻译） + + +使用 Vert 编写的自动化单元测试 + +- **第三阶段（Certik 重新评估第二次安全审计）“版本 v1.0.0”** + +将提供所有智能合约源代码 (*.cpp) + +### 项目概况 **概述** - **名称：金库协议** @@ -158,15 +184,8 @@ Fully support sEOS (vault asset) in all our DeFi protocol - **与EOSIO的关系：** 一种公共设施，为 EOS用户和项目团队提供各种质押策略以获得更多收益，并提供开源，这将有助于EOSIO代码资源库。 - **感兴趣的原因：** 它为 EOS 用户和项目团队提供了多种质押策略以获得更多收益。它将为 Defibox 团队带来锁仓量和收入，同时让参与者受益。生态系统提升：吸引不活跃的EOS代币，这将繁荣生态系统。 -- **项目详情** --https://eos.defibox.io/vault --https://bloks.io/account/vault.defi --https://bloks.io/account/stoken.defi -https://twitter.com/DefiboxOfficial/status/1593966063334871042 -上线53小时内获得3,000,000 EOS 锁仓量 - -**生态系统** +### 生态系统 - **您的项目在哪里以及如何融入生态系统？** -用户可以通过存入代币获得相应的代币收益。资产可灵活存取，链上数据公开透明。 Valut收益主要来自Defibox协议收益、Yield+奖励、BP收益、REX收益等。同时，为了提高效用，协议会发行一个标准的EOS代币sToken，代表存单。 sToken可以在多种DeFi协议中使用以获得更多收益。 @@ -182,7 +201,7 @@ https://twitter.com/DefiboxOfficial/status/1593966063334871042 - **如果是这样，您的项目有何不同？** -Vault广泛支持EOS上的所有用户，而BSS仅适用于拥有BOX代币的Defibox用户。 -**团队** +### 团队 - **团队成员：** 16 - **团队负责人：** Eason @@ -198,29 +217,26 @@ https://twitter.com/DefiboxOfficial/status/1593966063334871042 **里程碑总结** -- **总预计持续时间：**3 个月 +- **总预计持续时间：**3 个月 （剩余3周） - **全职当量 (FTE)：**5 FTE -- **总成本：** 80,000 美元，其中 24,000 美元用于安全审计费用，56,000 美元用于开发成本。 -- **可交付成果：** -质押收益系统模板，包括： -协议设计 -智能合约开发 -用户文档 -技术文档 -单元测试 -用户测试说明 +- **总成本：** 80,000 美元 +- **可交付成果：** + + | 可交付成果 | 状态 | 成本 | + | ---------- | :-----------: | :-----------: | + | 协议设计 - 原型图 | 完成 | $3,000 | + | 协议设计 - 原型图（中/英/韩） | 未完成 | $5,000 | + | 智能合约开发（原型） | 完成 | $12,000 | + | 智能合约开发（生产） | 未完成 | $12,000 | + | 开发者文档 | 完成 | $4,000 | + | 用户文档 | 未完成 | $6,000 | + | 自动合约测试 | 未完成 | $14,000 | + | Certik审计 | 完成 | $24,000 | + | 合计 | 未完成 | $80,000 | -**未来的计划** --高额奖金活动宣传项目：https://eos.defibox.io/lottery -在我们所有的 DeFi 协议中完全支持 sEOS（金库资产） **附加信息** **您是如何得知赠款计划的？：** EOS网络基金会网站 -**上线数据** 上线53小时内获得3,000,000 EOS 锁仓量，目前锁仓量约为3,400,000 EOS。 -![image](https://user-images.githubusercontent.com/93515916/203501634-7ee79252-dff3-48dd-96f7-b941d58bea66.png) - -***Certik审计：*** https://www.certik.com/projects/defibox -***关于开源：对ENF开源并随后根据ENF的要求对社区开源*** From 86f9564199fed68a615e2e085970d62ab2cd14a2 Mon Sep 17 00:00:00 2001 From: Evm_nams_service <118707458+evmns@users.noreply.github.com> Date: Tue, 29 Nov 2022 18:59:12 +0800 Subject: [PATCH 025/170] Update EVMNS.md --- applications/EVMNS.md | 108 ++++++++++++++---------------------------- 1 file changed, 36 insertions(+), 72 deletions(-) diff --git a/applications/EVMNS.md b/applications/EVMNS.md index e53037c7..66e77ee0 100644 --- a/applications/EVMNS.md +++ b/applications/EVMNS.md @@ -50,26 +50,20 @@ EVMNS domains use the ERC721 protocol standard with .evm as the domain suffix, s Namehash is a recursive process that generates a unique hash for any valid name. Starting from the Namehash of any name (e.g., the Namehash of "abc.evm"), one can derive the Namehash of any subname (e.g., the Namehash of "ab. abc.evm"), and the derivation process does not require knowledge of or processing of the readable original name "abc.evm". It is this feature that allows EVMNS to be a hierarchical system without having to deal with readable text strings internally.

Before using Namehash for hashing, the name first needs to be normalized with the help of the UTS-46 standard to ensure that the letters in the name are case-insensitive and to prohibit the use of invalid characters. Any hashing and resolving of names must first be normalized to ensure that all users get consistency of EVMNS.
### Ecosystem Fit -* #### Where and how does your project fit into the ecosystem? - EOS has integrated short domain name function in the main chain since its launch, and naturally supports user-defined account name, which is the first to achieve a good experience of human readability and easy to remember, **It would be a great pity if this advantage is not continued on EVM,** As we know, EVMNS, as a DID domain naming system, can fulfill the requirement well and help EVM to better continue the convenience and efficiency of EOS. - - Considering the better integration of EVM and EOS users, EOS mainnet users will have the privilege to register EVM domains (5-digit and above length domains) at a special price, **which not only fills the gap in the EOS ecological DID domain system, but also further helps the growth of EOS user scale** (more new users will create EOS accounts in order to get the privilege to register EVM domain at a special price). In addition, it also helps EOS users to have the same experience of EOS account name on EVM, and EOS users can also create their own decentralized super business cards, personal decentralized WEB3 homepage/website. It's a multi-benefit! - - What's more, EVMNS will also provides free technical support to holders of existing short names on the EOS mainnet to assist them in issuing corresponding DID domain service agreements in the EVM, such as assisting holder of short name ‘eos’ to issue domain protocol with the suffix .eos on EVM, contributing to the ecological prosperity of EOS and the EVM together. -* #### Who is your target audience ? +- **Where and how does your project fit into the ecosystem?** + EOS has integrated short domain name function in the main chain since its launch, and naturally supports user-defined account name, which is the first to achieve a good experience of human readability and easy to remember, **It would be a great pity if this advantage is not continued on EVM,** As we know, EVMNS, as a DID domain naming system, can fulfill the requirement well and help EVM to better continue the convenience and efficiency of EOS.
+Considering the better integration of EVM and EOS users, EOS mainnet users will have the privilege to register EVM domains (5-digit and above length domains) at a special price, **which not only fills the gap in the EOS ecological DID domain system, but also further helps the growth of EOS user scale** (more new users will create EOS accounts in order to get the privilege to register EVM domain at a special price). In addition, it also helps EOS users to have the same experience of EOS account name on EVM, and EOS users can also create their own decentralized super business cards, personal decentralized WEB3 homepage/website. It's a multi-benefit!
+What's more, EVMNS will also provides free technical support to holders of existing short names on the EOS mainnet to assist them in issuing corresponding DID domain service agreements in the EVM, such as assisting holder of short name ‘eos’ to issue domain protocol with the suffix .eos on EVM, contributing to the ecological prosperity of EOS and the EVM together. +- **Who is your target audience ?** Our users are positioned as WEB3 ecological users, corresponding to blockchains including but not limited to EOS, EVM, ETH, BSC, etc. -* #### What need(s) does your project meet? - **One identity accessible to multiple blockchains.** There is no doubt that we are moving towards a multi-chain future, where each WEB3 user travels through different blockchains and dApps, having and managing multiple identities, multiple usernames, multiple sets of identity information, full of tedium and inconvenience and lacking a good experience. - - With EVMNS, you can ensure that one universal identity remains intact, not only for all applications, but for all blockchains. You will only have to manage one set of identities, such as your profile, Email, Twitter, Telegram, ETH address, EOS address, EVM address, etc. How wonderful it will be to be able to sync to all chains with one edit. - - EVMNS will also meet these needs: human readable and memorable WEB3 usernames, a more user-friendly experience in WEB3 world, decentralized super business cards, and personal decentralized WEB3 homepage/website. For more information, see our research **< Why DID is needed>** in Additional Information at the end of this article. -* #### Are there any other projects similar to yours in the EOSIO ecosystem? - There are no other projects on EOS and EVM ecosystem that are similar to EVMNS for now. - - But there are similar DID projects in other blockchains, such as ENS on ETH, SPACE ID on BSC, Bonfida on Solana, EVNS on Evmos, PNS on Polka, and cross-chain DID service‘.bit’, etc. The DID domain naming service protocol has become one of the basic projects on every blockchain, showing a blossoming market. See our research **< DID Market Analysis>** in Additional Information at the end of this article for more details on the market. - - Compared to other DID domain projects, EVMNS has a special feature. Benefited from EOS's industry-leading transaction speeds (0.5 seconds), high TPS and low transaction costs, users will have an unparalleled experience when using EVMNS. They will be able to confirm the successful modification of their identity information in seconds, without worrying about block congestion or the cost of interacting with the chain, and will be able to enjoy the WEB3 world more smoothly, which will be an important advantage of EVMNS. +- **What need(s) does your project meet?** + **One identity accessible to multiple blockchains.** There is no doubt that we are moving towards a multi-chain future, where each WEB3 user travels through different blockchains and dApps, having and managing multiple identities, multiple usernames, multiple sets of identity information, full of tedium and inconvenience and lacking a good experience. +With EVMNS, you can ensure that one universal identity remains intact, not only for all applications, but for all blockchains. You will only have to manage one set of identities, such as your profile, Email, Twitter, Telegram, ETH address, EOS address, EVM address, etc. How wonderful it will be to be able to sync to all chains with one edit. +EVMNS will also meet these needs: human readable and memorable WEB3 usernames, a more user-friendly experience in WEB3 world, decentralized super business cards, and personal decentralized WEB3 homepage/website. For more information, see our research **< Why DID is needed>** in Additional Information at the end of this article. +- **Are there any other projects similar to yours in the EOSIO ecosystem?** +There are no other projects on EOS and EVM ecosystem that are similar to EVMNS for now. +But there are similar DID projects in other blockchains, such as ENS on ETH, SPACE ID on BSC, Bonfida on Solana, EVNS on Evmos, PNS on Polka, and cross-chain DID service‘.bit’, etc. The DID domain naming service protocol has become one of the basic projects on every blockchain, showing a blossoming market. See our research **< DID Market Analysis>** in Additional Information at the end of this article for more details on the market. +Compared to other DID domain projects, EVMNS has a special feature. Benefited from EOS's industry-leading transaction speeds (0.5 seconds), high TPS and low transaction costs, users will have an unparalleled experience when using EVMNS. They will be able to confirm the successful modification of their identity information in seconds, without worrying about block congestion or the cost of interacting with the chain, and will be able to enjoy the WEB3 world more smoothly, which will be an important advantage of EVMNS. # Team ### Team members @@ -184,75 +178,45 @@ Therefore, the development content, duration and cost of the multi-chain ecology We learned of the program by following announcements on ENF’s Twitter and other channels. ### Some of our research -* #### What is DID -DID is the abbreviation of ‘Decentralized Identity’ , which is a kind of digital identity without a centralized institution as the final guarantee, and is an extension and expansion in WEB 3 of the concept of "user portrait" in WEB2. - +- **What is DID** + DID is the abbreviation of ‘Decentralized Identity’ , which is a kind of digital identity without a centralized institution as the final guarantee, and is an extension and expansion in WEB 3 of the concept of "user portrait" in WEB2. The final form of DID development may be that each user has a unique network-wide identity, and multiple local identities for segmented scenarios. Users remember and identify DIDs through domains, manage DIDs and interact with applications through wallets, and integrate different credentials and local identities on multiple chains through wallets. - -* #### Why DID is needed - * ##### Human readable and easy to remember WEB3 username +- **Why DID is needed** + - **Human readable and easy to remember WEB3 username** Although each of us has a unique ID number, in our daily life, we generally use 'name' as an identifier of one's identity (although there will be renames) because it is easier for daily communication. - - The world of WEB3 has the same problem: while people currently interact primarily based on wallet addresses, no one wants to remember that long string of characters. If the digital identity of WEB3 needs a 'name', then what EVMNS is doing is hoping to be that 'name'. - - * ##### A more user-friendly WEB3 experience - In WEB2 world, digital identity is platform-centered, and different products within the same group are connected through an account system. For example, Tencent's mailbox, games and finance can all use the same account; Google, Facebook and other top Internet enterprises also have their own account systems. Although this kind of identity system is easy to build, its disadvantages have been widely known: the accounts between platforms do not interoperate with each other, and users have no way to control their own identity data. - - In WEB3 world, user interaction is mainly based on wallet address, so a series of activities related to the address constitute the most native decentralized digital identity DID of WEB3, and it can be naturally interoperable between different dApp applications without barriers. In this way, users can quickly find their acquaintance and friends when they enter new applications and games, without having to re-add them back by themselves like in WEB2 world. - - Imagine a peer-to-peer chat where you can find the desired contact by simply searching for xxx. evm instead of an 18-digit irregular address starting with 0x. What a wonderful experience, and each EVM domain is unique so you don't have to worry about matching the wrong person. - - Moreover, by using a DID name to connect to various cryptocurrency addresses, you can receive cryptocurrency payments from others through that domain name without having to copy and paste long addresses. - - * ##### Decentralized Super Business Card +The world of WEB3 has the same problem: while people currently interact primarily based on wallet addresses, no one wants to remember that long string of characters. If the digital identity of WEB3 needs a 'name', then what EVMNS is doing is hoping to be that 'name'. + - **A more user-friendly WEB3 experience** + In WEB2 world, digital identity is platform-centered, and different products within the same group are connected through an account system. For example, Tencent's mailbox, games and finance can all use the same account; Google, Facebook and other top Internet enterprises also have their own account systems. Although this kind of identity system is easy to build, its disadvantages have been widely known: the accounts between platforms do not interoperate with each other, and users have no way to control their own identity data.
+In WEB3 world, user interaction is mainly based on wallet address, so a series of activities related to the address constitute the most native decentralized digital identity DID of WEB3, and it can be naturally interoperable between different dApp applications without barriers. In this way, users can quickly find their acquaintance and friends when they enter new applications and games, without having to re-add them back by themselves like in WEB2 world.
+Imagine a peer-to-peer chat where you can find the desired contact by simply searching for xxx. evm instead of an 18-digit irregular address starting with 0x. What a wonderful experience, and each EVM domain is unique so you don't have to worry about matching the wrong person.
+Moreover, by using a DID name to connect to various cryptocurrency addresses, you can receive cryptocurrency payments from others through that domain name without having to copy and paste long addresses.
+ - **Decentralized Super Business Card** Each DID domain is a unique NFT, and the owner is free to set the content they wish to map or record, in addition to the common EVM wallet address, other cryptocurrency addresses, but also avatars/pictures, Email, Website, profile, Twitter/Telegram accounts and other content, no one can tamper or delete the information, the user has full control of his or her identity information. A DID may seem like a simple domain name, but it contains unlimited content, and **is a super business card for the WEB3 world.** - - * ##### Personal decentralized WEB3 homepage/website - EVMNS allows users to create personal decentralized homepages/websites and upload them to the Interplanetary File System (IPFS), a global network of storage protocols that allow computers around the world to store and share data in a peer-to-peer fashion. - - In short, EVMNS and IPFS can help users to establish personal homepages/blogs and websites, with functions similar to the combination of RSS feeds + WEB3 Medium. **Users will have full ownership, including domain name, content and data,** completely avoiding the possibility of being deleted by registrars/data operators. - - * ##### WEB3 Infrastructure + - **Personal decentralized WEB3 homepage/website** + EVMNS allows users to create personal decentralized homepages/websites and upload them to the Interplanetary File System (IPFS), a global network of storage protocols that allow computers around the world to store and share data in a peer-to-peer fashion. +In short, EVMNS and IPFS can help users to establish personal homepages/blogs and websites, with functions similar to the combination of RSS feeds + WEB3 Medium. **Users will have full ownership, including domain name, content and data,** completely avoiding the possibility of being deleted by registrars/data operators. + - **WEB3 Infrastructure** DID is also known as the "identity infrastructure" of WEB3 applications. As discussed above, it is basically determined that DID and avatar are the basic and essential elements of WEB3, being the identity of the WEB3 world. - -* #### DID Market Analysis - ##### ENS (Ethereum Name Service) +- **DID Market Analysis**
+ **ENS (Ethereum Name Service)**
ENS was launched on May 4, 2017 by Alex Van de Sande and Nick Johnson of the ETH Foundation. In November 2021, ENS issued its own governance token and launched an airdrop. At the same time, ENS established the ENS DAO to enable community governance, where token holders will participate in the management of the assets, as well as voting on DAO proposals and co-voting on the use of the vault. - - Earlier in the interview Vitalik said, "**The Ethereum Domain Name Service ENS is by far the most successful non-financial ETH application,** which can basically be compared to a decentralized phone book." - - As of November 27, 2022, **the total amount of ENS domain registration reached 2.79 million** and the number of Ethereum addresses holding ENS domains reached 609,000. Since November 2021, the number of monthly ENS registrations has shown explosive growth, reaching a peak of 437,000 monthly registrations in September 2022. - -
- -
（Data source dune.com/makoto/ens)
- -**Total registration revenue of ENS domains has exceeded $60 million,** of which nearly $50 million has been realized so far in 2022 alone. Total secondary market transactions have reached 112.39K ETH and $197 million. - +Earlier in the interview Vitalik said, "**The Ethereum Domain Name Service ENS is by far the most successful non-financial ETH application,** which can basically be compared to a decentralized phone book." +As of November 27, 2022, **the total amount of ENS domain registration reached 2.79 million** and the number of Ethereum addresses holding ENS domains reached 609,000. Since November 2021, the number of monthly ENS registrations has shown explosive growth, reaching a peak of 437,000 monthly registrations in September 2022.
（Data source dune.com/makoto/ens)
**Total registration revenue of ENS domains has exceeded $60 million,** of which nearly $50 million has been realized so far in 2022 alone. Total secondary market transactions have reached 112.39K ETH and $197 million. ![](https://github.com/evmns/evm_name_service/blob/main/t3.png?raw=true ) -
（Data source NFTGO.io）
-Whether it is the registration scale, transaction scale, or the number of holder’s addresses, ENS is far ahead of similar projects, occupying the absolute leading position and having the strongest community consensus. -

+Whether it is the registration scale, transaction scale, or the number of holder’s addresses, ENS is far ahead of similar projects, occupying the absolute leading position and having the strongest community consensus.

The following is the partial sales of historical.
paradigm.eth, 420ETH
000.eth, 300ETH
-Opensea.eth, 99.89ETH
-Nike.eth, 60ETH
-Samsung.eth, 60ETH
- - +1.Opensea.eth, 99.89ETH
+2.Nike.eth, 60ETH
+3.Samsung.eth, 60ETH
##### SPACE ID (BNB Chain Name Service) SPACE ID is a decentralized domain naming service protocol developed based on BNB Chain, officially launched in August 2022, with .bnb as the domain suffix, essentially the same as ENS, and dedicated to building a common name service network that seamlessly connects people, information, assets and applications across the blockchain. And by allowing users to bind their identities across multiple chains, communities can build their own domain naming services through SPACE ID's network. To date, more than 40 applications have announced that they have enabled integration of the SPACE ID protocol. - **A seed round of funding led by Binance Labs was completed on September 2nd, 2022 for an undisclosed amount.** - As of November 27, 2022, SPACE ID domain name total registrations reached 304,000, the total number of holders’ addresses reached 98,700, and **the total registration revenue was 14,700 BNB, USD 4.42 million** (1 BNB = USD 300). The total secondary market transaction size was about 22,000 BNB, 6.60 million USD. - ![](https://github.com/evmns/evm_name_service/blob/main/t4.png?raw=true ) -
（Data source dune.com/spaceid/spaceid）
- At present, WEB3 domain services like ENS and SPACE ID are also BNS on Binance, Bonfida on Solana, EVNS on Evmos, PNS on Polka, and cross-chain DID service‘.bit’, etc. The DID domain naming service protocol has become one of the basic items of every blockchain, showing a blossoming market state. From cb03687d1e22b22346e419a7fd5f750618fcb7f9 Mon Sep 17 00:00:00 2001 From: Evm_nams_service <118707458+evmns@users.noreply.github.com> Date: Tue, 29 Nov 2022 19:24:33 +0800 Subject: [PATCH 026/170] Update EVMNS.md --- applications/EVMNS.md | 227 +++++++++++++++++++----------------------- 1 file changed, 102 insertions(+), 125 deletions(-) diff --git a/applications/EVMNS.md b/applications/EVMNS.md index 66e77ee0..c10d3090 100644 --- a/applications/EVMNS.md +++ b/applications/EVMNS.md @@ -1,30 +1,27 @@ # EOS Network Foundation Grant Proposal -- **Project Name:** EVMNS (EVM Name Service) -- **Team Name:** EVMNS Labs -- **EOS Payment Address:** evmnsdomains -- **Level:** 3 -- **Pomelo Grant(s):** N/A -- **Project is Open-Source:** Yes +- **Project Name:** EVMNS (EVM Name Service)
+- **Team Name:** EVMNS Labs
+- **EOS Payment Address:** evmnsdomains
+- **Level:** 3
+- **Pomelo Grant(s):** N/A
+- **Project is Open-Source:** Yes
- **Project was part of Token sale:** No -- **Repository where Project resides:** https://github.com/evmns/EVMNS +- **Repository where Project resides:** https://github.com/evmns/EVMNS
# Contact -**Contact Name:** Harry Davis - -**Contact Email:** evmns_manager@outlook.com - -**Website:** N/A +**Contact Name:** Harry Davis
+**Contact Email:** evmns_manager@outlook.com
+**Website:** N/A
# Project Overview -**EVMNS (EVM Name Service) is a distributed, open and extensible multi-chain DID domain naming system built on EVM and EOS,** relying on the high performance, security and reliability of EOS to better and seamlessly connect people, information, assets, dApps, etc. in the WEB3 world. - -EVMNS domains use the ERC721 protocol standard with .evm as the domain suffix, such as abc.evm, 123.evm, jack.evm, etc., to map human-readable and easy-to-remember names with all kinds of content at the same time, including but not limited to EVM addresses, EOS addresses, other cryptocurrency addresses, content hashes, URLs, and metadata. +**EVMNS (EVM Name Service) is a distributed, open and extensible multi-chain DID domain naming system built on EVM and EOS,** relying on the high performance, security and reliability of EOS to better and seamlessly connect people, information, assets, dApps, etc. in the WEB3 world.

+EVMNS domains use the ERC721 protocol standard with .evm as the domain suffix, such as abc.evm, 123.evm, jack.evm, etc., to map human-readable and easy-to-remember names with all kinds of content at the same time, including but not limited to EVM addresses, EOS addresses, other cryptocurrency addresses, content hashes, URLs, and metadata.

### Overview -- **Name:** EVMNS (EVM Name Service) -- **Brief Description:** A distributed, open and extensible multi-chain DID domain naming system built on EVM and EOS -- **Relationship to EOSIO:** EVMNS's multi-chain layout will bring more new users to EOS and EVM, because it helps users of other chains to know and understand EOS and EVM, and to enjoy the unique advantages of EOS (industry-leading transaction speeds, high TPS and low transaction cost), and help EOS to expand its positive influence in the WEB3 world. -- **Reason for Interest:** WEB3 trend is developing rapidly, a set of DID domain naming system with perfect function, multi-chain layout and good user experience is the "identity infrastructure" of WEB3 application, and it can be confirmed that DID is like an avatar, which is the basic and essential element and the identity of WEB3 world. For more information, see our research **< Why DID is needed\>** in Additional Information at the end of this article. +- **Name:** EVMNS (EVM Name Service)
+- **Brief Description:** A distributed, open and extensible multi-chain DID domain naming system built on EVM and EOS.
+- **Relationship to EOSIO:** EVMNS's multi-chain layout will bring more new users to EOS and EVM, because it helps users of other chains to know and understand EOS and EVM, and to enjoy the unique advantages of EOS (industry-leading transaction speeds, high TPS and low transaction cost), and help EOS to expand its positive influence in the WEB3 world.
+- **Reason for Interest:** WEB3 trend is developing rapidly, a set of DID domain naming system with perfect function, multi-chain layout and good user experience is the "identity infrastructure" of WEB3 application, and it can be confirmed that DID is like an avatar, which is the basic and essential element and the identity of WEB3 world. For more information, see our research **< Why DID is needed\>** in Additional Information at the end of this article.

### Project Details - **Mock-ups/designs of any UI components**

@@ -32,64 +29,58 @@ EVMNS domains use the ERC721 protocol standard with .evm as the domain suffix, s - **Implementation Overview**

EVMNS has two principal components. **Registry and Resolvers.**
![](https://github.com/evmns/evm_name_service/blob/main/registry.png?raw=true ) - - **EVMNS Registry**
+ - **EVMNS Registry**

The EVMNS registry is a smart contract that maintains a list of all domains and subdomains and stores three critical pieces of information about each domain: the owner of the domain, the resolver for the domain, and the caching time-to-live for all records under the domain.

The owner of a name can be an external account (a user) or a smart contract. A registrar is a smart contract that owns a top-level domain and distributes subdomains of that domain to users according to the rules in the contract.

The domain owner in the EVMNS registry is capable of:
1.Set the resolver and TTL for the domain;
2.Transfer ownership of the domain to another address;
3.Change the ownership of subdomains;

- The EVMNS registry exists simply to map domains to the resolver responsible for resolving that domain.
- - **Resolvers**
+ The EVMNS registry exists simply to map domains to the resolver responsible for resolving that domain.

+ - **Resolvers**

The resolver is responsible for converting domains to addresses. Any smart contract that meets the criteria related to resolvers can be used as a resolver program in EVMNS.

- Each record type (EVM address, content hash, etc.) defines one or more methods that the resolver must implement in order to provide such records. Adding a new record type does not require changes to the EVMNS registry or to existing resolvers.
+ Each record type (EVM address, content hash, etc.) defines one or more methods that the resolver must implement in order to provide such records. Adding a new record type does not require changes to the EVMNS registry or to existing resolvers.

Resolving a domain in EVMNS requires two steps: the first step is to ask the registry which resolver is responsible for the domain; the second step is to query that resolver for the result.

- Let's say we want to find the EVM address pointed by "abc.evm". First, we ask the registry which resolver is responsible for resolving "abc.evm"; then, we ask that resolver for the address of "abc.evm".
- - **About Namehash**
+ Let's say we want to find the EVM address pointed by "abc.evm". First, we ask the registry which resolver is responsible for resolving "abc.evm"; then, we ask that resolver for the address of "abc.evm".

+ - **About Namehash**

Resource constraints in smart contracts make it inefficient to interact directly with readable names, so EVMNS uses only fixed length 256-bit cryptographic hashes. In order to generate hashes from names while still retaining their hierarchical nature, EVMNS uses an algorithm called Namehash, which is used only to represent names within EVMNS.

Namehash is a recursive process that generates a unique hash for any valid name. Starting from the Namehash of any name (e.g., the Namehash of "abc.evm"), one can derive the Namehash of any subname (e.g., the Namehash of "ab. abc.evm"), and the derivation process does not require knowledge of or processing of the readable original name "abc.evm". It is this feature that allows EVMNS to be a hierarchical system without having to deal with readable text strings internally.

- Before using Namehash for hashing, the name first needs to be normalized with the help of the UTS-46 standard to ensure that the letters in the name are case-insensitive and to prohibit the use of invalid characters. Any hashing and resolving of names must first be normalized to ensure that all users get consistency of EVMNS.
+ Before using Namehash for hashing, the name first needs to be normalized with the help of the UTS-46 standard to ensure that the letters in the name are case-insensitive and to prohibit the use of invalid characters. Any hashing and resolving of names must first be normalized to ensure that all users get consistency of EVMNS.

### Ecosystem Fit -- **Where and how does your project fit into the ecosystem?** - EOS has integrated short domain name function in the main chain since its launch, and naturally supports user-defined account name, which is the first to achieve a good experience of human readability and easy to remember, **It would be a great pity if this advantage is not continued on EVM,** As we know, EVMNS, as a DID domain naming system, can fulfill the requirement well and help EVM to better continue the convenience and efficiency of EOS.
-Considering the better integration of EVM and EOS users, EOS mainnet users will have the privilege to register EVM domains (5-digit and above length domains) at a special price, **which not only fills the gap in the EOS ecological DID domain system, but also further helps the growth of EOS user scale** (more new users will create EOS accounts in order to get the privilege to register EVM domain at a special price). In addition, it also helps EOS users to have the same experience of EOS account name on EVM, and EOS users can also create their own decentralized super business cards, personal decentralized WEB3 homepage/website. It's a multi-benefit!
-What's more, EVMNS will also provides free technical support to holders of existing short names on the EOS mainnet to assist them in issuing corresponding DID domain service agreements in the EVM, such as assisting holder of short name ‘eos’ to issue domain protocol with the suffix .eos on EVM, contributing to the ecological prosperity of EOS and the EVM together. -- **Who is your target audience ?** - Our users are positioned as WEB3 ecological users, corresponding to blockchains including but not limited to EOS, EVM, ETH, BSC, etc. -- **What need(s) does your project meet?** - **One identity accessible to multiple blockchains.** There is no doubt that we are moving towards a multi-chain future, where each WEB3 user travels through different blockchains and dApps, having and managing multiple identities, multiple usernames, multiple sets of identity information, full of tedium and inconvenience and lacking a good experience. -With EVMNS, you can ensure that one universal identity remains intact, not only for all applications, but for all blockchains. You will only have to manage one set of identities, such as your profile, Email, Twitter, Telegram, ETH address, EOS address, EVM address, etc. How wonderful it will be to be able to sync to all chains with one edit. -EVMNS will also meet these needs: human readable and memorable WEB3 usernames, a more user-friendly experience in WEB3 world, decentralized super business cards, and personal decentralized WEB3 homepage/website. For more information, see our research **< Why DID is needed>** in Additional Information at the end of this article. -- **Are there any other projects similar to yours in the EOSIO ecosystem?** -There are no other projects on EOS and EVM ecosystem that are similar to EVMNS for now. -But there are similar DID projects in other blockchains, such as ENS on ETH, SPACE ID on BSC, Bonfida on Solana, EVNS on Evmos, PNS on Polka, and cross-chain DID service‘.bit’, etc. The DID domain naming service protocol has become one of the basic projects on every blockchain, showing a blossoming market. See our research **< DID Market Analysis>** in Additional Information at the end of this article for more details on the market. -Compared to other DID domain projects, EVMNS has a special feature. Benefited from EOS's industry-leading transaction speeds (0.5 seconds), high TPS and low transaction costs, users will have an unparalleled experience when using EVMNS. They will be able to confirm the successful modification of their identity information in seconds, without worrying about block congestion or the cost of interacting with the chain, and will be able to enjoy the WEB3 world more smoothly, which will be an important advantage of EVMNS. - +- **Where and how does your project fit into the ecosystem?**

+ EOS has integrated short domain name function in the main chain since its launch, and naturally supports user-defined account name, which is the first to achieve a good experience of human readability and easy to remember, **It would be a great pity if this advantage is not continued on EVM,** As we know, EVMNS, as a DID domain naming system, can fulfill the requirement well and help EVM to better continue the convenience and efficiency of EOS.

+Considering the better integration of EVM and EOS users, EOS mainnet users will have the privilege to register EVM domains (5-digit and above length domains) at a special price, **which not only fills the gap in the EOS ecological DID domain system, but also further helps the growth of EOS user scale** (more new users will create EOS accounts in order to get the privilege to register EVM domain at a special price). In addition, it also helps EOS users to have the same experience of EOS account name on EVM, and EOS users can also create their own decentralized super business cards, personal decentralized WEB3 homepage/website. It's a multi-benefit!

+What's more, EVMNS will also provides free technical support to holders of existing short names on the EOS mainnet to assist them in issuing corresponding DID domain service agreements in the EVM, such as assisting holder of short name ‘eos’ to issue domain protocol with the suffix .eos on EVM, contributing to the ecological prosperity of EOS and the EVM together.

+- **Who is your target audience ?**

+ Our users are positioned as WEB3 ecological users, corresponding to blockchains including but not limited to EOS, EVM, ETH, BSC, etc.

+- **What need(s) does your project meet?**

+ **One identity accessible to multiple blockchains.** There is no doubt that we are moving towards a multi-chain future, where each WEB3 user travels through different blockchains and dApps, having and managing multiple identities, multiple usernames, multiple sets of identity information, full of tedium and inconvenience and lacking a good experience.

+With EVMNS, you can ensure that one universal identity remains intact, not only for all applications, but for all blockchains. You will only have to manage one set of identities, such as your profile, Email, Twitter, Telegram, ETH address, EOS address, EVM address, etc. How wonderful it will be to be able to sync to all chains with one edit.

+EVMNS will also meet these needs: human readable and memorable WEB3 usernames, a more user-friendly experience in WEB3 world, decentralized super business cards, and personal decentralized WEB3 homepage/website. For more information, see our research **< Why DID is needed>** in Additional Information at the end of this article.

+- **Are there any other projects similar to yours in the EOSIO ecosystem?**

+There are no other projects on EOS and EVM ecosystem that are similar to EVMNS for now.

+But there are similar DID projects in other blockchains, such as ENS on ETH, SPACE ID on BSC, Bonfida on Solana, EVNS on Evmos, PNS on Polka, and cross-chain DID service‘.bit’, etc. The DID domain naming service protocol has become one of the basic projects on every blockchain, showing a blossoming market. See our research **< DID Market Analysis>** in Additional Information at the end of this article for more details on the market.

+Compared to other DID domain projects, EVMNS has a special feature. Benefited from EOS's industry-leading transaction speeds (0.5 seconds), high TPS and low transaction costs, users will have an unparalleled experience when using EVMNS. They will be able to confirm the successful modification of their identity information in seconds, without worrying about block congestion or the cost of interacting with the chain, and will be able to enjoy the WEB3 world more smoothly, which will be an important advantage of EVMNS.

# Team ### Team members -- **Team Leader: Harry Davis** -- Allen Harris -- Frank Lee - +- **Team Leader: Harry Davis**
+- Allen Harris
+- Frank Lee
### Legal Structure -- **Registered Legal Entity:** Jump Dream PTE. LTD. -- **Registered Address:** 5001 Beach Road#07-37, Golden Mile Complex, Singapore 199588 - +- **Registered Legal Entity:** Jump Dream PTE. LTD.
+- **Registered Address:** 5001 Beach Road#07-37, Golden Mile Complex, Singapore 199588
### Team Experience -The core members of EVMNS Labs are the first ecological participants of EOS, who experienced and witnessed the launch of EOS and are still deeply involved in the ecological construction. - -Team members have participated in several medium to large scale EOS projects before and after, and also developed ENS (Ethereum Name Service) related domain Exchange, domain bulk registry protocol, etc. We are not only EOS loyalists, but also ENS heavy players, with good understanding of DID domain naming system. - +The core members of EVMNS Labs are the first ecological participants of EOS, who experienced and witnessed the launch of EOS and are still deeply involved in the ecological construction.

+Team members have participated in several medium to large scale EOS projects before and after, and also developed ENS (Ethereum Name Service) related domain Exchange, domain bulk registry protocol, etc. We are not only EOS loyalists, but also ENS heavy players, with good understanding of DID domain naming system.

# Development Roadmap ### Milestone Summary -- **Estimated project development duration:** 12 weeks -- **Full Time Equivalent Employees (FTE):** 6 -- **Total cost:** $195,000 - +- **Estimated project development duration:** 12 weeks
+- **Full Time Equivalent Employees (FTE):** 6
+- **Total cost:** $195,000
### Milestone 1 - Requirements Analysis and official website -- **Estimated project development duration:** 2 weeks -- **Full Time Equivalent Employees (FTE):** 2 -- **Total cost:** $20,000 +- **Estimated project development duration:** 2 weeks
+- **Full Time Equivalent Employees (FTE):** 2
+- **Total cost:** $20,000
| ID | Deliverable |Specification| | ------------ | ------------ | ------------ | @@ -98,14 +89,11 @@ Team members have participated in several medium to large scale EOS projects bef | 0c. | Testing Guide | The functions of this milestone can be tested by running the unit tests we provide, and guidance on how to run these tests is provided in the Readme file. | | 0d. | Docker | Use Docker to start a container that runs a local nodevm instance where specific users and contracts are deployed for developer testing. This ensures that developers have the same environment when using EVMNS. | | 1 | Demand Analysis | Unpacking requirements, developing business process diagrams, planning business modules, standardizing development documentation and testing processes, etc. | -| 2 | Release official website | Including project introduction, Roadmap and other content. | - - +| 2 | Release official website | Including project introduction, Roadmap and other content. |

### Milestone 2 - Smart Contracts - -- **Estimated project development duration:** 4 weeks -- **Full Time Equivalent Employees (FTE):** 5 -- **Total cost:** $100,000 +- **Estimated project development duration:** 4 weeks
+- **Full Time Equivalent Employees (FTE):** 5
+- **Total cost:** $100,000
| ID | Deliverable |Specification| | ------------ | ------------ | ------------ | @@ -116,12 +104,11 @@ Team members have participated in several medium to large scale EOS projects bef | 1 | Core Contracts | At the core of EVMNS is a smart contract that maintains a list of all domains and sub-domains and stores three key pieces of information about each domain: the owner of the domain, the resolver of the domain, and the cached time to live (i.e., TTL) for all records under the domain. | | 2 | Domain registrar | EVMNS allows domain owners to manage all their domains, including sub-domain registrations. We will provide standard domain registration contracts and interfaces, allowing all compliant contracts to access and renew, transfer and other operations for domains. | | 3 | Root Node Management | Completing the design of the root node, EVMNS will lock the control of the root node so that the root owner cannot influence the ownership of the .evm domain and set the root node to be held jointly by the community in a multi-signature contract, guaranteeing all the power of the user. | -| 4 | Domain Resolver | Resolvers are responsible for the actual process of translating names into addresses. Any contract that implements the relevant standards may act as a resolver in EVMNS. | - +| 4 | Domain Resolver | Resolvers are responsible for the actual process of translating names into addresses. Any contract that implements the relevant standards may act as a resolver in EVMNS. |

### Milestone 3 - Key Systems and Components -- **Estimated project development duration:** 3 weeks -- **Full Time Equivalent Employees (FTE):** 3 -- **Total cost:** $45,000 +- **Estimated project development duration:** 3 weeks
+- **Full Time Equivalent Employees (FTE):** 3
+- **Total cost:** $45,000
| ID | Deliverable |Specification| | ------------ | ------------ | ------------ | @@ -132,12 +119,11 @@ Team members have participated in several medium to large scale EOS projects bef | 1 | Domain Manager | The Domain Manager in EVMNS is a domain management contract that allows domain owners to manage the domains they own, change names in the registry and transfer ownership to anyone else. | | 2 | Reverse resolver | The reverse resolver in EVMNS provides the ability to declare reverse records for use in configuring records as a convenient feature most commonly used as a way to specify address specification names. | | 3 | Metadata Storage Management System | Store the domain metadata independently in the metadata management system and access the corresponding metadata through api. | -| 4 | Domain Management System | Build EVMNS domain management system to realize administrators capability of financial review, daily log maintenance review, emergency management, etc. for EVMNS. | - +| 4 | Domain Management System | Build EVMNS domain management system to realize administrators capability of financial review, daily log maintenance review, emergency management, etc. for EVMNS. |

### Milestone 4 - In-depth testing -- **Estimated project development duration:** 2 weeks -- **Full Time Equivalent Employees (FTE):** 2 -- **Total cost:** $20,000 +- **Estimated project development duration:** 2 weeks
+- **Full Time Equivalent Employees (FTE):** 2
+- **Total cost:** $20,000
| ID | Deliverable |Specification| | ------------ | ------------ | ------------ | @@ -146,12 +132,11 @@ Team members have participated in several medium to large scale EOS projects bef | 0c. | Testing Guide | The functions of this milestone can be tested by running the unit tests we provide, and guidance on how to run these tests is provided in the Readme file. | | 0d. | Docker | Use Docker to start a container that runs a local nodevm instance where specific users and contracts are deployed for developer testing. This ensures that developers have the same environment when using EVMNS. | | 1 | In-depth test | Automated unit tests with 100% coverage and multiple rounds of functional testing are completed internally to ensure functionality and robustness. | -| 2 | dApp Development Documentation | Establish a perfect dApp development documentation system to meet and support the quick access of dApp developers. | - +| 2 | dApp Development Documentation | Establish a perfect dApp development documentation system to meet and support the quick access of dApp developers. |

### Milestone 5 - Deployment Test Network -- **Estimated project development duration:** 1 week -- **Full Time Equivalent Employees (FTE):** 2 -- **Total cost:** $10,000 +- **Estimated project development duration:** 1 week
+- **Full Time Equivalent Employees (FTE):** 2
+- **Total cost:** $10,000
| ID | Deliverable |Specification| | ------------ | ------------ | ------------ | @@ -161,47 +146,42 @@ Team members have participated in several medium to large scale EOS projects bef | 0d. | Docker | Use Docker to start a container that runs a local nodevm instance where specific users and contracts are deployed for developer testing. This ensures that developers have the same environment when using EVMNS. | | 0e. | Article| We will publish an English article about the project on medium.com, explaining how smart contracts work and how the project will be used. Also, we will illustrate the goals and outcomes set through the grant.| | 1 | New version of the official website | Including project introduction, domain registration and management, instruction documents, etc. | -| 2 | Deployment of test networks | Deploy the test environment and conduct public testing to further ensure the smooth launch and security of the system | - - +| 2 | Deployment of test networks | Deploy the test environment and conduct public testing to further ensure the smooth launch and security of the system |

### Multi-Chain Ecology -Multi-chain ecology is the focus of the second phase of development, and we will prioritize the completion of the first phase of development (the above five milestones) to maximize the assurance that EVMNS can be launched and run stably at the first time after the official launch of EVM. -Therefore, the development content, duration and cost of the multi-chain ecology will be separately defined before the launch of the second phase. - +Multi-chain ecology is the focus of the second phase of development, and we will prioritize the completion of the first phase of development (the above five milestones) to maximize the assurance that EVMNS can be launched and run stably at the first time after the official launch of EVM.

+Therefore, the development content, duration and cost of the multi-chain ecology will be separately defined before the launch of the second phase.

# Future Plans -- We will build EVMNS DAO, realize community management, and promote the implementation of decentralized operation and R&D of EVMNS. -- Register WEB2 domain with .evm suffix with DNS operators for domain resolution and binding services for traditional browsers so that users can directly access websites/personal homepages corresponding to .evm domain in Chrome, Edge and other browsers to achieve good interoperability between WEB3 and WEB2. -- Develop EOS plug-ins and browser plug-ins belonging to EVMNS to help users manage their EVMNS domains more easily through plug-ins, quick access, collection management of EVMNS domains of other users, etc. - +- We will build EVMNS DAO, realize community management, and promote the implementation of decentralized operation and R&D of EVMNS.

+- Register WEB2 domain with .evm suffix with DNS operators for domain resolution and binding services for traditional browsers so that users can directly access websites/personal homepages corresponding to .evm domain in Chrome, Edge and other browsers to achieve good interoperability between WEB3 and WEB2.

+- Develop EOS plug-ins and browser plug-ins belonging to EVMNS to help users manage their EVMNS domains more easily through plug-ins, quick access, collection management of EVMNS domains of other users, etc.

# Additional Information ### How did you hear about the Grants Program? -We learned of the program by following announcements on ENF’s Twitter and other channels. - +We learned of the program by following announcements on ENF’s Twitter and other channels.
### Some of our research -- **What is DID** - DID is the abbreviation of ‘Decentralized Identity’ , which is a kind of digital identity without a centralized institution as the final guarantee, and is an extension and expansion in WEB 3 of the concept of "user portrait" in WEB2. -The final form of DID development may be that each user has a unique network-wide identity, and multiple local identities for segmented scenarios. Users remember and identify DIDs through domains, manage DIDs and interact with applications through wallets, and integrate different credentials and local identities on multiple chains through wallets. -- **Why DID is needed** - - **Human readable and easy to remember WEB3 username** - Although each of us has a unique ID number, in our daily life, we generally use 'name' as an identifier of one's identity (although there will be renames) because it is easier for daily communication. -The world of WEB3 has the same problem: while people currently interact primarily based on wallet addresses, no one wants to remember that long string of characters. If the digital identity of WEB3 needs a 'name', then what EVMNS is doing is hoping to be that 'name'. - - **A more user-friendly WEB3 experience** - In WEB2 world, digital identity is platform-centered, and different products within the same group are connected through an account system. For example, Tencent's mailbox, games and finance can all use the same account; Google, Facebook and other top Internet enterprises also have their own account systems. Although this kind of identity system is easy to build, its disadvantages have been widely known: the accounts between platforms do not interoperate with each other, and users have no way to control their own identity data.
-In WEB3 world, user interaction is mainly based on wallet address, so a series of activities related to the address constitute the most native decentralized digital identity DID of WEB3, and it can be naturally interoperable between different dApp applications without barriers. In this way, users can quickly find their acquaintance and friends when they enter new applications and games, without having to re-add them back by themselves like in WEB2 world.
-Imagine a peer-to-peer chat where you can find the desired contact by simply searching for xxx. evm instead of an 18-digit irregular address starting with 0x. What a wonderful experience, and each EVM domain is unique so you don't have to worry about matching the wrong person.
-Moreover, by using a DID name to connect to various cryptocurrency addresses, you can receive cryptocurrency payments from others through that domain name without having to copy and paste long addresses.
- - **Decentralized Super Business Card** - Each DID domain is a unique NFT, and the owner is free to set the content they wish to map or record, in addition to the common EVM wallet address, other cryptocurrency addresses, but also avatars/pictures, Email, Website, profile, Twitter/Telegram accounts and other content, no one can tamper or delete the information, the user has full control of his or her identity information. A DID may seem like a simple domain name, but it contains unlimited content, and **is a super business card for the WEB3 world.** - - **Personal decentralized WEB3 homepage/website** - EVMNS allows users to create personal decentralized homepages/websites and upload them to the Interplanetary File System (IPFS), a global network of storage protocols that allow computers around the world to store and share data in a peer-to-peer fashion. -In short, EVMNS and IPFS can help users to establish personal homepages/blogs and websites, with functions similar to the combination of RSS feeds + WEB3 Medium. **Users will have full ownership, including domain name, content and data,** completely avoiding the possibility of being deleted by registrars/data operators. - - **WEB3 Infrastructure** - DID is also known as the "identity infrastructure" of WEB3 applications. As discussed above, it is basically determined that DID and avatar are the basic and essential elements of WEB3, being the identity of the WEB3 world. -- **DID Market Analysis**
- **ENS (Ethereum Name Service)**
- ENS was launched on May 4, 2017 by Alex Van de Sande and Nick Johnson of the ETH Foundation. In November 2021, ENS issued its own governance token and launched an airdrop. At the same time, ENS established the ENS DAO to enable community governance, where token holders will participate in the management of the assets, as well as voting on DAO proposals and co-voting on the use of the vault. -Earlier in the interview Vitalik said, "**The Ethereum Domain Name Service ENS is by far the most successful non-financial ETH application,** which can basically be compared to a decentralized phone book." -As of November 27, 2022, **the total amount of ENS domain registration reached 2.79 million** and the number of Ethereum addresses holding ENS domains reached 609,000. Since November 2021, the number of monthly ENS registrations has shown explosive growth, reaching a peak of 437,000 monthly registrations in September 2022.
（Data source dune.com/makoto/ens)
**Total registration revenue of ENS domains has exceeded $60 million,** of which nearly $50 million has been realized so far in 2022 alone. Total secondary market transactions have reached 112.39K ETH and $197 million. +- **What is DID**

+ DID is the abbreviation of ‘Decentralized Identity’ , which is a kind of digital identity without a centralized institution as the final guarantee, and is an extension and expansion in WEB 3 of the concept of "user portrait" in WEB2.

+The final form of DID development may be that each user has a unique network-wide identity, and multiple local identities for segmented scenarios. Users remember and identify DIDs through domains, manage DIDs and interact with applications through wallets, and integrate different credentials and local identities on multiple chains through wallets.

+- **Why DID is needed**

+ - **Human readable and easy to remember WEB3 username**

+ Although each of us has a unique ID number, in our daily life, we generally use 'name' as an identifier of one's identity (although there will be renames) because it is easier for daily communication.

+The world of WEB3 has the same problem: while people currently interact primarily based on wallet addresses, no one wants to remember that long string of characters. If the digital identity of WEB3 needs a 'name', then what EVMNS is doing is hoping to be that 'name'.

+ - **A more user-friendly WEB3 experience**

+ In WEB2 world, digital identity is platform-centered, and different products within the same group are connected through an account system. For example, Tencent's mailbox, games and finance can all use the same account; Google, Facebook and other top Internet enterprises also have their own account systems. Although this kind of identity system is easy to build, its disadvantages have been widely known: the accounts between platforms do not interoperate with each other, and users have no way to control their own identity data.

+In WEB3 world, user interaction is mainly based on wallet address, so a series of activities related to the address constitute the most native decentralized digital identity DID of WEB3, and it can be naturally interoperable between different dApp applications without barriers. In this way, users can quickly find their acquaintance and friends when they enter new applications and games, without having to re-add them back by themselves like in WEB2 world.

+Imagine a peer-to-peer chat where you can find the desired contact by simply searching for xxx. evm instead of an 18-digit irregular address starting with 0x. What a wonderful experience, and each EVM domain is unique so you don't have to worry about matching the wrong person.

+Moreover, by using a DID name to connect to various cryptocurrency addresses, you can receive cryptocurrency payments from others through that domain name without having to copy and paste long addresses.

+ - **Decentralized Super Business Card**

+ Each DID domain is a unique NFT, and the owner is free to set the content they wish to map or record, in addition to the common EVM wallet address, other cryptocurrency addresses, but also avatars/pictures, Email, Website, profile, Twitter/Telegram accounts and other content, no one can tamper or delete the information, the user has full control of his or her identity information. A DID may seem like a simple domain name, but it contains unlimited content, and **is a super business card for the WEB3 world.**

+ - **Personal decentralized WEB3 homepage/website**

+ EVMNS allows users to create personal decentralized homepages/websites and upload them to the Interplanetary File System (IPFS), a global network of storage protocols that allow computers around the world to store and share data in a peer-to-peer fashion.

+In short, EVMNS and IPFS can help users to establish personal homepages/blogs and websites, with functions similar to the combination of RSS feeds + WEB3 Medium. **Users will have full ownership, including domain name, content and data,** completely avoiding the possibility of being deleted by registrars/data operators.

+ - **WEB3 Infrastructure**

+ DID is also known as the "identity infrastructure" of WEB3 applications. As discussed above, it is basically determined that DID and avatar are the basic and essential elements of WEB3, being the identity of the WEB3 world.

+- **DID Market Analysis**

+ **ENS (Ethereum Name Service)**

+ ENS was launched on May 4, 2017 by Alex Van de Sande and Nick Johnson of the ETH Foundation. In November 2021, ENS issued its own governance token and launched an airdrop. At the same time, ENS established the ENS DAO to enable community governance, where token holders will participate in the management of the assets, as well as voting on DAO proposals and co-voting on the use of the vault.

+Earlier in the interview Vitalik said, "**The Ethereum Domain Name Service ENS is by far the most successful non-financial ETH application,** which can basically be compared to a decentralized phone book."

+As of November 27, 2022, **the total amount of ENS domain registration reached 2.79 million** and the number of Ethereum addresses holding ENS domains reached 609,000. Since November 2021, the number of monthly ENS registrations has shown explosive growth, reaching a peak of 437,000 monthly registrations in September 2022.

（Data source dune.com/makoto/ens)
**Total registration revenue of ENS domains has exceeded $60 million,** of which nearly $50 million has been realized so far in 2022 alone. Total secondary market transactions have reached 112.39K ETH and $197 million.

![](https://github.com/evmns/evm_name_service/blob/main/t3.png?raw=true )
（Data source NFTGO.io）
Whether it is the registration scale, transaction scale, or the number of holder’s addresses, ENS is far ahead of similar projects, occupying the absolute leading position and having the strongest community consensus.

@@ -210,14 +190,11 @@ paradigm.eth, 420ETH
000.eth, 300ETH
1.Opensea.eth, 99.89ETH
2.Nike.eth, 60ETH
-3.Samsung.eth, 60ETH
-##### SPACE ID (BNB Chain Name Service) - SPACE ID is a decentralized domain naming service protocol developed based on BNB Chain, officially launched in August 2022, with .bnb as the domain suffix, essentially the same as ENS, and dedicated to building a common name service network that seamlessly connects people, information, assets and applications across the blockchain. And by allowing users to bind their identities across multiple chains, communities can build their own domain naming services through SPACE ID's network. To date, more than 40 applications have announced that they have enabled integration of the SPACE ID protocol. -**A seed round of funding led by Binance Labs was completed on September 2nd, 2022 for an undisclosed amount.** -As of November 27, 2022, SPACE ID domain name total registrations reached 304,000, the total number of holders’ addresses reached 98,700, and **the total registration revenue was 14,700 BNB, USD 4.42 million** (1 BNB = USD 300). The total secondary market transaction size was about 22,000 BNB, 6.60 million USD. +3.Samsung.eth, 60ETH

+##### SPACE ID (BNB Chain Name Service)

+ SPACE ID is a decentralized domain naming service protocol developed based on BNB Chain, officially launched in August 2022, with .bnb as the domain suffix, essentially the same as ENS, and dedicated to building a common name service network that seamlessly connects people, information, assets and applications across the blockchain. And by allowing users to bind their identities across multiple chains, communities can build their own domain naming services through SPACE ID's network. To date, more than 40 applications have announced that they have enabled integration of the SPACE ID protocol.

+**A seed round of funding led by Binance Labs was completed on September 2nd, 2022 for an undisclosed amount.**

+As of November 27, 2022, SPACE ID domain name total registrations reached 304,000, the total number of holders’ addresses reached 98,700, and **the total registration revenue was 14,700 BNB, USD 4.42 million** (1 BNB = USD 300). The total secondary market transaction size was about 22,000 BNB, 6.60 million USD.

![](https://github.com/evmns/evm_name_service/blob/main/t4.png?raw=true )
（Data source dune.com/spaceid/spaceid）
At present, WEB3 domain services like ENS and SPACE ID are also BNS on Binance, Bonfida on Solana, EVNS on Evmos, PNS on Polka, and cross-chain DID service‘.bit’, etc. The DID domain naming service protocol has become one of the basic items of every blockchain, showing a blossoming market state. - - - From f1bca075dd29dd5d0da2945bb68915e8742b51f2 Mon Sep 17 00:00:00 2001 From: Evm_nams_service <118707458+evmns@users.noreply.github.com> Date: Tue, 29 Nov 2022 19:32:46 +0800 Subject: [PATCH 027/170] Update EVMNS.md --- applications/EVMNS.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/applications/EVMNS.md b/applications/EVMNS.md index c10d3090..5bc777ae 100644 --- a/applications/EVMNS.md +++ b/applications/EVMNS.md @@ -154,6 +154,7 @@ Therefore, the development content, duration and cost of the multi-chain ecology - We will build EVMNS DAO, realize community management, and promote the implementation of decentralized operation and R&D of EVMNS.

- Register WEB2 domain with .evm suffix with DNS operators for domain resolution and binding services for traditional browsers so that users can directly access websites/personal homepages corresponding to .evm domain in Chrome, Edge and other browsers to achieve good interoperability between WEB3 and WEB2.

- Develop EOS plug-ins and browser plug-ins belonging to EVMNS to help users manage their EVMNS domains more easily through plug-ins, quick access, collection management of EVMNS domains of other users, etc.

+ # Additional Information ### How did you hear about the Grants Program? We learned of the program by following announcements on ENF’s Twitter and other channels.
@@ -176,12 +177,12 @@ Moreover, by using a DID name to connect to various cryptocurrency addresses, yo EVMNS allows users to create personal decentralized homepages/websites and upload them to the Interplanetary File System (IPFS), a global network of storage protocols that allow computers around the world to store and share data in a peer-to-peer fashion.

In short, EVMNS and IPFS can help users to establish personal homepages/blogs and websites, with functions similar to the combination of RSS feeds + WEB3 Medium. **Users will have full ownership, including domain name, content and data,** completely avoiding the possibility of being deleted by registrars/data operators.

- **WEB3 Infrastructure**

- DID is also known as the "identity infrastructure" of WEB3 applications. As discussed above, it is basically determined that DID and avatar are the basic and essential elements of WEB3, being the identity of the WEB3 world.

+ DID is also known as the "identity infrastructure" of WEB3 applications. As discussed above, it is basically determined that DID and avatar are the basic and essential elements of WEB3, being the identity of the WEB3 world.

- **DID Market Analysis**

**ENS (Ethereum Name Service)**

- ENS was launched on May 4, 2017 by Alex Van de Sande and Nick Johnson of the ETH Foundation. In November 2021, ENS issued its own governance token and launched an airdrop. At the same time, ENS established the ENS DAO to enable community governance, where token holders will participate in the management of the assets, as well as voting on DAO proposals and co-voting on the use of the vault.

+ENS was launched on May 4, 2017 by Alex Van de Sande and Nick Johnson of the ETH Foundation. In November 2021, ENS issued its own governance token and launched an airdrop. At the same time, ENS established the ENS DAO to enable community governance, where token holders will participate in the management of the assets, as well as voting on DAO proposals and co-voting on the use of the vault.

Earlier in the interview Vitalik said, "**The Ethereum Domain Name Service ENS is by far the most successful non-financial ETH application,** which can basically be compared to a decentralized phone book."

-As of November 27, 2022, **the total amount of ENS domain registration reached 2.79 million** and the number of Ethereum addresses holding ENS domains reached 609,000. Since November 2021, the number of monthly ENS registrations has shown explosive growth, reaching a peak of 437,000 monthly registrations in September 2022.

（Data source dune.com/makoto/ens)
**Total registration revenue of ENS domains has exceeded $60 million,** of which nearly $50 million has been realized so far in 2022 alone. Total secondary market transactions have reached 112.39K ETH and $197 million.

+As of November 27, 2022, **the total amount of ENS domain registration reached 2.79 million** and the number of Ethereum addresses holding ENS domains reached 609,000. Since November 2021, the number of monthly ENS registrations has shown explosive growth, reaching a peak of 437,000 monthly registrations in September 2022.


（Data source dune.com/makoto/ens)
**Total registration revenue of ENS domains has exceeded $60 million,** of which nearly $50 million has been realized so far in 2022 alone. Total secondary market transactions have reached 112.39K ETH and $197 million.

![](https://github.com/evmns/evm_name_service/blob/main/t3.png?raw=true )
（Data source NFTGO.io）
Whether it is the registration scale, transaction scale, or the number of holder’s addresses, ENS is far ahead of similar projects, occupying the absolute leading position and having the strongest community consensus.

@@ -191,6 +192,7 @@ paradigm.eth, 420ETH
1.Opensea.eth, 99.89ETH
2.Nike.eth, 60ETH
3.Samsung.eth, 60ETH

+ ##### SPACE ID (BNB Chain Name Service)

SPACE ID is a decentralized domain naming service protocol developed based on BNB Chain, officially launched in August 2022, with .bnb as the domain suffix, essentially the same as ENS, and dedicated to building a common name service network that seamlessly connects people, information, assets and applications across the blockchain. And by allowing users to bind their identities across multiple chains, communities can build their own domain naming services through SPACE ID's network. To date, more than 40 applications have announced that they have enabled integration of the SPACE ID protocol.

**A seed round of funding led by Binance Labs was completed on September 2nd, 2022 for an undisclosed amount.**

From 130aa63fdffd4b2ee6977ec6a302b9e0f7c4c77c Mon Sep 17 00:00:00 2001 From: Evm_nams_service <118707458+evmns@users.noreply.github.com> Date: Tue, 29 Nov 2022 20:06:20 +0800 Subject: [PATCH 028/170] Update EVMNS.md --- applications/EVMNS.md | 34 ++++++++++++++++++---------------- 1 file changed, 18 insertions(+), 16 deletions(-) diff --git a/applications/EVMNS.md b/applications/EVMNS.md index 5bc777ae..662045c5 100644 --- a/applications/EVMNS.md +++ b/applications/EVMNS.md @@ -159,32 +159,34 @@ Therefore, the development content, duration and cost of the multi-chain ecology ### How did you hear about the Grants Program? We learned of the program by following announcements on ENF’s Twitter and other channels.
### Some of our research -- **What is DID**

+#### What is DID DID is the abbreviation of ‘Decentralized Identity’ , which is a kind of digital identity without a centralized institution as the final guarantee, and is an extension and expansion in WEB 3 of the concept of "user portrait" in WEB2.

The final form of DID development may be that each user has a unique network-wide identity, and multiple local identities for segmented scenarios. Users remember and identify DIDs through domains, manage DIDs and interact with applications through wallets, and integrate different credentials and local identities on multiple chains through wallets.

-- **Why DID is needed**

- - **Human readable and easy to remember WEB3 username**

+#### Why DID is needed +- **Human readable and easy to remember WEB3 username**

Although each of us has a unique ID number, in our daily life, we generally use 'name' as an identifier of one's identity (although there will be renames) because it is easier for daily communication.

The world of WEB3 has the same problem: while people currently interact primarily based on wallet addresses, no one wants to remember that long string of characters. If the digital identity of WEB3 needs a 'name', then what EVMNS is doing is hoping to be that 'name'.

- - **A more user-friendly WEB3 experience**

+- **A more user-friendly WEB3 experience**

In WEB2 world, digital identity is platform-centered, and different products within the same group are connected through an account system. For example, Tencent's mailbox, games and finance can all use the same account; Google, Facebook and other top Internet enterprises also have their own account systems. Although this kind of identity system is easy to build, its disadvantages have been widely known: the accounts between platforms do not interoperate with each other, and users have no way to control their own identity data.

In WEB3 world, user interaction is mainly based on wallet address, so a series of activities related to the address constitute the most native decentralized digital identity DID of WEB3, and it can be naturally interoperable between different dApp applications without barriers. In this way, users can quickly find their acquaintance and friends when they enter new applications and games, without having to re-add them back by themselves like in WEB2 world.

Imagine a peer-to-peer chat where you can find the desired contact by simply searching for xxx. evm instead of an 18-digit irregular address starting with 0x. What a wonderful experience, and each EVM domain is unique so you don't have to worry about matching the wrong person.

Moreover, by using a DID name to connect to various cryptocurrency addresses, you can receive cryptocurrency payments from others through that domain name without having to copy and paste long addresses.

- - **Decentralized Super Business Card**

+- **Decentralized Super Business Card**

Each DID domain is a unique NFT, and the owner is free to set the content they wish to map or record, in addition to the common EVM wallet address, other cryptocurrency addresses, but also avatars/pictures, Email, Website, profile, Twitter/Telegram accounts and other content, no one can tamper or delete the information, the user has full control of his or her identity information. A DID may seem like a simple domain name, but it contains unlimited content, and **is a super business card for the WEB3 world.**

- - **Personal decentralized WEB3 homepage/website**

+- **Personal decentralized WEB3 homepage/website**

EVMNS allows users to create personal decentralized homepages/websites and upload them to the Interplanetary File System (IPFS), a global network of storage protocols that allow computers around the world to store and share data in a peer-to-peer fashion.

In short, EVMNS and IPFS can help users to establish personal homepages/blogs and websites, with functions similar to the combination of RSS feeds + WEB3 Medium. **Users will have full ownership, including domain name, content and data,** completely avoiding the possibility of being deleted by registrars/data operators.

- - **WEB3 Infrastructure**

- DID is also known as the "identity infrastructure" of WEB3 applications. As discussed above, it is basically determined that DID and avatar are the basic and essential elements of WEB3, being the identity of the WEB3 world.

-- **DID Market Analysis**

- **ENS (Ethereum Name Service)**

-ENS was launched on May 4, 2017 by Alex Van de Sande and Nick Johnson of the ETH Foundation. In November 2021, ENS issued its own governance token and launched an airdrop. At the same time, ENS established the ENS DAO to enable community governance, where token holders will participate in the management of the assets, as well as voting on DAO proposals and co-voting on the use of the vault.

-Earlier in the interview Vitalik said, "**The Ethereum Domain Name Service ENS is by far the most successful non-financial ETH application,** which can basically be compared to a decentralized phone book."

-As of November 27, 2022, **the total amount of ENS domain registration reached 2.79 million** and the number of Ethereum addresses holding ENS domains reached 609,000. Since November 2021, the number of monthly ENS registrations has shown explosive growth, reaching a peak of 437,000 monthly registrations in September 2022.


（Data source dune.com/makoto/ens)
**Total registration revenue of ENS domains has exceeded $60 million,** of which nearly $50 million has been realized so far in 2022 alone. Total secondary market transactions have reached 112.39K ETH and $197 million.

+- **WEB3 Infrastructure**

+ DID is also known as the "identity infrastructure" of WEB3 applications. As discussed above, it is basically determined that DID and avatar are the basic and essential elements of WEB3, being the identity of the WEB3 world.

+ +#### DID Market Analysis + +- **ENS (Ethereum Name Service)**

+ ENS was launched on May 4, 2017 by Alex Van de Sande and Nick Johnson of the ETH Foundation. In November 2021, ENS issued its own governance token and launched an airdrop. At the same time, ENS established the ENS DAO to enable community governance, where token holders will participate in the management of the assets, as well as voting on DAO proposals and co-voting on the use of the vault.

Earlier in the interview Vitalik said, "**The Ethereum Domain Name Service ENS is by far the most successful non-financial ETH application,** which can basically be compared to a decentralized phone book."

+ As of November 27, 2022, **the total amount of ENS domain registration reached 2.79 million** and the number of Ethereum addresses holding ENS domains reached 609,000. Since November 2021, the number of monthly ENS registrations has shown explosive growth, reaching a peak of 437,000 monthly registrations in September 2022.


（Data source dune.com/makoto/ens)

+ **Total registration revenue of ENS domains has exceeded $60 million,** of which nearly $50 million has been realized so far in 2022 alone. Total secondary market transactions have reached 112.39K ETH and $197 million.

![](https://github.com/evmns/evm_name_service/blob/main/t3.png?raw=true ) -
（Data source NFTGO.io）
+
（Data source NFTGO.io）

Whether it is the registration scale, transaction scale, or the number of holder’s addresses, ENS is far ahead of similar projects, occupying the absolute leading position and having the strongest community consensus.

The following is the partial sales of historical.
paradigm.eth, 420ETH
@@ -193,10 +195,10 @@ paradigm.eth, 420ETH
2.Nike.eth, 60ETH
3.Samsung.eth, 60ETH

-##### SPACE ID (BNB Chain Name Service)

+- **SPACE ID (BNB Chain Name Service)**

SPACE ID is a decentralized domain naming service protocol developed based on BNB Chain, officially launched in August 2022, with .bnb as the domain suffix, essentially the same as ENS, and dedicated to building a common name service network that seamlessly connects people, information, assets and applications across the blockchain. And by allowing users to bind their identities across multiple chains, communities can build their own domain naming services through SPACE ID's network. To date, more than 40 applications have announced that they have enabled integration of the SPACE ID protocol.

**A seed round of funding led by Binance Labs was completed on September 2nd, 2022 for an undisclosed amount.**

As of November 27, 2022, SPACE ID domain name total registrations reached 304,000, the total number of holders’ addresses reached 98,700, and **the total registration revenue was 14,700 BNB, USD 4.42 million** (1 BNB = USD 300). The total secondary market transaction size was about 22,000 BNB, 6.60 million USD.

![](https://github.com/evmns/evm_name_service/blob/main/t4.png?raw=true ) -
（Data source dune.com/spaceid/spaceid）
+
（Data source dune.com/spaceid/spaceid）

At present, WEB3 domain services like ENS and SPACE ID are also BNS on Binance, Bonfida on Solana, EVNS on Evmos, PNS on Polka, and cross-chain DID service‘.bit’, etc. The DID domain naming service protocol has become one of the basic items of every blockchain, showing a blossoming market state. From db8a64cd3d783b6db41d91d3ed06626513605114 Mon Sep 17 00:00:00 2001 From: Evm_nams_service <118707458+evmns@users.noreply.github.com> Date: Tue, 29 Nov 2022 20:33:34 +0800 Subject: [PATCH 029/170] Update EVMNS.md --- applications/EVMNS.md | 30 ++++++++++++++++-------------- 1 file changed, 16 insertions(+), 14 deletions(-) diff --git a/applications/EVMNS.md b/applications/EVMNS.md index 662045c5..c7bcb74d 100644 --- a/applications/EVMNS.md +++ b/applications/EVMNS.md @@ -164,30 +164,32 @@ We learned of the program by following announcements on ENF’s Twitter and othe The final form of DID development may be that each user has a unique network-wide identity, and multiple local identities for segmented scenarios. Users remember and identify DIDs through domains, manage DIDs and interact with applications through wallets, and integrate different credentials and local identities on multiple chains through wallets.

#### Why DID is needed - **Human readable and easy to remember WEB3 username**

- Although each of us has a unique ID number, in our daily life, we generally use 'name' as an identifier of one's identity (although there will be renames) because it is easier for daily communication.

+ Although each of us has a unique ID number, in our daily life, we generally use 'name' as an identifier of one's identity (although there will be renames) because it is easier for daily communication.

The world of WEB3 has the same problem: while people currently interact primarily based on wallet addresses, no one wants to remember that long string of characters. If the digital identity of WEB3 needs a 'name', then what EVMNS is doing is hoping to be that 'name'.

- **A more user-friendly WEB3 experience**

- In WEB2 world, digital identity is platform-centered, and different products within the same group are connected through an account system. For example, Tencent's mailbox, games and finance can all use the same account; Google, Facebook and other top Internet enterprises also have their own account systems. Although this kind of identity system is easy to build, its disadvantages have been widely known: the accounts between platforms do not interoperate with each other, and users have no way to control their own identity data.

-In WEB3 world, user interaction is mainly based on wallet address, so a series of activities related to the address constitute the most native decentralized digital identity DID of WEB3, and it can be naturally interoperable between different dApp applications without barriers. In this way, users can quickly find their acquaintance and friends when they enter new applications and games, without having to re-add them back by themselves like in WEB2 world.

-Imagine a peer-to-peer chat where you can find the desired contact by simply searching for xxx. evm instead of an 18-digit irregular address starting with 0x. What a wonderful experience, and each EVM domain is unique so you don't have to worry about matching the wrong person.

-Moreover, by using a DID name to connect to various cryptocurrency addresses, you can receive cryptocurrency payments from others through that domain name without having to copy and paste long addresses.

+ In WEB2 world, digital identity is platform-centered, and different products within the same group are connected through an account system. For example, Tencent's mailbox, games and finance can all use the same account; Google, Facebook and other top Internet enterprises also have their own account systems. Although this kind of identity system is easy to build, its disadvantages have been widely known: the accounts between platforms do not interoperate with each other, and users have no way to control their own identity data.

+ In WEB3 world, user interaction is mainly based on wallet address, so a series of activities related to the address constitute the most native decentralized digital identity DID of WEB3, and it can be naturally interoperable between different dApp applications without barriers. In this way, users can quickly find their acquaintance and friends when they enter new applications and games, without having to re-add them back by themselves like in WEB2 world.

+ Imagine a peer-to-peer chat where you can find the desired contact by simply searching for xxx. evm instead of an 18-digit irregular address starting with 0x. What a wonderful experience, and each EVM domain is unique so you don't have to worry about matching the wrong person.

+ Moreover, by using a DID name to connect to various cryptocurrency addresses, you can receive cryptocurrency payments from others through that domain name without having to copy and paste long addresses.

- **Decentralized Super Business Card**

- Each DID domain is a unique NFT, and the owner is free to set the content they wish to map or record, in addition to the common EVM wallet address, other cryptocurrency addresses, but also avatars/pictures, Email, Website, profile, Twitter/Telegram accounts and other content, no one can tamper or delete the information, the user has full control of his or her identity information. A DID may seem like a simple domain name, but it contains unlimited content, and **is a super business card for the WEB3 world.**

+ Each DID domain is a unique NFT, and the owner is free to set the content they wish to map or record, in addition to the common EVM wallet address, other cryptocurrency addresses, but also avatars/pictures, Email, Website, profile, Twitter/Telegram accounts and other content, no one can tamper or delete the information, the user has full control of his or her identity information. A DID may seem like a simple domain name, but it contains unlimited content, and **is a super business card for the WEB3 world.**

- **Personal decentralized WEB3 homepage/website**

- EVMNS allows users to create personal decentralized homepages/websites and upload them to the Interplanetary File System (IPFS), a global network of storage protocols that allow computers around the world to store and share data in a peer-to-peer fashion.

+ EVMNS allows users to create personal decentralized homepages/websites and upload them to the Interplanetary File System (IPFS), a global network of storage protocols that allow computers around the world to store and share data in a peer-to-peer fashion.

In short, EVMNS and IPFS can help users to establish personal homepages/blogs and websites, with functions similar to the combination of RSS feeds + WEB3 Medium. **Users will have full ownership, including domain name, content and data,** completely avoiding the possibility of being deleted by registrars/data operators.

- **WEB3 Infrastructure**

- DID is also known as the "identity infrastructure" of WEB3 applications. As discussed above, it is basically determined that DID and avatar are the basic and essential elements of WEB3, being the identity of the WEB3 world.

- + DID is also known as the "identity infrastructure" of WEB3 applications. As discussed above, it is basically determined that DID and avatar are the basic and essential elements of WEB3, being the identity of the WEB3 world.

#### DID Market Analysis - -- **ENS (Ethereum Name Service)**

+- **ENS(Ethereum Name Service**

ENS was launched on May 4, 2017 by Alex Van de Sande and Nick Johnson of the ETH Foundation. In November 2021, ENS issued its own governance token and launched an airdrop. At the same time, ENS established the ENS DAO to enable community governance, where token holders will participate in the management of the assets, as well as voting on DAO proposals and co-voting on the use of the vault.

Earlier in the interview Vitalik said, "**The Ethereum Domain Name Service ENS is by far the most successful non-financial ETH application,** which can basically be compared to a decentralized phone book."

- As of November 27, 2022, **the total amount of ENS domain registration reached 2.79 million** and the number of Ethereum addresses holding ENS domains reached 609,000. Since November 2021, the number of monthly ENS registrations has shown explosive growth, reaching a peak of 437,000 monthly registrations in September 2022.


（Data source dune.com/makoto/ens)

+ As of November 27, 2022, **the total amount of ENS domain registration reached 2.79 million** and the number of Ethereum addresses holding ENS domains reached 609,000. Since November 2021, the number of monthly ENS registrations has shown explosive growth, reaching a peak of 437,000 monthly registrations in September 2022.

+

（Data source dune.com/makoto/ens)

+ **Total registration revenue of ENS domains has exceeded $60 million,** of which nearly $50 million has been realized so far in 2022 alone. Total secondary market transactions have reached 112.39K ETH and $197 million.

+ ![](https://github.com/evmns/evm_name_service/blob/main/t3.png?raw=true ) -
（Data source NFTGO.io）

-Whether it is the registration scale, transaction scale, or the number of holder’s addresses, ENS is far ahead of similar projects, occupying the absolute leading position and having the strongest community consensus.

+
（Data source NFTGO.io)

+ + Whether it is the registration scale, transaction scale, or the number of holder’s addresses, ENS is far ahead of similar projects, occupying the absolute leading position and having the strongest community consensus.

The following is the partial sales of historical.
paradigm.eth, 420ETH
000.eth, 300ETH
From 0ebfe2f8776818d0fc5dcc6238fd3dad073be7a7 Mon Sep 17 00:00:00 2001 From: Evm_nams_service <118707458+evmns@users.noreply.github.com> Date: Tue, 29 Nov 2022 20:53:46 +0800 Subject: [PATCH 030/170] Update EVMNS.md --- applications/EVMNS.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/applications/EVMNS.md b/applications/EVMNS.md index c7bcb74d..c3fe2239 100644 --- a/applications/EVMNS.md +++ b/applications/EVMNS.md @@ -178,18 +178,18 @@ The world of WEB3 has the same problem: while people currently interact primaril In short, EVMNS and IPFS can help users to establish personal homepages/blogs and websites, with functions similar to the combination of RSS feeds + WEB3 Medium. **Users will have full ownership, including domain name, content and data,** completely avoiding the possibility of being deleted by registrars/data operators.

- **WEB3 Infrastructure**

DID is also known as the "identity infrastructure" of WEB3 applications. As discussed above, it is basically determined that DID and avatar are the basic and essential elements of WEB3, being the identity of the WEB3 world.

+ #### DID Market Analysis -- **ENS(Ethereum Name Service**

+- **ENS(Ethereum Name Service)**

ENS was launched on May 4, 2017 by Alex Van de Sande and Nick Johnson of the ETH Foundation. In November 2021, ENS issued its own governance token and launched an airdrop. At the same time, ENS established the ENS DAO to enable community governance, where token holders will participate in the management of the assets, as well as voting on DAO proposals and co-voting on the use of the vault.

Earlier in the interview Vitalik said, "**The Ethereum Domain Name Service ENS is by far the most successful non-financial ETH application,** which can basically be compared to a decentralized phone book."

- As of November 27, 2022, **the total amount of ENS domain registration reached 2.79 million** and the number of Ethereum addresses holding ENS domains reached 609,000. Since November 2021, the number of monthly ENS registrations has shown explosive growth, reaching a peak of 437,000 monthly registrations in September 2022.

-

（Data source dune.com/makoto/ens)

+As of November 27, 2022, **the total amount of ENS domain registration reached 2.79 million** and the number of Ethereum addresses holding ENS domains reached 609,000. Since November 2021, the number of monthly ENS registrations has shown explosive growth, reaching a peak of 437,000 monthly registrations in September 2022.

+**Total registration revenue of ENS domains has exceeded $60 million,** of which nearly $50 million has been realized so far in 2022 alone. Total secondary market transactions have reached 112.39K ETH and $197 million.

+![](https://github.com/evmns/evm_name_service/blob/main/t2.png?raw=true ) +
（Data source dune.com/makoto/ens)

- **Total registration revenue of ENS domains has exceeded $60 million,** of which nearly $50 million has been realized so far in 2022 alone. Total secondary market transactions have reached 112.39K ETH and $197 million.

- ![](https://github.com/evmns/evm_name_service/blob/main/t3.png?raw=true )
（Data source NFTGO.io)

- - Whether it is the registration scale, transaction scale, or the number of holder’s addresses, ENS is far ahead of similar projects, occupying the absolute leading position and having the strongest community consensus.

+Whether it is the registration scale, transaction scale, or the number of holder’s addresses, ENS is far ahead of similar projects, occupying the absolute leading position and having the strongest community consensus.

The following is the partial sales of historical.
paradigm.eth, 420ETH
000.eth, 300ETH
From 37885a23ee69369a8174fdf3ff4b13d1db1aaeac Mon Sep 17 00:00:00 2001 From: Evm_nams_service <118707458+evmns@users.noreply.github.com> Date: Tue, 29 Nov 2022 21:06:50 +0800 Subject: [PATCH 031/170] Update EVMNS.md --- applications/EVMNS.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/applications/EVMNS.md b/applications/EVMNS.md index c3fe2239..e7ae7d01 100644 --- a/applications/EVMNS.md +++ b/applications/EVMNS.md @@ -147,7 +147,8 @@ Team members have participated in several medium to large scale EOS projects bef | 0e. | Article| We will publish an English article about the project on medium.com, explaining how smart contracts work and how the project will be used. Also, we will illustrate the goals and outcomes set through the grant.| | 1 | New version of the official website | Including project introduction, domain registration and management, instruction documents, etc. | | 2 | Deployment of test networks | Deploy the test environment and conduct public testing to further ensure the smooth launch and security of the system |

-### Multi-Chain Ecology + +#### Multi-Chain Ecology Multi-chain ecology is the focus of the second phase of development, and we will prioritize the completion of the first phase of development (the above five milestones) to maximize the assurance that EVMNS can be launched and run stably at the first time after the official launch of EVM.

Therefore, the development content, duration and cost of the multi-chain ecology will be separately defined before the launch of the second phase.

# Future Plans From c220c9b7307c3d963747e778e695ff098c09a580 Mon Sep 17 00:00:00 2001 From: DefiboxTeam Date: Tue, 29 Nov 2022 21:22:29 +0800 Subject: [PATCH 032/170] Update Defibox_vault.md --- applications/Defibox_vault.md | 23 +++++++++++++---------- 1 file changed, 13 insertions(+), 10 deletions(-) diff --git a/applications/Defibox_vault.md b/applications/Defibox_vault.md index 0a21e3e6..6be4726a 100644 --- a/applications/Defibox_vault.md +++ b/applications/Defibox_vault.md @@ -5,7 +5,7 @@ - **EOS Payment Address:** liquid.defi - **[Level](https://github.com/eosnetworkfoundation/grant-framework#grant-levels):** 3 - **Pomelo Grant(s):** https://pomelo.io/grants/vault -- **Project is Open-Source:** Yes +- **Project is Open-Source:** Yes* - **Project was part of Token sale:** No - **Repository where Project resides:** https://github.com/DefiboxTeam/DefiboxVault-interface > 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. @@ -22,7 +22,7 @@ ## Open source Timelines to open source -- **Stage 1 (Immediately) “Version beta v0.1.0”** +- **Stage One: [4] deliverables (completed)** https://github.com/defiboxswap/DefiboxVault-interface Includes *.hpp interface @@ -33,13 +33,18 @@ General documentation README.md Protocol Design (diagram) -- **Stage 2 (work to be completed)** +- **Stage Two: [4] deliverables (not completed)** Protocol Design Definition (translated in English/Korean/Chinese) -Automated unit tests written with Vert +SC development (production) -- **Stage 3 (re-evaluation 2nd Security Audit from Certik) “Version v1.0.0”** +User documentation + +Automatic Contracts Tests + + +- **Stage Three: (re-evaluation 2nd Security Audit from Certik) “Version v1.0.0”** All smart contract source code will be made available (*.cpp) @@ -123,7 +128,6 @@ https://github.com/defiboxswap | User documentation | Not completed | $6,000 | | Automatic Contracts Tests | Not completed | $14,000 | | Certik Audit | Completed | $24,000 | - | Total | Not completed | $80,000 | ## Additional Information @@ -142,7 +146,7 @@ https://github.com/defiboxswap - **EOS支付地址：** liquid.defi - **等级：** 3 - **Pomelo资助：** https://pomelo.io/grants/vault -- **项目是开源的：** 是 +- **项目是开源的：** 是* - **项目是代币销售的一部分：** 否 - **项目资源库：** https://github.com/DefiboxTeam/DefiboxVault-interface @@ -154,7 +158,7 @@ https://github.com/defiboxswap ### 开源 开源时间表 -- **第一阶段（立即）“测试版 v0.1.0”** +- **第一阶段，4个可交付成果（已完成）** https://github.com/defiboxswap/DefiboxVault-interface 包括 *.hpp 界面 @@ -165,7 +169,7 @@ https://github.com/defiboxswap/DefiboxVault-interface 协议设计（示意图） -- **第二阶段（待完成的工作）** +- **第二阶段，4个可交付成果（未完成）** 协议设计定义（英文/韩文/中文翻译） @@ -233,7 +237,6 @@ https://github.com/defiboxswap/DefiboxVault-interface | 用户文档 | 未完成 | $6,000 | | 自动合约测试 | 未完成 | $14,000 | | Certik审计 | 完成 | $24,000 | - | 合计 | 未完成 | $80,000 | **附加信息** From 6ea1530e4e1c304476ed490908ef74de1383c5f3 Mon Sep 17 00:00:00 2001 From: Evm_name_service <118707458+evmns@users.noreply.github.com> Date: Tue, 29 Nov 2022 22:12:57 +0800 Subject: [PATCH 033/170] Update EVMNS.md --- applications/EVMNS.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/applications/EVMNS.md b/applications/EVMNS.md index e7ae7d01..b162d5d1 100644 --- a/applications/EVMNS.md +++ b/applications/EVMNS.md @@ -10,9 +10,9 @@ - **Repository where Project resides:** https://github.com/evmns/EVMNS
# Contact -**Contact Name:** Harry Davis
-**Contact Email:** evmns_manager@outlook.com
-**Website:** N/A
+- **Contact Name:** Harry Davis +- **Contact Email:** evmns_manager@outlook.com +- **Website:** N/A # Project Overview **EVMNS (EVM Name Service) is a distributed, open and extensible multi-chain DID domain naming system built on EVM and EOS,** relying on the high performance, security and reliability of EOS to better and seamlessly connect people, information, assets, dApps, etc. in the WEB3 world.

From e69fe19c14ec730df8c1bdb4a62869d4b29681d2 Mon Sep 17 00:00:00 2001 From: DefiboxTeam Date: Tue, 29 Nov 2022 22:25:45 +0800 Subject: [PATCH 034/170] Update Defibox_vault.md --- applications/Defibox_vault.md | 67 +++++++++++++++-------------------- 1 file changed, 28 insertions(+), 39 deletions(-) diff --git a/applications/Defibox_vault.md b/applications/Defibox_vault.md index 6be4726a..34df4c81 100644 --- a/applications/Defibox_vault.md +++ b/applications/Defibox_vault.md @@ -19,35 +19,27 @@ > ⚠️ *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.* -## Open source -Timelines to open source +## Open source - Timelines -- **Stage One: [4] deliverables (completed)** -https://github.com/defiboxswap/DefiboxVault-interface +**Stage One (completed) "Version Beta v0.1.0"** -Includes *.hpp interface +> https://github.com/defiboxswap/DefiboxVault-interface -Prebuilt WASM binaries *.wasm & *.abi (with version control) +- [x] Includes *.hpp interface +- [x] Prebuilt WASM binaries *.wasm & *.abi (with version control) +- [x] General documentation README.md +- [x] Protocol Design (diagram) -General documentation README.md +**Stage Two (not completed)** -Protocol Design (diagram) +- [ ] Protocol Design Definition (translated in English/Korean/Chinese) +- [ ] SC development (production) +- [ ] User documentation +- [ ] Automatic Contracts Tests -- **Stage Two: [4] deliverables (not completed)** - -Protocol Design Definition (translated in English/Korean/Chinese) - -SC development (production) - -User documentation - -Automatic Contracts Tests - - -- **Stage Three: (re-evaluation 2nd Security Audit from Certik) “Version v1.0.0”** - -All smart contract source code will be made available (*.cpp) +**Stage Three (re-evaluation 2nd Security Audit from Certik) “Version v1.0.0”** +- [ ] All smart contract source code will be made available (*.cpp) ## Project Overview @@ -155,30 +147,27 @@ https://github.com/defiboxswap - **联系邮箱：** raven@defibox.io - **网站：** https://eos.defibox.io/vault -### 开源 -开源时间表 - -- **第一阶段，4个可交付成果（已完成）** -https://github.com/defiboxswap/DefiboxVault-interface - -包括 *.hpp 界面 - -预构建的 WASM 二进制文件 *.wasm & *.abi（带版本控制） - -通用文档 README.md +## 开源 - 时间表 -协议设计（示意图） +**第一阶段（已完成）“Beta 版 v0.1.0”** -- **第二阶段，4个可交付成果（未完成）** +> https://github.com/defiboxswap/DefiboxVault-interface -协议设计定义（英文/韩文/中文翻译） +- [x] 包括 *.hpp 接口 +- [x] 预构建的 WASM 二进制文件 *.wasm 和 *.abi（带版本控制） +- [x] 通用文档 README.md +- [x] 协议设计（图表） +**第二阶段（未完成）** -使用 Vert 编写的自动化单元测试 +- [ ] 协议设计定义（翻译成英文/韩文/中文） +- [ ] SC 开发（生产） +- [ ] 用户文档 +- [ ] 自动合约测试 -- **第三阶段（Certik 重新评估第二次安全审计）“版本 v1.0.0”** +**第三阶段（Certik 重新评估第二次安全审计）“版本 v1.0.0”** -将提供所有智能合约源代码 (*.cpp) +- [ ] 将提供所有智能合约源代码 (*.cpp) ### 项目概况 **概述** From 6166ab0e8b2f542b1563a7207577f5c924763c98 Mon Sep 17 00:00:00 2001 From: Evm_name_service <118707458+evmns@users.noreply.github.com> Date: Wed, 30 Nov 2022 09:05:26 +0800 Subject: [PATCH 035/170] Update EVMNS.md --- applications/EVMNS.md | 50 +++++++++++++++++++++---------------------- 1 file changed, 25 insertions(+), 25 deletions(-) diff --git a/applications/EVMNS.md b/applications/EVMNS.md index b162d5d1..9edef11f 100644 --- a/applications/EVMNS.md +++ b/applications/EVMNS.md @@ -1,13 +1,13 @@ # EOS Network Foundation Grant Proposal -- **Project Name:** EVMNS (EVM Name Service)
-- **Team Name:** EVMNS Labs
-- **EOS Payment Address:** evmnsdomains
-- **Level:** 3
-- **Pomelo Grant(s):** N/A
-- **Project is Open-Source:** Yes
+- **Project Name:** EVMNS (EVM Name Service) +- **Team Name:** EVMNS Labs +- **EOS Payment Address:** evmnsdomains +- **Level:** 3 +- **Pomelo Grant(s):** N/A +- **Project is Open-Source:** Yes - **Project was part of Token sale:** No -- **Repository where Project resides:** https://github.com/evmns/EVMNS
+- **Repository where Project resides:** https://github.com/evmns/EVMNS # Contact - **Contact Name:** Harry Davis @@ -74,13 +74,13 @@ The core members of EVMNS Labs are the first ecological participants of EOS, who Team members have participated in several medium to large scale EOS projects before and after, and also developed ENS (Ethereum Name Service) related domain Exchange, domain bulk registry protocol, etc. We are not only EOS loyalists, but also ENS heavy players, with good understanding of DID domain naming system.

# Development Roadmap ### Milestone Summary -- **Estimated project development duration:** 12 weeks
-- **Full Time Equivalent Employees (FTE):** 6
-- **Total cost:** $195,000
+- **Total Estimated Duration:** 12 weeks +- **Full-Time Equivalent (FTE):** 6 FTE +- **Total Costs:** 195,000 USD ### Milestone 1 - Requirements Analysis and official website -- **Estimated project development duration:** 2 weeks
-- **Full Time Equivalent Employees (FTE):** 2
-- **Total cost:** $20,000
+- **Estimated duration:** 2 weeks +- **FTE:** 2 +- **Costs:** 20,000 USD | ID | Deliverable |Specification| | ------------ | ------------ | ------------ | @@ -91,9 +91,9 @@ Team members have participated in several medium to large scale EOS projects bef | 1 | Demand Analysis | Unpacking requirements, developing business process diagrams, planning business modules, standardizing development documentation and testing processes, etc. | | 2 | Release official website | Including project introduction, Roadmap and other content. |

### Milestone 2 - Smart Contracts -- **Estimated project development duration:** 4 weeks
-- **Full Time Equivalent Employees (FTE):** 5
-- **Total cost:** $100,000
+- **Estimated duration:** 4 weeks +- **FTE:** 5 +- **Costs:** 100,000 USD | ID | Deliverable |Specification| | ------------ | ------------ | ------------ | @@ -106,9 +106,9 @@ Team members have participated in several medium to large scale EOS projects bef | 3 | Root Node Management | Completing the design of the root node, EVMNS will lock the control of the root node so that the root owner cannot influence the ownership of the .evm domain and set the root node to be held jointly by the community in a multi-signature contract, guaranteeing all the power of the user. | | 4 | Domain Resolver | Resolvers are responsible for the actual process of translating names into addresses. Any contract that implements the relevant standards may act as a resolver in EVMNS. |

### Milestone 3 - Key Systems and Components -- **Estimated project development duration:** 3 weeks
-- **Full Time Equivalent Employees (FTE):** 3
-- **Total cost:** $45,000
+- **Estimated duration:** 3 weeks +- **FTE:** 3 +- **Costs:** 45,000 USD | ID | Deliverable |Specification| | ------------ | ------------ | ------------ | @@ -121,9 +121,9 @@ Team members have participated in several medium to large scale EOS projects bef | 3 | Metadata Storage Management System | Store the domain metadata independently in the metadata management system and access the corresponding metadata through api. | | 4 | Domain Management System | Build EVMNS domain management system to realize administrators capability of financial review, daily log maintenance review, emergency management, etc. for EVMNS. |

### Milestone 4 - In-depth testing -- **Estimated project development duration:** 2 weeks
-- **Full Time Equivalent Employees (FTE):** 2
-- **Total cost:** $20,000
+- **Estimated duration:** 2 weeks +- **FTE:** 2 +- **Costs:** 20,000 USD | ID | Deliverable |Specification| | ------------ | ------------ | ------------ | @@ -134,9 +134,9 @@ Team members have participated in several medium to large scale EOS projects bef | 1 | In-depth test | Automated unit tests with 100% coverage and multiple rounds of functional testing are completed internally to ensure functionality and robustness. | | 2 | dApp Development Documentation | Establish a perfect dApp development documentation system to meet and support the quick access of dApp developers. |

### Milestone 5 - Deployment Test Network -- **Estimated project development duration:** 1 week
-- **Full Time Equivalent Employees (FTE):** 2
-- **Total cost:** $10,000
+- **Estimated duration:** 1 weeks +- **FTE:** 2 +- **Costs:** 10,000 USD | ID | Deliverable |Specification| | ------------ | ------------ | ------------ | From 5785433d7475a4b8055fd7c76ca8bbe608e4652c Mon Sep 17 00:00:00 2001 From: Evm_name_service <118707458+evmns@users.noreply.github.com> Date: Wed, 14 Dec 2022 11:29:25 +0800 Subject: [PATCH 036/170] Update EVMNS.md --- applications/EVMNS.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/applications/EVMNS.md b/applications/EVMNS.md index 9edef11f..6d7fd802 100644 --- a/applications/EVMNS.md +++ b/applications/EVMNS.md @@ -194,9 +194,9 @@ Whether it is the registration scale, transaction scale, or the number of holder The following is the partial sales of historical.
paradigm.eth, 420ETH
000.eth, 300ETH
-1.Opensea.eth, 99.89ETH
-2.Nike.eth, 60ETH
-3.Samsung.eth, 60ETH

+Opensea.eth, 99.89ETH
+Nike.eth, 60ETH
+Samsung.eth, 60ETH

- **SPACE ID (BNB Chain Name Service)**

SPACE ID is a decentralized domain naming service protocol developed based on BNB Chain, officially launched in August 2022, with .bnb as the domain suffix, essentially the same as ENS, and dedicated to building a common name service network that seamlessly connects people, information, assets and applications across the blockchain. And by allowing users to bind their identities across multiple chains, communities can build their own domain naming services through SPACE ID's network. To date, more than 40 applications have announced that they have enabled integration of the SPACE ID protocol.

From ebbfd1f30a906b3801a9cbdb51820a1aa7a77248 Mon Sep 17 00:00:00 2001 From: "Seth@Boid.com" <51824327+mchosc@users.noreply.github.com> Date: Fri, 13 Jan 2023 21:22:00 +0000 Subject: [PATCH 037/170] Create antelopeio-firewall.md --- applications/antelopeio-firewall.md | 1 + 1 file changed, 1 insertion(+) create mode 100644 applications/antelopeio-firewall.md diff --git a/applications/antelopeio-firewall.md b/applications/antelopeio-firewall.md new file mode 100644 index 00000000..78981922 --- /dev/null +++ b/applications/antelopeio-firewall.md @@ -0,0 +1 @@ +a From 995645540313deafe92f7c322bccc843a499e9be Mon Sep 17 00:00:00 2001 From: "Seth@Boid.com" <51824327+mchosc@users.noreply.github.com> Date: Mon, 16 Jan 2023 14:13:06 +0000 Subject: [PATCH 038/170] Create antelopeio_firewall.md --- applications/antelopeio_firewall.md | 234 ++++++++++++++++++++++++++++ 1 file changed, 234 insertions(+) create mode 100644 applications/antelopeio_firewall.md diff --git a/applications/antelopeio_firewall.md b/applications/antelopeio_firewall.md new file mode 100644 index 00000000..217f0aae --- /dev/null +++ b/applications/antelopeio_firewall.md @@ -0,0 +1,234 @@ +# EOS Network Foundation Grant Proposal + +- **Project Name:** Antelope Firewall +- **Team Name:** Animus Labs LTD (representing Boid.com) +- **EOS Payment Address:** animus.inc +- **[Level](https://github.com/eosnetworkfoundation/grant-framework#grant-levels):** 2 +- **Pomelo Grant(s):** [Boid Universe](https://pomelo.io/grants/boiduniverse); [EOSPOWERUP.IO](https://pomelo.io/grants/eospowerupio); [EOSIOIBC](https://pomelo.io/grants/eosioibc) +- **Project is Open-Source:** Yes +- **Project was part of Token sale:** No +- **Repository where Project resides:** https://github.com/animuslabs + +## Contact + +- **Contact Name:** John Heeter +- **Contact Email:** john@boid.com +- **Website:** https://www.animus.is + +## Project Overview + +This is a proposal to build a firewall/proxy that would be used in an Antelope node operator's infrastructure. The end goal is to lower the barrier to entry for infrastructure providers to offer highly reliable public endpoints. We are especially excited to make it easier for anyone to operate a reliable public Antelope node without a complex understanding of DevOps. + +### Overview + +- **Name:** Antelope Node Firewall +- **Brief Description:** Lower the barrier to entry for infrastructure providers to offer highly reliable public endpoints. +- **Relationship to EOSIO:** It's a layer on top of existing AntelopeIO API nodes. +- **Reason for Interest:** We want to solve common issues that API node operators have. + +### Project Details + +#### Problem +Antelope Leap nodes are easily abused without proper network infrastructure. When nodes are abused by bots and malicious attackers, they become unreliable or unusable for normal users and create considerable strain on infrastructure providers. Therefore today only a small subset of public EOS nodes are usable in production. Based on our custom eospowerup.io proxy that rotates between APIs provided by the top 50 BPs we found that less than 10 are reliable and usable for production applications. + +#### Proposed Solution +We propose an application that would sit behind an existing firewall such as NGINX (or replace your firewall for more simple networks) and in front of a Nodeos API and/or p2p node. The application would monitor incoming transactions and queries to perform smart logic such as blocking, or prioritizing based on the node operator's preference. The purpose is to make running highly available RPC nodes more accessible to node operators and reduce the load on the Nodeos software. The advantage of this application vs a traditional firewall is that this application is aware of Antelope transaction and query structure and can apply complex filter logic that a traditional firewall isn’t designed for. + +![AntelopeIO_Firewall_Diagram](https://ipfs.animus.is/ipfs/QmZ3qEwAGuaboNYAypJdXtcGnofQX4yPrYhVStQnX5u8Vh?filename=diagram-antelope-firewall.jpg) + +The initial version of the application would be written in Typescript and could be easily scaled across multiple cores and operated with high uptime via pm2. The application could run on the same VM as Leap but for optimal flexibility could be hosted on a dedicated VM that scales independently. + +#### **Features** + +- **Dynamic Blacklisting** Accounts, IPs, keys, and even specific contracts and actions can be blacklisted, throttled, and subjectively billed based on granular configuration. For example: the node operator may opt to only process one transfer action per account per second. For accounts that use inline actions or advanced techniques to subvert the firewall filtering, subjective CPU billing based on recent transaction history can effectively prevent abuse. All this logic can be easily configured by the node operator and dynamically automated based on metrics such as node CPU/RAM threshold logic. A side effect of this is that application specific nodes could provide fast and reliable operation for a limited subset of actions related to their application while throttling or deprioritizing other traffic. + +- **Transaction Handling** The Firewall can read incoming transaction data parameters and make subjective judgements based on the contents of the transaction. For example, you could block or subjectively bill any “transfer” action with a “from” data parameter that contains a blacklisted account. You could subjectively throttle transactions from accounts with a low balance, statistical analysis can grade accounts based on various metrics to give the account a “score” which helps the system understand if an account is a normal user or an automated bot and apply specialized rules accordingly. + +- **Query Handling** Repetitive requests for information can be automatically cached, throttled or blocked based on granular configuration and automatic statistics. This is especially useful to combat arbitrage bots which DDOS infrastructure. + +- **Detailed Statistics** Currently node operators have limited insight into what exactly is creating load for their Leap instances because general purpose firewalls don’t understand Antelope transaction/query structure. Our application can export detailed statistics in a format ingestible by Prometheus for visualization. + +- **Granular routing** The application could route queries and transactions to specific Leap instances such as an instance that is only responsible for push transactions that pertain to a specific contract. History queries could be routed to dedicated Hyperion nodes. + +- **Automated Deployment** Scripts for deployment via Docker, Ansible, or bare metal will be provided, Anyone could launch a highly available and production ready Leap instance from scratch in less than 30 minutes with minimal configuration and maintenance. + +#### **Future additions** +Once the base level application has reached a production ready state and iterated based on node operator feedback there are additional developments that could improve the application. + +- **Codebase** The application logic could be rewritten in Rust or C++ and used as a standalone application or integrated into Leap as a plugin. This would reduce CPU/RAM/Latency of the application but may limit some functionality and will greatly increase development cost. Therefore a Typescript version should be developed first for quick and cost-effective iteration. + +- **Monetization** Node operators who offer public APIs often do so as a free service that operates at a loss. This makes it difficult for operators to sustain the hardware and manpower required for high-availability RPC nodes. A monetization feature could be added to the firewall that would allow users to pay to have their contract actions whitelisted for less rate-limiting. For example, an application developer may pay a node operator a subscription fee to whitelist their contract operations in order to ensure a smooth experience for their users. Monetization can be totally automated with a smart contract and basic logic integrated into the firewall. + +#### **Feedback from node operators** +- **EOSN** Sounds very useful if it could replace NGINX/HAProxy. Consider building in Golang instead of Typescript. Increased performance and improved interoperability with Dfuse/Firehose such as reading Firehose blocks to reply to get_block requests without blocks.log. + +- **GenerEOS** I read your proposal and think it would be a useful product that would help many node operators. + +- **EOSphere** Love the idea .. like a patroneos 2.0, It really helped us at one point ,Would be great to have it again. + +- **EOSUSA** Should replace NGINX/HAProxy: If it's doing routing based on role, u dont wanna have more proxies scattered behind them, it should manage the routing and balancing + +### Ecosystem Fit + +Antelope Firewall can be an integral part of EOSIO/AntelopeIO ecosystem as an application firewall. + +Node operators in the EOSIO/AntelopeIO ecosystem can create a better user experience for normal users and applications that rely on public infrastructure. + +Reducing the load on the Nodeos application will reduce infrastructure costs and improve RPC api reliability for common users. + +Additionally, this application would make it easy for application developers to host public nodes which throttle transactions and queries unrelated to their core application. + +#### Existing solutions +Running a reliable Leap RPC/P2P on EOS and other high-traffic Antelope chains requires advanced DevOps skills. Node operators are required to maintain a considerably complex network infrastructure to support such a service. Typically this involves multiple layers of specialized Leap Nodes that act as filters for transaction propagation. + +Existing EVM solutions: +- https://github.com/ethereum-optimism/optimism/tree/develop/proxyd +- https://github.com/emeraldpay/dshackle + + +## Team + +### Team members + +- **Team Leader:** John Heeter - Founder @ Boid.com +- Jowita Choscilowicz - Project Manager +- John Heeter - Technical Lead / Development +- Seth Choscilowicz - Development / DevOps + +### Legal Structure + +- **Registered Legal Entity:** Animus Labs LTD +- **Registered Address:** Hunkins Waterfront Plaza, Main Street, Charlestown, Nevis + +### Team Experience + +John Heeter - 8 years of developement experience (5 years blockchain experience eosio) / full stack dev; technical artist 3 years; technical director 3 years +Jowita Choscilowicz - director 10 years / project manager 4 years / systems engineer 3 years +Seth Choscilowicz - blockchain dev ops 4 years eosio / systems engineer 14 years + +### Team Org Repos + +- https://github.com/boid-com +- https://github.com/animuslabs + +### Team Member Repos + +- https://github.com/jdheeter +- https://github.com/mchosc + +### Team LinkedIn Profiles + +- https://www.linkedin.com/in/johnheeter +- https://www.linkedin.com/in/mchosc +- https://www.linkedin.com/in/jchoscilowicz + +## Development Status + +The Antelope Firewall project is in the phase of architecture analysis and design. The project has not begun development yet. + +We have collected our current experience from various organizations for which we have worked and from different clients for whom we have implemented projects. Experiences and conclusions from work in WEB2 environments are reflected in WEB3 ecosystems and in our opinion it is worth using these experiences and ideas that have been verified by the WEB2 market. + +We created the concept of an application firewall for EOS and collected feedback from public node operators to illustrate the problem: + +1. **EOS USA** +- EOS: +api: 1.5mil/hr +hyp: 200/hr about 50/50% api response 200/500 +failures ~100% failed push trx (500) + +- WAX: +api: 150K/hr +hyp: 205K/hr 5% +failures (push trx) but it´s heavily rate limited, response 50x abusers + +- Proton: +api: 1.4mil/hr +hyp: 1500/hr about 50/50% api response 200/500 +failures ~100% failed push trx (500) + +- 1mil/hr blocked non-routable by proxy (no valid host headers for nodes) +- 117K/hr blocked at firewall for known abusive IP ranges + +2. **EOS Nation** +20% failure rate, relying on Fail2Ban to prevent most bad queries/trx from reaching nodes, estimated 10x failure rate without Fail2Ban. + +3. **Greymass** +50-100 failed transactions per second reach Leap instances, multitudes more are caught by firewalls/rate limiters. + +4. **Boid BP** +Global API stats on EOS / Telos Mainnet / Telos Testnet / Hyperion / Hyperion Testnet about 1 mln per hour with spikes of 6k per second with automatic block of miners on EOS Mainnet 15% failure rate + +5. **GenerEOS** +We use a combination of things in terms of firewall including nginx rate limits, Fail2ban, and for some chains also caching. I know that our APIs and p2p still get hammered and often are not usable. + +6. **EOSphere** +On EOS we have a 43% transaction failure rate. We successfully process 300k EOS Transactions / hour. We fail 230k EOS Transactions / hour. Most of the failures are push transactions. 13.1Mil Successful EOS Actions / Transactions per day. Our WAX infra is over 30Mil Successful Actions / Transactions per day. + +7. **EOS Amsterdam** +Approximately 90%+ transactions that make it through our existing rate-limiting solutions result in failures. Currently using: https://gist.github.com/cc32d9/2466e15c14882b2d696415f6c2777954 + +The application firewall turns out to be a natural element that should be an integral part of the EOSIO system. + +## Development Roadmap + +### Overview + +- **Total estimated duration:** 6 months +- **Full-Time Equivalent (FTE):** 2-2.5 +- **Total costs:** 50,000 USD + + +### Milestone 1 — Create Antelope Firewall Prototype + +- **Estimated duration:** 5 weeks +- **FTE:** 2.5 +- **Costs:** 10,000 USD + +| ID | Deliverable | Specification | +| ----- | ----------- | ------------- | +| 0a. | License | MIT | +| 0b. | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how to configure and run, including technical draft: short document will act as an overview of the technical implementation details as part of the development planning stage. Will guide code structure and development milestones. | +| 0c. | Deployment | We will provide a Prototype with a limited basic functionalities implemented. For example the firewall will be able to route queries to nodes and return responses with basic blacklisting functionality. | + +### Milestone 2 — Implement Antelope Firewall MVP version + +- **Estimated Duration:** 10 weeks +- **FTE:** 2 +- **Costs:** 17,000 USD + +| ID | Deliverable | Specification | +| ----- | ----------- | ------------- | +| 0a. | License | MIT | +| 0b. | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how to configure and run Alpha and Beta version (MVP). | +| 0c. | Deployment Alpha | We will provide a Alpha version with a major features implemented in a basic way. We will begin running on our own nodes. | +| 0d. | Deployment Beta (MVP) | We will provide a Beta version (MVP) with all features implemented in a basic way. The app should be ready to distribute to external infra providers for feedback and testing. | + +### Milestone 3 — Implement Antelope Firewall 1.0 version + +- **Estimated Duration:** 14 weeks +- **FTE:** 2 +- **Costs:** 23,000 USD + +| ID | Deliverable | Specification | +| ----- | ----------- | ------------- | +| 0a. | License | MIT | +| 0b. | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how to configure and run Antelope Firewall 1.0 version, which covers all of the application functionality and configuration. Also we will create deployment scripts for various platforms to simplify the process of getting started. | +| 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. | Deployment | We will provide an Antelope Firewall 1.0 version - production ready solution, based on feedback from infra providers and issues discovered during beta testing. | +| 0e. | Article | We will publish an **article** that explains what are the features of the product, how does it work and what was achieved as part of the grant. | + +## Future Plans + +The Antelope Firewall probably will be useful for EOS node operators, ensuring a high level of security. + +We plan to offer a solution to active block producers, in the first place to everyone we've talked to so far: EOS USA, EOS Nation, Greymass, Boid BP, GenerEOS, EOSphere, EOS Amsterdam. We assume that we will reach 30 block producers within the first 3 months from the release of version 1.0. The next step in the coming months will be reaching out to other EOS block producers. + +At the same time is important for us to collect feedback from the users of the tool by sending them a survey regarding the functionalities in 1.0 version. On this basis, we want to develop the application and prepare a set of new functionalities in 2.0. version. The new features will address the node operators needs. + +In the long term, we plan to promote the Antelope Firewall in the dApps Providers target group in EOSIO ecosystems. + +## Additional Information + +**How did you hear about the Grants Program?** Twitter + +So far, we have been implementing the project with our own funds, we do not want to go beyond the EOSIO environment with the idea. We submit the application for funding only to the EOS Network Foundation. From 2e6675a8b45c97a9ec35a16e872f47fcad6e640a Mon Sep 17 00:00:00 2001 From: "Seth@Boid.com" <51824327+mchosc@users.noreply.github.com> Date: Mon, 16 Jan 2023 14:13:19 +0000 Subject: [PATCH 039/170] Delete antelopeio-firewall.md --- applications/antelopeio-firewall.md | 1 - 1 file changed, 1 deletion(-) delete mode 100644 applications/antelopeio-firewall.md diff --git a/applications/antelopeio-firewall.md b/applications/antelopeio-firewall.md deleted file mode 100644 index 78981922..00000000 --- a/applications/antelopeio-firewall.md +++ /dev/null @@ -1 +0,0 @@ -a From a94de00afee4e08d2da8efe755526da00a9df365 Mon Sep 17 00:00:00 2001 From: Veronica Diaz <94094597+Creamyvanill@users.noreply.github.com> Date: Mon, 23 Jan 2023 12:10:27 -0400 Subject: [PATCH 040/170] Create eosreddit2.md --- applications/eosreddit2.md | 212 +++++++++++++++++++++++++++++++++++++ 1 file changed, 212 insertions(+) create mode 100644 applications/eosreddit2.md diff --git a/applications/eosreddit2.md b/applications/eosreddit2.md new file mode 100644 index 00000000..8ae1dcd6 --- /dev/null +++ b/applications/eosreddit2.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 **Team Name:** ) 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 (such as **Team Name:**. +> +> 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 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 EOSIO:** An indication of how your project relates to / integrates into EOSIO. +- **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 EOSIO 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 EOSIO 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/ +- https://www.linkedin.com/ + +## 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. +- **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 EOSIO 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 EOSIO 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 EOSIO | 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 EOSIO 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 ef8e7bd7e319eace73a41b7cd8c3aae83df5348a Mon Sep 17 00:00:00 2001 From: Veronica Diaz <94094597+Creamyvanill@users.noreply.github.com> Date: Mon, 23 Jan 2023 13:07:16 -0400 Subject: [PATCH 041/170] Update eosreddit2.md --- applications/eosreddit2.md | 43 ++++++++++++++------------------------ 1 file changed, 16 insertions(+), 27 deletions(-) diff --git a/applications/eosreddit2.md b/applications/eosreddit2.md index 8ae1dcd6..e19f4018 100644 --- a/applications/eosreddit2.md +++ b/applications/eosreddit2.md @@ -1,40 +1,29 @@ # 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 **Team Name:** ) 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 (such as **Team Name:**. -> -> 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 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. +- **Project Name:** EOS VISIONS +- **Team Name:** Creamy Vainilla C.A +- **EOS Payment Address:** eosvisionorg +- **[Level](https://github.com/eosnetworkfoundation/grant-framework#grant-levels):** 1 +- **Pomelo Grant(s):** https://pomelo.io/grants/eosvision +- **Project is Open-Source:** Yes +- **Project was part of Token sale:** No +- **Repository where Project resides:** https://github.com/eosvision1 ## Contact -- **Contact Name:** Full name of the contact person in your team -- **Contact Email:** myemail@mycompany.com -- **Website:** https://yourwebsite.com +- **Contact Name:** Verónica Coromoto Díaz Duran. +- **Contact Email:** veronica14diazdiaz@gmail.com +- **Website:** (https://eosvision.io/) > ⚠️ *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. +- **Name:** EOS VISION x REDDIT AND FACEBOOK +- **Brief Description:** Welcome to EOS REDDIT 2.0, the new stage of EOS REDDIT, where we will be able to turn the old, lonely and depressed Reddit into a new way of reading the news and giving constructive opinions. Our trained team prepares to work on 3 Fundamental Pillars, offering a new face to Reddit, as well as providing new alternatives and attention to users with a misconception of EOS. Let's get ready to interact in all of Reddit in a respectful way, not only in the official EOS Reddit, trying to give a good marketing to what is being developed in EOS, reaching other Subreddits informing in a simple way developments, processes, improvements and projects that we have within the ecosystem. +- **Relationship to EOSIO:** We prepare to promote the EOS and EOSIO community in the best possible way, with good marketing, as well as to demonstrate that the work that is done together between the blockchains has borne fruit and momentum to EOSIO. Reddit has an extensive number of users who will not hesitate to look at the information related to EOS AND EOSIO. +- **Reason for Interest:** EOS VISION proposes to support the EOS community on Reddit, which has 97.7k members, is being one of the largest EOS communities, it is also the one with the most FUD of all EOS, since a couple of years, It has been a bit abandoned, and has been recovering thanks to the team of EOS SUPPORT and EOS BEES. We have seen how necessary and important this social network can be to attract both new users and new projects, so we propose to support Reddit. + ### Overview From 9f0036867bc83c715e20304a0f555ec1fbe9e641 Mon Sep 17 00:00:00 2001 From: Veronica Diaz <94094597+Creamyvanill@users.noreply.github.com> Date: Mon, 23 Jan 2023 13:10:50 -0400 Subject: [PATCH 042/170] Update eosreddit2.md --- applications/eosreddit2.md | 13 +++---------- 1 file changed, 3 insertions(+), 10 deletions(-) diff --git a/applications/eosreddit2.md b/applications/eosreddit2.md index e19f4018..786822a6 100644 --- a/applications/eosreddit2.md +++ b/applications/eosreddit2.md @@ -18,22 +18,15 @@ > ⚠️ *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 +Educate and inform the world of cryptocurrencies about the latest events on EOS and its technological improvements, generate active use of Reddit by promoting the adoption of EOS, promoting the different content of interest to users on Reddit and Facebook. + +### Overview - **Name:** EOS VISION x REDDIT AND FACEBOOK - **Brief Description:** Welcome to EOS REDDIT 2.0, the new stage of EOS REDDIT, where we will be able to turn the old, lonely and depressed Reddit into a new way of reading the news and giving constructive opinions. Our trained team prepares to work on 3 Fundamental Pillars, offering a new face to Reddit, as well as providing new alternatives and attention to users with a misconception of EOS. Let's get ready to interact in all of Reddit in a respectful way, not only in the official EOS Reddit, trying to give a good marketing to what is being developed in EOS, reaching other Subreddits informing in a simple way developments, processes, improvements and projects that we have within the ecosystem. - **Relationship to EOSIO:** We prepare to promote the EOS and EOSIO community in the best possible way, with good marketing, as well as to demonstrate that the work that is done together between the blockchains has borne fruit and momentum to EOSIO. Reddit has an extensive number of users who will not hesitate to look at the information related to EOS AND EOSIO. - **Reason for Interest:** EOS VISION proposes to support the EOS community on Reddit, which has 97.7k members, is being one of the largest EOS communities, it is also the one with the most FUD of all EOS, since a couple of years, It has been a bit abandoned, and has been recovering thanks to the team of EOS SUPPORT and EOS BEES. We have seen how necessary and important this social network can be to attract both new users and new projects, so we propose to support Reddit. - -### 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 EOSIO:** An indication of how your project relates to / integrates into EOSIO. -- **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): From cea6b491c5ba4495e4029b1c7d61de4b3a0b65b6 Mon Sep 17 00:00:00 2001 From: Veronica Diaz <94094597+Creamyvanill@users.noreply.github.com> Date: Mon, 23 Jan 2023 13:23:44 -0400 Subject: [PATCH 043/170] Update eosreddit2.md --- applications/eosreddit2.md | 44 ++++++++++++++++++++++---------------- 1 file changed, 25 insertions(+), 19 deletions(-) diff --git a/applications/eosreddit2.md b/applications/eosreddit2.md index 786822a6..c3aceb7d 100644 --- a/applications/eosreddit2.md +++ b/applications/eosreddit2.md @@ -53,40 +53,46 @@ Educate and inform the world of cryptocurrencies about the latest events on EOS ## 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:** +- Verónica Díaz +- Nelson Aular ### 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:** It is currently being legalized, for now we have the Creamy Vanilla C.A registry. +- **Registered Address:** Venezuela Cojedes, San Carlos. C-165 ### 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. +-Verónica Díaz + - Founder of Creamy Vanilla the first Smoothies store in EOS. Just like the Vanill Creamy collection on AtomicHub. + - Community Manager of EOSTARTER. + - Working bee and administrator in EOS BEES in Spanish. + - Active Eden member. + - Defibox administrator in Spanish. + - Ambassador of EOS SUPPORT in Spanish. + - Discord Manager of Function Loops Club (International Producer.) + - And moderator of different channels and social networks (EOS COMMUNITY DISCORD, EOS FACEBOOK, EOS REDDIT, EOS TELEGRAM AND EDEN ON EOS) -> 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. +-Nelson Aular + - Social Media and CM of EOS VISION. + - Co-founder of Eos- Español and community manager. + - Defibox moderator in Spanish. + - And moderator of different channels and social networks (EOS FACEBOOK, EOS REDDIT, EOS VISION TELEGRAM) -### Team Org Repos -- https://github.com/ -- https://github.com// -- https://github.com// +### Team Org Repos -> Please also provide the GitHub accounts of all team members. If they contain no activity, references to projects hosted elsewhere or live are also fine. +- [https://github.com/](https://github.com/eosvision1) ### Team Member Repos -- https://github.com/ -- https://github.com/ +-https://github.com/Creamyvanill +-https://github.com/nelsonaularq ### Team LinkedIn Profiles (if available) -- https://www.linkedin.com/ -- https://www.linkedin.com/ +- https://www.linkedin.com/in/ver%C3%B3nica-d%C3%ADaz-duran-6bbaa123a/ +- https://www.linkedin.com/mwlite/in/nelson-aular-a137b2259 ## Development Status From c52d00a8efaa631e5cb85d725bdd7b7399478bd3 Mon Sep 17 00:00:00 2001 From: DefiboxTeam Date: Tue, 7 Feb 2023 11:08:17 +0800 Subject: [PATCH 044/170] Update Defibox_vault.md --- applications/Defibox_vault.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/applications/Defibox_vault.md b/applications/Defibox_vault.md index 34df4c81..9fce1341 100644 --- a/applications/Defibox_vault.md +++ b/applications/Defibox_vault.md @@ -7,7 +7,7 @@ - **Pomelo Grant(s):** https://pomelo.io/grants/vault - **Project is Open-Source:** Yes* - **Project was part of Token sale:** No -- **Repository where Project resides:** https://github.com/DefiboxTeam/DefiboxVault-interface +- **Repository where Project resides:** https://github.com/defiboxswap/DefiboxVault-interface > 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 From 6e2f9ae318e472255cae5e572ae2a3315f9e5531 Mon Sep 17 00:00:00 2001 From: DefiboxTeam Date: Tue, 7 Feb 2023 11:16:26 +0800 Subject: [PATCH 045/170] Update Defibox_vault.md Updated project repo link. --- applications/Defibox_vault.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/applications/Defibox_vault.md b/applications/Defibox_vault.md index 9fce1341..48169041 100644 --- a/applications/Defibox_vault.md +++ b/applications/Defibox_vault.md @@ -140,7 +140,7 @@ https://github.com/defiboxswap - **Pomelo资助：** https://pomelo.io/grants/vault - **项目是开源的：** 是* - **项目是代币销售的一部分：** 否 -- **项目资源库：** https://github.com/DefiboxTeam/DefiboxVault-interface +- **项目资源库：** https://github.com/defiboxswap/DefiboxVault-interface ### 联系人 - **联系人姓名：** Raven From 6e4e6b5cbb017ffd4560e77ea097cf59d3e688ec Mon Sep 17 00:00:00 2001 From: Evm_name_service <118707458+evmns@users.noreply.github.com> Date: Tue, 7 Feb 2023 16:34:54 +0800 Subject: [PATCH 046/170] Update EVMNS.md --- applications/EVMNS.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/applications/EVMNS.md b/applications/EVMNS.md index 6d7fd802..d4c513c8 100644 --- a/applications/EVMNS.md +++ b/applications/EVMNS.md @@ -72,6 +72,9 @@ Compared to other DID domain projects, EVMNS has a special feature. Benefited fr ### Team Experience The core members of EVMNS Labs are the first ecological participants of EOS, who experienced and witnessed the launch of EOS and are still deeply involved in the ecological construction.

Team members have participated in several medium to large scale EOS projects before and after, and also developed ENS (Ethereum Name Service) related domain Exchange, domain bulk registry protocol, etc. We are not only EOS loyalists, but also ENS heavy players, with good understanding of DID domain naming system.

+### Team Member Repos +- Allen Harris,https://github.com/sutaiyi +- Frank Lee,https://github.com/chenminmin4 # Development Roadmap ### Milestone Summary - **Total Estimated Duration:** 12 weeks From b33e9480806c16feb5b39bf9ffc3ccb74d299aa4 Mon Sep 17 00:00:00 2001 From: Evm_name_service <118707458+evmns@users.noreply.github.com> Date: Tue, 7 Feb 2023 16:49:06 +0800 Subject: [PATCH 047/170] Update EVMNS.md --- applications/EVMNS.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/applications/EVMNS.md b/applications/EVMNS.md index d4c513c8..8c4c5d0f 100644 --- a/applications/EVMNS.md +++ b/applications/EVMNS.md @@ -71,10 +71,11 @@ Compared to other DID domain projects, EVMNS has a special feature. Benefited fr - **Registered Address:** 5001 Beach Road#07-37, Golden Mile Complex, Singapore 199588
### Team Experience The core members of EVMNS Labs are the first ecological participants of EOS, who experienced and witnessed the launch of EOS and are still deeply involved in the ecological construction.

-Team members have participated in several medium to large scale EOS projects before and after, and also developed ENS (Ethereum Name Service) related domain Exchange, domain bulk registry protocol, etc. We are not only EOS loyalists, but also ENS heavy players, with good understanding of DID domain naming system.

+Team members have participated in several medium to large scale EOS projects before and after, and also developed ENS (Ethereum Name Service) related domain Exchange, domain bulk registry protocol, etc. We are not only EOS loyalists, but also ENS heavy players, with good understanding of DID domain naming system.
### Team Member Repos -- Allen Harris,https://github.com/sutaiyi -- Frank Lee,https://github.com/chenminmin4 +- Allen Harris, https://github.com/sutaiyi +- Frank Lee, https://github.com/chenminmin4 + # Development Roadmap ### Milestone Summary - **Total Estimated Duration:** 12 weeks @@ -155,6 +156,7 @@ Team members have participated in several medium to large scale EOS projects bef Multi-chain ecology is the focus of the second phase of development, and we will prioritize the completion of the first phase of development (the above five milestones) to maximize the assurance that EVMNS can be launched and run stably at the first time after the official launch of EVM.

Therefore, the development content, duration and cost of the multi-chain ecology will be separately defined before the launch of the second phase.

# Future Plans +- Miltiple rounds of in-depth testing will be carried out first after the testnet is deployed. When all the problems found in the test are fixed, we will start the security audit of the smart contract to further ensure security. On the premise that the security audit is completely passed, it will finally be deployed to the mainnet and the project will be officially launched.It is estimated that it will take about 1 month to complete the above items.

- We will build EVMNS DAO, realize community management, and promote the implementation of decentralized operation and R&D of EVMNS.

- Register WEB2 domain with .evm suffix with DNS operators for domain resolution and binding services for traditional browsers so that users can directly access websites/personal homepages corresponding to .evm domain in Chrome, Edge and other browsers to achieve good interoperability between WEB3 and WEB2.

- Develop EOS plug-ins and browser plug-ins belonging to EVMNS to help users manage their EVMNS domains more easily through plug-ins, quick access, collection management of EVMNS domains of other users, etc.

From 14f4065aff7076769324c428de0c9b49c28a11cc Mon Sep 17 00:00:00 2001 From: Nathan James Date: Tue, 7 Feb 2023 22:19:16 +0200 Subject: [PATCH 048/170] Small changes to spelling & formatting. --- applications/EVMNS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/applications/EVMNS.md b/applications/EVMNS.md index 8c4c5d0f..41457878 100644 --- a/applications/EVMNS.md +++ b/applications/EVMNS.md @@ -156,7 +156,7 @@ Team members have participated in several medium to large scale EOS projects bef Multi-chain ecology is the focus of the second phase of development, and we will prioritize the completion of the first phase of development (the above five milestones) to maximize the assurance that EVMNS can be launched and run stably at the first time after the official launch of EVM.

Therefore, the development content, duration and cost of the multi-chain ecology will be separately defined before the launch of the second phase.

# Future Plans -- Miltiple rounds of in-depth testing will be carried out first after the testnet is deployed. When all the problems found in the test are fixed, we will start the security audit of the smart contract to further ensure security. On the premise that the security audit is completely passed, it will finally be deployed to the mainnet and the project will be officially launched.It is estimated that it will take about 1 month to complete the above items.

+- Multiple rounds of in-depth testing will be carried out first after the testnet is deployed. When all the problems found in the test are fixed, we will start the security audit of the smart contract to further ensure security. On the premise that the security audit is completely passed, it will finally be deployed to the mainnet and the project will be officially launched. It is estimated that it will take about 1 month to complete the above items.

- We will build EVMNS DAO, realize community management, and promote the implementation of decentralized operation and R&D of EVMNS.

- Register WEB2 domain with .evm suffix with DNS operators for domain resolution and binding services for traditional browsers so that users can directly access websites/personal homepages corresponding to .evm domain in Chrome, Edge and other browsers to achieve good interoperability between WEB3 and WEB2.

- Develop EOS plug-ins and browser plug-ins belonging to EVMNS to help users manage their EVMNS domains more easily through plug-ins, quick access, collection management of EVMNS domains of other users, etc.

From 4069f100b63241b822fbbcd5f055c46f45e39896 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Sat, 11 Feb 2023 14:01:07 -0500 Subject: [PATCH 049/170] Compress space before cut fields --- .github/workflows/grant-translated.yaml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/.github/workflows/grant-translated.yaml b/.github/workflows/grant-translated.yaml index 57123e24..77f61c60 100644 --- a/.github/workflows/grant-translated.yaml +++ b/.github/workflows/grant-translated.yaml @@ -44,16 +44,16 @@ jobs: - name: assign the env from the email name id: grep_email run: | - export APP_EMAIL=`/bin/grep "**Contact Email:**" ${{ needs.get_filename.outputs.filename }} | cut -d" " -f4` + export APP_EMAIL=`/bin/grep "**Contact Email:**" ${{ needs.get_filename.outputs.filename }} | tr -s " " | cut -d" " -f4` #echo "::set-env name=APP_EMAIL::$APP_EMAIL" echo "::set-output name=email_addr::$APP_EMAIL" - export CNAME=`/bin/grep "**Contact Name:**" ${{ needs.get_filename.outputs.filename }} | cut -d" " -f4-8` + export CNAME=`/bin/grep "**Contact Name:**" ${{ needs.get_filename.outputs.filename }} | tr -s " " | cut -d" " -f4-8` echo "::set-output name=contact_name::$CNAME" - export PNAME=`/bin/grep "**Project Name:**" ${{ needs.get_filename.outputs.filename }} | cut -d" " -f4-8` + export PNAME=`/bin/grep "**Project Name:**" ${{ needs.get_filename.outputs.filename }} | tr -s " " | cut -d" " -f4-8` echo "::set-output name=project_name::$PNAME" - export TNAME=`/bin/grep "**Team Name:**" ${{ needs.get_filename.outputs.filename }} | cut -d" " -f4-8` + export TNAME=`/bin/grep "**Team Name:**" ${{ needs.get_filename.outputs.filename }} | tr -s " " | cut -d" " -f4-8` echo "::set-output name=team_name::$TNAME" - export TCOST=`/bin/grep "**Total Costs:**" ${{ needs.get_filename.outputs.filename }} | cut -d" " -f4-8` + export TCOST=`/bin/grep "**Total Costs:**" ${{ needs.get_filename.outputs.filename }} | tr -s " " | cut -d" " -f4-8` echo "::set-output name=total_cost::$TCOST" echo ${{ github.actor }} ${{ github.event_name }} ${{ github.event.pull_request.head.repo.owner.login }} From af9e803f96a67da0b7ca491d5584a1e0321ed062 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Sat, 11 Feb 2023 14:16:03 -0500 Subject: [PATCH 050/170] Add -F to grep and fix writing to $GITHUB_OUT --- .github/workflows/grant-translated.yaml | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/.github/workflows/grant-translated.yaml b/.github/workflows/grant-translated.yaml index 77f61c60..20ca7a1c 100644 --- a/.github/workflows/grant-translated.yaml +++ b/.github/workflows/grant-translated.yaml @@ -44,17 +44,17 @@ jobs: - name: assign the env from the email name id: grep_email run: | - export APP_EMAIL=`/bin/grep "**Contact Email:**" ${{ needs.get_filename.outputs.filename }} | tr -s " " | cut -d" " -f4` - #echo "::set-env name=APP_EMAIL::$APP_EMAIL" - echo "::set-output name=email_addr::$APP_EMAIL" - export CNAME=`/bin/grep "**Contact Name:**" ${{ needs.get_filename.outputs.filename }} | tr -s " " | cut -d" " -f4-8` - echo "::set-output name=contact_name::$CNAME" - export PNAME=`/bin/grep "**Project Name:**" ${{ needs.get_filename.outputs.filename }} | tr -s " " | cut -d" " -f4-8` - echo "::set-output name=project_name::$PNAME" - export TNAME=`/bin/grep "**Team Name:**" ${{ needs.get_filename.outputs.filename }} | tr -s " " | cut -d" " -f4-8` - echo "::set-output name=team_name::$TNAME" - export TCOST=`/bin/grep "**Total Costs:**" ${{ needs.get_filename.outputs.filename }} | tr -s " " | cut -d" " -f4-8` - echo "::set-output name=total_cost::$TCOST" + export APP_EMAIL=`/bin/grep -F "**Contact Email:**" ${{ needs.get_filename.outputs.filename }} | tr -s " " | cut -d" " -f4` + echo "email_addr=$APP_EMAIL" >> $GITHUB_OUTPUT + # old way-> echo "::set-output name=email_addr::$APP_EMAIL" + export CNAME=`/bin/grep -F "**Contact Name:**" ${{ needs.get_filename.outputs.filename }} | tr -s " " | cut -d" " -f4-8` + echo "contact_name=$CNAME" >> $GITHUB_OUTPUT + export PNAME=`/bin/grep -F "**Project Name:**" ${{ needs.get_filename.outputs.filename }} | tr -s " " | cut -d" " -f4-8` + echo "project_name=$PNAME" >> $GITHUB_OUTPUT + export TNAME=`/bin/grep -F "**Team Name:**" ${{ needs.get_filename.outputs.filename }} | tr -s " " | cut -d" " -f4-8` + echo "team_name=$TNAME" >> $GITHUB_OUTPUT + export TCOST=`/bin/grep -F "**Total Costs:**" ${{ needs.get_filename.outputs.filename }} | tr -s " " | cut -d" " -f4-8` + echo "total_cost=$TCOST" >> $GITHUB_OUTPUT echo ${{ github.actor }} ${{ github.event_name }} ${{ github.event.pull_request.head.repo.owner.login }} checklabel: From adbdb8f0bec0580f9581bd14078669b3b395ae98 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Sat, 11 Feb 2023 14:25:18 -0500 Subject: [PATCH 051/170] Update grant-translated.yaml --- .github/workflows/grant-translated.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/workflows/grant-translated.yaml b/.github/workflows/grant-translated.yaml index 20ca7a1c..f58e5901 100644 --- a/.github/workflows/grant-translated.yaml +++ b/.github/workflows/grant-translated.yaml @@ -56,6 +56,7 @@ jobs: export TCOST=`/bin/grep -F "**Total Costs:**" ${{ needs.get_filename.outputs.filename }} | tr -s " " | cut -d" " -f4-8` echo "total_cost=$TCOST" >> $GITHUB_OUTPUT echo ${{ github.actor }} ${{ github.event_name }} ${{ github.event.pull_request.head.repo.owner.login }} + echo $APP_MAIL $CNAME $PNAME $TNAME $TCOST checklabel: needs: [get_filename, parse_app] From 45ef20ee75a390f18396b250683cf97407cb6e2c Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Sat, 11 Feb 2023 14:26:34 -0500 Subject: [PATCH 052/170] Minor typo - Total costs -> Total Costs --- applications/antelopeio_firewall.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/applications/antelopeio_firewall.md b/applications/antelopeio_firewall.md index 217f0aae..79240595 100644 --- a/applications/antelopeio_firewall.md +++ b/applications/antelopeio_firewall.md @@ -175,7 +175,7 @@ The application firewall turns out to be a natural element that should be an int - **Total estimated duration:** 6 months - **Full-Time Equivalent (FTE):** 2-2.5 -- **Total costs:** 50,000 USD +- **Total Costs:** 50,000 USD ### Milestone 1 — Create Antelope Firewall Prototype From c125e76c06a709bde61649f00d6c9b14a72b3243 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Wed, 15 Feb 2023 09:21:17 -0500 Subject: [PATCH 053/170] Update README.md Change max Grant size to $200k --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index dda41480..edd8068b 100644 --- a/README.md +++ b/README.md @@ -10,7 +10,7 @@ The odds of getting your project approved increase if you follow our [acceptance The EOS Network Foundation (ENF) funds development grants for "Public Good" as well as those to “for profit” entities - with the goal that all grants will enhance the EOS community. Grants proposals are accepted in three levels, each having different amounts and acceptance criteria. ENF Grants have guidelines, an application process, and a multi-stage approval process. They also have a milestone based pay-out system. - + From 905ae784d6c989ec2a576ace5eb476a6faa272d1 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Wed, 15 Feb 2023 09:22:29 -0500 Subject: [PATCH 054/170] Update pull_request_template.md Change max grant to $200k --- .github/pull_request_template.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md index 91d627cf..983bb5d2 100644 --- a/.github/pull_request_template.md +++ b/.github/pull_request_template.md @@ -7,9 +7,9 @@ ### For which grant [level](https://github.com/eosnetworkfoundation/grant-framework#grant-levels) are you applying? -- [ ] **Level 1**: Up to $10,000, 2 approvals -- [ ] **Level 2**: Up to $50,000, 3 approvals -- [ ] **Level 3**: Unlimited, 4 approvals +- [ ] **Level 1**: Up to $10,000, 2 approvals +- [ ] **Level 2**: Up to $50,000, 3 approvals +- [ ] **Level 3**: Up to $200,000, 4 approvals ### Application Checklist From 91c125bc8823607ed0607ba41cc6c7171dfa5844 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Wed, 15 Feb 2023 09:24:42 -0500 Subject: [PATCH 055/170] Update README.md Remove reference to EOSIO --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index edd8068b..777140bf 100644 --- a/README.md +++ b/README.md @@ -1,7 +1,7 @@ # EOS Network Foundation Grant Framework -As part of the EOS Network Foundation's (ENF) charter to grow and support the EOS ecosystem, the ENF has developed a multi-level grant program to help power research, software development, and maintenance of the EOSIO code base. For more information about the ENF, please visit our [website](https://eosnetwork.com/) or [YouTube account](https://www.youtube.com/c/EverythingEOS). +As part of the EOS Network Foundation's (ENF) charter to grow and support the EOS ecosystem, the ENF has developed a multi-level grant program to help power research, software development, and maintenance of the [Antelope](https://antelope.io/) code base. For more information about the ENF, please visit our [website](https://eosnetwork.com/) or [YouTube account](https://www.youtube.com/c/EverythingEOS). ## Grant Guidelines Individuals, small teams, and companies are all permitted to apply for grants. The purpose of the grants is to enable developers, businesses and individuals to build on EOS. Grants [vary in size](#grant-levels) based on the size and scope of the initiative. All forms of projects are open for submission, core chain modifications, tools, libraries, etc. as long as they are fully open-source. Strong technical projects that clearly add to the Public Good are preferred. @@ -90,12 +90,12 @@ The Grant Committee are senior members of the EOS community that know the priori ### Grant Evaluators The Grant Evaluators review applications approved by the Grant Committee for technical merit and achievability. They are more technical in nature and are more concerned with whether the proposal solves the problem optimally, is realizable in the specified time frame, and utilizes proper processes as required for the milestone achievement metrics. +- [Bart Wyatt](https://github.com/wanderingbort) - [Areg Hayrapetian](https://github.com/arhag) - [Matt Witherspoon](https://github.com/spoonincode) - [Bucky Kittinger](https://github.com/larryk85) -- [Bart Wyatt](https://github.com/wanderingbort) -- [Denis Carriere](https://github.com/DenisCarriere) - [Nathan James](https://github.com/nsjames) +- [Denis Carriere](https://github.com/DenisCarriere) ### Grant Operations The Grant Operations team manages the overall workflow of the ENF Grant process including: application acceptance and routing, notification of acceptance or rejection, monitoring of milestones and distribution of payments. From 29f08650103b40fd3990e7c0e74ccd52a56797b5 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Wed, 15 Feb 2023 09:26:00 -0500 Subject: [PATCH 056/170] Update minimum-requirements.md --- docs/minimum-requirements.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/minimum-requirements.md b/docs/minimum-requirements.md index 3c075329..0195fbf1 100644 --- a/docs/minimum-requirements.md +++ b/docs/minimum-requirements.md @@ -2,7 +2,7 @@ - All code produced as part of a grant must be open-sourced, and it must also not rely on closed-source software for full functionality. - We prefer MIT, but Apache 2.0, GPLv3, or Unlicense are also acceptable. - We do not award grants for projects that have been the object of a successful token sale. -- Grant deliverables must contribute to the EOS network first and foremost. +- Grant deliverables must contribute to the EOS Network first and foremost. - As a general rule, teams are asked to finish a grant before applying for another one. - Lastly, we do not fund projects that actively encourage gambling, illicit trade, money laundering or criminal activities. - We require all projects to create documentation that explains how their project works. From dcf5f2707f5fa90cd0e488e369b81e2078daa324 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Wed, 15 Feb 2023 09:26:49 -0500 Subject: [PATCH 057/170] Update grant-badge.md --- docs/grant-badge.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/grant-badge.md b/docs/grant-badge.md index 06217bcc..00fdb355 100644 --- a/docs/grant-badge.md +++ b/docs/grant-badge.md @@ -25,5 +25,5 @@ To that end, we’ve created a set of badges for grant recipients. They are avai Also, please don't use the **name or logo of the EOS Network Foundation** in any context that could misrepresent your relationship with the EOS Network Foundation. Infringement of these guidelines can result in an immediate annulment of the grant. -In case of any questions, please don’t hesitate to reach out to us at grants@eosn.foundation. +In case of any questions, please don’t hesitate to reach out to us at grants@eosnetwork.com. From 0b62f3222d3af01bbf1059794c6aed9c1a511991 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Wed, 15 Feb 2023 09:28:25 -0500 Subject: [PATCH 058/170] Update maintenance-grants.md --- docs/maintenance-grants.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/maintenance-grants.md b/docs/maintenance-grants.md index c3a2ae70..92ffec1a 100644 --- a/docs/maintenance-grants.md +++ b/docs/maintenance-grants.md @@ -1,7 +1,7 @@ # Maintenance Grants -Maintenance Grants are yet another idea to get involved with the EOS Mainnet community. If you are a user of an open-source library that has gone out of date, or you simply want to work on small new features/fix bugs in these repos, we can support your contributions via a grant. We are happy to award rolling grants on a monthly basis, as long as the work done within each time period is performed to a quality standard deemed satisfactory by the grant evaluators. +Maintenance Grants are yet another idea to get involved with the EOS Network community. If you are a user of an open-source library that has gone out of date, or you simply want to work on small new features/fix bugs in these repos, we can support your contributions via a grant. We are happy to award rolling grants on a monthly basis, as long as the work done within each time period is performed to a quality standard deemed satisfactory by the grant evaluators. The process of applying for a Maintenance Grant is similar to what was already outlined above, but instead of defining very detailed deliverables for each milestone upfront, we will ask you to specify, where possible: From da870415b89313f3bb6648f0f3cb8e45d7ae76b3 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Wed, 15 Feb 2023 09:31:54 -0500 Subject: [PATCH 059/170] Update grant_guidelines_per_category.md --- docs/grant_guidelines_per_category.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/grant_guidelines_per_category.md b/docs/grant_guidelines_per_category.md index cbc4bb75..8af0cd43 100644 --- a/docs/grant_guidelines_per_category.md +++ b/docs/grant_guidelines_per_category.md @@ -4,11 +4,11 @@ While we ask teams to provide details of their envisioned solution, we are aware The list below serves only as a guide and is not exhaustive. -## Core EISIO Chain / Sub-modules +## Core Antelope Chain / Sub-modules ### Applies to -- Building/extending the core EOSIO code base or sub-modules. +- Building/extending the core [Antelope](https://antelope.io/) code base or sub-modules. ### Requirements From 54b5342f0cf0f04271974460a4e5972b193259f6 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Wed, 15 Feb 2023 09:41:20 -0500 Subject: [PATCH 060/170] Update application-template.md Remove all references to EOSIO --- applications/application-template.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/applications/application-template.md b/applications/application-template.md index 8ae1dcd6..ba538094 100644 --- a/applications/application-template.md +++ b/applications/application-template.md @@ -42,7 +42,7 @@ - **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 EOSIO:** An indication of how your project relates to / integrates into EOSIO. +- **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 @@ -60,12 +60,12 @@ ### Ecosystem Fit -> Help us locate your project in the EOSIO landscape and what problems it tries to solve by answering each of these questions: +> 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 EOSIO ecosystem? +- 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? @@ -152,7 +152,7 @@ For each milestone, > - 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 EOSIO Application +### Milestone 1 Example — Implement EOS Application - **Estimated duration:** 1 month - **FTE:** 2 @@ -161,11 +161,11 @@ For each milestone, | 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 EOSIO nodes and send test transactions, which will show how the new functionality works. | +| 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 EOSIO | We will create an integration layer ... (Please list the functionality that will be implemented for the first milestone) | +| 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 ... | @@ -181,7 +181,7 @@ For each milestone, | 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 EOSIO nodes and send test transactions, which will show how the new functionality works. | +| 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.) From c6db14d0d146337fe8fcae453af4e121812e9d4c Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Wed, 15 Feb 2023 09:42:07 -0500 Subject: [PATCH 061/170] Update application-template.md --- applications/application-template.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/applications/application-template.md b/applications/application-template.md index ba538094..db4238ef 100644 --- a/applications/application-template.md +++ b/applications/application-template.md @@ -8,7 +8,7 @@ > > Please do not remove the bolding of labels (such as **Team Name:** ) 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 (such as **Team Name:**. +> Please note that this application will be **automatically parsed**. Please only put the data required in the fields following the bolded labels (such as **Team Name:** ). > > 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! > From 4720caa789d9dd86c7b7028569c174734cb9c1a9 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Wed, 15 Feb 2023 09:43:03 -0500 Subject: [PATCH 062/170] Update application-template.md --- applications/application-template.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/applications/application-template.md b/applications/application-template.md index db4238ef..8f483f05 100644 --- a/applications/application-template.md +++ b/applications/application-template.md @@ -12,7 +12,7 @@ > > 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 lines starting with a `>` (such as this one and the ones above and below) should be removed. +> 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 7b5f931d952c2d31dba393135611d1cd2680812d Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Wed, 15 Feb 2023 09:44:21 -0500 Subject: [PATCH 063/170] Update application-template.md --- applications/application-template.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/applications/application-template.md b/applications/application-template.md index 8f483f05..bbe09978 100644 --- a/applications/application-template.md +++ b/applications/application-template.md @@ -103,8 +103,8 @@ ### Team LinkedIn Profiles (if available) -- https://www.linkedin.com/ -- https://www.linkedin.com/ +- https://www.linkedin.com/in/ +- https://www.linkedin.com/in/ ## Development Status From ae11b5b4d385fc32ec4b6abcec8958f950c79ef2 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Wed, 15 Feb 2023 09:45:49 -0500 Subject: [PATCH 064/170] Update application-template.md --- applications/application-template.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/applications/application-template.md b/applications/application-template.md index bbe09978..c03a7ca7 100644 --- a/applications/application-template.md +++ b/applications/application-template.md @@ -138,7 +138,7 @@ For each milestone, > 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. +> 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 From 96c36792459cd6a9394b1543578ea5fb129de8d6 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Wed, 15 Feb 2023 12:44:20 -0500 Subject: [PATCH 065/170] Comment out echo that seems problematic --- .github/workflows/grant-translated.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/grant-translated.yaml b/.github/workflows/grant-translated.yaml index f58e5901..4d496bd9 100644 --- a/.github/workflows/grant-translated.yaml +++ b/.github/workflows/grant-translated.yaml @@ -56,7 +56,7 @@ jobs: export TCOST=`/bin/grep -F "**Total Costs:**" ${{ needs.get_filename.outputs.filename }} | tr -s " " | cut -d" " -f4-8` echo "total_cost=$TCOST" >> $GITHUB_OUTPUT echo ${{ github.actor }} ${{ github.event_name }} ${{ github.event.pull_request.head.repo.owner.login }} - echo $APP_MAIL $CNAME $PNAME $TNAME $TCOST + #echo $APP_MAIL $CNAME $PNAME $TNAME $TCOST checklabel: needs: [get_filename, parse_app] From b0934a4b21ee5d3241db3d8d3c032794a2ea266f Mon Sep 17 00:00:00 2001 From: Veronica Diaz <94094597+Creamyvanill@users.noreply.github.com> Date: Fri, 17 Feb 2023 10:25:00 -0400 Subject: [PATCH 066/170] Update eosreddit2.md --- applications/eosreddit2.md | 45 +++++++++++++++++++++----------------- 1 file changed, 25 insertions(+), 20 deletions(-) diff --git a/applications/eosreddit2.md b/applications/eosreddit2.md index c3aceb7d..267e97ed 100644 --- a/applications/eosreddit2.md +++ b/applications/eosreddit2.md @@ -15,7 +15,6 @@ - **Contact Email:** veronica14diazdiaz@gmail.com - **Website:** (https://eosvision.io/) -> ⚠️ *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 Educate and inform the world of cryptocurrencies about the latest events on EOS and its technological improvements, generate active use of Reddit by promoting the adoption of EOS, promoting the different content of interest to users on Reddit and Facebook. @@ -29,33 +28,39 @@ Educate and inform the world of cryptocurrencies about the latest events on EOS ### 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): +Our Mission Educate and inform the crypto world about the most recent events on EOS and its technological improvements, generate active use of Reddit and Facebook, promote the adoption of EOS and encourage the arrival of more users to these networks by promoting different content of interest . to all the people on Reddit and Facebook and thus connect these networks with others of great importance such as Discord, Telegram etc. -- 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 +Projects Secondary Objectives: Weekly and daily bulletins, extremely important information announcements. Podcasts with the EOS community, as well as special videos about using different dApps or projects. General support to the different EOS projects. Informative courses for new users in EOS. Reports, summaries and translations of the work carried out in EOS VISION. -### Ecosystem Fit +Aimed at resolving current issues such as Interacting and correcting misconceptions about EOS on social media, especially the social media we will be focusing on (Facebook and Reddit), which have been based on price, as well as respectfully encouraging users to express their opinions and negative aspects dedicated to FUD to show and encourage them to consult the new stage of EOS, the new opportunities and the different options that have been developed on the Network. + +Documentation of basic components, protocols, architecture, etc. to implement. We intend to use the reports, news, videos and other RELEVANT information found in the EOS COMMUNITY, and thus spread it on the social networks of Reddit and Facebook. Currently we use ENF Networks on Reddit and we bring the information punctually from the main source of information, his blog and twitter. + +What your project is not or will not provide or implement We will support Reddit, but it will not be owned by us, EOS REDDIT and EOS Facebook are owned by the community and anyone can provide their services. +This is a place for you to manage expectations and clarify any limitations that may not be obvious. + + PILLARS OF THE REDDIT VISION Updated based on the needs of the community. -> Help us locate your project in the EOSIO landscape and what problems it tries to solve by answering each of these questions: +1. Encourage users to React to Publications: At this stage we need users to be able to read the information and react to it, EOS VISION will focus on working to receive more reactions on the different networks as well as more comments on them. + +2.Moderation and Growth of Networks and Users: Encourage more people to join social networks, as well as moderate them extensively and widely, Reddit is one of the main Spammer entries into the ecosystem and we are ready to kill it. this. + +3. Growth of the ENF Official account on Reddit: Reddit already has the support of the ENF and we plan to continue promoting their networks. These months Reddit and Facebook have had a better and more complete information area thanks to the information development created by the NFE core team. We hope soon to be able to continue to grow this account and be fully verifiable. + +### Ecosystem Fit -- 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 EOSIO ecosystem? - - If so, how is your project different? - - If not, are there similar projects in related ecosystems? + • Where and how does your project fit into the ecosystem? Our project is in Ecosystem Growth, we hope to give good support to both EOS and projects, on Reddit and Facebook. + • Who is your target audience (chain/dapp/wallet/UI developers, designers, your own user base, some dapp's userbase, yourself)? Our hearing is based on: Journalists crypto users. New users on EOS and EOSIO. + • What need(s) does your project meet? A new opportunity for reddit and facebook and using these networks that have many users are given the opportunity to learn more about EOS, its dApps, ecosystem and development in these social networks and show what is being created. + • Are there any other projects similar to yours in the EOSIO ecosystem? + ◦ If so, how is your project different? + ◦ If not, are there similar projects in related ecosystems? Yes, currently some of the users within EOS post on Reddit, but not daily, EOS NATION and EOS SUPPORT post important details whenever needed. The difference of our proposal is that we intend to have Reddit active daily, with any relevant information. + ## Team **Team Leader:** - Verónica Díaz -- Nelson Aular ### Legal Structure - **Registered Legal Entity:** It is currently being legalized, for now we have the Creamy Vanilla C.A registry. @@ -91,7 +96,7 @@ Educate and inform the world of cryptocurrencies about the latest events on EOS ### Team LinkedIn Profiles (if available) -- https://www.linkedin.com/in/ver%C3%B3nica-d%C3%ADaz-duran-6bbaa123a/ +- https://www.linkedin.com/in/veronicadiazvcdd/ - https://www.linkedin.com/mwlite/in/nelson-aular-a137b2259 ## Development Status From 550af772e0b1926b9f5bf8ad868a7dff8ee510b6 Mon Sep 17 00:00:00 2001 From: Veronica Diaz <94094597+Creamyvanill@users.noreply.github.com> Date: Fri, 17 Feb 2023 10:39:49 -0400 Subject: [PATCH 067/170] Update eosreddit2.md --- applications/eosreddit2.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/applications/eosreddit2.md b/applications/eosreddit2.md index 267e97ed..1dd115cb 100644 --- a/applications/eosreddit2.md +++ b/applications/eosreddit2.md @@ -50,8 +50,11 @@ This is a place for you to manage expectations and clarify any limitations that ### Ecosystem Fit • Where and how does your project fit into the ecosystem? Our project is in Ecosystem Growth, we hope to give good support to both EOS and projects, on Reddit and Facebook. - • Who is your target audience (chain/dapp/wallet/UI developers, designers, your own user base, some dapp's userbase, yourself)? Our hearing is based on: Journalists crypto users. New users on EOS and EOSIO. + + • Who is your target audience (chain/dapp/wallet/UI developers, designers, your own user base, some dapp's userbase, yourself)? Our hearing is based on: Journalists crypto users. New users on EOS and Antelope. + • What need(s) does your project meet? A new opportunity for reddit and facebook and using these networks that have many users are given the opportunity to learn more about EOS, its dApps, ecosystem and development in these social networks and show what is being created. + • Are there any other projects similar to yours in the EOSIO ecosystem? ◦ If so, how is your project different? ◦ If not, are there similar projects in related ecosystems? Yes, currently some of the users within EOS post on Reddit, but not daily, EOS NATION and EOS SUPPORT post important details whenever needed. The difference of our proposal is that we intend to have Reddit active daily, with any relevant information. From e420d61cfa0bfdbe5dc6def420982ce95fc51a20 Mon Sep 17 00:00:00 2001 From: Veronica Diaz <94094597+Creamyvanill@users.noreply.github.com> Date: Sat, 18 Feb 2023 10:44:15 -0400 Subject: [PATCH 068/170] Update eosreddit2.md --- applications/eosreddit2.md | 92 +++++++++++--------------------------- 1 file changed, 26 insertions(+), 66 deletions(-) diff --git a/applications/eosreddit2.md b/applications/eosreddit2.md index 1dd115cb..a7bd2409 100644 --- a/applications/eosreddit2.md +++ b/applications/eosreddit2.md @@ -60,10 +60,11 @@ This is a place for you to manage expectations and clarify any limitations that ◦ If not, are there similar projects in related ecosystems? Yes, currently some of the users within EOS post on Reddit, but not daily, EOS NATION and EOS SUPPORT post important details whenever needed. The difference of our proposal is that we intend to have Reddit active daily, with any relevant information. -## Team +### Team members + +- **Team Leader:** Verónica Díaz +- Nelson Aular - **Team Leader:** -- Verónica Díaz ### Legal Structure - **Registered Legal Entity:** It is currently being legalized, for now we have the Creamy Vanilla C.A registry. @@ -104,13 +105,7 @@ This is a place for you to manage expectations and clarify any limitations that ## 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. +-We create daily content for the EOS community as well as special videos in Spanish, we have not wasted a single day developing good content for other areas, Reddit and Facebook have made great progress in recent months but we seek to improve these networks as a whole, we will continue to develop new ones opportunities and more. ## Development Roadmap @@ -132,77 +127,42 @@ For each milestone, ### 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. -- **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 EOSIO 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 EOSIO 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 EOSIO | 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 1 — Increased Reactions and Growth of Reddit and Facebook. -### Milestone 2 Example — Additional features - -- **Estimated Duration:** 1 month -- **FTE:** 2 -- **Costs:** 4,000 USD +- **Estimated duration:** 7 month +- **FTE:** +- **Costs:** 10,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 EOSIO 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. | increased upvote and karma to daily posts: | Upvote increase and incentive to reactions from different posts. Creation of system to increase users and upvote. | +| 0b. | Documentation | Creation of reports, reports and summaries regarding the metrics of the different social networks. | +| 0c. | Statistics and analysis on the growth of Reddit and Facebook | Karma and uptove stats tracking, as well as Facebook stats tracking. | +| 0d. | attention and moderation of networks | moderation of scammers and different posts that contain scams and false content. | +| 0e. | Attention and translation in languages. | greater attention to the public based on different languages. | +| 1. | Growth of the official ENF account on Reddit and Post on Facebook. | Reddit is already supported by ENF and we plan to continue promoting their networks and their posts for increased users and relevant content from EOS and Antelope. | +## Future Plans -... Add more milestones as above as needed ... +> Please include here: +Streaming Fireside Chat on Reddit. -## Future Plans +Customer service development for Reddit (Automatically redirect to EOS SUPPORT.) -> Please include here: +Reddit-Discord reward system: An opportunity for users to get EOS by participating in the community, Based on daily posts, comments, votes and more. -- 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. + We want to implement a direct alliance with different projects to maintain a more extensive activity on Reddit, which can share, participate and support the networks where we are working. ## Additional Information **How did you hear about the Grants Program?** EOS Network Foundation Website / Medium / Twitter / Element / Announcement by another team / personal recommendation / etc. +Twitter + > 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. +Since the last time, EOS VISION has scaled and positioned itself on reddit and facebook to solve problems that kept these networks alone, now it is to make them grow more, with more users and more opportunities. +https://github.com/eosnetworkfoundation/grant-framework/pull/44 +I have previously applied for an initial grant to the grant framework and it was successfully approved, as well as having all its milestones approved and completed: From 865aef23d03a40129e836c9e5de851517c1310e5 Mon Sep 17 00:00:00 2001 From: Veronica Diaz <94094597+Creamyvanill@users.noreply.github.com> Date: Sat, 18 Feb 2023 10:46:06 -0400 Subject: [PATCH 069/170] Update eosreddit2.md --- applications/eosreddit2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/applications/eosreddit2.md b/applications/eosreddit2.md index a7bd2409..1562dc25 100644 --- a/applications/eosreddit2.md +++ b/applications/eosreddit2.md @@ -164,5 +164,5 @@ Twitter > 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: Since the last time, EOS VISION has scaled and positioned itself on reddit and facebook to solve problems that kept these networks alone, now it is to make them grow more, with more users and more opportunities. -https://github.com/eosnetworkfoundation/grant-framework/pull/44 I have previously applied for an initial grant to the grant framework and it was successfully approved, as well as having all its milestones approved and completed: +https://github.com/eosnetworkfoundation/grant-framework/pull/44 From 0db5ea3c4a08b6aaa04770872965509ec03cdc50 Mon Sep 17 00:00:00 2001 From: Veronica Diaz <94094597+Creamyvanill@users.noreply.github.com> Date: Sat, 18 Feb 2023 10:54:53 -0400 Subject: [PATCH 070/170] Update eosreddit2.md --- applications/eosreddit2.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/applications/eosreddit2.md b/applications/eosreddit2.md index 1562dc25..5e934b8d 100644 --- a/applications/eosreddit2.md +++ b/applications/eosreddit2.md @@ -22,10 +22,11 @@ Educate and inform the world of cryptocurrencies about the latest events on EOS ### Overview - **Name:** EOS VISION x REDDIT AND FACEBOOK -- **Brief Description:** Welcome to EOS REDDIT 2.0, the new stage of EOS REDDIT, where we will be able to turn the old, lonely and depressed Reddit into a new way of reading the news and giving constructive opinions. Our trained team prepares to work on 3 Fundamental Pillars, offering a new face to Reddit, as well as providing new alternatives and attention to users with a misconception of EOS. Let's get ready to interact in all of Reddit in a respectful way, not only in the official EOS Reddit, trying to give a good marketing to what is being developed in EOS, reaching other Subreddits informing in a simple way developments, processes, improvements and projects that we have within the ecosystem. -- **Relationship to EOSIO:** We prepare to promote the EOS and EOSIO community in the best possible way, with good marketing, as well as to demonstrate that the work that is done together between the blockchains has borne fruit and momentum to EOSIO. Reddit has an extensive number of users who will not hesitate to look at the information related to EOS AND EOSIO. -- **Reason for Interest:** EOS VISION proposes to support the EOS community on Reddit, which has 97.7k members, is being one of the largest EOS communities, it is also the one with the most FUD of all EOS, since a couple of years, It has been a bit abandoned, and has been recovering thanks to the team of EOS SUPPORT and EOS BEES. We have seen how necessary and important this social network can be to attract both new users and new projects, so we propose to support Reddit. - +- **Brief Description:** Welcome to EOS REDDIT 2.0, the next stage of EOS REDDIT and Facebook. +Reddit and Facebook have become a new way to read the news and give constructive feedback. Our trained team is gearing up to work on updated 3 Fundamental Pillars, bringing a new face to Reddit as well as bringing new alternatives and care to users with a misconception of EOS. Let's get ready to interact all over Reddit and Facebook in a respectful way, not just the official EOS Reddit, trying to give good marketing to what is being developed on EOS, communicating with other Subreddits and other Facebook groups easily reporting on developments . processes, improvements and projects that we have within the ecosystem. +- **Relationship to EOSIO:** We prepare to promote the EOS and Antelope community in the best possible way, with good marketing, as well as to demonstrate that the work that is done together between the blockchains has borne fruit and momentum to Antelope. Reddit has an extensive number of users who will not hesitate to look at the information related to EOS AND Antelope. +- **Reason for Interest:** EOS VISION proposes to support the EOS community on Reddit and Facebook, reddit has 97.7k members, it is being one of the largest EOS communities, as well as Facebook has 171.K users, Reddit is the social network that contains the most FUD of all EOS networks, we have recovered reddit and facebook but we have to continue taking big steps, this has been recovering thanks to the EOS SUPPORT and EOS NATION team and the ENF. We have seen how necessary and important this social network can be to attract both new users and new projects, so we suggest you support Reddit. +- ### Project Details Our Mission Educate and inform the crypto world about the most recent events on EOS and its technological improvements, generate active use of Reddit and Facebook, promote the adoption of EOS and encourage the arrival of more users to these networks by promoting different content of interest . to all the people on Reddit and Facebook and thus connect these networks with others of great importance such as Discord, Telegram etc. From b3edc08e5f00799fcb4b89a442a268094e55886d Mon Sep 17 00:00:00 2001 From: Veronica Diaz <94094597+Creamyvanill@users.noreply.github.com> Date: Sat, 18 Feb 2023 10:56:21 -0400 Subject: [PATCH 071/170] Update eosreddit2.md --- applications/eosreddit2.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/applications/eosreddit2.md b/applications/eosreddit2.md index 5e934b8d..c947232a 100644 --- a/applications/eosreddit2.md +++ b/applications/eosreddit2.md @@ -26,7 +26,7 @@ Educate and inform the world of cryptocurrencies about the latest events on EOS Reddit and Facebook have become a new way to read the news and give constructive feedback. Our trained team is gearing up to work on updated 3 Fundamental Pillars, bringing a new face to Reddit as well as bringing new alternatives and care to users with a misconception of EOS. Let's get ready to interact all over Reddit and Facebook in a respectful way, not just the official EOS Reddit, trying to give good marketing to what is being developed on EOS, communicating with other Subreddits and other Facebook groups easily reporting on developments . processes, improvements and projects that we have within the ecosystem. - **Relationship to EOSIO:** We prepare to promote the EOS and Antelope community in the best possible way, with good marketing, as well as to demonstrate that the work that is done together between the blockchains has borne fruit and momentum to Antelope. Reddit has an extensive number of users who will not hesitate to look at the information related to EOS AND Antelope. - **Reason for Interest:** EOS VISION proposes to support the EOS community on Reddit and Facebook, reddit has 97.7k members, it is being one of the largest EOS communities, as well as Facebook has 171.K users, Reddit is the social network that contains the most FUD of all EOS networks, we have recovered reddit and facebook but we have to continue taking big steps, this has been recovering thanks to the EOS SUPPORT and EOS NATION team and the ENF. We have seen how necessary and important this social network can be to attract both new users and new projects, so we suggest you support Reddit. -- + ### Project Details Our Mission Educate and inform the crypto world about the most recent events on EOS and its technological improvements, generate active use of Reddit and Facebook, promote the adoption of EOS and encourage the arrival of more users to these networks by promoting different content of interest . to all the people on Reddit and Facebook and thus connect these networks with others of great importance such as Discord, Telegram etc. @@ -42,11 +42,11 @@ This is a place for you to manage expectations and clarify any limitations that PILLARS OF THE REDDIT VISION Updated based on the needs of the community. -1. Encourage users to React to Publications: At this stage we need users to be able to read the information and react to it, EOS VISION will focus on working to receive more reactions on the different networks as well as more comments on them. +•1. Encourage users to React to Publications: At this stage we need users to be able to read the information and react to it, EOS VISION will focus on working to receive more reactions on the different networks as well as more comments on them. -2.Moderation and Growth of Networks and Users: Encourage more people to join social networks, as well as moderate them extensively and widely, Reddit is one of the main Spammer entries into the ecosystem and we are ready to kill it. this. +•2.Moderation and Growth of Networks and Users: Encourage more people to join social networks, as well as moderate them extensively and widely, Reddit is one of the main Spammer entries into the ecosystem and we are ready to kill it. this. -3. Growth of the ENF Official account on Reddit: Reddit already has the support of the ENF and we plan to continue promoting their networks. These months Reddit and Facebook have had a better and more complete information area thanks to the information development created by the NFE core team. We hope soon to be able to continue to grow this account and be fully verifiable. +•3. Growth of the ENF Official account on Reddit: Reddit already has the support of the ENF and we plan to continue promoting their networks. These months Reddit and Facebook have had a better and more complete information area thanks to the information development created by the NFE core team. We hope soon to be able to continue to grow this account and be fully verifiable. ### Ecosystem Fit From 881719dd86bb6f316cfe0197b4bd1f660405cd12 Mon Sep 17 00:00:00 2001 From: Mikael337 <109104659+Mikael337@users.noreply.github.com> Date: Sun, 26 Feb 2023 10:19:53 +0200 Subject: [PATCH 072/170] Create alphaday.md --- applications/alphaday.md | 174 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 174 insertions(+) create mode 100644 applications/alphaday.md diff --git a/applications/alphaday.md b/applications/alphaday.md new file mode 100644 index 00000000..e14f7b53 --- /dev/null +++ b/applications/alphaday.md @@ -0,0 +1,174 @@ +# EOS Network Foundation Grant Proposal + +- **Project Name:** Alphaday +- **Team Name:** Alphabox Solutions Pte. Ltd. +- **EOS Payment Address:** depositpanda Memo: ctopjucyhyvhhbxbm55ygtqckitg9qdp +- **[Level](https://github.com/eosnetworkfoundation/grant-framework#grant-levels):** 1 +- **Pomelo Grant(s):** N/A +- **Project is Open-Source:** Yes +- **Project was part of Token sale:** No +- **Repository where Project resides:** https://github.com/AlphadayHQ + +## Contact + +- **Contact Name:** Deniz Omer +- **Contact Email:** deniz@alphaday.com +- **Website:** https://alphaday.com/ + +## Project Overview + +### Overview + +> Please provide the following: + +- **Name:** Alphaday +- **Brief Description:** Alphaday is a powerful crypto workflow aggregator that pulls in news, on-chain data, social media, web3 services and much more into one customizable UI. +- **Relationship to EOS Network / Antelope:** As a data aggregator community dashboard, Alphaday is blockchain-agnostic. +- **Reason for Interest:** Our app is designed to generate interest, increase user engagement & retention, and educate new users with regard to cryptocurrency projects and the industry in general. + +### Project Details + +Our product is already live at : https://app.alphaday.com + +Alphaday is a React-Typescript dashboard on the frontend using a Python-Django backend built on distributed infrastructure with Postgres and Redis Databases. + +Pitch Deck: https://bit.ly/Alphadaydeck + +Github: https://github.com/AlphadayHQ + +### Ecosystem Fit + +Project fit: Social - A data aggregator as a Community dashboard. + +Target audience: We aim to create a dashboard that serves any EOS Network user, holders, developers, VCs, and pretty much any stakeholder whether they are completely new to the EOS Network ecosystem or an expert. + +Our dashboard aims to provide a single end-point from which users can consume all the information on a project they could possibly want. In this case, we would like to build a EOS Network Community Dashboard that aggregates all the discussions, talking points, narratives, events, metrics, official announcements and much much more into one single dashboard. With one glance at this dashboard EOS Network community members would have a top-down view of what is happening across the entire EOS Network ecosystem. From this view they could then jump deeper into their areas of interest (i.e. devs to dev documentation, EOS holders to twitter and reddit discussions, investors to on-chain metrics across both EOS Network’s own pages and to third-party data providers) + +Alphaday has no direct competitors as it aims to recreate a crypto user’s daily workflow (i.e. their general experience) inside a single dashboard. i.e. if a EOS Network ecosystem participant wakes up, checks their portfolio, reads twitter, browses the EOS Network governance forum, listens to the latest podcast featuring EOS Network team members, does a bit of on-chain research, instead of having this workflow spread across a dozen tabs, it’s all available within a single screen on Alphaday. + +## Team + +### Team members + +**Team Leader:** Deniz Omer + +Team Members: + +Devs: +Felipe Faraggi \ +Charles Nwankwo \ +Jonathan Irhodia \ +Vicente Almonacid \ +Pablo Palomo \ +Gideon Anyalewechi \ +Content/Ops: \ +Paris Charanas Giannakou \ +Mikael Hagopian + +### Legal Structure +- **Registered Legal Entity:** Alphabox Solutions Pte. Ltd. +- **Registered Address:** North Canal Road, Singapore, 059294 Singapore + +### Team Experience + +The founder, Deniz Omer, has been involved in the Ethereum space since early 2016 and joined Kyber Network in 2017 as Head of Ecosystem Growth before quitting to start Alphaday full-time in 2021. Previously he worked at Thomson Reuters for a decade building financial products that rivaled the Bloomberg Terminal. He is currently also a Venture Partner at IOSG.VC. + +His co-founder, Felipe, has also been involved in Ethereum since 2016 and was a Developer Advocate at Pegasys and Consensys before quitting to work full time on Alphaday. + +Alphaday’s third co-founder is DeFiDude who used to be a community manager at both Aave and Kyber Network before co-founding Alphaday. + +### Team Org Repos + +https://github.com/AlphadayHQ + +### Team Member Repos + +https://github.com/faraggi \ +https://github.com/ppalomo \ +https://github.com/v-almonacid \ +https://github.com/elcharitas \ +https://github.com/Xavier-Charles \ +https://github.com/getgiddy + +### Team LinkedIn Profiles + +https://www.linkedin.com/in/denizomer/ \ +https://www.linkedin.com/in/faraggi/ \ +https://www.linkedin.com/in/vicente-almonacid/ \ +https://www.linkedin.com/in/getgiddy/ \ +https://www.linkedin.com/in/pablo-palomo-07127711/ \ +https://linkedin.com/in/elcharitas \ +https://www.linkedin.com/in/charles-nwankwo-01/ \ +https://www.linkedin.com/in/paris-charanas-giannakou-788386231/ \ +https://www.linkedin.com/in/mikael-h-87bb4ba4/ + +## Development Status + +Our app is already live at: https://app.alphaday.com/ + +We have already signed several agreements with other projects and are currently working on releasing their dashboards. You can already see a few of these dashboards live in the web-app (e.g. Verasity, Impossible Finance, Arbitrum) and several more are on their way within the next month. + +Besides building dashboards for specific projects, we are simultaneously working on developing and improving our app’s features, widgets, content, and performance. + +## Development Roadmap + +### Milestone 1 — Development and Deployment of Initial Dashboard + +**Estimated Duration:** 2 months \ +**FTE:** 0.5 \ +**Costs:** 1,500 USD + +We would like to create a EOS Network ecosystem dashboard that aggregates the following information into a single community dashboard: + +| Number | Deliverable | Specification | +| -----: | ----------- | ------------- | +| 1. | Blog | The latest EOS Network official announcements and blog post content | +| 2. | News | A feed of all news mentions of EOS Network from coindesk, cointelegraph and 20+ other news sources aggregated from across the internet. | +| 3. | Calendar | A calendar containing all EOS Network events including EOS Network Governance votes, meetups, hackathons with EOS Network bounties, AMAs. | +| 4. | Podcasts | Podcast feed containing the latest appearances and interviews given by EOS Network team members. | +| 5. | Videos | Youtube stream containing educational EOS Network content. | +| 6. | Documentation | EOS Documentation directory. | +| 7. | Social Media | Twitter, Discord, & Telegram Integration to show a feed of latest discussions. | +| 8. | Other Info | FAQ, Technical Whitepaper, EOS tokenomics information. | +| 9. | Devs & Builders | Grants and Bounties links with descriptions and other resources to guide devs and builders. | +| 10. | Ecosystem & App | Links and descriptions of Dapps and other platforms within the EOS ecosystem. | + +We should be able to build and deploy the above dashboard within 2 months so if this grant is approved we want to launch the EOS Network dashboard by April 2023. + +Thereafter, we will maintain & curate the dashboard on a daily basis as well as improve the functionality and availability of features in our application as a whole. + +Please note that we can add and remove widgets and/or contents as required by your team. For a brief idea about other widgets and data that we can include, please visit our Live product page (Beta) at: https://app.alphaday.com/ + +### Milestone 2 — Maintenance + +**Estimated Duration:** 12 months continuous \ +**FTE:** 0.5 \ +**Costs:** 1,500 USD + +| 1. | Maintenance & Curation | Continuous daily maintenance and curation of content of the dashboard by a specialist over a year. | + +### Milestone Summary + +- **Total Estimated Duration:** 2 months for deployment, 12 months of maintenance. +- **Full-Time Equivalent (FTE):** 1 FTE +- **Total Costs:** 3,000 USD + +## Future Plans + +In addition to building the EOS Network dashboard, we will be constantly monitoring and improving existing features on Alphaday and adding new widgets and features as we go along. These enhancements will automatically apply to the EOS Dashboard. + +In terms of numbers: +We’ve been growing MAU 40% month-on-month with minimal marketing as we wanted to build a solid and stable product before scaling up our marketing but we expect to reach 10k MAU by March and overall our goal is to 10x our MAU every year. + +Considering EOSIO has 255K twitter followers and using this as a very crude proxy for community size, we would consider it a success if we could serve at least 1% of them on a monthly basis (2.55K MAU). + +For further details on our roadmap please view our Pitch Deck: https://bit.ly/Alphadaydeck + +## Additional Information + +**How did you hear about the Grants Program?** +EOS Network Foundation Website + +If we get this grant, we will start working on the board immediately and we should have it ready within 2 months. Once we’ve launched the board, we will do user interviews and feedback sessions to tune the dashboard. We will continue this process of iterating, deploying, and collecting feedback continuously to build a dashboard that EOS stakeholders truly love to use. + +We are in the process of applying for grants to further develop our app and dashboard. More than a dozen projects have already approved to fund us and we are currently in the process of building or have already released their dashboards. You can see the ones already released at https://app.alphaday.com/ to get a brief idea of how “https://app.alphaday.com/b/eos” would look. From 4e1111ab55925f563cfb389f0c281cb5ff65ef02 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Mon, 6 Mar 2023 14:19:50 -0500 Subject: [PATCH 073/170] Added containers for additional quarters --- docs/accepted_grant_applications.md | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/docs/accepted_grant_applications.md b/docs/accepted_grant_applications.md index 9211093e..d1882782 100644 --- a/docs/accepted_grant_applications.md +++ b/docs/accepted_grant_applications.md @@ -6,12 +6,38 @@ ## Table of Contents +- [2023](#2023) + - [Season 5 - First Quarter 2023](#wave-5---first-quarter-2023) + - [2022](#2022) + - [Season 4 - Fourth Quarter 2022](#wave-4---fourth-quarter-2022) + - [Season 3 - Third Quarter 2022](#wave-3---third-quarter-2022) - [Season 2 - Second Quarter 2022](#wave-2---second-quarter-2022) - [Season 1 - First Quarter 2022](#wave-1---first-quarter-2022) +# 2023 + +## Wave 1 - First Quarter 2023 + +| Team | Project Name / Application | Repo | Terminated | First Delivery | Completed +| :--- | :------ | :--- | :--------: | :------------: | :-------: | +| [Name](https://example.com/) | [ProjectName](../applications/application_template.md) | [GitHub](https://github.com/) |
  • [ ]
|
  • [ ]
|
  • [ ]
| + + # 2022 +## Wave 4 - Fourth Quarter 2022 + +| Team | Project Name / Application | Repo | Terminated | First Delivery | Completed +| :--- | :------ | :--- | :--------: | :------------: | :-------: | +| [Name](https://example.com/) | [ProjectName](../applications/application_template.md) | [GitHub](https://github.com/) |
  • [ ]
|
  • [ ]
|
  • [ ]
| + +## Wave 3 - Third Quarter 2022 + +| Team | Project Name / Application | Repo | Terminated | First Delivery | Completed +| :--- | :------ | :--- | :--------: | :------------: | :-------: | +| [Name](https://example.com/) | [ProjectName](../applications/application_template.md) | [GitHub](https://github.com/) |
  • [ ]
|
  • [ ]
|
  • [ ]
| + ## Wave 2 - Second Quarter 2022 | Team | Project Name / Application | Repo | Terminated | First Delivery | Completed From 056ccfa7bf663b7756bf8a9f22759eb2d9958ba6 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Mon, 6 Mar 2023 14:22:05 -0500 Subject: [PATCH 074/170] Update accepted_grant_applications.md --- docs/accepted_grant_applications.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/accepted_grant_applications.md b/docs/accepted_grant_applications.md index d1882782..bcfe88bf 100644 --- a/docs/accepted_grant_applications.md +++ b/docs/accepted_grant_applications.md @@ -21,7 +21,7 @@ | Team | Project Name / Application | Repo | Terminated | First Delivery | Completed | :--- | :------ | :--- | :--------: | :------------: | :-------: | -| [Name](https://example.com/) | [ProjectName](../applications/application_template.md) | [GitHub](https://github.com/) |
  • [ ]
|
  • [ ]
|
  • [ ]
| +| [Name](https://example.com/) | [ProjectName](../applications/application-template.md) | [GitHub](https://github.com/) |
  • [ ]
|
  • [ ]
|
  • [ ]
| # 2022 @@ -30,13 +30,13 @@ | Team | Project Name / Application | Repo | Terminated | First Delivery | Completed | :--- | :------ | :--- | :--------: | :------------: | :-------: | -| [Name](https://example.com/) | [ProjectName](../applications/application_template.md) | [GitHub](https://github.com/) |
  • [ ]
|
  • [ ]
|
  • [ ]
| +| [Name](https://example.com/) | [ProjectName](../applications/application-template.md) | [GitHub](https://github.com/) |
  • [ ]
|
  • [ ]
|
  • [ ]
| ## Wave 3 - Third Quarter 2022 | Team | Project Name / Application | Repo | Terminated | First Delivery | Completed | :--- | :------ | :--- | :--------: | :------------: | :-------: | -| [Name](https://example.com/) | [ProjectName](../applications/application_template.md) | [GitHub](https://github.com/) |
  • [ ]
|
  • [ ]
|
  • [ ]
| +| [Name](https://example.com/) | [ProjectName](../applications/application-template.md) | [GitHub](https://github.com/) |
  • [ ]
|
  • [ ]
|
  • [ ]
| ## Wave 2 - Second Quarter 2022 From be2a8d4c7da924da72cfb5c21c4df297d7b51128 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Mon, 6 Mar 2023 14:23:42 -0500 Subject: [PATCH 075/170] Update accepted_grant_applications.md --- docs/accepted_grant_applications.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/accepted_grant_applications.md b/docs/accepted_grant_applications.md index bcfe88bf..663db72d 100644 --- a/docs/accepted_grant_applications.md +++ b/docs/accepted_grant_applications.md @@ -21,7 +21,7 @@ | Team | Project Name / Application | Repo | Terminated | First Delivery | Completed | :--- | :------ | :--- | :--------: | :------------: | :-------: | -| [Name](https://example.com/) | [ProjectName](../applications/application-template.md) | [GitHub](https://github.com/) |
  • [ ]
|
  • [ ]
|
  • [ ]
| +| [Name](https://example.com/) | [ProjectName](../applications/application-template.md) | [GitHub]([https://github.com/](https://github.com/eosnetworkfoundation)) |
  • [ ]
|
  • [ ]
|
  • [ ]
| # 2022 @@ -30,13 +30,13 @@ | Team | Project Name / Application | Repo | Terminated | First Delivery | Completed | :--- | :------ | :--- | :--------: | :------------: | :-------: | -| [Name](https://example.com/) | [ProjectName](../applications/application-template.md) | [GitHub](https://github.com/) |
  • [ ]
|
  • [ ]
|
  • [ ]
| +| [Name](https://example.com/) | [ProjectName](../applications/application-template.md) | [GitHub]([https://github.com/](https://github.com/eosnetworkfoundation)) |
  • [ ]
|
  • [ ]
|
  • [ ]
| ## Wave 3 - Third Quarter 2022 | Team | Project Name / Application | Repo | Terminated | First Delivery | Completed | :--- | :------ | :--- | :--------: | :------------: | :-------: | -| [Name](https://example.com/) | [ProjectName](../applications/application-template.md) | [GitHub](https://github.com/) |
  • [ ]
|
  • [ ]
|
  • [ ]
| +| [Name](https://example.com/) | [ProjectName](../applications/application-template.md) | [GitHub]([https://github.com/](https://github.com/eosnetworkfoundation)) |
  • [ ]
|
  • [ ]
|
  • [ ]
| ## Wave 2 - Second Quarter 2022 From 589ec41e7431d1bb59e3273003decfaa3da9b77f Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Mon, 6 Mar 2023 14:26:09 -0500 Subject: [PATCH 076/170] Update accepted_grant_applications.md --- docs/accepted_grant_applications.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/accepted_grant_applications.md b/docs/accepted_grant_applications.md index 663db72d..c54cb44f 100644 --- a/docs/accepted_grant_applications.md +++ b/docs/accepted_grant_applications.md @@ -21,7 +21,7 @@ | Team | Project Name / Application | Repo | Terminated | First Delivery | Completed | :--- | :------ | :--- | :--------: | :------------: | :-------: | -| [Name](https://example.com/) | [ProjectName](../applications/application-template.md) | [GitHub]([https://github.com/](https://github.com/eosnetworkfoundation)) |
  • [ ]
|
  • [ ]
|
  • [ ]
| +| [Name](https://example.com/) | [ProjectName](../applications/application-template.md) | [GitHub](https://github.com/eosnetworkfoundation) |
  • [ ]
|
  • [ ]
|
  • [ ]
| # 2022 @@ -30,13 +30,13 @@ | Team | Project Name / Application | Repo | Terminated | First Delivery | Completed | :--- | :------ | :--- | :--------: | :------------: | :-------: | -| [Name](https://example.com/) | [ProjectName](../applications/application-template.md) | [GitHub]([https://github.com/](https://github.com/eosnetworkfoundation)) |
  • [ ]
|
  • [ ]
|
  • [ ]
| +| [Name](https://example.com/) | [ProjectName](../applications/application-template.md) | [GitHub](https://github.com/eosnetworkfoundation) |
  • [ ]
|
  • [ ]
|
  • [ ]
| ## Wave 3 - Third Quarter 2022 | Team | Project Name / Application | Repo | Terminated | First Delivery | Completed | :--- | :------ | :--- | :--------: | :------------: | :-------: | -| [Name](https://example.com/) | [ProjectName](../applications/application-template.md) | [GitHub]([https://github.com/](https://github.com/eosnetworkfoundation)) |
  • [ ]
|
  • [ ]
|
  • [ ]
| +| [Name](https://example.com/) | [ProjectName](../applications/application-template.md) | [GitHub](https://github.com/eosnetworkfoundation) |
  • [ ]
|
  • [ ]
|
  • [ ]
| ## Wave 2 - Second Quarter 2022 From 120cd12d704c9f501d73d516c05ae05ece3abfae Mon Sep 17 00:00:00 2001 From: "Seth@Boid.com" <51824327+mchosc@users.noreply.github.com> Date: Wed, 8 Mar 2023 15:50:23 +0000 Subject: [PATCH 077/170] Update antelopeio_firewall.md --- applications/antelopeio_firewall.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/applications/antelopeio_firewall.md b/applications/antelopeio_firewall.md index 79240595..d9374e3e 100644 --- a/applications/antelopeio_firewall.md +++ b/applications/antelopeio_firewall.md @@ -36,7 +36,7 @@ We propose an application that would sit behind an existing firewall such as NGI ![AntelopeIO_Firewall_Diagram](https://ipfs.animus.is/ipfs/QmZ3qEwAGuaboNYAypJdXtcGnofQX4yPrYhVStQnX5u8Vh?filename=diagram-antelope-firewall.jpg) -The initial version of the application would be written in Typescript and could be easily scaled across multiple cores and operated with high uptime via pm2. The application could run on the same VM as Leap but for optimal flexibility could be hosted on a dedicated VM that scales independently. +The initial version of the application would be written in Rust and could be easily scaled across multiple cores and operated with high uptime. The application could run on the same VM as Leap but for optimal flexibility could be hosted on a dedicated VM that scales independently. #### **Features** From 6bfccbae9c78fad785429d37434c50c00704cbe1 Mon Sep 17 00:00:00 2001 From: "Seth@Boid.com" <51824327+mchosc@users.noreply.github.com> Date: Wed, 8 Mar 2023 15:53:59 +0000 Subject: [PATCH 078/170] Update antelopeio_firewall.md --- applications/antelopeio_firewall.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/applications/antelopeio_firewall.md b/applications/antelopeio_firewall.md index d9374e3e..0bcec0d0 100644 --- a/applications/antelopeio_firewall.md +++ b/applications/antelopeio_firewall.md @@ -55,8 +55,6 @@ The initial version of the application would be written in Rust and could be eas #### **Future additions** Once the base level application has reached a production ready state and iterated based on node operator feedback there are additional developments that could improve the application. -- **Codebase** The application logic could be rewritten in Rust or C++ and used as a standalone application or integrated into Leap as a plugin. This would reduce CPU/RAM/Latency of the application but may limit some functionality and will greatly increase development cost. Therefore a Typescript version should be developed first for quick and cost-effective iteration. - - **Monetization** Node operators who offer public APIs often do so as a free service that operates at a loss. This makes it difficult for operators to sustain the hardware and manpower required for high-availability RPC nodes. A monetization feature could be added to the firewall that would allow users to pay to have their contract actions whitelisted for less rate-limiting. For example, an application developer may pay a node operator a subscription fee to whitelist their contract operations in order to ensure a smooth experience for their users. Monetization can be totally automated with a smart contract and basic logic integrated into the firewall. #### **Feedback from node operators** From 7d440a0686d0e36b30bb485b2293c6f570d53576 Mon Sep 17 00:00:00 2001 From: Veronica Diaz <94094597+Creamyvanill@users.noreply.github.com> Date: Tue, 21 Mar 2023 12:38:28 -0400 Subject: [PATCH 079/170] Update eosreddit2.md --- applications/eosreddit2.md | 112 ++++++++++++++++++++++++++----------- 1 file changed, 78 insertions(+), 34 deletions(-) diff --git a/applications/eosreddit2.md b/applications/eosreddit2.md index c947232a..c931df48 100644 --- a/applications/eosreddit2.md +++ b/applications/eosreddit2.md @@ -1,37 +1,58 @@ # EOS Network Foundation Grant Proposal -- **Project Name:** EOS VISIONS +> 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 **Team Name:** ) 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 (such as **Team Name:** ). +> +> 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:** EOS VISIONS - **Team Name:** Creamy Vainilla C.A -- **EOS Payment Address:** eosvisionorg +- **EOS Payment Address:** eosvisionorg - **[Level](https://github.com/eosnetworkfoundation/grant-framework#grant-levels):** 1 -- **Pomelo Grant(s):** https://pomelo.io/grants/eosvision -- **Project is Open-Source:** Yes -- **Project was part of Token sale:** No -- **Repository where Project resides:** https://github.com/eosvision1 +- **Pomelo Grant(s):** [List URL(s) to Pomelo grants for your team (or list N/A for non-applicable)](https://pomelo.io/grants/eosvision) +- **Project is Open-Source:** Yes/ +- **Project was part of Token sale:** Yes/No +- **Repository where Project resides:**[ https://github.com//](https://github.com/eosvision1) +> 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:** Verónica Coromoto Díaz Duran. -- **Contact Email:** veronica14diazdiaz@gmail.com -- **Website:** (https://eosvision.io/) - +- **Contact Email:** veronica14diazdiaz@gmail.com +- **Website:** https://eosvision.io/ +- +> ⚠️ *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 -Educate and inform the world of cryptocurrencies about the latest events on EOS and its technological improvements, generate active use of Reddit by promoting the adoption of EOS, promoting the different content of interest to users on Reddit and Facebook. + +-Educate and inform the world of cryptocurrencies about the latest events on EOS and its technological improvements, generate active use of Reddit by promoting the adoption of EOS, promoting the different content of interest to users on Reddit and Facebook. ### Overview +> Please provide the following: + - **Name:** EOS VISION x REDDIT AND FACEBOOK - **Brief Description:** Welcome to EOS REDDIT 2.0, the next stage of EOS REDDIT and Facebook. Reddit and Facebook have become a new way to read the news and give constructive feedback. Our trained team is gearing up to work on updated 3 Fundamental Pillars, bringing a new face to Reddit as well as bringing new alternatives and care to users with a misconception of EOS. Let's get ready to interact all over Reddit and Facebook in a respectful way, not just the official EOS Reddit, trying to give good marketing to what is being developed on EOS, communicating with other Subreddits and other Facebook groups easily reporting on developments . processes, improvements and projects that we have within the ecosystem. -- **Relationship to EOSIO:** We prepare to promote the EOS and Antelope community in the best possible way, with good marketing, as well as to demonstrate that the work that is done together between the blockchains has borne fruit and momentum to Antelope. Reddit has an extensive number of users who will not hesitate to look at the information related to EOS AND Antelope. +- **Relationship to EOS Network / Antelope:** We prepare to promote the EOS and Antelope community in the best possible way, with good marketing, as well as to demonstrate that the work that is done together between the blockchains has borne fruit and momentum to Antelope. Reddit has an extensive number of users who will not hesitate to look at the information related to EOS AND Antelope. - **Reason for Interest:** EOS VISION proposes to support the EOS community on Reddit and Facebook, reddit has 97.7k members, it is being one of the largest EOS communities, as well as Facebook has 171.K users, Reddit is the social network that contains the most FUD of all EOS networks, we have recovered reddit and facebook but we have to continue taking big steps, this has been recovering thanks to the EOS SUPPORT and EOS NATION team and the ENF. We have seen how necessary and important this social network can be to attract both new users and new projects, so we suggest you support Reddit. ### Project Details -Our Mission Educate and inform the crypto world about the most recent events on EOS and its technological improvements, generate active use of Reddit and Facebook, promote the adoption of EOS and encourage the arrival of more users to these networks by promoting different content of interest . to all the people on Reddit and Facebook and thus connect these networks with others of great importance such as Discord, Telegram etc. +> 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): -Projects Secondary Objectives: Weekly and daily bulletins, extremely important information announcements. Podcasts with the EOS community, as well as special videos about using different dApps or projects. General support to the different EOS projects. Informative courses for new users in EOS. Reports, summaries and translations of the work carried out in EOS VISION. +-Our Mission Educate and inform the crypto world about the most recent events on EOS and its technological improvements, generate active use of Reddit and Facebook, promote the adoption of EOS and encourage the arrival of more users to these networks by promoting different content of interest . to all the people on Reddit and Facebook and thus connect these networks with others of great importance such as Discord, Telegram etc. + +-Projects Secondary Objectives: Weekly and daily bulletins, extremely important information announcements. Podcasts with the EOS community, as well as special videos about using different dApps or projects. General support to the different EOS projects. Informative courses for new users in EOS. Reports, summaries and translations of the work carried out in EOS VISION. Aimed at resolving current issues such as Interacting and correcting misconceptions about EOS on social media, especially the social media we will be focusing on (Facebook and Reddit), which have been based on price, as well as respectfully encouraging users to express their opinions and negative aspects dedicated to FUD to show and encourage them to consult the new stage of EOS, the new opportunities and the different options that have been developed on the Network. @@ -40,8 +61,7 @@ Documentation of basic components, protocols, architecture, etc. to implement. W What your project is not or will not provide or implement We will support Reddit, but it will not be owned by us, EOS REDDIT and EOS Facebook are owned by the community and anyone can provide their services. This is a place for you to manage expectations and clarify any limitations that may not be obvious. - PILLARS OF THE REDDIT VISION Updated based on the needs of the community. - + PILLARS OF THE REDDIT VISION Updated based on the needs of the community: •1. Encourage users to React to Publications: At this stage we need users to be able to read the information and react to it, EOS VISION will focus on working to receive more reactions on the different networks as well as more comments on them. •2.Moderation and Growth of Networks and Users: Encourage more people to join social networks, as well as moderate them extensively and widely, Reddit is one of the main Spammer entries into the ecosystem and we are ready to kill it. this. @@ -50,30 +70,35 @@ This is a place for you to manage expectations and clarify any limitations that ### Ecosystem Fit - • Where and how does your project fit into the ecosystem? Our project is in Ecosystem Growth, we hope to give good support to both EOS and projects, on Reddit and Facebook. +> 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? Our project is in Ecosystem Growth, we hope to give good support to both EOS and projects, on Reddit and Facebook. - • Who is your target audience (chain/dapp/wallet/UI developers, designers, your own user base, some dapp's userbase, yourself)? Our hearing is based on: Journalists crypto users. New users on EOS and Antelope. + -Who is your target audience (chain/dapp/wallet/UI developers, designers, your own user base, some dapp's userbase, yourself)? Our hearing is based on: Journalists crypto users. New users on EOS and Antelope. - • What need(s) does your project meet? A new opportunity for reddit and facebook and using these networks that have many users are given the opportunity to learn more about EOS, its dApps, ecosystem and development in these social networks and show what is being created. + -What need(s) does your project meet? A new opportunity for reddit and facebook and using these networks that have many users are given the opportunity to learn more about EOS, its dApps, ecosystem and development in these social networks and show what is being created. • Are there any other projects similar to yours in the EOSIO ecosystem? ◦ If so, how is your project different? - ◦ If not, are there similar projects in related ecosystems? Yes, currently some of the users within EOS post on Reddit, but not daily, EOS NATION and EOS SUPPORT post important details whenever needed. The difference of our proposal is that we intend to have Reddit active daily, with any relevant information. - + ◦If not, are there similar projects in related ecosystems? + - Yes, currently some of the users within EOS post on Reddit, but not daily, EOS NATION and EOS SUPPORT post important details whenever needed. The difference of our proposal is that we intend to have Reddit active daily, with any relevant information. + +## Team ### Team members - **Team Leader:** Verónica Díaz - Nelson Aular - ### Legal Structure - **Registered Legal Entity:** It is currently being legalized, for now we have the Creamy Vanilla C.A registry. -- **Registered Address:** Venezuela Cojedes, San Carlos. C-165 +- **Registered Address:** Venezuela Cojedes, San Carlos. C-165 ### Team Experience --Verónica Díaz +> 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. + +-Verónica Díaz: - Founder of Creamy Vanilla the first Smoothies store in EOS. Just like the Vanill Creamy collection on AtomicHub. - Community Manager of EOSTARTER. - Working bee and administrator in EOS BEES in Spanish. @@ -82,22 +107,24 @@ This is a place for you to manage expectations and clarify any limitations that - Ambassador of EOS SUPPORT in Spanish. - Discord Manager of Function Loops Club (International Producer.) - And moderator of different channels and social networks (EOS COMMUNITY DISCORD, EOS FACEBOOK, EOS REDDIT, EOS TELEGRAM AND EDEN ON EOS) - --Nelson Aular + + -Nelson Aular: - Social Media and CM of EOS VISION. - Co-founder of Eos- Español and community manager. - Defibox moderator in Spanish. - And moderator of different channels and social networks (EOS FACEBOOK, EOS REDDIT, EOS VISION TELEGRAM) +> 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/eosvision1) -- [https://github.com/](https://github.com/eosvision1) +> 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/Creamyvanill --https://github.com/nelsonaularq +-(https://github.com/Creamyvanill) +-(https://github.com/nelsonaularq) ### Team LinkedIn Profiles (if available) @@ -106,6 +133,8 @@ This is a place for you to manage expectations and clarify any limitations that ## 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: + -We create daily content for the EOS community as well as special videos in Spanish, we have not wasted a single day developing good content for other areas, Reddit and Facebook have made great progress in recent months but we seek to improve these networks as a whole, we will continue to develop new ones opportunities and more. ## Development Roadmap @@ -128,25 +157,43 @@ For each milestone, ### 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 — Increased Reactions and Growth of Reddit and Facebook. - **Estimated duration:** 7 month -- **FTE:** +- **FTE:** 2 - **Costs:** 10,000 USD | ID | Deliverable | Specification | | ----- | ----------- | ------------- | | 0a. | increased upvote and karma to daily posts: | Upvote increase and incentive to reactions from different posts. Creation of system to increase users and upvote. | | 0b. | Documentation | Creation of reports, reports and summaries regarding the metrics of the different social networks. | -| 0c. | Statistics and analysis on the growth of Reddit and Facebook | Karma and uptove stats tracking, as well as Facebook stats tracking. | +| 0c. | Statistics and analysis on the growth of Reddit and Facebook | arma and uptove stats tracking, as well as Facebook stats tracking. | | 0d. | attention and moderation of networks | moderation of scammers and different posts that contain scams and false content. | -| 0e. | Attention and translation in languages. | greater attention to the public based on different languages. | +| 0e. | Attention and translation in languages | greater attention to the public based on different languages. | | 1. | Growth of the official ENF account on Reddit and Post on Facebook. | Reddit is already supported by ENF and we plan to continue promoting their networks and their posts for increased users and relevant content from EOS and Antelope. | ## 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. Streaming Fireside Chat on Reddit. Customer service development for Reddit (Automatically redirect to EOS SUPPORT.) @@ -155,13 +202,10 @@ Reddit-Discord reward system: An opportunity for users to get EOS by participati We want to implement a direct alliance with different projects to maintain a more extensive activity on Reddit, which can share, participate and support the networks where we are working. - ## Additional Information **How did you hear about the Grants Program?** EOS Network Foundation Website / Medium / Twitter / Element / Announcement by another team / personal recommendation / etc. - Twitter - > 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: Since the last time, EOS VISION has scaled and positioned itself on reddit and facebook to solve problems that kept these networks alone, now it is to make them grow more, with more users and more opportunities. From 9ce15fa780ee8f2b8650f0da9155703cb42b30e7 Mon Sep 17 00:00:00 2001 From: Veronica Diaz <94094597+Creamyvanill@users.noreply.github.com> Date: Tue, 21 Mar 2023 12:40:38 -0400 Subject: [PATCH 080/170] Update eosreddit2.md --- applications/eosreddit2.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/applications/eosreddit2.md b/applications/eosreddit2.md index c931df48..94b37748 100644 --- a/applications/eosreddit2.md +++ b/applications/eosreddit2.md @@ -18,10 +18,10 @@ - **Team Name:** Creamy Vainilla C.A - **EOS Payment Address:** eosvisionorg - **[Level](https://github.com/eosnetworkfoundation/grant-framework#grant-levels):** 1 -- **Pomelo Grant(s):** [List URL(s) to Pomelo grants for your team (or list N/A for non-applicable)](https://pomelo.io/grants/eosvision) +- **Pomelo Grant(s):** https://pomelo.io/grants/eosvision - **Project is Open-Source:** Yes/ - **Project was part of Token sale:** Yes/No -- **Repository where Project resides:**[ https://github.com//](https://github.com/eosvision1) +- **Repository where Project resides:** https://github.com/eosvision1 > 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 @@ -117,7 +117,7 @@ This is a place for you to manage expectations and clarify any limitations that > 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/eosvision1) +- https://github.com/eosvision1 > 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. From e2af39328af9e0db5ba3bf4d57a0ee52c377708e Mon Sep 17 00:00:00 2001 From: Veronica Diaz <94094597+Creamyvanill@users.noreply.github.com> Date: Tue, 21 Mar 2023 12:41:22 -0400 Subject: [PATCH 081/170] Update eosreddit2.md --- applications/eosreddit2.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/applications/eosreddit2.md b/applications/eosreddit2.md index 94b37748..96be675f 100644 --- a/applications/eosreddit2.md +++ b/applications/eosreddit2.md @@ -19,8 +19,8 @@ - **EOS Payment Address:** eosvisionorg - **[Level](https://github.com/eosnetworkfoundation/grant-framework#grant-levels):** 1 - **Pomelo Grant(s):** https://pomelo.io/grants/eosvision -- **Project is Open-Source:** Yes/ -- **Project was part of Token sale:** Yes/No +- **Project is Open-Source:** Yes +- **Project was part of Token sale:** No - **Repository where Project resides:** https://github.com/eosvision1 > 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. From b8b8cff6d9533b6f6f9fa4cbd32d0b3e801e7651 Mon Sep 17 00:00:00 2001 From: Veronica Diaz <94094597+Creamyvanill@users.noreply.github.com> Date: Tue, 21 Mar 2023 13:03:48 -0400 Subject: [PATCH 082/170] Update eosreddit2.md --- applications/eosreddit2.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/applications/eosreddit2.md b/applications/eosreddit2.md index 96be675f..be9c8c14 100644 --- a/applications/eosreddit2.md +++ b/applications/eosreddit2.md @@ -27,7 +27,7 @@ ## Contact - **Contact Name:** Verónica Coromoto Díaz Duran. -- **Contact Email:** veronica14diazdiaz@gmail.com +- **Contact Email:** veronica14diazdiaz@gmail.com - **Website:** https://eosvision.io/ - > ⚠️ *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.* @@ -160,9 +160,9 @@ For each milestone, > 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 +- **Total Estimated Duration:** 7 months +- **Full-Time Equivalent (FTE):** 7 +- **Total Costs:** 10,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.
@@ -176,7 +176,7 @@ For each milestone, ### Milestone 1 — Increased Reactions and Growth of Reddit and Facebook. - **Estimated duration:** 7 month -- **FTE:** 2 +- **FTE:** - **Costs:** 10,000 USD | ID | Deliverable | Specification | From b4df26f6a13509ef22f377eb590bcc160cc1f0e9 Mon Sep 17 00:00:00 2001 From: Veronica Diaz <94094597+Creamyvanill@users.noreply.github.com> Date: Tue, 21 Mar 2023 13:04:29 -0400 Subject: [PATCH 083/170] Update eosreddit2.md --- applications/eosreddit2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/applications/eosreddit2.md b/applications/eosreddit2.md index be9c8c14..c693bf9b 100644 --- a/applications/eosreddit2.md +++ b/applications/eosreddit2.md @@ -161,7 +161,7 @@ For each milestone, > 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:** 7 months -- **Full-Time Equivalent (FTE):** 7 +- **Full-Time Equivalent (FTE):** - **Total Costs:** 10,000 USD > Please note that this application is automatically parsed.
From 3fb399559bfa2a9cd623521d86d1b8471d4b66f3 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Wed, 22 Mar 2023 17:22:00 -0400 Subject: [PATCH 084/170] Removed all comment lines --- applications/eosreddit2.md | 49 ++++---------------------------------- 1 file changed, 4 insertions(+), 45 deletions(-) diff --git a/applications/eosreddit2.md b/applications/eosreddit2.md index c693bf9b..c84c9f1f 100644 --- a/applications/eosreddit2.md +++ b/applications/eosreddit2.md @@ -1,19 +1,5 @@ # 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 **Team Name:** ) 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 (such as **Team Name:** ). -> -> 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:** EOS VISIONS - **Team Name:** Creamy Vainilla C.A - **EOS Payment Address:** eosvisionorg @@ -22,7 +8,6 @@ - **Project is Open-Source:** Yes - **Project was part of Token sale:** No - **Repository where Project resides:** https://github.com/eosvision1 -> 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 @@ -30,7 +15,7 @@ - **Contact Email:** veronica14diazdiaz@gmail.com - **Website:** https://eosvision.io/ - -> ⚠️ *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 @@ -38,8 +23,6 @@ ### Overview -> Please provide the following: - - **Name:** EOS VISION x REDDIT AND FACEBOOK - **Brief Description:** Welcome to EOS REDDIT 2.0, the next stage of EOS REDDIT and Facebook. Reddit and Facebook have become a new way to read the news and give constructive feedback. Our trained team is gearing up to work on updated 3 Fundamental Pillars, bringing a new face to Reddit as well as bringing new alternatives and care to users with a misconception of EOS. Let's get ready to interact all over Reddit and Facebook in a respectful way, not just the official EOS Reddit, trying to give good marketing to what is being developed on EOS, communicating with other Subreddits and other Facebook groups easily reporting on developments . processes, improvements and projects that we have within the ecosystem. @@ -48,8 +31,6 @@ Reddit and Facebook have become a new way to read the news and give constructive ### 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): - -Our Mission Educate and inform the crypto world about the most recent events on EOS and its technological improvements, generate active use of Reddit and Facebook, promote the adoption of EOS and encourage the arrival of more users to these networks by promoting different content of interest . to all the people on Reddit and Facebook and thus connect these networks with others of great importance such as Discord, Telegram etc. -Projects Secondary Objectives: Weekly and daily bulletins, extremely important information announcements. Podcasts with the EOS community, as well as special videos about using different dApps or projects. General support to the different EOS projects. Informative courses for new users in EOS. Reports, summaries and translations of the work carried out in EOS VISION. @@ -62,11 +43,11 @@ What your project is not or will not provide or implement We will support Reddit This is a place for you to manage expectations and clarify any limitations that may not be obvious. PILLARS OF THE REDDIT VISION Updated based on the needs of the community: -•1. Encourage users to React to Publications: At this stage we need users to be able to read the information and react to it, EOS VISION will focus on working to receive more reactions on the different networks as well as more comments on them. +- 1. Encourage users to React to Publications: At this stage we need users to be able to read the information and react to it, EOS VISION will focus on working to receive more reactions on the different networks as well as more comments on them. -•2.Moderation and Growth of Networks and Users: Encourage more people to join social networks, as well as moderate them extensively and widely, Reddit is one of the main Spammer entries into the ecosystem and we are ready to kill it. this. +- 2.Moderation and Growth of Networks and Users: Encourage more people to join social networks, as well as moderate them extensively and widely, Reddit is one of the main Spammer entries into the ecosystem and we are ready to kill it. this. -•3. Growth of the ENF Official account on Reddit: Reddit already has the support of the ENF and we plan to continue promoting their networks. These months Reddit and Facebook have had a better and more complete information area thanks to the information development created by the NFE core team. We hope soon to be able to continue to grow this account and be fully verifiable. +- 3. Growth of the ENF Official account on Reddit: Reddit already has the support of the ENF and we plan to continue promoting their networks. These months Reddit and Facebook have had a better and more complete information area thanks to the information development created by the NFE core team. We hope soon to be able to continue to grow this account and be fully verifiable. ### Ecosystem Fit @@ -96,8 +77,6 @@ This is a place for you to manage expectations and clarify any limitations that ### 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. - -Verónica Díaz: - Founder of Creamy Vanilla the first Smoothies store in EOS. Just like the Vanill Creamy collection on AtomicHub. - Community Manager of EOSTARTER. @@ -114,13 +93,9 @@ This is a place for you to manage expectations and clarify any limitations that - Defibox moderator in Spanish. - And moderator of different channels and social networks (EOS FACEBOOK, EOS REDDIT, EOS VISION TELEGRAM) -> 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/eosvision1 -> 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/Creamyvanill) @@ -133,8 +108,6 @@ This is a place for you to manage expectations and clarify any limitations that ## 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: - -We create daily content for the EOS community as well as special videos in Spanish, we have not wasted a single day developing good content for other areas, Reddit and Facebook have made great progress in recent months but we seek to improve these networks as a whole, we will continue to develop new ones opportunities and more. ## Development Roadmap @@ -157,22 +130,10 @@ For each milestone, ### 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:** 7 months - **Full-Time Equivalent (FTE):** - **Total Costs:** 10,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 — Increased Reactions and Growth of Reddit and Facebook. - **Estimated duration:** 7 month @@ -190,8 +151,6 @@ For each milestone, ## 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. Streaming Fireside Chat on Reddit. From 3e418ec2236e20c4db691d6aa1edff934d97aff7 Mon Sep 17 00:00:00 2001 From: "Seth@Boid.com" <51824327+mchosc@users.noreply.github.com> Date: Thu, 30 Mar 2023 00:17:55 +0100 Subject: [PATCH 085/170] Update antelopeio_firewall.md --- applications/antelopeio_firewall.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/applications/antelopeio_firewall.md b/applications/antelopeio_firewall.md index 0bcec0d0..d1a39a09 100644 --- a/applications/antelopeio_firewall.md +++ b/applications/antelopeio_firewall.md @@ -186,7 +186,7 @@ The application firewall turns out to be a natural element that should be an int | ----- | ----------- | ------------- | | 0a. | License | MIT | | 0b. | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how to configure and run, including technical draft: short document will act as an overview of the technical implementation details as part of the development planning stage. Will guide code structure and development milestones. | -| 0c. | Deployment | We will provide a Prototype with a limited basic functionalities implemented. For example the firewall will be able to route queries to nodes and return responses with basic blacklisting functionality. | +| 0c. | Deployment | We will provide a Prototype with a limited basic functionalities implemented. For example the firewall will be able to route queries to nodes and return responses with basic blacklisting functionality. Main focus will be on gRPC. | ### Milestone 2 — Implement Antelope Firewall MVP version @@ -200,6 +200,7 @@ The application firewall turns out to be a natural element that should be an int | 0b. | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how to configure and run Alpha and Beta version (MVP). | | 0c. | Deployment Alpha | We will provide a Alpha version with a major features implemented in a basic way. We will begin running on our own nodes. | | 0d. | Deployment Beta (MVP) | We will provide a Beta version (MVP) with all features implemented in a basic way. The app should be ready to distribute to external infra providers for feedback and testing. | +| 0e. | HTTP gRPC and P2P Functionality | We will integrate HTTP gRPC and P2P functionality into the Antelope Firewall. | ### Milestone 3 — Implement Antelope Firewall 1.0 version @@ -214,6 +215,7 @@ The application firewall turns out to be a natural element that should be an int | 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. | Deployment | We will provide an Antelope Firewall 1.0 version - production ready solution, based on feedback from infra providers and issues discovered during beta testing. | | 0e. | Article | We will publish an **article** that explains what are the features of the product, how does it work and what was achieved as part of the grant. | +|0f. | HTTP gRPC and P2P Continued Development | We will continue the development of the HTTP gRPC and P2P functionality, refining and optimizing its performance, and ensuring seamless integration with the Antelope Firewall. | ## Future Plans From a0d9e0607f9383333cb881c319508a745277059b Mon Sep 17 00:00:00 2001 From: "Seth@Boid.com" <51824327+mchosc@users.noreply.github.com> Date: Thu, 30 Mar 2023 00:59:03 +0100 Subject: [PATCH 086/170] Update antelopeio_firewall.md --- applications/antelopeio_firewall.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/applications/antelopeio_firewall.md b/applications/antelopeio_firewall.md index d1a39a09..5ff600d3 100644 --- a/applications/antelopeio_firewall.md +++ b/applications/antelopeio_firewall.md @@ -186,7 +186,7 @@ The application firewall turns out to be a natural element that should be an int | ----- | ----------- | ------------- | | 0a. | License | MIT | | 0b. | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how to configure and run, including technical draft: short document will act as an overview of the technical implementation details as part of the development planning stage. Will guide code structure and development milestones. | -| 0c. | Deployment | We will provide a Prototype with a limited basic functionalities implemented. For example the firewall will be able to route queries to nodes and return responses with basic blacklisting functionality. Main focus will be on gRPC. | +| 0c. | Deployment | We will provide a Prototype with a limited basic functionalities implemented. For example the firewall will be able to route queries to nodes and return responses with basic blacklisting functionality. | ### Milestone 2 — Implement Antelope Firewall MVP version @@ -199,8 +199,7 @@ The application firewall turns out to be a natural element that should be an int | 0a. | License | MIT | | 0b. | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how to configure and run Alpha and Beta version (MVP). | | 0c. | Deployment Alpha | We will provide a Alpha version with a major features implemented in a basic way. We will begin running on our own nodes. | -| 0d. | Deployment Beta (MVP) | We will provide a Beta version (MVP) with all features implemented in a basic way. The app should be ready to distribute to external infra providers for feedback and testing. | -| 0e. | HTTP gRPC and P2P Functionality | We will integrate HTTP gRPC and P2P functionality into the Antelope Firewall. | +| 0d. | Deployment Beta (MVP) | We will provide a Beta version (MVP) with all features implemented in a basic way. The app should be ready to distribute to external infra providers for feedback and testing. HTTP RPC and P2P Functionality | ### Milestone 3 — Implement Antelope Firewall 1.0 version @@ -213,9 +212,8 @@ The application firewall turns out to be a natural element that should be an int | 0a. | License | MIT | | 0b. | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how to configure and run Antelope Firewall 1.0 version, which covers all of the application functionality and configuration. Also we will create deployment scripts for various platforms to simplify the process of getting started. | | 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. | Deployment | We will provide an Antelope Firewall 1.0 version - production ready solution, based on feedback from infra providers and issues discovered during beta testing. | -| 0e. | Article | We will publish an **article** that explains what are the features of the product, how does it work and what was achieved as part of the grant. | -|0f. | HTTP gRPC and P2P Continued Development | We will continue the development of the HTTP gRPC and P2P functionality, refining and optimizing its performance, and ensuring seamless integration with the Antelope Firewall. | +| 0d. | Deployment | We will provide an Antelope Firewall 1.0 version - production ready solution, based on feedback from infra providers and issues discovered during beta testing. HTTP RPC and P2P Functionality | +| 0e. | Article | We will publish an **article** that explains what are the features of the product, how does it work and what was achieved as part of the grant. | ## Future Plans From b7db06609f03755a5b5d1e055237ecc6b6b38611 Mon Sep 17 00:00:00 2001 From: Nathan James Date: Tue, 4 Apr 2023 13:17:39 +0300 Subject: [PATCH 087/170] Aligning document with ecosystem --- docs/announcement-guidelines.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/announcement-guidelines.md b/docs/announcement-guidelines.md index c24670dc..6adbf0da 100644 --- a/docs/announcement-guidelines.md +++ b/docs/announcement-guidelines.md @@ -16,7 +16,7 @@ We also cross-promote the most recent projects and their milestones on Twitter o - Suggested flow for the post: - This is what the team has built so far. - These are the team's future development plans. - - This is how the technology will contribute to the Polkadot ecosystem. + - This is how the technology will contribute to the EOS ecosystem. ## Key components From aa5e20a3bdbea25cbdf531fdc5b679f4d290998a Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Wed, 12 Apr 2023 13:21:42 -0400 Subject: [PATCH 088/170] Update application-template.md --- applications/application-template.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/applications/application-template.md b/applications/application-template.md index c03a7ca7..41b44e97 100644 --- a/applications/application-template.md +++ b/applications/application-template.md @@ -8,7 +8,7 @@ > > Please do not remove the bolding of labels (such as **Team Name:** ) 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 (such as **Team Name:** ). +> 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! > From d88422fbb33d0ee8fff9e7dd22f73d4eaf4c470b Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Wed, 12 Apr 2023 13:22:28 -0400 Subject: [PATCH 089/170] Update application-template.md --- applications/application-template.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/applications/application-template.md b/applications/application-template.md index 41b44e97..7a6fdb4c 100644 --- a/applications/application-template.md +++ b/applications/application-template.md @@ -6,7 +6,7 @@ > > 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 **Team Name:** ) as it is needed by the automated parsers - that includes the bolding on lines starting with a bullet as part of a list. +> 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. > From ff6e911f505f8daec9abe7d27e9a5ae90677c71c Mon Sep 17 00:00:00 2001 From: tim Date: Thu, 5 Jan 2023 14:52:27 -0600 Subject: [PATCH 090/170] Add grant proposal for FACINGS NFT Collection Manager Stage 2 --- .../facings-nft-collection-manager-stage-2.md | 232 ++++++++++++++++++ 1 file changed, 232 insertions(+) create mode 100644 applications/facings-nft-collection-manager-stage-2.md diff --git a/applications/facings-nft-collection-manager-stage-2.md b/applications/facings-nft-collection-manager-stage-2.md new file mode 100644 index 00000000..09d158d5 --- /dev/null +++ b/applications/facings-nft-collection-manager-stage-2.md @@ -0,0 +1,232 @@ +# EOS Network Foundation Grant Proposal + +- **Project Name:** NFT Collection Manager Stage 2 +- **Team Name:** FACINGS, Inc. +- **EOS Payment Address:** facings +- **[Level](https://github.com/eosnetworkfoundation/grant-framework#grant-levels):** 3 +- **Pomelo Grant(s):** https://pomelo.io/grants/eospyo +- **Project is Open-Source:** Yes +- **Project was part of Token sale:** No +- **Repository where Project resides:** https://github.com/FACINGS/collection-manager + + +## Contact + +- **Contact Name:** Rob Konsdorf +- **Contact Email:** rob@facings.io +- **Website:** https://facings.io + + +## Project Overview + +Our goal with the NFT Collection Manager is to create a publishing platform that leverages EOS’s robustness and attracts gaming studios to a more simplistic and user friendly launchpad. We believe the integration of the Collection Manager with additional features down the road will be a very compelling choice, supporting EOS in its endeavor to become a premier gaming blockchain, while maintaining excitement for other trends and collections. + +### Overview + +- **Name:** NFT Collection Manager +- **Brief Description:** An interface to the AtomicAssets standard which makes it easy to manage your own Atomic NFT Collections, and plugins to ensure high quality releases and gamification integration. +- **Relationship to EOSIO:** FACINGS has been launching AtomicAssets NFTs since its inception in early 2021. Its parent company and initial investor, Detroit Ledger Technologies (formerly EOS DETROIT), has been in the Antelope/EOSIO ecosystem since its inception as a pioneer block producer on EOS and other Antelope blockchains. +- **Reason for Interest:** Our team and experience combined with the need for an open-source creator that is friendlier to use makes for a perfect fit. The lack of development on EOS for NFTs and gamification resources makes it a necessity going forward. + + +### Project Details + +**Mock-ups/designs of any UI components** + +These designs are from past prototypes, to give an example, but does not represent the final product: +https://drive.google.com/drive/folders/1iN2bQJhB_w_A_fKXC8-iYr3Re2-rbqSt + +**Data models of the core functionality** + +The data model will be largely based on the AtomicAssets [schema](https://github.com/pinknetworkx/atomicassets-contract/wiki/Tables). + +**API specifications of the core functionality** + +We seek to implement the entirety of the [AtomicAssets](https://github.com/pinknetworkx/atomicassets-contract/wiki/Actions) allowed actions in the NFT Collection Manager, bringing together the power of existing actions into the EOS framework for implementation with complex collections and gamification. + + +**An overview of the technology stack to be used** + +The NFT Collection Manager is a client-side app built in NextJS and talks directly with public blockchain API nodes. Our goal is to minimize dependencies. Therefore we intend for all of the data to be stored on-chain, with IPFS being used to store all NFT images. + + +**Documentation of core components, protocols, architecture, etc. to be deployed** + +- Jungle4 EOS testnet support +- Data handling/validation +- TypeScript implementation +- Plugin Architecture + - Data standard & import functionality + - Smart Airdrops + + +**PoC/MVP or other relevant prior work or research on the topic** + +We have an internal proof of concept that was shared in our previous grant application. The creator is currently hosted at https://creator.facings.io. You can see the details of our previous grant here: https://github.com/eosnetworkfoundation/grant-framework/blob/main/applications/facings-nft-collection-manager.md + + +**What your project is _not_ or will _not_ provide or implement** + +Stage 1 was designed to generate a proof of concept working feature set on which we are immediately following up with a Stage 2 grant proposal to maximize the use and effectiveness of the Collection Manager and add feature sets toward our goals of easy collection management and gamification. Our project will not include or promote NFT sales, token creation, token backing, or the staking of NFTs. No drops will be possible with Stage 2 of the project, aside from airdrops and basic transfers. + + +### Ecosystem Fit + +**Where and how does your project fit into the ecosystem?** + +The only NFT creator on EOS is AtomicHub, which is closed source and allows collection owners to publish NFTs. Our project will provide an open source solution for EOS that is easy to use. Another relevant project is NeftyBlocks; they have many advanced features but their UI is also closed-source and only available on WAX. Advancing NFTs, play & earn, and GameFi on EOS with an easy to use, functional collection manager fills a void in the EOS NFT ecosystem. + + +**Who is your target audience (chain/dapp/wallet/UI developers, designers, your own user base, some dapp's userbase, yourself)?** + +Our target audience consists of game developers, creators, and members of the EOS community and other Antelope chains. We aim to encourage members of other chains to create on EOS in the future. By leveling the playing field on EOS with improved tooling, there is a compelling argument for game producers and collection enthusiasts to develop and launch on EOS. + + +**What need(s) does your project meet?** + +The AtomicHub creator is a barebones UI integrating directly to a blockchain node, as well as their own internal IPFS node for file storage. It is available to everyone and anyone may publish without limits using their own resources. Nefty’s creator is much more complex with features like Pack Generation and Blending. However, neither of these platforms are open source. + +We have created an open-source NFT collection manager which is both fully functional on its own, and represents a reference implementation of the AtomicAssets standard across the Antelope ecosystem as an open-source alternative to the other two choices. On top of the core functionality, we are excited to enable advanced workflows and gamification with a plugin system. By leveraging the existing Atomic standard, anyone is able to produce feature rich NFTs and manage them seamlessly, creating a launchpad for gamification that can be a boon to the EOS network. EOS has the opportunity to be a big player in the gaming market which is struggling to find operating chains that fulfill all of the utility of blockchain with decentralized NFT ownership. The market is ripe to take the next step and EOS is poised to be the platform of choice. + + +**Are there any other projects similar to yours in the EOSIO ecosystem?** + +There are no viable open source projects meeting this need. + + +## Team + +### Team members + +- **Team Leader:** Rob Konsdorf (Robrigo), CEO +- Keir Kleinknecht (Banana), COO +- Roadscape, Software Engineer +- Felblob, Product Manager +- Marcelo Souza, UI Engineer +- Elton Ponglio, Product Designer +- Marcos Moreira, DevOps Engineer + + +### Legal Structure +- **Registered Legal Entity:** FACINGS, Inc. +- **Registered Address:** 1570 Woodward Ave. FL 3 Detroit, MI 48226 + +### Team Experience + +The FACINGS team brings multidisciplinary experience to the table. It is led by Rob Konsdorf, a co-founder of Detroit Ledger Technologies and blockchain technologist, and Keir Kleinknecht, a multi-technology, seasoned traditional exec and GameFi NFT analyst. The team has experience shipping software together, having created a “white-glove” NFT collection launch product and process responsible for shipping over 700,000 WAX NFTs for early collection partners, and generating over $500,000 in gross sales. Our research and first hand experience shipping in the NFT space makes us uniquely qualified to build tools to make the lives of NFT collection owners easier. + +Specific successes and experience from our team include the success of projects on Telos and WAX, including WAX Labs and the OIG Election portal, both led by Rob Konsdorf. Keir has run over 13 successful startup companies, been an executive Board member for 3 Public Companies and ran several VC firms with net assets over $300 MM. Roadscape our Sr Software Engineer developed interface products at Steemit Inc, including the site that would become hive.blog, as well as leading the project for a content scaling layer called Hivemind. Collectively our engineers bring a vast amount of experience to and from web3 and are poised to execute this project with efficiency. + +Recently, we completed and delivered the first stage of this project as an ENF grant on time and on budget. + + +### Team Org Repos + +- https://github.com/facings +- https://github.com/FACINGS/eospyo + +### Team Member Repos + +- https://github.com/robrigo +- https://drive.google.com/drive/folders/1OfEwjO_ho5QTB9dfrbjMk2IUPEZ6iq6m?usp=sharing +- https://github.com/roadscape +- https://github.com/felsin +- https://github.com/mr-souza +- https://github.com/pongilo +- https://github.com/mmoreirasantosdev + + +### Team LinkedIn Profiles (if available) + +- https://www.linkedin.com/in/robertkonsdorf/ +- https://www.linkedin.com/in/keirkleinknecht/ +- https://www.linkedin.com/in/mr-souza/ +- https://www.linkedin.com/in/marcos-moreira-51285b16/ + + +## Development Status + +We recently delivered Stage 1 of this project as an ENF grant and have been preparing for Stage 2 of development, having started research and preliminary design of the plugin system, and developing numerous UX and usability improvements, as well as progress on TypeScript implementation. + + +## Development Roadmap + + +### Milestone Summary + +- **Total Estimated Duration:** 4.5 months +- **Full-Time Equivalent (FTE):** 4 FTE +- **Total Costs:** 180,000 USD + + +### Milestone 1 — TypeScript, UX, and Plugins Core + +- **Estimated duration:** 2 months +- **FTE:** 4 +- **Costs:** 80,000 USD + +| Number | Deliverable | Specification | +| -----: | ----------- | ------------- | +| 0a. | License | GPLv3 | +| 0b. | Documentation | We will provide an updated ‘Getting Started’ guide and deployment instructions. We will document how to add, configure, and build new plugins. We will add a comprehensive User Guide. | +| 0c. | Testing Guide | (1) Two methods of quickly verifying completion of typescript migration; (2) walkthrough to test each new UI feature; (3) a step-by-step guide for adding a plugin | +| 0d. | Docker | We will provide a Dockerfile that can be used to launch a UI instance and test all the functionality delivered with this milestone. | +| 1. | TypeScript Implementation | Converting all components to TypeScript to improve maintainability and reliability. This has been requested by the EOS community. | +| 2. | UX Improvements | (1) Jungle4 EOS testnet support
(2) Airdrop - allow minting to multiple accounts
(3) Transfers - filter NFTs by name or collection
(4) Upgrade navigation / breadcrumbs and small screen optimization
(5) IPFS updates - manual address entry, previews, validation, view originals
(6) Metadata handling - new social links for collection, better defaults for schema, allow blank immutable fields, improved input validations | +| 3. | Plugin Architecture | Design and implement a client-side plugin framework which allows for added functionality at the collection level in the UI. The plugin system itself adds no external dependencies while increasing modularity and flexibility of the app. It also allows maintainers to inject functionality (and API integrations) while retaining a common core to contribute back to. | + + + +### Milestone 2 — Data Import Plugin + +- **Estimated Duration:** 1.5 months +- **FTE:** 4 +- **Costs:** 60,000 USD + +| Number | Deliverable | Specification | +| -----: | ----------- | ------------- | +| 0a. | License | GPLv3 | +| 0b. | Documentation | We will document the portable data standard used by the import system and provide usage instructions. | +| 0c. | Testing Guide | A testing script with sample data files will be provided to demonstrate usage of the import plugin; one sample will demonstate how validation failures are treated; the other will demonstate the success case. The test can be performed locally or via our hosted instance. | +| 0d. | Docker | We will provide a Dockerfile that can be used to launch a UI instance and test all the functionality delivered with this milestone. | +| 1. | Import Function | - Development of an AtomicAssets CSV standard
- Ability to import a CSV to create a schema and templates and submit the transactions in batches
- Minimal data validation to help detect user errors | +| 2. | Advanced Validation | - Improved validation results/reporting
- Data validation heuristics upon import: (a) Uniqueness; (b) Completeness; (c) Datatype optimization | + + +### Milestone 3 — Airdrop Plugin + +- **Estimated Duration:** 1 month +- **FTE:** 4 +- **Costs:** 40,000 USD + +| Number | Deliverable | Specification | +| -----: | ----------- | ------------- | +| 0a. | License | GPLv3 | +| 0b. | Documentation | We will provide an Airdrop guide with general usage instructions, as well as documentation of the Airdrop plugin itself. | +| 0c. | Testing Guide | A step-by-step script to demonstrate the airdrop functionality locally or via our hosted instance. | +| 0d. | Docker | We will provide a Dockerfile that can be used to launch a UI instance and test all the functionality delivered with this milestone. | +| 0e. | Article | We will publish an article describing the work we performed as part of the grant, introduce the plugin system, and highlight the new possibilities and sample plugins. | +| 1. | Airdrop Plugin Core | - Specify single & multiple recipients
- Specify drop assets by (a) minting a specific Template ID; or (b) transfer multiple Asset IDs
- Randomize recipients (i.e. mint numbers) using random.org
- Batch submits | +| 2. | Airdrop API Queries | Look-up Queries:
- everyone who has specific template
- everyone who doesn’t have specific templates within a collection
- everyone who has any item from a collection

Unique Queries:
- option to send single or multiple assets to matched accounts | + + +## Future Plans + +As indicated in the Development Status section, FACINGS set out to build a fully custodial NFT launchpad which serves as a bridge into web3 for brands, creators, and games looking to integrate NFTs into their product offerings. Our vision is to streamline access to tools for managing composable NFT use cases, and abstract away the complexity of tapping into them for entities that do not have a pre-existing knowledge of web3, or may not be technical in nature. In some cases with big firms, they may not have a policy for accounting for crypto even, making participation that requires holding and securing tokens difficult. + +The NFT Collection Manager is a stepping stone towards realizing that vision, setting the foundational elements of our content management experience for publishers, and making them available for all to use and build upon. + +Our goal is to create a platform that leverages EOS’s robustness and attracts gaming studios to a more simplistic and user friendly launch. We believe the integration of the creator UI with additional features down the road will be a very compelling choice, turning EOS into the premier gamification center, while maintaining excitement for other trends and collections. + +FACINGS envisions sustaining our business with a premium tier of features built on top of the open source core, with a usage-based business model (pay-as-you-publish). Premium features incorporated as plugins could include facilitation of sales, redeemable NFTs, composable crafting, and support for mint on demand and preminted packs. + +The integration of the plugin system further opens up this project to growth and contributions which can be leveraged by any fork or maintainer. By allowing new functionality to be added as encapsulated plugins, it becomes safer and simpler to create and share new features without requiring modifications to the core, nor new forks or diverging codebases. + +Future features that could also be valuable to prioritize work on includes integrating best-of-breed onboarding experiences, automatic collection microsite generation (configurable sales sites), enabling purchasers to pay for their own on-chain account with a credit card in the purchasing flow, and richer functionality to support the needs of NFT-integrated games including event triggers for mutable data. + + +## Additional Information + +**How did you hear about the Grants Program?** EOS Network Foundation Website / Medium / Twitter / Element / Announcement by another team / personal recommendation / etc. + +Robrigo has been following the ENF since its inception and saw the blog announcement for the grants framework. After brainstorming with the team, we crafted our initial proposal for this project. This proposal represents a continuation of the development started in stage 1. From 6564527698e0efd48c8b203cc183f5e6ff7cfc97 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Mon, 24 Apr 2023 10:52:26 -0400 Subject: [PATCH 091/170] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 777140bf..8029a889 100644 --- a/README.md +++ b/README.md @@ -15,7 +15,7 @@ The EOS Network Foundation (ENF) funds development grants for "Public Good" as w - + From 3fea4ee29268141991643b0ddd2555ee8d41f98b Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Mon, 24 Apr 2023 10:53:28 -0400 Subject: [PATCH 092/170] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 8029a889..e84336a6 100644 --- a/README.md +++ b/README.md @@ -24,7 +24,7 @@ The EOS Network Foundation (ENF) funds development grants for "Public Good" as w
 Individual / SmallTeam / MediumCompany / Large
AmountUp to $10,000Up to $50,000Over $50,000
AmountUp to $10,000Up to $50,000Up to $200,000
Requirements
  • No prior Pomelo grant required
  • Selection by Grant Committee
  • 2 Grant Evaluator approvals
Requirements
  • No prior Pomelo grant required
  • Selection by Grant Committee
  • 2 Grant Evaluator approvals
  • Prior Pomelo grant required
  • Selection by Grant Committee
  • 3 Grant Evaluator approvals
  • Special KYC process
  • Selection by Grant Committee
  • 4 Grant Evaluator approvals
  • Pitch Call
  • Grants > $100k - ENF Approval
  • Special KYC process
  • Selection by Grant Committee
  • 4 Grant Evaluator approvals
  • Prior Pomelo grant recommended
  • Grants > $100k - ENF Approval
Benefits
  • All benefits from Levels 1 and 2
  • Introductions to ENF Ventures VC partners*
-* ENF Ventures will be established at a future date in 2022. +* ENF Ventures will be established at a future date in 2023. ## Three Grant Types There are three types of grants that the ENF considers. Some are originated by the community itself, and some are proposed in the form of an RFP by the ENF. From 13daa8946527db3bfe26f17b1b8fd5b8ab671aa2 Mon Sep 17 00:00:00 2001 From: jdheeter Date: Tue, 25 Apr 2023 23:45:08 -0500 Subject: [PATCH 093/170] formatting --- applications/antelopeio_firewall.md | 165 ++++++++++++++-------------- 1 file changed, 83 insertions(+), 82 deletions(-) diff --git a/applications/antelopeio_firewall.md b/applications/antelopeio_firewall.md index 5ff600d3..13be491e 100644 --- a/applications/antelopeio_firewall.md +++ b/applications/antelopeio_firewall.md @@ -1,19 +1,19 @@ # EOS Network Foundation Grant Proposal -- **Project Name:** Antelope Firewall -- **Team Name:** Animus Labs LTD (representing Boid.com) -- **EOS Payment Address:** animus.inc -- **[Level](https://github.com/eosnetworkfoundation/grant-framework#grant-levels):** 2 -- **Pomelo Grant(s):** [Boid Universe](https://pomelo.io/grants/boiduniverse); [EOSPOWERUP.IO](https://pomelo.io/grants/eospowerupio); [EOSIOIBC](https://pomelo.io/grants/eosioibc) -- **Project is Open-Source:** Yes -- **Project was part of Token sale:** No -- **Repository where Project resides:** https://github.com/animuslabs +- **Project Name:** Antelope Firewall +- **Team Name:** Animus Labs LTD (representing Boid.com) +- **EOS Payment Address:** animus.inc +- **[Level](https://github.com/eosnetworkfoundation/grant-framework#grant-levels):** 2 +- **Pomelo Grant(s):** [Boid Universe](https://pomelo.io/grants/boiduniverse); [EOSPOWERUP.IO](https://pomelo.io/grants/eospowerupio); [EOSIOIBC](https://pomelo.io/grants/eosioibc) +- **Project is Open-Source:** Yes +- **Project was part of Token sale:** No +- **Repository where Project resides:** ## Contact -- **Contact Name:** John Heeter -- **Contact Email:** john@boid.com -- **Website:** https://www.animus.is +- **Contact Name:** John Heeter +- **Contact Email:** john@boid.com +- **Website:** ## Project Overview @@ -21,10 +21,10 @@ This is a proposal to build a firewall/proxy that would be used in an Antelope n ### Overview -- **Name:** Antelope Node Firewall -- **Brief Description:** Lower the barrier to entry for infrastructure providers to offer highly reliable public endpoints. -- **Relationship to EOSIO:** It's a layer on top of existing AntelopeIO API nodes. -- **Reason for Interest:** We want to solve common issues that API node operators have. +- **Name:** Antelope Node Firewall +- **Brief Description:** Lower the barrier to entry for infrastructure providers to offer highly reliable public endpoints. +- **Relationship to EOSIO:** It's a layer on top of existing AntelopeIO API nodes. +- **Reason for Interest:** We want to solve common issues that API node operators have. ### Project Details @@ -32,7 +32,7 @@ This is a proposal to build a firewall/proxy that would be used in an Antelope n Antelope Leap nodes are easily abused without proper network infrastructure. When nodes are abused by bots and malicious attackers, they become unreliable or unusable for normal users and create considerable strain on infrastructure providers. Therefore today only a small subset of public EOS nodes are usable in production. Based on our custom eospowerup.io proxy that rotates between APIs provided by the top 50 BPs we found that less than 10 are reliable and usable for production applications. #### Proposed Solution -We propose an application that would sit behind an existing firewall such as NGINX (or replace your firewall for more simple networks) and in front of a Nodeos API and/or p2p node. The application would monitor incoming transactions and queries to perform smart logic such as blocking, or prioritizing based on the node operator's preference. The purpose is to make running highly available RPC nodes more accessible to node operators and reduce the load on the Nodeos software. The advantage of this application vs a traditional firewall is that this application is aware of Antelope transaction and query structure and can apply complex filter logic that a traditional firewall isn’t designed for. +We propose an application that would sit behind an existing firewall such as NGINX (or replace your firewall for more simple networks) and in front of a Nodeos API and/or p2p node. The application would monitor incoming transactions and queries to perform smart logic such as blocking, or prioritizing based on the node operator's preference. The purpose is to make running highly available RPC nodes more accessible to node operators and reduce the load on the Nodeos software. The advantage of this application vs a traditional firewall is that this application is aware of Antelope transaction and query structure and can apply complex filter logic that a traditional firewall isn’t designed for. ![AntelopeIO_Firewall_Diagram](https://ipfs.animus.is/ipfs/QmZ3qEwAGuaboNYAypJdXtcGnofQX4yPrYhVStQnX5u8Vh?filename=diagram-antelope-firewall.jpg) @@ -52,12 +52,13 @@ The initial version of the application would be written in Rust and could be eas - **Automated Deployment** Scripts for deployment via Docker, Ansible, or bare metal will be provided, Anyone could launch a highly available and production ready Leap instance from scratch in less than 30 minutes with minimal configuration and maintenance. -#### **Future additions** +#### **Future additions** Once the base level application has reached a production ready state and iterated based on node operator feedback there are additional developments that could improve the application. - **Monetization** Node operators who offer public APIs often do so as a free service that operates at a loss. This makes it difficult for operators to sustain the hardware and manpower required for high-availability RPC nodes. A monetization feature could be added to the firewall that would allow users to pay to have their contract actions whitelisted for less rate-limiting. For example, an application developer may pay a node operator a subscription fee to whitelist their contract operations in order to ensure a smooth experience for their users. Monetization can be totally automated with a smart contract and basic logic integrated into the firewall. -#### **Feedback from node operators** +#### **Feedback from node operators** + - **EOSN** Sounds very useful if it could replace NGINX/HAProxy. Consider building in Golang instead of Typescript. Increased performance and improved interoperability with Dfuse/Firehose such as reading Firehose blocks to reply to get_block requests without blocks.log. - **GenerEOS** I read your proposal and think it would be a useful product that would help many node operators. @@ -70,33 +71,33 @@ Once the base level application has reached a production ready state and iterate Antelope Firewall can be an integral part of EOSIO/AntelopeIO ecosystem as an application firewall. -Node operators in the EOSIO/AntelopeIO ecosystem can create a better user experience for normal users and applications that rely on public infrastructure. +Node operators in the EOSIO/AntelopeIO ecosystem can create a better user experience for normal users and applications that rely on public infrastructure. Reducing the load on the Nodeos application will reduce infrastructure costs and improve RPC api reliability for common users. Additionally, this application would make it easy for application developers to host public nodes which throttle transactions and queries unrelated to their core application. #### Existing solutions -Running a reliable Leap RPC/P2P on EOS and other high-traffic Antelope chains requires advanced DevOps skills. Node operators are required to maintain a considerably complex network infrastructure to support such a service. Typically this involves multiple layers of specialized Leap Nodes that act as filters for transaction propagation. +Running a reliable Leap RPC/P2P on EOS and other high-traffic Antelope chains requires advanced DevOps skills. Node operators are required to maintain a considerably complex network infrastructure to support such a service. Typically this involves multiple layers of specialized Leap Nodes that act as filters for transaction propagation. -Existing EVM solutions: -- https://github.com/ethereum-optimism/optimism/tree/develop/proxyd -- https://github.com/emeraldpay/dshackle +Existing EVM solutions: +- +- ## Team ### Team members -- **Team Leader:** John Heeter - Founder @ Boid.com +- **Team Leader:** John Heeter - Founder @ Boid.com - Jowita Choscilowicz - Project Manager - John Heeter - Technical Lead / Development - Seth Choscilowicz - Development / DevOps ### Legal Structure -- **Registered Legal Entity:** Animus Labs LTD -- **Registered Address:** Hunkins Waterfront Plaza, Main Street, Charlestown, Nevis +- **Registered Legal Entity:** Animus Labs LTD +- **Registered Address:** Hunkins Waterfront Plaza, Main Street, Charlestown, Nevis ### Team Experience @@ -106,118 +107,118 @@ Seth Choscilowicz - blockchain dev ops 4 years eosio / systems engineer 14 years ### Team Org Repos -- https://github.com/boid-com -- https://github.com/animuslabs +- +- ### Team Member Repos -- https://github.com/jdheeter -- https://github.com/mchosc +- +- ### Team LinkedIn Profiles -- https://www.linkedin.com/in/johnheeter -- https://www.linkedin.com/in/mchosc -- https://www.linkedin.com/in/jchoscilowicz +- +- +- ## Development Status The Antelope Firewall project is in the phase of architecture analysis and design. The project has not begun development yet. -We have collected our current experience from various organizations for which we have worked and from different clients for whom we have implemented projects. Experiences and conclusions from work in WEB2 environments are reflected in WEB3 ecosystems and in our opinion it is worth using these experiences and ideas that have been verified by the WEB2 market. +We have collected our current experience from various organizations for which we have worked and from different clients for whom we have implemented projects. Experiences and conclusions from work in WEB2 environments are reflected in WEB3 ecosystems and in our opinion it is worth using these experiences and ideas that have been verified by the WEB2 market. We created the concept of an application firewall for EOS and collected feedback from public node operators to illustrate the problem: -1. **EOS USA** -- EOS: -api: 1.5mil/hr -hyp: 200/hr about 50/50% api response 200/500 +1. **EOS USA** + +- EOS: +api: 1.5mil/hr +hyp: 200/hr about 50/50% api response 200/500 failures ~100% failed push trx (500) -- WAX: -api: 150K/hr -hyp: 205K/hr 5% +- WAX: +api: 150K/hr +hyp: 205K/hr 5% failures (push trx) but it´s heavily rate limited, response 50x abusers -- Proton: -api: 1.4mil/hr -hyp: 1500/hr about 50/50% api response 200/500 +- Proton: +api: 1.4mil/hr +hyp: 1500/hr about 50/50% api response 200/500 failures ~100% failed push trx (500) -- 1mil/hr blocked non-routable by proxy (no valid host headers for nodes) +- 1mil/hr blocked non-routable by proxy (no valid host headers for nodes) - 117K/hr blocked at firewall for known abusive IP ranges -2. **EOS Nation** +2. **EOS Nation** 20% failure rate, relying on Fail2Ban to prevent most bad queries/trx from reaching nodes, estimated 10x failure rate without Fail2Ban. -3. **Greymass** +3. **Greymass** 50-100 failed transactions per second reach Leap instances, multitudes more are caught by firewalls/rate limiters. -4. **Boid BP** +4. **Boid BP** Global API stats on EOS / Telos Mainnet / Telos Testnet / Hyperion / Hyperion Testnet about 1 mln per hour with spikes of 6k per second with automatic block of miners on EOS Mainnet 15% failure rate -5. **GenerEOS** +5. **GenerEOS** We use a combination of things in terms of firewall including nginx rate limits, Fail2ban, and for some chains also caching. I know that our APIs and p2p still get hammered and often are not usable. -6. **EOSphere** +6. **EOSphere** On EOS we have a 43% transaction failure rate. We successfully process 300k EOS Transactions / hour. We fail 230k EOS Transactions / hour. Most of the failures are push transactions. 13.1Mil Successful EOS Actions / Transactions per day. Our WAX infra is over 30Mil Successful Actions / Transactions per day. -7. **EOS Amsterdam** -Approximately 90%+ transactions that make it through our existing rate-limiting solutions result in failures. Currently using: https://gist.github.com/cc32d9/2466e15c14882b2d696415f6c2777954 +7. **EOS Amsterdam** +Approximately 90%+ transactions that make it through our existing rate-limiting solutions result in failures. Currently using: -The application firewall turns out to be a natural element that should be an integral part of the EOSIO system. +The application firewall turns out to be a natural element that should be an integral part of the EOSIO system. ## Development Roadmap ### Overview -- **Total estimated duration:** 6 months -- **Full-Time Equivalent (FTE):** 2-2.5 -- **Total Costs:** 50,000 USD - +- **Total estimated duration:** 6 months +- **Full-Time Equivalent (FTE):** 2-2.5 +- **Total Costs:** 50,000 USD ### Milestone 1 — Create Antelope Firewall Prototype -- **Estimated duration:** 5 weeks -- **FTE:** 2.5 -- **Costs:** 10,000 USD +- **Estimated duration:** 5 weeks +- **FTE:** 2.5 +- **Costs:** 10,000 USD -| ID | Deliverable | Specification | -| ----- | ----------- | ------------- | -| 0a. | License | MIT | +| ID | Deliverable | Specification | +| --- | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 0a. | License | MIT | | 0b. | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how to configure and run, including technical draft: short document will act as an overview of the technical implementation details as part of the development planning stage. Will guide code structure and development milestones. | -| 0c. | Deployment | We will provide a Prototype with a limited basic functionalities implemented. For example the firewall will be able to route queries to nodes and return responses with basic blacklisting functionality. | +| 0c. | Deployment | We will provide a Prototype with a limited basic functionalities implemented. For example the firewall will be able to route queries to nodes and return responses with basic blacklisting functionality. | ### Milestone 2 — Implement Antelope Firewall MVP version -- **Estimated Duration:** 10 weeks -- **FTE:** 2 -- **Costs:** 17,000 USD +- **Estimated Duration:** 10 weeks +- **FTE:** 2 +- **Costs:** 17,000 USD -| ID | Deliverable | Specification | -| ----- | ----------- | ------------- | -| 0a. | License | MIT | -| 0b. | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how to configure and run Alpha and Beta version (MVP). | -| 0c. | Deployment Alpha | We will provide a Alpha version with a major features implemented in a basic way. We will begin running on our own nodes. | +| ID | Deliverable | Specification | +| --- | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 0a. | License | MIT | +| 0b. | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how to configure and run Alpha and Beta version (MVP). | +| 0c. | Deployment Alpha | We will provide a Alpha version with a major features implemented in a basic way. We will begin running on our own nodes. | | 0d. | Deployment Beta (MVP) | We will provide a Beta version (MVP) with all features implemented in a basic way. The app should be ready to distribute to external infra providers for feedback and testing. HTTP RPC and P2P Functionality | ### Milestone 3 — Implement Antelope Firewall 1.0 version -- **Estimated Duration:** 14 weeks -- **FTE:** 2 -- **Costs:** 23,000 USD +- **Estimated Duration:** 14 weeks +- **FTE:** 2 +- **Costs:** 23,000 USD -| ID | Deliverable | Specification | -| ----- | ----------- | ------------- | -| 0a. | License | MIT | +| ID | Deliverable | Specification | +| --- | ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 0a. | License | MIT | | 0b. | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how to configure and run Antelope Firewall 1.0 version, which covers all of the application functionality and configuration. Also we will create deployment scripts for various platforms to simplify the process of getting started. | -| 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. | Deployment | We will provide an Antelope Firewall 1.0 version - production ready solution, based on feedback from infra providers and issues discovered during beta testing. HTTP RPC and P2P Functionality | -| 0e. | Article | We will publish an **article** that explains what are the features of the product, how does it work and what was achieved as part of the grant. | +| 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. | Deployment | We will provide an Antelope Firewall 1.0 version - production ready solution, based on feedback from infra providers and issues discovered during beta testing. HTTP RPC and P2P Functionality | +| 0e. | Article | We will publish an **article** that explains what are the features of the product, how does it work and what was achieved as part of the grant. | ## Future Plans -The Antelope Firewall probably will be useful for EOS node operators, ensuring a high level of security. +The Antelope Firewall probably will be useful for EOS node operators, ensuring a high level of security. We plan to offer a solution to active block producers, in the first place to everyone we've talked to so far: EOS USA, EOS Nation, Greymass, Boid BP, GenerEOS, EOSphere, EOS Amsterdam. We assume that we will reach 30 block producers within the first 3 months from the release of version 1.0. The next step in the coming months will be reaching out to other EOS block producers. From 4b2ef5fb8c41c8b04c251692749fa73ee3b6c7e7 Mon Sep 17 00:00:00 2001 From: jdheeter Date: Wed, 26 Apr 2023 00:10:24 -0500 Subject: [PATCH 094/170] additional details --- applications/antelopeio_firewall.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/applications/antelopeio_firewall.md b/applications/antelopeio_firewall.md index 13be491e..1bf03697 100644 --- a/applications/antelopeio_firewall.md +++ b/applications/antelopeio_firewall.md @@ -4,7 +4,7 @@ - **Team Name:** Animus Labs LTD (representing Boid.com) - **EOS Payment Address:** animus.inc - **[Level](https://github.com/eosnetworkfoundation/grant-framework#grant-levels):** 2 -- **Pomelo Grant(s):** [Boid Universe](https://pomelo.io/grants/boiduniverse); [EOSPOWERUP.IO](https://pomelo.io/grants/eospowerupio); [EOSIOIBC](https://pomelo.io/grants/eosioibc) + - **Project is Open-Source:** Yes - **Project was part of Token sale:** No - **Repository where Project resides:** @@ -32,7 +32,7 @@ This is a proposal to build a firewall/proxy that would be used in an Antelope n Antelope Leap nodes are easily abused without proper network infrastructure. When nodes are abused by bots and malicious attackers, they become unreliable or unusable for normal users and create considerable strain on infrastructure providers. Therefore today only a small subset of public EOS nodes are usable in production. Based on our custom eospowerup.io proxy that rotates between APIs provided by the top 50 BPs we found that less than 10 are reliable and usable for production applications. #### Proposed Solution -We propose an application that would sit behind an existing firewall such as NGINX (or replace your firewall for more simple networks) and in front of a Nodeos API and/or p2p node. The application would monitor incoming transactions and queries to perform smart logic such as blocking, or prioritizing based on the node operator's preference. The purpose is to make running highly available RPC nodes more accessible to node operators and reduce the load on the Nodeos software. The advantage of this application vs a traditional firewall is that this application is aware of Antelope transaction and query structure and can apply complex filter logic that a traditional firewall isn’t designed for. +We propose an application that would sit behind an existing firewall such as NGINX (or replace your firewall for more simple networks) and in front of a Nodeos API node. The application would monitor incoming transactions and queries to perform smart logic such as blocking, or prioritizing based on the node operator's preference. The purpose is to make running highly available RPC nodes more accessible to node operators and reduce the load on the Nodeos software. The advantage of this application vs a traditional firewall is that this application is aware of Antelope transaction and query structure and can apply complex filter logic that a traditional firewall isn’t designed for. ![AntelopeIO_Firewall_Diagram](https://ipfs.animus.is/ipfs/QmZ3qEwAGuaboNYAypJdXtcGnofQX4yPrYhVStQnX5u8Vh?filename=diagram-antelope-firewall.jpg) @@ -78,7 +78,7 @@ Reducing the load on the Nodeos application will reduce infrastructure costs and Additionally, this application would make it easy for application developers to host public nodes which throttle transactions and queries unrelated to their core application. #### Existing solutions -Running a reliable Leap RPC/P2P on EOS and other high-traffic Antelope chains requires advanced DevOps skills. Node operators are required to maintain a considerably complex network infrastructure to support such a service. Typically this involves multiple layers of specialized Leap Nodes that act as filters for transaction propagation. +Running a reliable Leap RPC on EOS and other high-traffic Antelope chains requires advanced DevOps skills. Node operators are required to maintain a considerably complex network infrastructure to support such a service. Typically this involves multiple layers of specialized Leap Nodes that act as filters for transaction propagation. Existing EVM solutions: @@ -199,8 +199,8 @@ The application firewall turns out to be a natural element that should be an int | --- | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 0a. | License | MIT | | 0b. | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how to configure and run Alpha and Beta version (MVP). | -| 0c. | Deployment Alpha | We will provide a Alpha version with a major features implemented in a basic way. We will begin running on our own nodes. | -| 0d. | Deployment Beta (MVP) | We will provide a Beta version (MVP) with all features implemented in a basic way. The app should be ready to distribute to external infra providers for feedback and testing. HTTP RPC and P2P Functionality | +| 0c. | Deployment Alpha | We will provide a Alpha version with a major features implemented in a basic way. We will begin running on our own nodes. Our goal is to implement blacklisting, round-robin routing and special rules-based transaction handling logic. | +| 0d. | Deployment Beta (MVP) | We will provide a Beta version (MVP) with all features implemented in a basic way. The app should be ready to distribute to external infra providers for feedback and testing of the HTTP RPC functionality. This release will include improvements of functionality implemented in the Alpha. Additionally this release will include statistics and monitoring endpoints for prometheus. Additionally this release will include contract and account prioritization functionality, for example queries for certain contract tables could be rate-limited at a different rate. | ### Milestone 3 — Implement Antelope Firewall 1.0 version @@ -213,12 +213,12 @@ The application firewall turns out to be a natural element that should be an int | 0a. | License | MIT | | 0b. | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how to configure and run Antelope Firewall 1.0 version, which covers all of the application functionality and configuration. Also we will create deployment scripts for various platforms to simplify the process of getting started. | | 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. | Deployment | We will provide an Antelope Firewall 1.0 version - production ready solution, based on feedback from infra providers and issues discovered during beta testing. HTTP RPC and P2P Functionality | +| 0d. | Deployment | We will provide an Antelope Firewall 1.0 version - production ready solution, based on feedback from infra providers and issues discovered during beta testing. The focus of this release is improving features from the Beta and we may add additional configuration or functionality based on beta testing feedback from infra providers. | | 0e. | Article | We will publish an **article** that explains what are the features of the product, how does it work and what was achieved as part of the grant. | ## Future Plans -The Antelope Firewall probably will be useful for EOS node operators, ensuring a high level of security. +The Antelope Firewall will be useful for EOS node operators, ensuring a high level of security. We plan to offer a solution to active block producers, in the first place to everyone we've talked to so far: EOS USA, EOS Nation, Greymass, Boid BP, GenerEOS, EOSphere, EOS Amsterdam. We assume that we will reach 30 block producers within the first 3 months from the release of version 1.0. The next step in the coming months will be reaching out to other EOS block producers. From 1bd14c4f2e33df9966550679dc4ef279eff9cb65 Mon Sep 17 00:00:00 2001 From: Nathan James Date: Fri, 28 Apr 2023 05:06:01 -0700 Subject: [PATCH 095/170] Clarifying expectations and intention of application grants (#177) --- .gitignore | 15 +++++++++++++++ README.md | 27 ++++++++++++++++++++++++--- 2 files changed, 39 insertions(+), 3 deletions(-) create mode 100644 .gitignore diff --git a/.gitignore b/.gitignore new file mode 100644 index 00000000..9db11748 --- /dev/null +++ b/.gitignore @@ -0,0 +1,15 @@ +# VSCode +.vscode/* +!.vscode/settings.json +!.vscode/tasks.json +!.vscode/launch.json +!.vscode/extensions.json +*.code-workspace +# Local History for Visual Studio Code +.history/ + + # Jetbrains +.idea/ +*.iml +*.iws +*.ipr diff --git a/README.md b/README.md index e84336a6..dc1ec28a 100644 --- a/README.md +++ b/README.md @@ -27,13 +27,34 @@ The EOS Network Foundation (ENF) funds development grants for "Public Good" as w * ENF Ventures will be established at a future date in 2023. ## Three Grant Types -There are three types of grants that the ENF considers. Some are originated by the community itself, and some are proposed in the form of an RFP by the ENF. +There are three types of grants that the ENF considers. Some are originated by the community itself, and some are +proposed in the form of an RFP by the ENF. + ### 1. New Proposal -Most grant applications will take the form of a "New Proposal" from a member of the EOS community. These projects range from core chain enhancements, SDKs, tools, and applications. These are initiated by members of the community and run through the standard [Grant Process](#grant-process) below. You may also want to look at the [list of approved applications](docs/accepted_grant_applications.md). +Most grant applications will take the form of a "New Proposal" from a member of the EOS community. +These projects range from core chain enhancements, SDKs, tools, and applications. These are initiated by members of the +community and run through the standard [Grant Process](#grant-process) below. + +> ⚠ **Grants are meant to kickstart your project, not sustain it** +> +> Our grant program is designed to provide initial support to projects so that they can become self-sustaining. +> We do not provide long-term funding, and if a project fails to become self-sustaining after reaching the minimum +> viable product (MVP) stage, we may consider it uninteresting to the wider community and stop approving grants for it. +> +> This rule does not apply to grants that focus on components that should not have a business model, +> such as core chain enhancements, developer tooling, and so on. Those will always be evaluated based on the value +> they bring to the community they are targeted at. + ### 2. Maintenance Grant -Maintenance grants are also initiated by the community to bring back support for a library, SDK or tool that has fallen out of maintenance. These proposals are more limited in scope and milestone to ensure proper progress is made. Maintenance grants should not be used to add feature or functionality to existing code, but to bring it up to current levels of the chain, operating system, or programming language levels. New functionality to existing projects can be applied via a "New Proposal". Read more about [Maintenance Grants](docs/maintenance-grants.md). +Maintenance grants are also initiated by the community to bring back support for a library, SDK or tool that has fallen +out of maintenance. These proposals are more limited in scope and milestone to ensure proper progress is made. +Maintenance grants should not be used to add feature or functionality to existing code, but to bring it up to current +levels of the chain, operating system, or programming language levels. New functionality to existing projects can be +applied via a "New Proposal". Read more about [Maintenance Grants](docs/maintenance-grants.md). + ### 3. RFP Response From time to time, the ENF will propose a work request to the community in the form of an RFP. All community members, teams and companies are welcome to reply to the RFP. Responses from multiple teams are expected. The ENF will then select the best RFP response and award the work to the team that submitted it. [Read more on RFPs and how to reply to them](docs/rfp_info.md). +

## Grant Process (for New Proposals) From 656ce4deaece85d604f898d46bb03698f1e5132a Mon Sep 17 00:00:00 2001 From: Lilbansheemebe <106165820+Lilbansheemebe@users.noreply.github.com> Date: Mon, 8 May 2023 12:24:24 -0400 Subject: [PATCH 096/170] Create am-big-sheet.yml --- .github/workflows/am-big-sheet.yml | 78 ++++++++++++++++++++++++++++++ 1 file changed, 78 insertions(+) create mode 100644 .github/workflows/am-big-sheet.yml diff --git a/.github/workflows/am-big-sheet.yml b/.github/workflows/am-big-sheet.yml new file mode 100644 index 00000000..60b5282d --- /dev/null +++ b/.github/workflows/am-big-sheet.yml @@ -0,0 +1,78 @@ +name: Reusable Gsheet Update +on: + workflow_call: + inputs: + project_name: + required: true + type: string + contact_name: + required: true + type: string + team_name: + required: true + type: string + app_email: + required: true + type: string + total_cost: + required: true + type: string + legal_entity: + required: true + type: string + legal_addr: + required: true + type: string + level: + required: true + type: string + eos_addr: + required: true + type: string + github_actor: + required: true + type: string + pr_no: + required: true + type: string + website: + required: true + type: string + open_source: + required: true + type: string + token_sale: + required: true + type: string + basename: + required: true + type: string + + secrets: + gsheet_private_key: + required: true + +jobs: + appendrow: + runs-on: ubuntu-latest + steps: + - id: 'update_worksheet' + uses: jroehl/gsheet.action@v1.2.0 + with: + spreadsheetId: 128L-4NQpOT0f2MLRcd5NiNAMsxS_Y1XGqFRXnyxtfLk + commands: | + [ + { "command": "appendData", "args": { "data": [["${{ inputs.pr_no }}", "${{ inputs.project_name }}", + "${{ inputs.team_name }}", + "${{ inputs.open_source }}", "${{ inputs.token_sale }}", + "${{ inputs.level }}", "${{ inputs.total_cost }}", + "${{ inputs.eos_addr }}", + "${{ inputs.github_actor }}", + "${{ inputs.website }}", "${{ inputs.basename }}", + "${{ inputs.contact_name }}", "${{ inputs.app_email }}", + "${{ inputs.legal_entity }}", "${{ inputs.legal_addr }}" + ]], "worksheetTitle": "GrantInfo", "minCol": 1 }} + ] + env: + GSHEET_CLIENT_EMAIL: enf-grant-service-account@sonorous-haven-350712.iam.gserviceaccount.com + GSHEET_PRIVATE_KEY: ${{ secrets.gsheet_private_key }} From 9e84490000a6fdeffaa67c39b51697bf64c0be4f Mon Sep 17 00:00:00 2001 From: Lilbansheemebe <106165820+Lilbansheemebe@users.noreply.github.com> Date: Mon, 8 May 2023 12:28:50 -0400 Subject: [PATCH 097/170] Create am-big-parser --- .github/workflows/am-big-parser | 110 ++++++++++++++++++++++++++++++++ 1 file changed, 110 insertions(+) create mode 100644 .github/workflows/am-big-parser diff --git a/.github/workflows/am-big-parser b/.github/workflows/am-big-parser new file mode 100644 index 00000000..490f245f --- /dev/null +++ b/.github/workflows/am-big-parser @@ -0,0 +1,110 @@ +# Parse the ENF Grant Framework Application and return the important parts +# Alysha Mims modified copy of - Ted Cahall 25May2022 - +# 30June2022 modified to scrape more fields. +# 12Nov2022 - Added more fields for the Big Scrape and made a new file from old one +# File may be called from a PR or with a filename passed in (not associated with a PR) +# +name: Reusable "Big" Application Parser +on: + workflow_call: + inputs: + filename: + required: true + type: string + outputs: + app_email: + value: ${{ jobs.parse.outputs.app_email }} + contact_name: + value: ${{ jobs.parse.outputs.contact_name }} + project_name: + value: ${{ jobs.parse.outputs.project_name }} + team_name: + value: ${{ jobs.parse.outputs.team_name }} + total_cost: + value: ${{ jobs.parse.outputs.total_cost }} + legal_entity: + value: ${{ jobs.parse.outputs.legal_entity }} + legal_addr: + value: ${{ jobs.parse.outputs.legal_addr }} + level: + value: ${{ jobs.parse.outputs.level }} + eos_addr: + value: ${{ jobs.parse.outputs.eos_addr }} + repo_owner: + value: ${{ jobs.parse.outputs.repo_owner }} + github_actor: + value: ${{ jobs.parse.outputs.github_actor }} + pr_no: + value: ${{ jobs.parse.outputs.pr_no }} + website: + value: ${{ jobs.parse.outputs.website }} + open_source: + value: ${{ jobs.parse.outputs.open_source }} + token_sale: + value: ${{ jobs.parse.outputs.token_sale }} + basename: + value: ${{ jobs.parse.outputs.basename }} + +jobs: + parse: + #if: inputs.filename + runs-on: ubuntu-latest + outputs: + app_email: ${{ steps.grep_appl.outputs.email_addr }} + contact_name: ${{ steps.grep_appl.outputs.contact_name }} + project_name: ${{ steps.grep_appl.outputs.project_name }} + team_name: ${{ steps.grep_appl.outputs.team_name }} + total_cost: ${{ steps.grep_appl.outputs.total_cost }} + legal_entity: ${{ steps.grep_appl.outputs.legal_entity }} + legal_addr: ${{ steps.grep_appl.outputs.legal_addr }} + level: ${{ steps.grep_appl.outputs.level }} + eos_addr: ${{ steps.grep_appl.outputs.eos_addr }} + basename: ${{ steps.grep_appl.outputs.basename }} + github_actor: ${{ steps.grep_appl.outputs.github_actor }} + pr_no: ${{ steps.grep_appl.outputs.pr_no }} + website: ${{ steps.grep_appl.outputs.website }} + open_source: ${{ steps.grep_appl.outputs.open_source }} + token_sale: ${{ steps.grep_appl.outputs.token_sale }} + + steps: + - name: Checkout + id: checkout + uses: actions/checkout@v3 + with: + ref: ${{ github.event.pull_request.head.sha }} + + # Parse the application template for the required fields + - name: assign the env variables from the parsing + id: grep_appl + run: | + export APP_EMAIL=`/bin/grep -F "**Contact Email:**" ${{ inputs.filename }} | tr -s " " | cut -d" " -f4` + echo "email_addr=$APP_EMAIL" >> $GITHUB_OUTPUT + export CNAME=`/bin/grep -F "**Contact Name:**" ${{ inputs.filename }} | tr -s " " | cut -d" " -f4-8` + echo "contact_name=$CNAME" >> $GITHUB_OUTPUT + export PNAME=`/bin/grep -F "**Project Name:**" ${{ inputs.filename }} | tr -s " " | cut -d" " -f4-10` + echo "project_name=$PNAME" >> $GITHUB_OUTPUT + export TNAME=`/bin/grep -F "**Team Name:**" ${{ inputs.filename }} | tr -s " " | cut -d" " -f4-10` + echo "team_name=$TNAME" >> $GITHUB_OUTPUT + export TCOST=`/bin/grep -F "**Total Costs:**" ${{ inputs.filename }} | tr -s " " | cut -d" " -f4-8` + echo "total_cost=$TCOST" >> $GITHUB_OUTPUT + export LENTITY=`/bin/grep -F "**Registered Legal Entity:**" ${{ inputs.filename }} | tr -s " " | cut -d" " -f5-12` + echo "legal_entity=$LENTITY" >> $GITHUB_OUTPUT + export LADDR=`/bin/grep -F "**Registered Address:**" ${{ inputs.filename }} | tr -s " " | cut -d" " -f4-30` + echo "legal_addr=$LADDR" >> $GITHUB_OUTPUT + export LEVEL=`/bin/grep -F "**[Level](https" ${{ inputs.filename }} | tr -s " " | cut -d" " -f3-8` + echo "level=$LEVEL" >> $GITHUB_OUTPUT + export EOSADDR=`/bin/grep -F "**EOS Payment Address:**" ${{ inputs.filename }} | tr -s " " | cut -d" " -f5-8` + echo "eos_addr=$EOSADDR" >> $GITHUB_OUTPUT + export WEBSITE=`/bin/grep -F "**Website:**" ${{ inputs.filename }} | tr -s " " | cut -d" " -f3-8` + echo "website=$WEBSITE" >> $GITHUB_OUTPUT + export OPENSOURCE=`/bin/grep -F "**Project is Open-Source:**" ${{ inputs.filename }} | tr -s " " | cut -d" " -f5` + echo "open_Source=$OPENSOURCE" >> $GITHUB_OUTPUT + export TOKENSALE=`/bin/grep -F "**Project was part of Token sale:**" ${{ inputs.filename }} | tr -s " " | cut -d" " -f8` + echo "token_sale=$TOKENSALE" >> $GITHUB_OUTPUT + # following three only work when parser launched by a pull request + echo "repo_owner=${{ github.event.pull_request.head.repo.owner.login }}" >> $GITHUB_OUTPUT + echo "pr_no=${{ github.event.pull_request.number }}" >> $GITHUB_OUTPUT + echo "github_actor=${{ github.actor }}" >> $GITHUB_OUTPUT + export BASENAME=`/bin/echo ${{ inputs.filename }} | cut -d"/" -f2` + echo "basename=$BASENAME" >> $GITHUB_OUTPUT + echo $BASENAME From 63ef439d15dd7310d724cde55f11b672b5bfb40a Mon Sep 17 00:00:00 2001 From: Lilbansheemebe <106165820+Lilbansheemebe@users.noreply.github.com> Date: Mon, 8 May 2023 12:32:45 -0400 Subject: [PATCH 098/170] Rename am-big-parser to am-big-parser.yml --- .github/workflows/{am-big-parser => am-big-parser.yml} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename .github/workflows/{am-big-parser => am-big-parser.yml} (100%) diff --git a/.github/workflows/am-big-parser b/.github/workflows/am-big-parser.yml similarity index 100% rename from .github/workflows/am-big-parser rename to .github/workflows/am-big-parser.yml From 38149dde7b4652cce31893652912b7690e0b267b Mon Sep 17 00:00:00 2001 From: Lilbansheemebe <106165820+Lilbansheemebe@users.noreply.github.com> Date: Mon, 8 May 2023 12:33:39 -0400 Subject: [PATCH 099/170] Create am-scrape-appfile.yml --- .github/workflows/am-scrape-appfile.yml | 78 +++++++++++++++++++++++++ 1 file changed, 78 insertions(+) create mode 100644 .github/workflows/am-scrape-appfile.yml diff --git a/.github/workflows/am-scrape-appfile.yml b/.github/workflows/am-scrape-appfile.yml new file mode 100644 index 00000000..e804bcd8 --- /dev/null +++ b/.github/workflows/am-scrape-appfile.yml @@ -0,0 +1,78 @@ +# Scrape application file to the "DataBigScrape" spreadsheet +# Alysha Mims copy of Ted Cahall 12Nov2022 +# + +name: Scrape Application to Gsheet + +on: + workflow_dispatch: + inputs: + AppFile: + type: string + description: Name of Application File + +jobs: + build: + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v3 + + - name: greet + id: test_echo + run: | + echo "Application file is: ${{ github.event.inputs.AppFile }}" + export APP_EMAIL=`/bin/grep "**Contact Email:**" "applications/${{ github.event.inputs.AppFile }}" | cut -d" " -f4` + echo "email_addr=$APP_EMAIL" >> $GITHUB_OUTPUT + echo email addr is $APP_EMAIL + - name: test_output + run: echo "the new output test shows the email_addr is ${{ steps.test_echo.outputs.email_addr }}" + + call-parser: + uses: ./.github/workflows/am-big-parser.yml + with: + filename: "applications/${{ github.event.inputs.AppFile }}" + needs: build + + echo-the-returned-fields: + runs-on: ubuntu-latest + needs: call-parser + steps: + - id: echo-output + run: | + echo "basename ${{ needs.call-parser.outputs.basename }} " + echo "project name ${{ needs.call-parser.outputs.project_name }} " + echo "contact name ${{ needs.call-parser.outputs.contact_name }}" + echo "team name ${{ needs.call-parser.outputs.team_name }}" + echo "app_email ${{ needs.call-parser.outputs.app_email }}" + echo "total cost ${{ needs.call-parser.outputs.total_cost }}" + echo "legal entity ${{ needs.call-parser.outputs.legal_entity }}" + echo "legal addr ${{ needs.call-parser.outputs.legal_addr }}" + echo "level ${{ needs.call-parser.outputs.level }}" + echo "eos_addr ${{ needs.call-parser.outputs.eos_addr }}" + echo "github_actor ${{ needs.call-parser.outputs.github_actor }}" + echo "pr_no ${{ needs.call-parser.outputs.pr_no }}" + echo "website ${{ needs.call-parser.outputs.website }}" + echo "open_source ${{ needs.call-parser.outputs.open_source }}" + echo "token_sale ${{ needs.call-parser.outputs.token_sale }}" + write-spreadsheet: + uses: ./.github/workflows/am-big-gsheet.yml + needs: call-parser + with: + project_name: ${{ needs.call-parser.outputs.project_name }} + contact_name: ${{ needs.call-parser.outputs.contact_name }} + team_name: ${{ needs.call-parser.outputs.team_name }} + app_email: ${{ needs.call-parser.outputs.app_email }} + total_cost: ${{ needs.call-parser.outputs.total_cost }} + legal_entity: ${{ needs.call-parser.outputs.legal_entity }} + legal_addr: ${{ needs.call-parser.outputs.legal_addr }} + level: ${{ needs.call-parser.outputs.level }} + eos_addr: ${{ needs.call-parser.outputs.eos_addr }} + github_actor: ${{ needs.call-parser.outputs.github_actor }} + pr_no: ${{ needs.call-parser.outputs.pr_no }} + website: ${{ needs.call-parser.outputs.website }} + open_source: ${{ needs.call-parser.outputs.open_source }} + token_sale: ${{ needs.call-parser.outputs.token_sale }} + basename: ${{ needs.call-parser.outputs.basename }} + secrets: + gsheet_private_key: ${{ secrets.GHSEET_API_KEY }} From f3a0542dcf3e25c8d1851274ba7c5d70a90dfd8f Mon Sep 17 00:00:00 2001 From: Lilbansheemebe <106165820+Lilbansheemebe@users.noreply.github.com> Date: Mon, 8 May 2023 12:35:52 -0400 Subject: [PATCH 100/170] Rename am-big-sheet.yml to am-big-gsheet.yml --- .github/workflows/{am-big-sheet.yml => am-big-gsheet.yml} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename .github/workflows/{am-big-sheet.yml => am-big-gsheet.yml} (100%) diff --git a/.github/workflows/am-big-sheet.yml b/.github/workflows/am-big-gsheet.yml similarity index 100% rename from .github/workflows/am-big-sheet.yml rename to .github/workflows/am-big-gsheet.yml From 433d6632884b4238cb2d1f873d1c69f0b1042b7b Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Mon, 8 May 2023 20:37:50 -0400 Subject: [PATCH 101/170] Update am-scrape-appfile.yml --- .github/workflows/am-scrape-appfile.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/am-scrape-appfile.yml b/.github/workflows/am-scrape-appfile.yml index e804bcd8..7e8a262f 100644 --- a/.github/workflows/am-scrape-appfile.yml +++ b/.github/workflows/am-scrape-appfile.yml @@ -2,7 +2,7 @@ # Alysha Mims copy of Ted Cahall 12Nov2022 # -name: Scrape Application to Gsheet +name: AM Scrape Application to Gsheet on: workflow_dispatch: From 8d33ba9ecd61ddc0357e05e64d3562f230622e3e Mon Sep 17 00:00:00 2001 From: ABurton22 <114498504+ABurton22@users.noreply.github.com> Date: Mon, 15 May 2023 08:36:54 -0400 Subject: [PATCH 102/170] README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index dc1ec28a..b0185899 100644 --- a/README.md +++ b/README.md @@ -1,7 +1,7 @@ # EOS Network Foundation Grant Framework -As part of the EOS Network Foundation's (ENF) charter to grow and support the EOS ecosystem, the ENF has developed a multi-level grant program to help power research, software development, and maintenance of the [Antelope](https://antelope.io/) code base. For more information about the ENF, please visit our [website](https://eosnetwork.com/) or [YouTube account](https://www.youtube.com/c/EverythingEOS). +As part of the EOS Network Foundation's (ENF) charter to grow and support the EOS ecosystem, the ENF has developed a multi-level grant program to help power research, software development, and maintenance of the [Antelope](https://antelope.io/) code base. For more information about the ENF, please visit our [website]([https://eosnetwork.com/](https://eosnetwork.com/funding/)) or [YouTube account](https://www.youtube.com/c/EverythingEOS). ## Grant Guidelines Individuals, small teams, and companies are all permitted to apply for grants. The purpose of the grants is to enable developers, businesses and individuals to build on EOS. Grants [vary in size](#grant-levels) based on the size and scope of the initiative. All forms of projects are open for submission, core chain modifications, tools, libraries, etc. as long as they are fully open-source. Strong technical projects that clearly add to the Public Good are preferred. From 09f34d5339dedc44125032a2b9240821b9396b7b Mon Sep 17 00:00:00 2001 From: ABurton22 <114498504+ABurton22@users.noreply.github.com> Date: Mon, 15 May 2023 08:38:17 -0400 Subject: [PATCH 103/170] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index b0185899..d5f5594b 100644 --- a/README.md +++ b/README.md @@ -1,7 +1,7 @@ # EOS Network Foundation Grant Framework -As part of the EOS Network Foundation's (ENF) charter to grow and support the EOS ecosystem, the ENF has developed a multi-level grant program to help power research, software development, and maintenance of the [Antelope](https://antelope.io/) code base. For more information about the ENF, please visit our [website]([https://eosnetwork.com/](https://eosnetwork.com/funding/)) or [YouTube account](https://www.youtube.com/c/EverythingEOS). +As part of the EOS Network Foundation's (ENF) charter to grow and support the EOS ecosystem, the ENF has developed a multi-level grant program to help power research, software development, and maintenance of the [Antelope](https://antelope.io/) code base. For more information about the ENF, please visit our [website](https://eosnetwork.com/funding/) or [YouTube account](https://www.youtube.com/c/EverythingEOS). ## Grant Guidelines Individuals, small teams, and companies are all permitted to apply for grants. The purpose of the grants is to enable developers, businesses and individuals to build on EOS. Grants [vary in size](#grant-levels) based on the size and scope of the initiative. All forms of projects are open for submission, core chain modifications, tools, libraries, etc. as long as they are fully open-source. Strong technical projects that clearly add to the Public Good are preferred. From d5a1d9dff78949417629bac2f409b2d68c6103bc Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Thu, 18 May 2023 12:39:14 -0400 Subject: [PATCH 104/170] Update am-big-gsheet.yml Added AM to the name for Workflow Runs... --- .github/workflows/am-big-gsheet.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/am-big-gsheet.yml b/.github/workflows/am-big-gsheet.yml index 60b5282d..1e8049b6 100644 --- a/.github/workflows/am-big-gsheet.yml +++ b/.github/workflows/am-big-gsheet.yml @@ -1,4 +1,4 @@ -name: Reusable Gsheet Update +name: AM Reusable Gsheet Update on: workflow_call: inputs: From 6718049938430d53288a699bbe34327d8da9f516 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Thu, 18 May 2023 12:39:43 -0400 Subject: [PATCH 105/170] Update am-big-parser.yml Added AM to the name for workflow runs... --- .github/workflows/am-big-parser.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/am-big-parser.yml b/.github/workflows/am-big-parser.yml index 490f245f..2e7258a6 100644 --- a/.github/workflows/am-big-parser.yml +++ b/.github/workflows/am-big-parser.yml @@ -4,7 +4,7 @@ # 12Nov2022 - Added more fields for the Big Scrape and made a new file from old one # File may be called from a PR or with a filename passed in (not associated with a PR) # -name: Reusable "Big" Application Parser +name: AM Reusable "Big" Application Parser on: workflow_call: inputs: From 1e7226d8a09e4f6d301fd808af631d3135273ca8 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Thu, 18 May 2023 12:44:04 -0400 Subject: [PATCH 106/170] Update test-inputs.yml --- .github/workflows/test-inputs.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/workflows/test-inputs.yml b/.github/workflows/test-inputs.yml index ab7399db..a6330597 100644 --- a/.github/workflows/test-inputs.yml +++ b/.github/workflows/test-inputs.yml @@ -32,6 +32,7 @@ jobs: - name: greet run: | echo "string is ${{ github.event.inputs.string }}" + echo "string2 is ${{ github.event.inputs.string2 }}" echo "environment is ${{ github.event.inputs.environment }}" echo "boolean is ${{ github.event.inputs.boolean }}" echo "choice is ${{ github.event.inputs.choice }}" From 8def6f2faef9bd12d83841001e740f21122e8383 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Thu, 18 May 2023 12:47:32 -0400 Subject: [PATCH 107/170] Update test-inputs.yml --- .github/workflows/test-inputs.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/test-inputs.yml b/.github/workflows/test-inputs.yml index a6330597..770ee2a0 100644 --- a/.github/workflows/test-inputs.yml +++ b/.github/workflows/test-inputs.yml @@ -27,7 +27,7 @@ jobs: runs-on: ubuntu-latest steps: - - uses: actions/checkout@v2 + - uses: actions/checkout@latest - name: greet run: | From cfb87ce2f5db877c6f52f69afa6cd7b029a9e7dc Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Thu, 18 May 2023 12:50:37 -0400 Subject: [PATCH 108/170] Update test-inputs.yml --- .github/workflows/test-inputs.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/test-inputs.yml b/.github/workflows/test-inputs.yml index 770ee2a0..a206746f 100644 --- a/.github/workflows/test-inputs.yml +++ b/.github/workflows/test-inputs.yml @@ -27,7 +27,7 @@ jobs: runs-on: ubuntu-latest steps: - - uses: actions/checkout@latest + - uses: actions/checkout@v3 - name: greet run: | From 4f4dad312b6d3699f27cc810ca2ddc56dcb9e910 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Thu, 18 May 2023 12:58:06 -0400 Subject: [PATCH 109/170] Update pr-received.yml Update Ana06/get-changed-files to latest version --- .github/workflows/pr-received.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/pr-received.yml b/.github/workflows/pr-received.yml index c4b1dee8..b3384eaa 100644 --- a/.github/workflows/pr-received.yml +++ b/.github/workflows/pr-received.yml @@ -26,7 +26,7 @@ jobs: steps: - name: Get application file name id: 'files' - uses: Ana06/get-changed-files@v2.1.0 + uses: Ana06/get-changed-files@v2.2.0 with: filter: 'applications/*.md' From 2c96dcf212edc3d5748e0a134a25e1e821bf5b70 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Thu, 18 May 2023 17:13:24 -0400 Subject: [PATCH 110/170] Create test-jobs-exit.yml --- .github/workflows/test-jobs-exit.yml | 34 ++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+) create mode 100644 .github/workflows/test-jobs-exit.yml diff --git a/.github/workflows/test-jobs-exit.yml b/.github/workflows/test-jobs-exit.yml new file mode 100644 index 00000000..47e7f5a1 --- /dev/null +++ b/.github/workflows/test-jobs-exit.yml @@ -0,0 +1,34 @@ +name: Test Jobs Exit plus file test + +on: + workflow_dispatch: + inputs: + string: + type: string + description: Enter a sample filename with or without extension + +jobs: + echofile: + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v3 + + - name: greet + run: | + echo "string is ${{ github.event.inputs.string }}" + + testfile: + runs-on: ubuntu-latest + steps: + - name: testyes + if: ${{ endsWith(github.event.inputs.string, '.md') }} + run: | + echo "filename ends with .md" + - name: testno: + if: ${{ !endsWith(github.event.inputs.string, '.md') }} + run: | + echo "filename does not end with .md" + + + From a865d358e12d754d8c233054ef5677efda9266c4 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Thu, 18 May 2023 17:14:14 -0400 Subject: [PATCH 111/170] Update test-jobs-exit.yml --- .github/workflows/test-jobs-exit.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/test-jobs-exit.yml b/.github/workflows/test-jobs-exit.yml index 47e7f5a1..e5ca31fc 100644 --- a/.github/workflows/test-jobs-exit.yml +++ b/.github/workflows/test-jobs-exit.yml @@ -25,7 +25,7 @@ jobs: if: ${{ endsWith(github.event.inputs.string, '.md') }} run: | echo "filename ends with .md" - - name: testno: + - name: testno if: ${{ !endsWith(github.event.inputs.string, '.md') }} run: | echo "filename does not end with .md" From 2924e7a66f7dc1a81b164903d7d0ce34f9361742 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Thu, 18 May 2023 17:18:28 -0400 Subject: [PATCH 112/170] Update test-jobs-exit.yml --- .github/workflows/test-jobs-exit.yml | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/.github/workflows/test-jobs-exit.yml b/.github/workflows/test-jobs-exit.yml index e5ca31fc..1810d047 100644 --- a/.github/workflows/test-jobs-exit.yml +++ b/.github/workflows/test-jobs-exit.yml @@ -29,6 +29,15 @@ jobs: if: ${{ !endsWith(github.event.inputs.string, '.md') }} run: | echo "filename does not end with .md" + echo "This job has aborted" + exit 1 + + nextjobstep: + runs-on: ubuntu-latest + steps: + - name: finaljob + run: | + echo "job completed successfully" From 602d3aa7a014581d2a916558f3a93f105df662d1 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Thu, 18 May 2023 17:24:46 -0400 Subject: [PATCH 113/170] Update test-jobs-exit.yml --- .github/workflows/test-jobs-exit.yml | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/.github/workflows/test-jobs-exit.yml b/.github/workflows/test-jobs-exit.yml index 1810d047..7765d8a7 100644 --- a/.github/workflows/test-jobs-exit.yml +++ b/.github/workflows/test-jobs-exit.yml @@ -3,7 +3,7 @@ name: Test Jobs Exit plus file test on: workflow_dispatch: inputs: - string: + filename: type: string description: Enter a sample filename with or without extension @@ -14,26 +14,28 @@ jobs: steps: - uses: actions/checkout@v3 - - name: greet + - name: echofilename run: | - echo "string is ${{ github.event.inputs.string }}" + echo "string is ${{ github.event.inputs.filename }}" testfile: runs-on: ubuntu-latest + needs: echofile steps: - name: testyes - if: ${{ endsWith(github.event.inputs.string, '.md') }} + if: ${{ endsWith(github.event.inputs.filename, '.md') }} run: | - echo "filename ends with .md" + echo "filename ${{github.event.inputs.filename}} ends with .md" - name: testno - if: ${{ !endsWith(github.event.inputs.string, '.md') }} + if: ${{ !endsWith(github.event.inputs.filename, '.md') }} run: | - echo "filename does not end with .md" + echo "filename ${{github.event.inputs.filename}} does not end with .md" echo "This job has aborted" exit 1 nextjobstep: runs-on: ubuntu-latest + needs: testfile steps: - name: finaljob run: | From b70022d48838030d9de0a814326e2d9e74e8861c Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Thu, 18 May 2023 17:30:42 -0400 Subject: [PATCH 114/170] Update test-jobs-exit.yml --- .github/workflows/test-jobs-exit.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/test-jobs-exit.yml b/.github/workflows/test-jobs-exit.yml index 7765d8a7..5d78c435 100644 --- a/.github/workflows/test-jobs-exit.yml +++ b/.github/workflows/test-jobs-exit.yml @@ -29,7 +29,7 @@ jobs: - name: testno if: ${{ !endsWith(github.event.inputs.filename, '.md') }} run: | - echo "filename ${{github.event.inputs.filename}} does not end with .md" + echo "::error filename ${{github.event.inputs.filename}} does not end with .md" echo "This job has aborted" exit 1 From 2922864fa5f14e4cd909e026a40b27fbbe3531d8 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Thu, 18 May 2023 17:39:28 -0400 Subject: [PATCH 115/170] Update test-jobs-exit.yml --- .github/workflows/test-jobs-exit.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/.github/workflows/test-jobs-exit.yml b/.github/workflows/test-jobs-exit.yml index 5d78c435..91b6238c 100644 --- a/.github/workflows/test-jobs-exit.yml +++ b/.github/workflows/test-jobs-exit.yml @@ -28,10 +28,10 @@ jobs: echo "filename ${{github.event.inputs.filename}} ends with .md" - name: testno if: ${{ !endsWith(github.event.inputs.filename, '.md') }} - run: | - echo "::error filename ${{github.event.inputs.filename}} does not end with .md" - echo "This job has aborted" - exit 1 + uses: actions/github-script@v3 + with: + script: | + core.setFailed('filename ${{github.event.inputs.filename}} does not end with .md') nextjobstep: runs-on: ubuntu-latest From 934f212eaa7bdacb620271b542f8f683fc52e602 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Thu, 18 May 2023 17:40:34 -0400 Subject: [PATCH 116/170] Update test-jobs-exit.yml --- .github/workflows/test-jobs-exit.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/.github/workflows/test-jobs-exit.yml b/.github/workflows/test-jobs-exit.yml index 91b6238c..8d972f9b 100644 --- a/.github/workflows/test-jobs-exit.yml +++ b/.github/workflows/test-jobs-exit.yml @@ -29,9 +29,9 @@ jobs: - name: testno if: ${{ !endsWith(github.event.inputs.filename, '.md') }} uses: actions/github-script@v3 - with: - script: | - core.setFailed('filename ${{github.event.inputs.filename}} does not end with .md') + with: + script: | + core.setFailed('filename ${{github.event.inputs.filename}} does not end with .md') nextjobstep: runs-on: ubuntu-latest From 1d7d3393c92ee6e5f55000a2dfbb7ed4ec60cddd Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Thu, 18 May 2023 17:42:44 -0400 Subject: [PATCH 117/170] Update test-jobs-exit.yml --- .github/workflows/test-jobs-exit.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/test-jobs-exit.yml b/.github/workflows/test-jobs-exit.yml index 8d972f9b..ea446ba3 100644 --- a/.github/workflows/test-jobs-exit.yml +++ b/.github/workflows/test-jobs-exit.yml @@ -28,7 +28,7 @@ jobs: echo "filename ${{github.event.inputs.filename}} ends with .md" - name: testno if: ${{ !endsWith(github.event.inputs.filename, '.md') }} - uses: actions/github-script@v3 + uses: actions/github-script@v6 with: script: | core.setFailed('filename ${{github.event.inputs.filename}} does not end with .md') From a50796f1b427df52bc086ff85e6339db2193e809 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Thu, 18 May 2023 18:06:02 -0400 Subject: [PATCH 118/170] Update test-jobs-exit.yml --- .github/workflows/test-jobs-exit.yml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/.github/workflows/test-jobs-exit.yml b/.github/workflows/test-jobs-exit.yml index ea446ba3..29e0fd1a 100644 --- a/.github/workflows/test-jobs-exit.yml +++ b/.github/workflows/test-jobs-exit.yml @@ -26,12 +26,18 @@ jobs: if: ${{ endsWith(github.event.inputs.filename, '.md') }} run: | echo "filename ${{github.event.inputs.filename}} ends with .md" - - name: testno + - name: testmissingmd if: ${{ !endsWith(github.event.inputs.filename, '.md') }} uses: actions/github-script@v6 with: script: | core.setFailed('filename ${{github.event.inputs.filename}} does not end with .md') + - name: testspaces + if: ${{ contains(github.event.inputs.filename, ' ') }} + uses: actions/github-script@v6 + with: + script: | + core.setFailed('filename ${{github.event.inputs.filename}} cannot contain spaces. Exiting.') nextjobstep: runs-on: ubuntu-latest From 5ee7c592f9f5444fb79b12f6472cd106d9b9d39c Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Thu, 18 May 2023 18:07:48 -0400 Subject: [PATCH 119/170] Update test-jobs-exit.yml --- .github/workflows/test-jobs-exit.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/test-jobs-exit.yml b/.github/workflows/test-jobs-exit.yml index 29e0fd1a..a3a2e898 100644 --- a/.github/workflows/test-jobs-exit.yml +++ b/.github/workflows/test-jobs-exit.yml @@ -37,7 +37,7 @@ jobs: uses: actions/github-script@v6 with: script: | - core.setFailed('filename ${{github.event.inputs.filename}} cannot contain spaces. Exiting.') + core.setFailed('filename \'${{github.event.inputs.filename}}\' cannot contain spaces. Exiting.') nextjobstep: runs-on: ubuntu-latest From fa07aa496a8e1b6bf59a276d8207280a8979ba2c Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Thu, 18 May 2023 18:11:07 -0400 Subject: [PATCH 120/170] Update test-jobs-exit.yml --- .github/workflows/test-jobs-exit.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/.github/workflows/test-jobs-exit.yml b/.github/workflows/test-jobs-exit.yml index a3a2e898..cc6d984e 100644 --- a/.github/workflows/test-jobs-exit.yml +++ b/.github/workflows/test-jobs-exit.yml @@ -22,17 +22,17 @@ jobs: runs-on: ubuntu-latest needs: echofile steps: - - name: testyes + - name: tets-has-md if: ${{ endsWith(github.event.inputs.filename, '.md') }} run: | echo "filename ${{github.event.inputs.filename}} ends with .md" - - name: testmissingmd + - name: test-missing-md if: ${{ !endsWith(github.event.inputs.filename, '.md') }} uses: actions/github-script@v6 with: script: | core.setFailed('filename ${{github.event.inputs.filename}} does not end with .md') - - name: testspaces + - name: test-spaces if: ${{ contains(github.event.inputs.filename, ' ') }} uses: actions/github-script@v6 with: From 7623588f783d372674c3e2e6b45975a8e84b9bac Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Thu, 18 May 2023 18:13:02 -0400 Subject: [PATCH 121/170] Update test-jobs-exit.yml --- .github/workflows/test-jobs-exit.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/test-jobs-exit.yml b/.github/workflows/test-jobs-exit.yml index cc6d984e..0801ba18 100644 --- a/.github/workflows/test-jobs-exit.yml +++ b/.github/workflows/test-jobs-exit.yml @@ -16,7 +16,7 @@ jobs: - name: echofilename run: | - echo "string is ${{ github.event.inputs.filename }}" + echo "The filename is ${{ github.event.inputs.filename }}" testfile: runs-on: ubuntu-latest From 021974b3efd0a26b30c5cef00fc2992b6b1722a0 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Thu, 18 May 2023 18:13:31 -0400 Subject: [PATCH 122/170] Update test-jobs-exit.yml --- .github/workflows/test-jobs-exit.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/test-jobs-exit.yml b/.github/workflows/test-jobs-exit.yml index 0801ba18..87fe478f 100644 --- a/.github/workflows/test-jobs-exit.yml +++ b/.github/workflows/test-jobs-exit.yml @@ -22,7 +22,7 @@ jobs: runs-on: ubuntu-latest needs: echofile steps: - - name: tets-has-md + - name: test-has-md if: ${{ endsWith(github.event.inputs.filename, '.md') }} run: | echo "filename ${{github.event.inputs.filename}} ends with .md" From 6c304fe1a299c304130addee335305429945be59 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Thu, 18 May 2023 18:16:49 -0400 Subject: [PATCH 123/170] Update test-jobs-exit.yml --- .github/workflows/test-jobs-exit.yml | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/.github/workflows/test-jobs-exit.yml b/.github/workflows/test-jobs-exit.yml index 87fe478f..09141db8 100644 --- a/.github/workflows/test-jobs-exit.yml +++ b/.github/workflows/test-jobs-exit.yml @@ -1,3 +1,10 @@ +# This is a test job to test various filenames for two known error conditions: +# 1) missing the ".md" file extension +# 2) embedded spaced in the filename +# The job will exit and print an error message to the Annotations (Console) so others can diagnose. +# +# Ted Cahall 18May2023 +# name: Test Jobs Exit plus file test on: @@ -10,10 +17,8 @@ on: jobs: echofile: runs-on: ubuntu-latest - steps: - uses: actions/checkout@v3 - - name: echofilename run: | echo "The filename is ${{ github.event.inputs.filename }}" From 5c514ae1a1e7a5997ad3ecac64a4e6ff59bf0d75 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Thu, 18 May 2023 18:23:02 -0400 Subject: [PATCH 124/170] Create ru-check-filename.yml --- .github/workflows/ru-check-filename.yml | 36 +++++++++++++++++++++++++ 1 file changed, 36 insertions(+) create mode 100644 .github/workflows/ru-check-filename.yml diff --git a/.github/workflows/ru-check-filename.yml b/.github/workflows/ru-check-filename.yml new file mode 100644 index 00000000..93b718f6 --- /dev/null +++ b/.github/workflows/ru-check-filename.yml @@ -0,0 +1,36 @@ +# Reusable filename checker +# Checks for the following conditions and exits if found: +# 1) missing the ".md" file extension +# 2) embedded spaced in the filename +# The job will exit and print an error message to the Annotations (Console) so others can diagnose. +# +# Ted Cahall 18May2023 +# +name: Reusable Filename checker +on: + workflow_call: + inputs: + filename: + required: true + type: string + +jobs: + checkfile: + runs-on: ubuntu-latest + steps: + - name: test-has-md + if: ${{ endsWith(github.event.inputs.filename, '.md') }} + run: | + echo "filename ${{github.event.inputs.filename}} ends with .md" + - name: test-missing-md + if: ${{ !endsWith(github.event.inputs.filename, '.md') }} + uses: actions/github-script@v6 + with: + script: | + core.setFailed('filename ${{github.event.inputs.filename}} does not end with .md') + - name: test-spaces + if: ${{ contains(github.event.inputs.filename, ' ') }} + uses: actions/github-script@v6 + with: + script: | + core.setFailed('filename \'${{github.event.inputs.filename}}\' cannot contain spaces. Exiting.') From 2be5208555bc3d7fe76f9c59e3085c0e09f68a2f Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Thu, 18 May 2023 18:30:02 -0400 Subject: [PATCH 125/170] Create test-ru-check-filename.yml --- .github/workflows/test-ru-check-filename.yml | 38 ++++++++++++++++++++ 1 file changed, 38 insertions(+) create mode 100644 .github/workflows/test-ru-check-filename.yml diff --git a/.github/workflows/test-ru-check-filename.yml b/.github/workflows/test-ru-check-filename.yml new file mode 100644 index 00000000..b1a9a3a6 --- /dev/null +++ b/.github/workflows/test-ru-check-filename.yml @@ -0,0 +1,38 @@ +# This is a test job to test various filenames for two known error conditions: +# 1) missing the ".md" file extension +# 2) embedded spaced in the filename +# The job will exit and print an error message to the Annotations (Console) so others can diagnose. +# +# Ted Cahall 18May2023 +# +name: Test Jobs Exit plus file test + +on: + workflow_dispatch: + inputs: + filename: + type: string + description: Enter a sample filename with or without extension + +jobs: + echofile: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v3 + - name: echofilename + run: | + echo "The filename is ${{ github.event.inputs.filename }}" + + testfile: + needs: echofile + uses: ./.github/workflows/ru-check-filename.yml + with: + filename: "${{ github.event.inputs.filename }}" + + job-complete: + runs-on: ubuntu-latest + steps: + - name: echofilename + run: | + echo "Job Complete. The filename is ${{ github.event.inputs.filename }}" + From 996bb67d639ebda7910cb1cacb5c069d287703fd Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Thu, 18 May 2023 18:31:21 -0400 Subject: [PATCH 126/170] Update test-ru-check-filename.yml --- .github/workflows/test-ru-check-filename.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/test-ru-check-filename.yml b/.github/workflows/test-ru-check-filename.yml index b1a9a3a6..04575e6f 100644 --- a/.github/workflows/test-ru-check-filename.yml +++ b/.github/workflows/test-ru-check-filename.yml @@ -5,7 +5,7 @@ # # Ted Cahall 18May2023 # -name: Test Jobs Exit plus file test +name: Test Reusable Check Filename on: workflow_dispatch: From 095f0c8a7c82dbbd3409981e95290fae22679469 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Thu, 18 May 2023 18:33:37 -0400 Subject: [PATCH 127/170] Update test-ru-check-filename.yml --- .github/workflows/test-ru-check-filename.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/workflows/test-ru-check-filename.yml b/.github/workflows/test-ru-check-filename.yml index 04575e6f..c9b081aa 100644 --- a/.github/workflows/test-ru-check-filename.yml +++ b/.github/workflows/test-ru-check-filename.yml @@ -31,6 +31,7 @@ jobs: job-complete: runs-on: ubuntu-latest + needs: testfile steps: - name: echofilename run: | From fef61f75668b02061646d787700759802ade9b00 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Thu, 18 May 2023 18:42:37 -0400 Subject: [PATCH 128/170] Exit on bad filename issues Check for space in filename Check that file ends in .md --- .github/workflows/pr-received.yml | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/.github/workflows/pr-received.yml b/.github/workflows/pr-received.yml index b3384eaa..ca727d1e 100644 --- a/.github/workflows/pr-received.yml +++ b/.github/workflows/pr-received.yml @@ -30,15 +30,21 @@ jobs: with: filter: 'applications/*.md' + testfile: + needs: get_filename + uses: ./.github/workflows/ru-check-filename.yml + with: + filename: "${{ needs.get_filename.outputs.filename }}" + call-parser: uses: ./.github/workflows/ru-big-parser.yml with: filename: "${{ needs.get_filename.outputs.filename }}" - needs: get_filename + needs: [get_filename, testfile] echo-the-returned-fields: runs-on: ubuntu-latest - needs: [get_filename, call-parser] + needs: [get_filename, testfile, call-parser] steps: - id: echo-output run: | From efb79ee673e0735231cca98feae0850eb59830ad Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Thu, 18 May 2023 18:50:32 -0400 Subject: [PATCH 129/170] Update pr-received.yml --- .github/workflows/pr-received.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/pr-received.yml b/.github/workflows/pr-received.yml index ca727d1e..39918ca9 100644 --- a/.github/workflows/pr-received.yml +++ b/.github/workflows/pr-received.yml @@ -44,7 +44,7 @@ jobs: echo-the-returned-fields: runs-on: ubuntu-latest - needs: [get_filename, testfile, call-parser] + needs: call-parser steps: - id: echo-output run: | From 81c78b8cfd3a4e010e88800ada02656109f0897c Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Thu, 18 May 2023 18:52:56 -0400 Subject: [PATCH 130/170] Update pr-received.yml --- .github/workflows/pr-received.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/.github/workflows/pr-received.yml b/.github/workflows/pr-received.yml index 39918ca9..3b12a744 100644 --- a/.github/workflows/pr-received.yml +++ b/.github/workflows/pr-received.yml @@ -30,17 +30,17 @@ jobs: with: filter: 'applications/*.md' - testfile: - needs: get_filename - uses: ./.github/workflows/ru-check-filename.yml - with: - filename: "${{ needs.get_filename.outputs.filename }}" +# testfile: +# needs: get_filename +# uses: ./.github/workflows/ru-check-filename.yml +# with: +# filename: "${{ needs.get_filename.outputs.filename }}" call-parser: uses: ./.github/workflows/ru-big-parser.yml with: filename: "${{ needs.get_filename.outputs.filename }}" - needs: [get_filename, testfile] + needs: get_filename echo-the-returned-fields: runs-on: ubuntu-latest From 9024cc517a3f3b20b59419c7e10d3683c9a1f624 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Thu, 18 May 2023 20:40:23 -0400 Subject: [PATCH 131/170] Update pr-received.yml --- .github/workflows/pr-received.yml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/.github/workflows/pr-received.yml b/.github/workflows/pr-received.yml index 3b12a744..69d49d23 100644 --- a/.github/workflows/pr-received.yml +++ b/.github/workflows/pr-received.yml @@ -30,11 +30,11 @@ jobs: with: filter: 'applications/*.md' -# testfile: -# needs: get_filename -# uses: ./.github/workflows/ru-check-filename.yml -# with: -# filename: "${{ needs.get_filename.outputs.filename }}" + testfile: + uses: ./.github/workflows/ru-check-filename.yml + with: + filename: "${{ needs.get_filename.outputs.filename }}" + needs: get_filename call-parser: uses: ./.github/workflows/ru-big-parser.yml From e7ec6332bcde6c893069d67daec6d7482cf15dba Mon Sep 17 00:00:00 2001 From: Ryan Tjhin <99659545+RyanTjhin@users.noreply.github.com> Date: Fri, 19 May 2023 16:28:59 +0700 Subject: [PATCH 132/170] Create tokenomics_enhancement_neutroswap.md --- .../tokenomics_enhancement_neutroswap.md | 212 ++++++++++++++++++ 1 file changed, 212 insertions(+) create mode 100644 applications/tokenomics_enhancement_neutroswap.md diff --git a/applications/tokenomics_enhancement_neutroswap.md b/applications/tokenomics_enhancement_neutroswap.md new file mode 100644 index 00000000..7a6fdb4c --- /dev/null +++ b/applications/tokenomics_enhancement_neutroswap.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 0baa9c81ceafa79c1838b519aef09c21afd4969f Mon Sep 17 00:00:00 2001 From: Ryan Tjhin Date: Fri, 19 May 2023 21:09:52 +0700 Subject: [PATCH 133/170] Probably final --- .../tokenomics_enhancement_neutroswap.md | 331 ++++++++++-------- 1 file changed, 183 insertions(+), 148 deletions(-) diff --git a/applications/tokenomics_enhancement_neutroswap.md b/applications/tokenomics_enhancement_neutroswap.md index 7a6fdb4c..1d04d756 100644 --- a/applications/tokenomics_enhancement_neutroswap.md +++ b/applications/tokenomics_enhancement_neutroswap.md @@ -1,212 +1,247 @@ # 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. +- **Project Name:** Neutroswap +- **Team Name:** Nava Labs +- **EOS Payment Address:** 0x7De5A1Aa67ec3f67C326689FD36abA20ba703E65 +- **[Level](https://github.com/eosnetworkfoundation/grant-framework#grant-levels):** 3 +- **Pomelo Grant(s):** N/A +- **Project is Open-Source:** Yes +- **Project was part of Token sale:** No +- **Repository where Project resides:** https://github.com/Nava-Labs/neutroswap-contract ## 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.* +- **Contact Name:** Jonas Aditya Sunandar +- **Contact Email:** contact@neutroswap.io +- **Website:** https://neutroswap.io ## 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. +Neutroswap is an automated market-maker (AMM) on the EOS EVM blockchain that is community-driven and offers the low fees for swapping assets. Neutroswap's staking and yield farming rewards are among the highest in the EOS EVM ecosystem, attracting those seeking profitable returns on their assets. Our team decides to focus more towards bringing liquidity to EOS EVM chain more. It will enable more users, projects and exposure coming to EOS EVM due to TVL increase and project development. ### 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. +- **Name:** Neutroswap +- **Brief Description:** A community-driven interconnected tokenomics ecosystem with burn and yield booster mechanism +- **Relationship to EOS Network / Antelope:** Our app brings liquidity to EOS EVM attracting more projects and users to use the chain. +- **Reason for Interest:** Capital efficiency, impermanent loss mitigation, higher fee rewards, reduced slippage, improved price discovery for our app users. ### 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): +We have successfully launched $NEUTRO token alongside our Neutroswap V2: -- 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 +1. The first DApp that reached $1,000,000 in TVL +2. The first EOS EVM token listed on Coingecko +3. The first working app on EOS EVM and has active users. +4. Bring more than 2000+ transactions on average per day since launch. +5. Bring $150,000+ volume daily accross Neutroswap V2 pool. +6. The first project that triggers influencers to look at EOS EVM. +7. $NEUTRO all-time price $0.41 +8. [Burned 98% of max supply](https://twitter.com/Neutroswap/status/1653759171664429056?s=20) (980,000,000 $NEUTRO) -### Ecosystem Fit +We are shifting our focus to enhance the utility and value of the $NEUTRO token. Previously, it was primarily utilized for incentivizing users through Neutro Farms and Vaults. Our plan now includes introducing $xNEUTRO, a locked version of the token similar to $veCRV by Curve Finance. Additionally, we will implement various updates such as Plugins, a new distribution mechanism for protocol revenue, a deflationary mechanism, and spNFTs. -> Help us locate your project in the EOS Network landscape and what problems it tries to solve by answering each of these questions: +[**xNEUTRO**](https://docs.neutroswap.io/neutroswap-v2-coming-soon/xneutro-token) -- 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? +$xNEUTRO will be non-transferable and act as our governance token. $xNEUTRO main utility is the ability for it to be allocated by users to our various [plugins](https://docs.neutroswap.io/neutroswap-v2-coming-soon/plugins) such as: -## Team +- [Dividends](https://docs.neutroswap.io/neutroswap-v2-coming-soon/plugins/dividends): Giving $xNEUTRO holders a portion of revenue generated by Neutroswap +- [Yield Multiplier](https://docs.neutroswap.io/neutroswap-v2-coming-soon/plugins/yield-multiplier): Boosting users' yield up to 2x +- [Launchpad](https://docs.neutroswap.io/neutroswap-v2-coming-soon/plugins/launchpad): Giving priority access to $xNEUTRO holders allocating to this plugin more exclusivity access to Neutroswap upcoming Launchpad -### Team members +[**Staked Positions NFT (spNFTs)**](https://docs.neutroswap.io/neutroswap-v2-coming-soon/staked-positions-spnfts) -- **Team Leader:** Name of team leader -- Name of team member 1 -- Name of team member 2 -- Name of team member 3, etc. +The upcoming mechanism will replace the existing Neutro Farms as they both serve similar purposes. The key distinction is that instead of solely depositing LP tokens into the Farms smart contract, users will receive spNFTs in exchange for their deposited LP tokens, making it tradeable. -### 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) +[**Protocol Revenue Distribution**](https://docs.neutroswap.io/neutroswap-v2-coming-soon/protocol-revenue) -### Team Experience +The protocol-generated revenue will be distributed as follows: -> 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. +- 60% is allocated to Liquidity Providers in the form of LP tokens. +- 22.5% is distributed as dividends to $xNEUTRO holders. +- 12.5% is dedicated to the buyback and burn of $NEUTRO tokens. +- 5% is allocated to the Core Contributors' funds. -> 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. +The Core Contributors funds will be solely utilized to cover operational expenses. At the end of each month, any remaining unused amount will be reallocated at the team's discretion, either towards Dividends or for Buyback and Burn purposes. -### Team Org Repos +[**Deflationary Mechanism**](https://docs.neutroswap.io/neutroswap-v2-coming-soon/deflationary-mechanism) -- https://github.com/ -- https://github.com// -- https://github.com// +We applied a few mechanism that will increase the buying pressure of $NEUTRO with the aim of making it for attractive for future investors, while increasing value for $NEUTRO holders. -> 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. +- Buyback and Burn: A portion of the protocol revenues is allocated towards the buyback and burn of $NEUTRO tokens, creating persistent buying pressure on the token. +- xNEUTRO Reedem: During the [redeem of $xNEUTRO to $NEUTRO](https://docs.neutroswap.io/neutroswap-v2-coming-soon/xneutro-token/convert-redeem#redeeming-xneutro-greater-than-neutro), if the vesting duration is not set to the maximum, the xNEUTRO:NEUTRO ratio will be adjusted to a value below 1:1, ranging from 1:0.5 as the minimum. Any surplus $NEUTRO obtained during this process will be automatically burned. +- xNEUTRO Deallocation: When users deallocate $xNEUTRO from a Plugin, a deallocation tax is imposed, typically set at 0.5%. This tax may vary across contracts. Furthermore, the corresponding amount of $NEUTRO will be automatically burned as a result of the deallocation process. -### Team Member Repos +### Ecosystem Fit -- https://github.com/ -- https://github.com/ +- Where and how does your project fit into the ecosystem? -### Team LinkedIn Profiles (if available) +- Who is your target audience (chain/dapp/wallet/UI developers, designers, your own user base, some dapp's userbase, yourself)? -- https://www.linkedin.com/in/ -- https://www.linkedin.com/in/ + Farmers, DeFi users, crypto users in general, traders -## Development Status +- What need(s) does your project meet? -> 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: + Neutroswap will be the pioneering project on EOS EVM to introduce advanced tokenomics, which has the potential to ignite competition from other projects. Through healthy competition, we aim to foster greater innovation within the DeFi ecosystem on EOS EVM. -- 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. +- Are there any other projects similar to yours in the EOS Network / Antelope ecosystem? -## Development Roadmap + Currently, there are no projects offering similar features and complex tokenomics as our planned implementation for Neutroswap. However, as mentioned before, there is the possibility of Noahswap and Frogge following suit and introducing similar functionalities on EOS EVM. -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. +## Team -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. +### Team members -For each milestone, +- **Team Leader:** Jonas Aditya Sunandar +- Erwin Phanglius +- Akramurridjal Rahman +- Ryan Tjin +- Kevin Jacob Surtan +- William Wijaya +- Might need to onboard more -- 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). +### Advisor -> :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.** +- Wilsen Tiomajaya, Co-founder of GGG -### Milestone Summary +### Legal Structure -> 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 +- **Registered Legal Entity:** PT Nava Labs +- **Registered Address:** Foresta Fiore B3 No 10 BSD, Tangerang Selatan, Indonesia -> 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. +### Team Experience -### Milestone 1 Example — Implement EOS Application +- [EMURGO/Cardano](https://emurgo.io/) +- [Good Games Guild](https://goodgamesguild.com/) +- [Whitehackers](https://www.whitehackers.dev/) +- [Arbipad](https://arbipad.com/) +- Metaversepad +- [HARA token](https://www.hara.ag/) +- [Asosiasi Blockchain Indonesia](https://asosiasiblockchain.co.id/) +- [Coinvestasi](https://coinvestasi.com/) -- **Estimated duration:** 1 month -- **FTE:** 2 -- **Costs:** 8,000 USD +### Team Org Repos -| 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 ... | +- https://github.com/Nava-Labs +- https://github.com/Nava-Labs/neutroswap-contract +### Team Member Repos +- https://github.com/xerod +- https://github.com/jonassunandar +- https://github.com/erwinphanglius +- https://github.com/RyanTjhin -### Milestone 2 Example — Additional features +### Team LinkedIn Profiles (if available) -- **Estimated Duration:** 1 month -- **FTE:** 2 -- **Costs:** 4,000 USD +- https://www.linkedin.com/in/jonas-sunandar-83307b164/ +- https://www.linkedin.com/in/wilsen-t-110533113/ +- https://www.linkedin.com/in/akramurridjal/ +- https://www.linkedin.com/in/erwin-phanglius-a22a121a6/ +- https://www.linkedin.com/in/ryan-tjhin-90b16521b/ +- https://www.linkedin.com/in/william-wijaya-792075199/ -| 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 ... | +## Development Status +We have completed the [technical documentation](https://docs.neutroswap.io/neutroswap-v2-coming-soon) outlining our planned updates. However, we are currently engaged in ongoing research and fine-tuning our implementation approach. The development of the UI/UX design is also in progress. -... Add more milestones as above as needed ... +## Development Roadmap +### Milestone Summary + +- **Total Estimated Duration:** 3 months +- **Full-Time Equivalent (FTE):** 6 FTE +- **Total Costs:** 100,000 USD + +### Milestone 0 - Requirement Analysis and Marketing Plan + +- **Estimated duration:** 2 weeks +- **FTE:** 2 +- **Costs:** 20,000 USD + +| ID | Deliverable | Specification | +| --- | -------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 0a. | License | MIT | +| 0b. | Threads | Publish **twitter threads** explaining all the updates that'll we'll be rolling out | +| 0c. | Marketing | Form a group of multiple DeFi influencers and create a plan that can help bring more awareness about DeFi EOS EVM ecosystem | +| 1. | General Requirement and Migration Plan | **Smart contract Requirement**
Write a detailed requirements for the smart contract

**Subgraph Migration Plan**
Analyze required changes on 3 of our subgraphs, and create migration plan for it

**High Fidelity Prototype**
Publish a high-fidelity prototype for the new UI required for the updates. The prototype will be publicly available in Figma for others to use.

**Front-end Migration Plan**
Do a code structure research on how the current and future component would work together

**Integration Testing Plan**
Research on how our current toolchain like ethers and foundry would work in the testing environment | +| 2. | Documentation | Enhance the technical documentation and tutorial to comprehensively explain all the updates, enabling users to familiarize themselves with the new enhancements. | + +### Milestone 1 - Smart Contract Development, Audit, and Marketing Site + +- **Estimated duration:** 3 weeks +- **FTE:** 3 +- **Costs:** 30,000 USD + +| ID | Deliverable | Specification | +| --- | ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 0a. | License | Apache 2.0 | +| 0b. | Documentation | We will provide both **inline documentation** of the code and a technical **tutorial** that explains how users can utilize all of the new updates works. | +| 0c. | Unit Test | Core functions will be fully covered by unit tests to ensure functionality and robustness. These test will be provided in the repository for the public | +| 0d. | Testing Guide | Guide will also be included in the repository | +| 1. | Smart Contract Security Audit | Publish the all the necessary smart contract such as xNEUTRO, spNFTs, plugins in a public repo with the audit report included. This smart contract will also publicly available on our team Github | +| 2. | Marketing Page | Product landing page makeover that also describes all of the new features | + +### Milestone 2 - Graph Node Deployment, Subgraphs, and Web Development + +- **Estimated duration:** 3 weeks +- **FTE:** 4 +- **Costs:** 20,000 USD + +| ID | Deliverable | Specification | +| --- | -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 0a. | License | Apache 2.0 | +| 0b. | Integration Tests | Integration tests will be developed, including new and modified tests. | +| 1. | Subgraph Development | Publish a public subgraphs that can be used publicly | +| 3. | Additional UI | Implementing the high-fidelity prototype from earlier stage. Adding new components necessary enabling users to interact with all of the new updates while keeping the current UI accessible to all users | +| 4. | Analytics | User will be able to see xNEUTRO, spNFTs, and activity in all of the new contracts | +| 5. | Testnet Deployment | Deploy the new contract, subgraphs, and web to the EOSEVM Testnet environment | +| 6. | Medium Post | All contract addresses and public subgraph links will be available on both Discord and Medium account | + +### Milestone 3 - Neutroswap V3 Mainnet Deployment + +- **Estimated duration:** 2 weeks +- **FTE:** 2 +- **Costs:** 30,000 USD + +| ID | Deliverable | Specification | +| --- | ------------------------- | --------------------------------------------------------------------------------- | +| 0a. | License | Apache 2.0 | +| 0b. | Testnet Integration Test | Do integration testing on testnet before migrating the whole stack to the mainnet | +| 1. | Smart Contract Deployment | Deploy smart contract to the EOS-EVM mainnet | +| 2. | Graph Node Deployment | Publish a private graph-node instance for the EOS-EVM mainnet environment | +| 3. | Subgraph Deployment | Publish public subgraphs for Neutroswap V3 and start indexing EOS-EVM mainnet | +| 4. | V3 UI Deployment | Deploy the new UI to Production | ## Future Plans -> Please include here: +Upon implementing all the aforementioned updates, we anticipate a notable surge in Neutroswap users, aligning with the growth of EOS EVM users and potential developers. Furthermore, we have strategic plans to intensify our business development endeavors by seeking new partnerships that will benefit both Neutroswap and the EOS EVM ecosystem as a whole. -- 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 Twitter / personal recommendation -## Additional Information +As we look to the future of Neutroswap and EOS EVM, we believe that a grant to bring liquidity to the platform is essential. We've been proud to build Neutroswap without raising any investment from VC firms, and we're hopeful that ENF will see the value in our work and provide the support we need to continue to grow and innovate on EOS EVM. + +We have done our best to trigger the initial wave of EOS EVM by becoming: + +1. The first DApp that reached $1,000,000 in TVL +2. The first EOS EVM token listed on Coingecko +3. The first working app on EOS EVM and has active users. +4. Bring more than 2000+ transactions on average per day since launch +5. Bring $150,000+ volume daily accross Neutroswap V2 DEX +6. The first project that triggers influencers to look at EOS EVM + +By supporting Neutroswap as a catalyst project, ENF can help to attract the attention of other EVM developers and encourage them to build on EOS EVM. This can lead to an influx of proposals seeking grants, which would be a welcome problem for ENF to have. However, the most important thing is to generate traction, volume, TVL, and attract more users, especially builders, to the EOS EVM ecosystem. With ENF's support, we can continue to lead the charge and set the standard for innovation and growth in EOS EVM. -**How did you hear about the Grants Program?** EOS Network Foundation Website / Medium / Twitter / Element / Announcement by another team / personal recommendation / etc. +Thank you for considering our proposal -> 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: +Links: -- 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. +- Website: https://neutroswap.io/ +- V2 Audit: https://github.com/solidproof/projects/tree/main/NeutroSwap +- Docs: https://docs.neutroswap.io/ +- DefiLlama: https://defillama.com/protocol/neutroswap +- CoinGecko: https://www.coingecko.com/en/coins/neutroswap +- CoinMarketCap: https://coinmarketcap.com/dexscan/eos%20evm/0xb3fb2548287bcadd5a045270b3182c1fc6318684/ +- Linktree: https://linktr.ee/Neutroswap From a4edb8b9a137a568f4a6a5747ae7ba69dee84d7b Mon Sep 17 00:00:00 2001 From: Ryan Tjhin Date: Fri, 19 May 2023 21:13:40 +0700 Subject: [PATCH 134/170] Probably final --- .../tokenomics_enhancement_neutroswap.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/applications/tokenomics_enhancement_neutroswap.md b/applications/tokenomics_enhancement_neutroswap.md index 1d04d756..d5fe9705 100644 --- a/applications/tokenomics_enhancement_neutroswap.md +++ b/applications/tokenomics_enhancement_neutroswap.md @@ -198,20 +198,20 @@ We have completed the [technical documentation](https://docs.neutroswap.io/neutr | 5. | Testnet Deployment | Deploy the new contract, subgraphs, and web to the EOSEVM Testnet environment | | 6. | Medium Post | All contract addresses and public subgraph links will be available on both Discord and Medium account | -### Milestone 3 - Neutroswap V3 Mainnet Deployment +### Milestone 3 - Neutroswap Updates Mainnet Deployment - **Estimated duration:** 2 weeks - **FTE:** 2 - **Costs:** 30,000 USD -| ID | Deliverable | Specification | -| --- | ------------------------- | --------------------------------------------------------------------------------- | -| 0a. | License | Apache 2.0 | -| 0b. | Testnet Integration Test | Do integration testing on testnet before migrating the whole stack to the mainnet | -| 1. | Smart Contract Deployment | Deploy smart contract to the EOS-EVM mainnet | -| 2. | Graph Node Deployment | Publish a private graph-node instance for the EOS-EVM mainnet environment | -| 3. | Subgraph Deployment | Publish public subgraphs for Neutroswap V3 and start indexing EOS-EVM mainnet | -| 4. | V3 UI Deployment | Deploy the new UI to Production | +| ID | Deliverable | Specification | +| --- | ------------------------- | ---------------------------------------------------------------------------------- | +| 0a. | License | Apache 2.0 | +| 0b. | Testnet Integration Test | Do integration testing on testnet before migrating the whole stack to the mainnet | +| 1. | Smart Contract Deployment | Deploy smart contract to the EOS-EVM mainnet | +| 2. | Graph Node Deployment | Publish a private graph-node instance for the EOS-EVM mainnet environment | +| 3. | Subgraph Deployment | Publish public subgraphs for Neutroswap updates and start indexing EOS-EVM mainnet | +| 4. | New UI Deployment | Deploy the new UI to Production | ## Future Plans From d4e670c3937be8cb4002279f509dc6657f7fcd67 Mon Sep 17 00:00:00 2001 From: Jonas Sunandar Date: Fri, 19 May 2023 21:33:33 +0700 Subject: [PATCH 135/170] Update tokenomics_enhancement_neutroswap.md Add links and fix typos --- applications/tokenomics_enhancement_neutroswap.md | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/applications/tokenomics_enhancement_neutroswap.md b/applications/tokenomics_enhancement_neutroswap.md index d5fe9705..86daf16c 100644 --- a/applications/tokenomics_enhancement_neutroswap.md +++ b/applications/tokenomics_enhancement_neutroswap.md @@ -28,13 +28,13 @@ Neutroswap is an automated market-maker (AMM) on the EOS EVM blockchain that is ### Project Details -We have successfully launched $NEUTRO token alongside our Neutroswap V2: +We have successfully launched $NEUTRO token alongside our Neutroswap V1: -1. The first DApp that reached $1,000,000 in TVL -2. The first EOS EVM token listed on Coingecko +1. The first DApp that reached $1,500,000 in TVL +2. The first EOS EVM token listed on best platform [Crypto.com](https://crypto.com/price/neutroswap), [Coingecko](https://www.coingecko.com/en/coins/neutroswap), CoinMarketCap, [Debank](https://debank.com/protocols/eos_neutroswap/assets), [GeckoTerminal](https://www.geckoterminal.com/eos-evm/pools/0xb3fb2548287bcadd5a045270b3182c1fc6318684), [DappRadar](https://dappradar.com/dapp/neutroswap), [Ave.ai](https://ave.ai/token/0xf4bd487a8190211e62925435963d996b59a860c0-eos?from=Default) 3. The first working app on EOS EVM and has active users. -4. Bring more than 2000+ transactions on average per day since launch. -5. Bring $150,000+ volume daily accross Neutroswap V2 pool. +4. Bring more than 7500+ transactions on average per day since launch. +5. Bring $150,000+ volume daily accross Neutroswap pool. 6. The first project that triggers influencers to look at EOS EVM. 7. $NEUTRO all-time price $0.41 8. [Burned 98% of max supply](https://twitter.com/Neutroswap/status/1653759171664429056?s=20) (980,000,000 $NEUTRO) @@ -239,9 +239,11 @@ Thank you for considering our proposal Links: - Website: https://neutroswap.io/ -- V2 Audit: https://github.com/solidproof/projects/tree/main/NeutroSwap +- Audit: https://github.com/solidproof/projects/tree/main/NeutroSwap - Docs: https://docs.neutroswap.io/ - DefiLlama: https://defillama.com/protocol/neutroswap +- Debank: https://debank.com/protocols/eos_neutroswap/assets +- Crypto.com: https://crypto.com/price/neutroswap - CoinGecko: https://www.coingecko.com/en/coins/neutroswap - CoinMarketCap: https://coinmarketcap.com/dexscan/eos%20evm/0xb3fb2548287bcadd5a045270b3182c1fc6318684/ - Linktree: https://linktr.ee/Neutroswap From 8e8ee7eebd9768077db57b17340351063cf06485 Mon Sep 17 00:00:00 2001 From: Jonas Sunandar Date: Fri, 19 May 2023 21:41:25 +0700 Subject: [PATCH 136/170] Update tokenomics_enhancement_neutroswap.md Prettier link list --- .../tokenomics_enhancement_neutroswap.md | 37 +++++++++++++------ 1 file changed, 26 insertions(+), 11 deletions(-) diff --git a/applications/tokenomics_enhancement_neutroswap.md b/applications/tokenomics_enhancement_neutroswap.md index 86daf16c..4eece223 100644 --- a/applications/tokenomics_enhancement_neutroswap.md +++ b/applications/tokenomics_enhancement_neutroswap.md @@ -30,8 +30,15 @@ Neutroswap is an automated market-maker (AMM) on the EOS EVM blockchain that is We have successfully launched $NEUTRO token alongside our Neutroswap V1: -1. The first DApp that reached $1,500,000 in TVL -2. The first EOS EVM token listed on best platform [Crypto.com](https://crypto.com/price/neutroswap), [Coingecko](https://www.coingecko.com/en/coins/neutroswap), CoinMarketCap, [Debank](https://debank.com/protocols/eos_neutroswap/assets), [GeckoTerminal](https://www.geckoterminal.com/eos-evm/pools/0xb3fb2548287bcadd5a045270b3182c1fc6318684), [DappRadar](https://dappradar.com/dapp/neutroswap), [Ave.ai](https://ave.ai/token/0xf4bd487a8190211e62925435963d996b59a860c0-eos?from=Default) +1. The first DApp that reached $1,500,000 in TVL in EOS EVM +2. The first EOS EVM token listed on best platforms: +- [Debank](https://debank.com/protocols/eos_neutroswap/assets) +- [Crypto.com](https://crypto.com/price/neutroswap) +- [Coingecko](https://www.coingecko.com/en/coins/neutroswap) +- [CoinMarketCap](https://coinmarketcap.com/dexscan/networks/eos-evm/) +- [GeckoTerminal](https://www.geckoterminal.com/eos-evm/pools/0xb3fb2548287bcadd5a045270b3182c1fc6318684) +- [DappRadar](https://dappradar.com/dapp/neutroswap) +- [Ave.ai](https://ave.ai/token/0xf4bd487a8190211e62925435963d996b59a860c0-eos?from=Default) 3. The first working app on EOS EVM and has active users. 4. Bring more than 7500+ transactions on average per day since launch. 5. Bring $150,000+ volume daily accross Neutroswap pool. @@ -75,7 +82,7 @@ We applied a few mechanism that will increase the buying pressure of $NEUTRO wit ### Ecosystem Fit - Where and how does your project fit into the ecosystem? - +Currently, EOS EVM needs more TVL to achieve organic exposure and attract new users. That's why we're thrilled to have already seen significant growth since our launch. But we're not stopping there. Our team is committed to further strengthening EOS EVM by providing even more value through our upcoming V2 version. With V2, we're confident that we can continue to drive growth and make EOS EVM an even more vibrant and successful ecosystem - Who is your target audience (chain/dapp/wallet/UI developers, designers, your own user base, some dapp's userbase, yourself)? Farmers, DeFi users, crypto users in general, traders @@ -106,7 +113,7 @@ We applied a few mechanism that will increase the buying pressure of $NEUTRO wit ### Legal Structure -- **Registered Legal Entity:** PT Nava Labs +- **Registered Legal Entity:** Nava Labs Inc. - **Registered Address:** Foresta Fiore B3 No 10 BSD, Tangerang Selatan, Indonesia ### Team Experience @@ -224,13 +231,21 @@ Upon implementing all the aforementioned updates, we anticipate a notable surge As we look to the future of Neutroswap and EOS EVM, we believe that a grant to bring liquidity to the platform is essential. We've been proud to build Neutroswap without raising any investment from VC firms, and we're hopeful that ENF will see the value in our work and provide the support we need to continue to grow and innovate on EOS EVM. We have done our best to trigger the initial wave of EOS EVM by becoming: - -1. The first DApp that reached $1,000,000 in TVL -2. The first EOS EVM token listed on Coingecko +1. The first DApp that reached $1,500,000 in TVL in EOS EVM +2. The first EOS EVM token listed on best platforms: +- [Debank](https://debank.com/protocols/eos_neutroswap/assets) +- [Crypto.com](https://crypto.com/price/neutroswap) +- [Coingecko](https://www.coingecko.com/en/coins/neutroswap) +- [CoinMarketCap](https://coinmarketcap.com/dexscan/networks/eos-evm/) +- [GeckoTerminal](https://www.geckoterminal.com/eos-evm/pools/0xb3fb2548287bcadd5a045270b3182c1fc6318684) +- [DappRadar](https://dappradar.com/dapp/neutroswap) +- [Ave.ai](https://ave.ai/token/0xf4bd487a8190211e62925435963d996b59a860c0-eos?from=Default) 3. The first working app on EOS EVM and has active users. -4. Bring more than 2000+ transactions on average per day since launch -5. Bring $150,000+ volume daily accross Neutroswap V2 DEX -6. The first project that triggers influencers to look at EOS EVM +4. Bring more than 7500+ transactions on average per day since launch. +5. Bring $150,000+ volume daily accross Neutroswap pool. +6. The first project that triggers influencers to look at EOS EVM. +7. $NEUTRO all-time price $0.41 +8. [Burned 98% of max supply](https://twitter.com/Neutroswap/status/1653759171664429056?s=20) (980,000,000 $NEUTRO) By supporting Neutroswap as a catalyst project, ENF can help to attract the attention of other EVM developers and encourage them to build on EOS EVM. This can lead to an influx of proposals seeking grants, which would be a welcome problem for ENF to have. However, the most important thing is to generate traction, volume, TVL, and attract more users, especially builders, to the EOS EVM ecosystem. With ENF's support, we can continue to lead the charge and set the standard for innovation and growth in EOS EVM. @@ -239,7 +254,7 @@ Thank you for considering our proposal Links: - Website: https://neutroswap.io/ -- Audit: https://github.com/solidproof/projects/tree/main/NeutroSwap +- V1 Audit: https://github.com/solidproof/projects/tree/main/NeutroSwap - Docs: https://docs.neutroswap.io/ - DefiLlama: https://defillama.com/protocol/neutroswap - Debank: https://debank.com/protocols/eos_neutroswap/assets From d60dbffe2ed02c46e8f9004507fe2645c9a6160b Mon Sep 17 00:00:00 2001 From: Jonas Sunandar Date: Fri, 19 May 2023 21:42:25 +0700 Subject: [PATCH 137/170] New legal name add mailing address and company name --- applications/tokenomics_enhancement_neutroswap.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/applications/tokenomics_enhancement_neutroswap.md b/applications/tokenomics_enhancement_neutroswap.md index 4eece223..03dfc79b 100644 --- a/applications/tokenomics_enhancement_neutroswap.md +++ b/applications/tokenomics_enhancement_neutroswap.md @@ -114,7 +114,7 @@ Currently, EOS EVM needs more TVL to achieve organic exposure and attract new us ### Legal Structure - **Registered Legal Entity:** Nava Labs Inc. -- **Registered Address:** Foresta Fiore B3 No 10 BSD, Tangerang Selatan, Indonesia +- **Registered Address:** 8 The Green STE R Dover, DE 19901 Delaware ### Team Experience From d729b62d096ec36b42a36ebc6a824cb4374a7130 Mon Sep 17 00:00:00 2001 From: Jonas Sunandar Date: Fri, 19 May 2023 21:49:12 +0700 Subject: [PATCH 138/170] Update tokenomics_enhancement_neutroswap.md add numbering in new tokenomics --- applications/tokenomics_enhancement_neutroswap.md | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/applications/tokenomics_enhancement_neutroswap.md b/applications/tokenomics_enhancement_neutroswap.md index 03dfc79b..92a8ca1f 100644 --- a/applications/tokenomics_enhancement_neutroswap.md +++ b/applications/tokenomics_enhancement_neutroswap.md @@ -46,9 +46,11 @@ We have successfully launched $NEUTRO token alongside our Neutroswap V1: 7. $NEUTRO all-time price $0.41 8. [Burned 98% of max supply](https://twitter.com/Neutroswap/status/1653759171664429056?s=20) (980,000,000 $NEUTRO) +### New tokenomics + We are shifting our focus to enhance the utility and value of the $NEUTRO token. Previously, it was primarily utilized for incentivizing users through Neutro Farms and Vaults. Our plan now includes introducing $xNEUTRO, a locked version of the token similar to $veCRV by Curve Finance. Additionally, we will implement various updates such as Plugins, a new distribution mechanism for protocol revenue, a deflationary mechanism, and spNFTs. -[**xNEUTRO**](https://docs.neutroswap.io/neutroswap-v2-coming-soon/xneutro-token) +#### [**1. xNEUTRO**](https://docs.neutroswap.io/neutroswap-v2-coming-soon/xneutro-token) $xNEUTRO will be non-transferable and act as our governance token. $xNEUTRO main utility is the ability for it to be allocated by users to our various [plugins](https://docs.neutroswap.io/neutroswap-v2-coming-soon/plugins) such as: @@ -56,11 +58,11 @@ $xNEUTRO will be non-transferable and act as our governance token. $xNEUTRO main - [Yield Multiplier](https://docs.neutroswap.io/neutroswap-v2-coming-soon/plugins/yield-multiplier): Boosting users' yield up to 2x - [Launchpad](https://docs.neutroswap.io/neutroswap-v2-coming-soon/plugins/launchpad): Giving priority access to $xNEUTRO holders allocating to this plugin more exclusivity access to Neutroswap upcoming Launchpad -[**Staked Positions NFT (spNFTs)**](https://docs.neutroswap.io/neutroswap-v2-coming-soon/staked-positions-spnfts) +#### [**2. Staked Positions NFT (spNFTs)**](https://docs.neutroswap.io/neutroswap-v2-coming-soon/staked-positions-spnfts) The upcoming mechanism will replace the existing Neutro Farms as they both serve similar purposes. The key distinction is that instead of solely depositing LP tokens into the Farms smart contract, users will receive spNFTs in exchange for their deposited LP tokens, making it tradeable. -[**Protocol Revenue Distribution**](https://docs.neutroswap.io/neutroswap-v2-coming-soon/protocol-revenue) +#### [**3. Protocol Revenue Distribution**](https://docs.neutroswap.io/neutroswap-v2-coming-soon/protocol-revenue) The protocol-generated revenue will be distributed as follows: @@ -71,7 +73,7 @@ The protocol-generated revenue will be distributed as follows: The Core Contributors funds will be solely utilized to cover operational expenses. At the end of each month, any remaining unused amount will be reallocated at the team's discretion, either towards Dividends or for Buyback and Burn purposes. -[**Deflationary Mechanism**](https://docs.neutroswap.io/neutroswap-v2-coming-soon/deflationary-mechanism) +#### [**4. Deflationary Mechanism**](https://docs.neutroswap.io/neutroswap-v2-coming-soon/deflationary-mechanism) We applied a few mechanism that will increase the buying pressure of $NEUTRO with the aim of making it for attractive for future investors, while increasing value for $NEUTRO holders. @@ -82,7 +84,8 @@ We applied a few mechanism that will increase the buying pressure of $NEUTRO wit ### Ecosystem Fit - Where and how does your project fit into the ecosystem? -Currently, EOS EVM needs more TVL to achieve organic exposure and attract new users. That's why we're thrilled to have already seen significant growth since our launch. But we're not stopping there. Our team is committed to further strengthening EOS EVM by providing even more value through our upcoming V2 version. With V2, we're confident that we can continue to drive growth and make EOS EVM an even more vibrant and successful ecosystem +Currently, EOS EVM needs more TVL to achieve organic exposure and attract new users. That's why we're thrilled to have already seen significant growth since our launch. But we're not stopping there. Our team is committed to further strengthening EOS EVM by providing even more value through our new tokenomics. With $xNEUTRO, we're confident that we can continue to drive growth and make EOS EVM an even more vibrant and successful ecosystem + - Who is your target audience (chain/dapp/wallet/UI developers, designers, your own user base, some dapp's userbase, yourself)? Farmers, DeFi users, crypto users in general, traders From 613da69899173d94884116baac699633a579dabf Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Fri, 19 May 2023 16:25:29 -0400 Subject: [PATCH 139/170] Update ru-check-filename.yml --- .github/workflows/ru-check-filename.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/.github/workflows/ru-check-filename.yml b/.github/workflows/ru-check-filename.yml index 93b718f6..085958ca 100644 --- a/.github/workflows/ru-check-filename.yml +++ b/.github/workflows/ru-check-filename.yml @@ -19,18 +19,18 @@ jobs: runs-on: ubuntu-latest steps: - name: test-has-md - if: ${{ endsWith(github.event.inputs.filename, '.md') }} + if: ${{ endsWith(inputs.filename, '.md') }} run: | - echo "filename ${{github.event.inputs.filename}} ends with .md" + echo "filename ${{inputs.filename}} ends with .md" - name: test-missing-md - if: ${{ !endsWith(github.event.inputs.filename, '.md') }} + if: ${{ !endsWith(inputs.filename, '.md') }} uses: actions/github-script@v6 with: script: | - core.setFailed('filename ${{github.event.inputs.filename}} does not end with .md') + core.setFailed('filename ${{inputs.filename}} does not end with .md') - name: test-spaces - if: ${{ contains(github.event.inputs.filename, ' ') }} + if: ${{ contains(inputs.filename, ' ') }} uses: actions/github-script@v6 with: script: | - core.setFailed('filename \'${{github.event.inputs.filename}}\' cannot contain spaces. Exiting.') + core.setFailed('filename \'${{inputs.filename}}\' cannot contain spaces. Exiting.') From 8c3930fb81dfa86eae7db67d4a4f2864d0354808 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Fri, 19 May 2023 16:31:32 -0400 Subject: [PATCH 140/170] Perform filename checking and exit if bad Perform filename checking and exit if bad --- .github/workflows/pr-received.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/pr-received.yml b/.github/workflows/pr-received.yml index 69d49d23..59c89dda 100644 --- a/.github/workflows/pr-received.yml +++ b/.github/workflows/pr-received.yml @@ -40,7 +40,7 @@ jobs: uses: ./.github/workflows/ru-big-parser.yml with: filename: "${{ needs.get_filename.outputs.filename }}" - needs: get_filename + needs: [get_filename, testfile] echo-the-returned-fields: runs-on: ubuntu-latest From a19ee836d22bdb2775d3512e90a3b7c034c17838 Mon Sep 17 00:00:00 2001 From: Jonas Sunandar Date: Mon, 22 May 2023 19:17:30 +0800 Subject: [PATCH 141/170] Add V2 plugins illustration --- applications/tokenomics_enhancement_neutroswap.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/applications/tokenomics_enhancement_neutroswap.md b/applications/tokenomics_enhancement_neutroswap.md index 92a8ca1f..5c832eeb 100644 --- a/applications/tokenomics_enhancement_neutroswap.md +++ b/applications/tokenomics_enhancement_neutroswap.md @@ -50,6 +50,8 @@ We have successfully launched $NEUTRO token alongside our Neutroswap V1: We are shifting our focus to enhance the utility and value of the $NEUTRO token. Previously, it was primarily utilized for incentivizing users through Neutro Farms and Vaults. Our plan now includes introducing $xNEUTRO, a locked version of the token similar to $veCRV by Curve Finance. Additionally, we will implement various updates such as Plugins, a new distribution mechanism for protocol revenue, a deflationary mechanism, and spNFTs. +![Neutroswap V2 Plugins](https://drive.google.com/uc?export=view&id=1mk7WXKT4kBm8e272KN55_GdxFv1OANlb) + #### [**1. xNEUTRO**](https://docs.neutroswap.io/neutroswap-v2-coming-soon/xneutro-token) $xNEUTRO will be non-transferable and act as our governance token. $xNEUTRO main utility is the ability for it to be allocated by users to our various [plugins](https://docs.neutroswap.io/neutroswap-v2-coming-soon/plugins) such as: From 77482f4d7f435018e64855ba9b121491cc192246 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Mon, 22 May 2023 11:37:15 -0400 Subject: [PATCH 142/170] upgrade gsheet-action to latest version This should eliminate those node12 warnings. --- .github/workflows/ru-big-gsheet.yml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.github/workflows/ru-big-gsheet.yml b/.github/workflows/ru-big-gsheet.yml index ab501c25..a581b4cb 100644 --- a/.github/workflows/ru-big-gsheet.yml +++ b/.github/workflows/ru-big-gsheet.yml @@ -57,7 +57,8 @@ jobs: runs-on: ubuntu-latest steps: - id: 'update_worksheet' - uses: jroehl/gsheet.action@v1.2.0 + #uses: jroehl/gsheet.action@v1.2.0 + uses: jroehl/gsheet.action@v2.0.1 with: spreadsheetId: 1hTRqt_iGDmFvwbn9leKwr7e-tL9eqHS3-h_dDP5Fpu8 commands: | From 31fda2fdd5e548a04160d444dec68a6f7cdfe045 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Mon, 22 May 2023 14:27:04 -0400 Subject: [PATCH 143/170] Update to latest actions for node16 updated the latest for node 16 Ana06/get-changed-files@v2.0.0 jroehl/gsheet.action@v1.2.0 --- .github/workflows/grant-translated.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/grant-translated.yaml b/.github/workflows/grant-translated.yaml index 4d496bd9..81ff45b4 100644 --- a/.github/workflows/grant-translated.yaml +++ b/.github/workflows/grant-translated.yaml @@ -16,7 +16,7 @@ jobs: steps: - name: Get grant application file name id: 'files' - uses: Ana06/get-changed-files@v2.0.0 + uses: Ana06/get-changed-files@v2.2.0 with: filter: 'applications/*.md' @@ -64,7 +64,7 @@ jobs: runs-on: ubuntu-latest steps: - id: 'update_worksheet' - uses: jroehl/gsheet.action@v1.2.0 + uses: jroehl/gsheet.action@v2.0.1 with: #spreadsheetId: 1FsNUKcfAJAorZGHpEzbRKLVYWbpZ_93Ts-R-JTpRK_A #This is the DummyTest sheet spreadsheetId: 1RdSK5Y_URnTSzg__fRHV51jwO90x4AUMy0ym0ytWwKA From 19275598fbc314ba30c3178c3094168cc9f2865e Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Mon, 22 May 2023 14:35:18 -0400 Subject: [PATCH 144/170] Update grant-committee-approved.yml Update to latest version of Ana06/get-changed-files to removed node12 warnings. --- .github/workflows/grant-committee-approved.yml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.github/workflows/grant-committee-approved.yml b/.github/workflows/grant-committee-approved.yml index 272d8e63..f5c7bfd1 100644 --- a/.github/workflows/grant-committee-approved.yml +++ b/.github/workflows/grant-committee-approved.yml @@ -5,6 +5,7 @@ # grant-committee-approved.yml # # Ted Cahall 31May2022 +# Updated to remove node12 warnings 22May2023 name: Grant Committee Approved @@ -28,7 +29,7 @@ jobs: steps: - name: Get application file name id: 'files' - uses: Ana06/get-changed-files@v2.0.0 + uses: Ana06/get-changed-files@v2.2.0 with: filter: 'applications/*.md' From e48b0a87394841b08b0000c57ce15618aa152524 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Mon, 22 May 2023 14:36:51 -0400 Subject: [PATCH 145/170] Update grant-fully-approved.yml Updated Ana06/get-changed-files@v2.2.0 to remove node12 warnings. --- .github/workflows/grant-fully-approved.yml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.github/workflows/grant-fully-approved.yml b/.github/workflows/grant-fully-approved.yml index 9a4d63f6..1abd174f 100644 --- a/.github/workflows/grant-fully-approved.yml +++ b/.github/workflows/grant-fully-approved.yml @@ -5,6 +5,7 @@ # grant-fully-approved.yml # # Ted Cahall 28May2022 +# Updated to remove node12 warnings 22May2023 - Ana06/get-changed-files@v2.2.0 name: Grant Fully Approved @@ -28,7 +29,7 @@ jobs: steps: - name: Get application file name id: 'files' - uses: Ana06/get-changed-files@v2.0.0 + uses: Ana06/get-changed-files@v2.2.0 with: filter: 'applications/*.md' From 91d78f79ffdb6e8e1797df71aeee1a7c7b3e86a7 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Mon, 22 May 2023 14:56:22 -0400 Subject: [PATCH 146/170] updated to jroehl/gsheet.action@v2.0.1 updated to latest jroehl/gsheet.action@v2.0.1 to supress node12 warnings --- .github/workflows/reusable-gsheet.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/.github/workflows/reusable-gsheet.yml b/.github/workflows/reusable-gsheet.yml index d91049ad..31f76284 100644 --- a/.github/workflows/reusable-gsheet.yml +++ b/.github/workflows/reusable-gsheet.yml @@ -1,3 +1,5 @@ +# Write the dummy spreadsheet for testing etc. +# 22May2023 - updated to latest jroehl/gsheet.action@v2.0.1 to supress node12 warnings name: Reusable Gsheet Update on: workflow_call: @@ -14,8 +16,9 @@ jobs: runs-on: ubuntu-latest steps: - id: 'update_worksheet' - uses: jroehl/gsheet.action@v1.2.0 + uses: jroehl/gsheet.action@v2.0.1 with: + # this is the dummy spreadsheet spreadsheetId: 1FsNUKcfAJAorZGHpEzbRKLVYWbpZ_93Ts-R-JTpRK_A commands: | [ From 10798752f540d697b2981661fa9a49ca71acd4a1 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Mon, 22 May 2023 14:59:16 -0400 Subject: [PATCH 147/170] updated to dawidd6/action-send-mail@v3.7.1 updated to dawidd6/action-send-mail@v3.7.1 to supress node12 warnings --- .github/workflows/ru-committee-approved-email.yml | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/.github/workflows/ru-committee-approved-email.yml b/.github/workflows/ru-committee-approved-email.yml index 570019f2..fcd2042b 100644 --- a/.github/workflows/ru-committee-approved-email.yml +++ b/.github/workflows/ru-committee-approved-email.yml @@ -2,6 +2,7 @@ # and now will go to the evaluators. Gives them instructions on next steps. # # Ted Cahall 26May2022 +# 22May2023 - updated to dawidd6/action-send-mail@v3.7.1 to supress node12 warnings name: Committee Approved Email to Grantee on: @@ -34,7 +35,7 @@ jobs: runs-on: ubuntu-latest steps: - name: send email - uses: dawidd6/action-send-mail@v3.6.1 + uses: dawidd6/action-send-mail@v3.7.1 with: server_address: smtp.gmail.com server_port: 465 @@ -69,7 +70,7 @@ jobs: Best,
ENF Operations Team to: ${{inputs.app_email}} - from: grants@eosn.foundation - reply_to: grants@eosn.foundation - bcc: grants@eosn.foundation + from: grants@eosnetwork.com + reply_to: grants@eosnetwork.com + bcc: grants@eosnetwork.com From 5af3c93d792ce95b5c7b67ca1418a76a4c5d62e9 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Mon, 22 May 2023 15:00:53 -0400 Subject: [PATCH 148/170] updated to dawidd6/action-send-mail@v3.7.1 updated to dawidd6/action-send-mail@v3.7.1 to supress node12 warnings --- .github/workflows/ru-fully-approved-email.yml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.github/workflows/ru-fully-approved-email.yml b/.github/workflows/ru-fully-approved-email.yml index bb0a5f1b..7d0233e9 100644 --- a/.github/workflows/ru-fully-approved-email.yml +++ b/.github/workflows/ru-fully-approved-email.yml @@ -3,6 +3,7 @@ # They can now begin coding and submit their milestones. # # Ted Cahall 28May2022 +# 22May2023 - updated to dawidd6/action-send-mail@v3.7.1 to supress node12 warnings name: Fully Approved Email to Grantee on: @@ -35,7 +36,7 @@ jobs: runs-on: ubuntu-latest steps: - name: send email - uses: dawidd6/action-send-mail@v3.6.1 + uses: dawidd6/action-send-mail@v3.7.1 with: server_address: smtp.gmail.com server_port: 465 From 99074114130353b3318165bfeb442cd71038fdcf Mon Sep 17 00:00:00 2001 From: Lilbansheemebe <106165820+Lilbansheemebe@users.noreply.github.com> Date: Fri, 26 May 2023 18:10:04 -0400 Subject: [PATCH 149/170] Update accepted_grant_applications.md --- docs/accepted_grant_applications.md | 61 ++++++++++++++++++++--------- 1 file changed, 42 insertions(+), 19 deletions(-) diff --git a/docs/accepted_grant_applications.md b/docs/accepted_grant_applications.md index c54cb44f..cef97aae 100644 --- a/docs/accepted_grant_applications.md +++ b/docs/accepted_grant_applications.md @@ -6,51 +6,74 @@ ## Table of Contents -- [2023](#2023) - - [Season 5 - First Quarter 2023](#wave-5---first-quarter-2023) +- [2023](https://github.com/eosnetworkfoundation/grant-framework/edit/main/docs/accepted_grant_applications.md#2023) + - [Season 6 - Second Quarter 2023](https://github.com/eosnetworkfoundation/grant-framework/edit/main/docs/accepted_grant_applications.md#season-6---second-quarter-2023) + - [Season 5 - First Quarter 2023](https://github.com/eosnetworkfoundation/grant-framework/edit/main/docs/accepted_grant_applications.md#season-5---first-quarter-2023) -- [2022](#2022) - - [Season 4 - Fourth Quarter 2022](#wave-4---fourth-quarter-2022) - - [Season 3 - Third Quarter 2022](#wave-3---third-quarter-2022) - - [Season 2 - Second Quarter 2022](#wave-2---second-quarter-2022) - - [Season 1 - First Quarter 2022](#wave-1---first-quarter-2022) +- [2022](https://github.com/eosnetworkfoundation/grant-framework/edit/main/docs/accepted_grant_applications.md#2022) + - [Season 4 - Fourth Quarter 2022](https://github.com/eosnetworkfoundation/grant-framework/edit/main/docs/accepted_grant_applications.md#season-4---fourth-quarter-2022) + - [Season 3 - Third Quarter 2022](https://github.com/eosnetworkfoundation/grant-framework/edit/main/docs/accepted_grant_applications.md#season-3---third-quarter-2022) + - [Season 2 - Second Quarter 2022](https://github.com/eosnetworkfoundation/grant-framework/edit/main/docs/accepted_grant_applications.md#season-2---second-quarter-2022) + - [Season 1 - First Quarter 2022](https://github.com/eosnetworkfoundation/grant-framework/edit/main/docs/accepted_grant_applications.md#season-1---first-quarter-2022) # 2023 -## Wave 1 - First Quarter 2023 + + + + + + +## Season 6 - Second Quarter 2023 + +| Team | Project Name / Application | Repo | Terminated | First Delivery | Completed +| :--- | :------ | :--- | :--------: | :------------: | :-------: | +| [FACINGS, Inc.](https://facings.io) | [NFT Collection Manager Stage 2](../applications/facings-nft-collection-manager-stage-2.md) | [GitHub](https://github.com/FACINGS) |
  • [ ]
|
  • [X]
|
  • [ ]
| +| [Animus Labs LTD (representing Boid.com)](https://www.animus.is) | [Antelope Firewall](../applications/antelopeio_firewall.md) | [GitHub](https://github.com/mchosc) |
  • [ ]
|
  • [ ]
|
  • [ ]
| +| [Creamy Vainilla C.A](https://eosvision.io/) | [EOS VISIONS](../applications/eosreddit2.md) | [GitHub](https://github.com/Creamyvanill) |
  • [ ]
|
  • [ ]
|
  • [ ]
| +| [Alphabox Solutions Pte. Ltd.](https://alphaday.com/) | [Alphaday](../applications/alphaday.md) | [GitHub](https://github.com/Mikael337) |
  • [ ]
|
  • [ ]
|
  • [ ]
| + + +## Season 5 - First Quarter 2023 | Team | Project Name / Application | Repo | Terminated | First Delivery | Completed | :--- | :------ | :--- | :--------: | :------------: | :-------: | -| [Name](https://example.com/) | [ProjectName](../applications/application-template.md) | [GitHub](https://github.com/eosnetworkfoundation) |
  • [ ]
|
  • [ ]
|
  • [ ]
| +| [Defibox](https://eos.defibox.io/vault) | [Vault Protocol](../applications/Defibox_vault.md) | [GitHub](https://github.com/defiboxswap) |
  • [ ]
|
  • [ ]
|
  • [ ]
| +| EVMNS Labs | [EVMNS (EVM Name Service)](../applications/EVMNS.md) | [GitHub](https://github.com/evmns) |
  • [ ]
|
  • [X]
|
  • [ ]
| # 2022 -## Wave 4 - Fourth Quarter 2022 +## Season 4 - Fourth Quarter 2022 | Team | Project Name / Application | Repo | Terminated | First Delivery | Completed | :--- | :------ | :--- | :--------: | :------------: | :-------: | -| [Name](https://example.com/) | [ProjectName](../applications/application-template.md) | [GitHub](https://github.com/eosnetworkfoundation) |
  • [ ]
|
  • [ ]
|
  • [ ]
| +| [Lowkey codes](https://delightlabs.io/) | [Research for building Rust Antelope CDT](../applications/cost-comparing-research-rust-cdt.md) | [GitHub](https://github.com/DELIGHT-LABS) |
  • [ ]
|
  • [X]
|
  • [ ]
| -## Wave 3 - Third Quarter 2022 +## Season 3 - Third Quarter 2022 | Team | Project Name / Application | Repo | Terminated | First Delivery | Completed | :--- | :------ | :--- | :--------: | :------------: | :-------: | -| [Name](https://example.com/) | [ProjectName](../applications/application-template.md) | [GitHub](https://github.com/eosnetworkfoundation) |
  • [ ]
|
  • [ ]
|
  • [ ]
| +| [Zaisan BV](https://zaisan.io/about/) | [EOSIO Smart Contract Developer's Handbook](../applications/dev_book.md) | [GitHub](https://github.com/cc32d9) |
  • [ ]
|
  • [ ]
|
  • [X]
| +| [FACINGS, Inc.](https://facings.io) | [NFT Collection Manager Stage 1](../applications/facings-nft-collection-manager.md) | [GitHub](https://github.com/FACINGS) |
  • [ ]
|
  • [ ]
|
  • [X]
| +| [Nice1](https://nice1.org/) | [NICE1 Tools Ecosystem](../applications/nice1-tools-ecosystem.md) | [GitHub](https://github.com/nice1-blockchain) |
  • [ ]
|
  • [ ]
|
  • [ ]
| +| [Creamy Vainilla C.A](https://eosvision.io/) | [EOS VISIONS](../applications/eosreddit.md) | [GitHub](https://github.com/Creamyvanill) |
  • [ ]
|
  • [ ]
|
  • [X]
| +| [Tonomy Foundation](https://tonomy.foundation) | [Verifiable Credentials for the EOSIO SSI Toolkit](../applications/ssi-toolkit-verifiable-credentials.md) | [GitHub](https://github.com/Tonomy-Foundation) |
  • [ ]
|
  • [X]
|
  • [ ]
| +| [Agenix LLC](https://welcomewagon.ai) | [WelcomeWagon Cards](../applications/WelcomeWagonEngagement.md) | [GitHub](https://github.com/ChuckMacDonald) |
  • [ ]
|
  • [X]
|
  • [ ]
| -## Wave 2 - Second Quarter 2022 +## Season 2 - Second Quarter 2022 | Team | Project Name / Application | Repo | Terminated | First Delivery | Completed | :--- | :------ | :--- | :--------: | :------------: | :-------: | | [Time2Discover](https://time2discover.no/) | [The Lost Diamond](../applications/TheLostDiamond_BjornOmsland.md) | [GitHub](https://github.com/bjornomsland) |
  • [ ]
|
  • [ ]
|
  • [ ]
| -| [ZeroPass](https://zeropass.io/) | [EOS Cryptography Proposal](../applications/eos-cryptography-proposal.md) | [GitHub](https://github.com/ZeroPass/eosio.ck) |
  • [ ]
|
  • [x]
|
  • [ ]
| -| [GenerEOS Pty Ltd](https://genereos.io/) | [Smart Contract Testing](../applications/genereos-testing-libraries.md) | [GitHub](https://github.com/generEOS) |
  • [ ]
|
  • [ ]
|
  • [ ]
| -| [CETF](https://github.com/n0umen0n) | [Crypto Exchange Traded Funds](../applications/CETF.md) | [GitHub](https://github.com/n0umen0n) |
  • [ ]
|
  • [ ]
|
  • [ ]
| +| [ZeroPass](https://zeropass.io/) | [EOS Cryptography Proposal 1/2](../applications/eos-cryptography-proposal.md) | [GitHub](https://github.com/ZeroPass/eosio.ck) |
  • [ ]
|
  • [ ]
|
  • [X]
| +| [GenerEOS Pty Ltd](https://genereos.io/) | [Smart Contract Testing](../applications/genereos-testing-libraries.md) | [GitHub](https://github.com/generEOS) |
  • [ ]
|
  • [ ]
|
  • [X]
| +| [CETF](https://github.com/n0umen0n) | [Crypto Exchange Traded Funds](../applications/CETF.md) | [GitHub](https://github.com/n0umen0n) |
  • [ ]
|
  • [X]
|
  • [ ]
| | [TrustSwap](https://trustswap-testnet.web.app/) | [Trust Swap](../applications/trustswap.md) | [GitHub](https://github.com/evm20) |
  • [ ]
|
  • [ ]
|
  • [ ]
| -| [Zaisan BV](https://zaisan.io/about/) | [Chronicle](../applications/chronicle.md) | [GitHub](https://github.com/EOSChronicleProject/eos-chronicle) |
  • [ ]
|
  • [ ]
|
  • [ ]
| +| [Zaisan BV](https://zaisan.io/about/) | [Chronicle](../applications/chronicle.md) | [GitHub](https://github.com/EOSChronicleProject/eos-chronicle) |
  • [ ]
|
  • [X]
|
  • [ ]
| -## Wave 1 - First Quarter 2022 +## Season 1 - First Quarter 2022 The ENF Grant Framework Launched in 2022 Q2 From 4be4be3d318228299a0a698b8e3a4abc096f04e8 Mon Sep 17 00:00:00 2001 From: Lilbansheemebe <106165820+Lilbansheemebe@users.noreply.github.com> Date: Fri, 26 May 2023 18:14:26 -0400 Subject: [PATCH 150/170] Update accepted_grant_applications.md --- docs/accepted_grant_applications.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/docs/accepted_grant_applications.md b/docs/accepted_grant_applications.md index cef97aae..fb85b1ba 100644 --- a/docs/accepted_grant_applications.md +++ b/docs/accepted_grant_applications.md @@ -6,15 +6,15 @@ ## Table of Contents -- [2023](https://github.com/eosnetworkfoundation/grant-framework/edit/main/docs/accepted_grant_applications.md#2023) - - [Season 6 - Second Quarter 2023](https://github.com/eosnetworkfoundation/grant-framework/edit/main/docs/accepted_grant_applications.md#season-6---second-quarter-2023) - - [Season 5 - First Quarter 2023](https://github.com/eosnetworkfoundation/grant-framework/edit/main/docs/accepted_grant_applications.md#season-5---first-quarter-2023) - -- [2022](https://github.com/eosnetworkfoundation/grant-framework/edit/main/docs/accepted_grant_applications.md#2022) - - [Season 4 - Fourth Quarter 2022](https://github.com/eosnetworkfoundation/grant-framework/edit/main/docs/accepted_grant_applications.md#season-4---fourth-quarter-2022) - - [Season 3 - Third Quarter 2022](https://github.com/eosnetworkfoundation/grant-framework/edit/main/docs/accepted_grant_applications.md#season-3---third-quarter-2022) - - [Season 2 - Second Quarter 2022](https://github.com/eosnetworkfoundation/grant-framework/edit/main/docs/accepted_grant_applications.md#season-2---second-quarter-2022) - - [Season 1 - First Quarter 2022](https://github.com/eosnetworkfoundation/grant-framework/edit/main/docs/accepted_grant_applications.md#season-1---first-quarter-2022) +- [2023](https://github.com/eosnetworkfoundation/grant-framework/main/docs/accepted_grant_applications.md#2023) + - [Season 6 - Second Quarter 2023](https://github.com/eosnetworkfoundation/grant-framework/main/docs/accepted_grant_applications.md#season-6---second-quarter-2023) + - [Season 5 - First Quarter 2023](https://github.com/eosnetworkfoundation/grant-framework/main/docs/accepted_grant_applications.md#season-5---first-quarter-2023) + +- [2022](https://github.com/eosnetworkfoundation/grant-framework/main/docs/accepted_grant_applications.md#2022) + - [Season 4 - Fourth Quarter 2022](https://github.com/eosnetworkfoundation/grant-framework/main/docs/accepted_grant_applications.md#season-4---fourth-quarter-2022) + - [Season 3 - Third Quarter 2022](https://github.com/eosnetworkfoundation/grant-framework/main/docs/accepted_grant_applications.md#season-3---third-quarter-2022) + - [Season 2 - Second Quarter 2022](https://github.com/eosnetworkfoundation/grant-framework/main/docs/accepted_grant_applications.md#season-2---second-quarter-2022) + - [Season 1 - First Quarter 2022](https://github.com/eosnetworkfoundation/grant-framework/main/docs/accepted_grant_applications.md#season-1---first-quarter-2022) # 2023 From 35b3d429a9ffb11f5c4d670f4b8411d981560933 Mon Sep 17 00:00:00 2001 From: Lilbansheemebe <106165820+Lilbansheemebe@users.noreply.github.com> Date: Fri, 26 May 2023 18:15:45 -0400 Subject: [PATCH 151/170] Update accepted_grant_applications.md --- docs/accepted_grant_applications.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/docs/accepted_grant_applications.md b/docs/accepted_grant_applications.md index fb85b1ba..c05b3d52 100644 --- a/docs/accepted_grant_applications.md +++ b/docs/accepted_grant_applications.md @@ -6,15 +6,15 @@ ## Table of Contents -- [2023](https://github.com/eosnetworkfoundation/grant-framework/main/docs/accepted_grant_applications.md#2023) - - [Season 6 - Second Quarter 2023](https://github.com/eosnetworkfoundation/grant-framework/main/docs/accepted_grant_applications.md#season-6---second-quarter-2023) - - [Season 5 - First Quarter 2023](https://github.com/eosnetworkfoundation/grant-framework/main/docs/accepted_grant_applications.md#season-5---first-quarter-2023) - -- [2022](https://github.com/eosnetworkfoundation/grant-framework/main/docs/accepted_grant_applications.md#2022) - - [Season 4 - Fourth Quarter 2022](https://github.com/eosnetworkfoundation/grant-framework/main/docs/accepted_grant_applications.md#season-4---fourth-quarter-2022) - - [Season 3 - Third Quarter 2022](https://github.com/eosnetworkfoundation/grant-framework/main/docs/accepted_grant_applications.md#season-3---third-quarter-2022) - - [Season 2 - Second Quarter 2022](https://github.com/eosnetworkfoundation/grant-framework/main/docs/accepted_grant_applications.md#season-2---second-quarter-2022) - - [Season 1 - First Quarter 2022](https://github.com/eosnetworkfoundation/grant-framework/main/docs/accepted_grant_applications.md#season-1---first-quarter-2022) +- [2023](https://github.com/eosnetworkfoundation/grant-framework/blob/main/docs/accepted_grant_applications.md#2023) + - [Season 6 - Second Quarter 2023](https://github.com/eosnetworkfoundation/grant-framework/blob/main/docs/accepted_grant_applications.md#season-6---second-quarter-2023) + - [Season 5 - First Quarter 2023](https://github.com/eosnetworkfoundation/grant-framework/blob/main/docs/accepted_grant_applications.md#season-5---first-quarter-2023) + +- [2022](https://github.com/eosnetworkfoundation/grant-framework/blob/main/docs/accepted_grant_applications.md#2022) + - [Season 4 - Fourth Quarter 2022](https://github.com/eosnetworkfoundation/grant-framework/blob/main/docs/accepted_grant_applications.md#season-4---fourth-quarter-2022) + - [Season 3 - Third Quarter 2022](https://github.com/eosnetworkfoundation/grant-framework/blob/main/docs/accepted_grant_applications.md#season-3---third-quarter-2022) + - [Season 2 - Second Quarter 2022](https://github.com/eosnetworkfoundation/grant-framework/blob/main/docs/accepted_grant_applications.md#season-2---second-quarter-2022) + - [Season 1 - First Quarter 2022](https://github.com/eosnetworkfoundation/grant-framework/blob/main/docs/accepted_grant_applications.md#season-1---first-quarter-2022) # 2023 From be9251d710d64a8a3fee79d3abea75a2c739578d Mon Sep 17 00:00:00 2001 From: uddina Date: Sun, 28 May 2023 15:09:25 +0100 Subject: [PATCH 152/170] Completed Application --- applications/knockout_wars_game.md | 222 +++++++++++++++++++++++++++++ 1 file changed, 222 insertions(+) create mode 100644 applications/knockout_wars_game.md diff --git a/applications/knockout_wars_game.md b/applications/knockout_wars_game.md new file mode 100644 index 00000000..71803d60 --- /dev/null +++ b/applications/knockout_wars_game.md @@ -0,0 +1,222 @@ +# EOS Network Foundation Grant Proposal + +- **Project Name:** Knockout Wars Game +- **Team Name:** Gami Studio +- **EOS Payment Address:** junaydcrypto +- **[Level](https://github.com/eosnetworkfoundation/grant-framework#grant-levels):** 2 +- **Pomelo Grant(s):** N/A +- **Project is Open-Source:** Yes +- **Project was part of Token sale:** Yes +- **Repository where Project resides:** + + +## Contact + +- **Contact Name:** Junayd Miah +- **Contact Email:** junayd@gami.me +- **Website:** http://www.gami.me + + +## Project Overview + +This is a proposal to build & launch Knockout Wars Game on EOS EVM + +### Overview + +> Please provide the following: + +- **Name:** Knockout Wars, a Mobile Multiplayer Fireball Fighting Game +- **Brief Description:** We want to be the 1st Mobile Skill based fighting game on EOS EVM that is set up for mass adoption. + +We expect to achieve 100,000-125,000 YouTube views promoting our game tournaments with EOS EVM being the sponsor and receiving shout outs from the Influencers, generating much needed awareness of EOS EVM in the social space. + +We want to introduce our community to EOS (95K on Twitter & 22K on TG & 10K on YouTube) + +We want to grow our current MAU (closed beta) from 1,000 to 10,000 (10X increase) resulting in 100,000 games showcasing the EOS EVM branding inside the game. +All the above will result in EOS EVM gaining new exposure to new gaming communities. +- **Relationship to EOS Network / Antelope:** Enhance the EOS Gamefi ecosystem via EOS EVM +- **Reason for Interest:** I have been a member of the EOS community since 2018. Unfortunately, due to the instability caused by Block One I decided to launch the project on BSC. Now that we as a community have taken over from Block One and after discussing with Yves La Rose, I want to do my bit to contribute towards making Gamefi on EOS EVM flourish and ultimately highlight the exceptional technology underlying the EOS blockchain. + +### Project Details + +GAMI is an Influencer centric Web3 gaming studio set-up for onboarding the next 100 million gamers. + +Our debut game ‘Knockout Wars’ (link) is a Mobile Multiplayer Fireball Fighting Game inspired by Street Fighter & Dodgeball. Currently in closed beta testing with the community. + + +Most Web3 games are finding it difficult to gain mass adoption. + +We believe the solutions are as follows: + +1. Remove Web3 wallet barrier + +Gamers are alienated when required to adopt a Web3 wallet to play games, this becomes a barrier to mass adoption. Our games use social logins for all players, allowing them to adopt web3 at their own pace. + +2. Align incentives correctly for mass adoption + +Web3 gaming incentives are misaligned, as they focus on paying the gamer and not the promoter. We feel gamers should be rewarded with a fun experience, and promoters (influencers) should be rewarded financially. + +Our innovative #Influences&Earn program, incentivises Influencers to host captivating Tournaments, attracting audiences and boosting engagement, opening the doors to mass adoption. + +3. Sustainable economy + +Web3 games that require more paying users to sustain the Play2Earn economy are designed to fail, similar to pyramid schemes. Our economy uses NFT sales and sponsorship revenue to bring new money into the ecosystem to fund our onboarding strategy powered by our innovative #Influences&Earn programme, making it a sustainable economy setup for mass adoption. + +Note: Our solidity smart contracts will be open source but our unity game will not be open source. + +### Ecosystem Fit + +- Where and how does your project fit into the ecosystem? EOS Gamefi & EOS EVM +- Who is your target audience? Web2 & Web3 gamers +- What need(s) does your project meet? Mass adoption of Web3 gaming. Mass awareness of EOS EVM via the #Influence&Earn program +- Are there any other projects similar to yours in the EOS Network / Antelope ecosystem? We are not aware of other projects similar to this in the EOS ecosystem + +## Team + +### Team members + +- **Team Leader:** Junayd Miah +- Azad Uddin - Blockchain & Tech Lead +- Eric Odi - Unity Engineer +- Eleni Kouraki - 3D Artist +- Ammar Vohra - Backend Unity Developer +- Rahmat Ali - Product Manager +- Abdul Fattah - Community Manager + +### Legal Structure +- **Registered Legal Entity:** GAMI Studio LLC +- **Registered Address:** Richmond Hill Road, Kingstown, St. Vincent and the Grenadines, P.O. Box 2897 + +### Team Experience + +Junayd Miah - Over 15 years of experience growing an international influencer based fast fashion brand & 5 years of creative & B2B experience in the Web3 space +Azad Uddin - 20 years of development experience, with 4 years blockchain experience +Eric Odi – 9 years of Unity game development experience +Abdul Fattah – 8 years communications and community management experience +Ammar Vohra - 7 years of Unity backend game development experience +Rahmat Ali - 6 years of product management experience, with 3 years in web3 product management +Eleni Kouraki - 3 years of experience as a 3D artist + + +### Team Org Repos + +- + +### Team Member Repos + +### Team LinkedIn Profiles (if available) + +- https://www.linkedin.com/in/azad-uddin/ +- https://www.linkedin.com/in/eric-odi-7506ab195/ +- https://www.linkedin.com/in/eleni-kouraki-2358b91bb/ +- https://www.linkedin.com/in/rahmat-a-770667213/ +- https://www.linkedin.com/in/abdulfattah-junayd-413844120/ + + +## Development Status + +- The game is in closed early beta testing. +- Link to google play store. +- Use EOSEVM as invite code. + +## Development Roadmap + +The roadmap is seperated in to 4 distict deliverbales +- EOS EVM Token development +- DEX Launch with liqudity +- Integration of EOS Token and wallets to knockout wars game +- Launch the EOS EVM backed competitions of knockout wars + +### Milestone Summary + +- **Total Estimated Duration:** 3 months +- **Full-Time Equivalent (FTE):** 1 FTE +- **Total Costs:** 35,000 USD + +### Milestone 1 — EOS EVM Token development + +- **Estimated duration:** 1 month +- **FTE:** 1 +- **Costs:** 7,000 USD + +Develop a new Token with new features + +Features include: +Transaction fee will be split into the following +- Reflection to Token holders +- Burning +- Liquidity + +ERC20 token for EOS EVM with Bridging +- Develop token +- Testing token +Bridge the original token over to EOS EVM +- Test the bridging + +Development Costs: 7,000 USD +- The annual salary for calculation 84,000 USD +- (84,000 / 12) * 1 month + + + +### Milestone 2 — DEX Launch with liqudity + +- **Estimated Duration:** 1 Week +- **FTE:** 1 +- **Costs:** 13,000 USD + +Launch on an EOS EVM DEX + +Audit Cost 2,000USD +DevOps Token Launch Costs: 1,000 USD +Liquidity for the EOS DEX Cost: 10,000 USD + + +### Milestone 3 — Integration of EOS Token and wallets to Knockout Wars Game + +- **Estimated Duration:** 1 Month +- **FTE:** 1 +- **Costs:** 6,000 USD + +Integrate EOS EVM to Knockout wars +Unity Game Integration +- Integrate EOS wallets to knockout wars +- Unit test code +Development Costs: 6,000 USD +- The annual salary for calculation 72,000 USD +- (72,000 / 12) * 1 month + + +### Milestone 4 — Launch the EOS EVM backed competitions of Knockout Wars + +- **Estimated Duration:** 1 Month +- **FTE:** 1 +- **Costs:** 9,000 USD + +EOS Sponsored Competitions +- Prepare and organise 4 weekly competitions for Knockout Wars +- Each week a different Influencer will host the tournament. + +The campaign will market EOS +- Market to our community, including AMAs +- Youtube, Twitter and Telegram campaign +- Banners in knockout wars + +Influencer Costs: 4,000 USD +- Mid-level influencer 1,000 USD +- 4 influencers = 4 * 1,000 = 4,000 USD + +Design & Management Costs: 5,000 USD +- The annual salary for calculation 60,000 USD +- (60,000 / 12) * 1 month + + + +## Future Plans + +After successfully implementing our #Influence&Earn program and establishing a strong POC, we will seek further grants or VC investment to enhance & expand the #Influence&Earn program to on-board the next 100 million gamers. + + +## Additional Information + +**How did you hear about the Grants Program?** While discussing about it Yves La Rose From 63e03e7ed5403514082a8504b7a83bac4ee6e1d4 Mon Sep 17 00:00:00 2001 From: uddina Date: Sun, 28 May 2023 15:46:02 +0100 Subject: [PATCH 153/170] Text changes --- applications/knockout_wars_game.md | 61 +++++++++++++++--------------- 1 file changed, 31 insertions(+), 30 deletions(-) diff --git a/applications/knockout_wars_game.md b/applications/knockout_wars_game.md index 71803d60..c0dec20e 100644 --- a/applications/knockout_wars_game.md +++ b/applications/knockout_wars_game.md @@ -21,9 +21,8 @@ This is a proposal to build & launch Knockout Wars Game on EOS EVM -### Overview -> Please provide the following: +### Overview - **Name:** Knockout Wars, a Mobile Multiplayer Fireball Fighting Game - **Brief Description:** We want to be the 1st Mobile Skill based fighting game on EOS EVM that is set up for mass adoption. @@ -37,11 +36,12 @@ All the above will result in EOS EVM gaining new exposure to new gaming communit - **Relationship to EOS Network / Antelope:** Enhance the EOS Gamefi ecosystem via EOS EVM - **Reason for Interest:** I have been a member of the EOS community since 2018. Unfortunately, due to the instability caused by Block One I decided to launch the project on BSC. Now that we as a community have taken over from Block One and after discussing with Yves La Rose, I want to do my bit to contribute towards making Gamefi on EOS EVM flourish and ultimately highlight the exceptional technology underlying the EOS blockchain. + ### Project Details GAMI is an Influencer centric Web3 gaming studio set-up for onboarding the next 100 million gamers. -Our debut game ‘Knockout Wars’ (link) is a Mobile Multiplayer Fireball Fighting Game inspired by Street Fighter & Dodgeball. Currently in closed beta testing with the community. +Our debut game ‘Knockout Wars’ is a Mobile Multiplayer Fireball Fighting Game inspired by Street Fighter & Dodgeball. Currently in closed beta testing with the community. Most Web3 games are finding it difficult to gain mass adoption. @@ -50,17 +50,17 @@ We believe the solutions are as follows: 1. Remove Web3 wallet barrier -Gamers are alienated when required to adopt a Web3 wallet to play games, this becomes a barrier to mass adoption. Our games use social logins for all players, allowing them to adopt web3 at their own pace. +Gamers are alienated when required to adopt a Web3 wallet to play games, this becomes a barrier to mass adoption. Our games use social logins for all players, allowing them to adopt Web3 at their own pace. 2. Align incentives correctly for mass adoption Web3 gaming incentives are misaligned, as they focus on paying the gamer and not the promoter. We feel gamers should be rewarded with a fun experience, and promoters (influencers) should be rewarded financially. -Our innovative #Influences&Earn program, incentivises Influencers to host captivating Tournaments, attracting audiences and boosting engagement, opening the doors to mass adoption. +Our innovative #Influence&Earn program, incentivises Influencers to host captivating Tournaments, attracting audiences and boosting engagement, opening the doors to mass adoption. 3. Sustainable economy -Web3 games that require more paying users to sustain the Play2Earn economy are designed to fail, similar to pyramid schemes. Our economy uses NFT sales and sponsorship revenue to bring new money into the ecosystem to fund our onboarding strategy powered by our innovative #Influences&Earn programme, making it a sustainable economy setup for mass adoption. +Web3 games that require more paying users to sustain the Play2Earn economy are designed to fail, similar to pyramid schemes. Our economy uses NFT sales and sponsorship revenue to bring new money into the ecosystem to fund our onboarding strategy powered by our innovative #Influence&Earn program, making it a sustainable economy setup for mass adoption. Note: Our solidity smart contracts will be open source but our unity game will not be open source. @@ -71,6 +71,7 @@ Note: Our solidity smart contracts will be open source but our unity game will n - What need(s) does your project meet? Mass adoption of Web3 gaming. Mass awareness of EOS EVM via the #Influence&Earn program - Are there any other projects similar to yours in the EOS Network / Antelope ecosystem? We are not aware of other projects similar to this in the EOS ecosystem + ## Team ### Team members @@ -89,13 +90,13 @@ Note: Our solidity smart contracts will be open source but our unity game will n ### Team Experience -Junayd Miah - Over 15 years of experience growing an international influencer based fast fashion brand & 5 years of creative & B2B experience in the Web3 space -Azad Uddin - 20 years of development experience, with 4 years blockchain experience -Eric Odi – 9 years of Unity game development experience -Abdul Fattah – 8 years communications and community management experience -Ammar Vohra - 7 years of Unity backend game development experience -Rahmat Ali - 6 years of product management experience, with 3 years in web3 product management -Eleni Kouraki - 3 years of experience as a 3D artist +- Junayd Miah - Over 15 years of experience growing an international influencer based fast fashion brand & 5 years of creative & B2B experience in the Web3 space +- Azad Uddin - 20 years of development experience, with 4 years blockchain experience +- Eric Odi – 9 years of Unity game development experience +- Abdul Fattah – 8 years communications and community management experience +- Ammar Vohra - 7 years of Unity backend game development experience +- Rahmat Ali - 6 years of product management experience, with 3 years in web3 product management +- Eleni Kouraki - 3 years of experience as a 3D artist ### Team Org Repos @@ -116,16 +117,16 @@ Eleni Kouraki - 3 years of experience as a 3D artist ## Development Status - The game is in closed early beta testing. -- Link to google play store. +- to google play store. - Use EOSEVM as invite code. ## Development Roadmap -The roadmap is seperated in to 4 distict deliverbales +The roadmap is separated into 4 distinct deliverables - EOS EVM Token development - DEX Launch with liqudity -- Integration of EOS Token and wallets to knockout wars game -- Launch the EOS EVM backed competitions of knockout wars +- Integration of EOS Token and Wallets with Knockout Wars Game +- Launch the EOS EVM backed competitions of Knockout Wars Game ### Milestone Summary @@ -133,6 +134,7 @@ The roadmap is seperated in to 4 distict deliverbales - **Full-Time Equivalent (FTE):** 1 FTE - **Total Costs:** 35,000 USD + ### Milestone 1 — EOS EVM Token development - **Estimated duration:** 1 month @@ -141,8 +143,7 @@ The roadmap is seperated in to 4 distict deliverbales Develop a new Token with new features -Features include: -Transaction fee will be split into the following +Transaction fee feature will be split into the following - Reflection to Token holders - Burning - Liquidity @@ -167,27 +168,27 @@ Development Costs: 7,000 USD Launch on an EOS EVM DEX -Audit Cost 2,000USD -DevOps Token Launch Costs: 1,000 USD -Liquidity for the EOS DEX Cost: 10,000 USD +- Audit Cost 2,000USD +- DevOps Token Launch Costs: 1,000 USD +- Liquidity for the EOS DEX Cost: 10,000 USD -### Milestone 3 — Integration of EOS Token and wallets to Knockout Wars Game +### Milestone 3 — Integration of EOS Token and Wallets with Knockout Wars Game - **Estimated Duration:** 1 Month - **FTE:** 1 - **Costs:** 6,000 USD -Integrate EOS EVM to Knockout wars -Unity Game Integration -- Integrate EOS wallets to knockout wars +Unity Game Integration: Integrate EOS EVM to Knockout Wars Game + +- Integrate EOS wallets with Knockout Wars - Unit test code -Development Costs: 6,000 USD +- Development Costs: 6,000 USD - The annual salary for calculation 72,000 USD - (72,000 / 12) * 1 month -### Milestone 4 — Launch the EOS EVM backed competitions of Knockout Wars +### Milestone 4 — Launch the EOS EVM backed competitions of Knockout Wars Game - **Estimated Duration:** 1 Month - **FTE:** 1 @@ -195,12 +196,12 @@ Development Costs: 6,000 USD EOS Sponsored Competitions - Prepare and organise 4 weekly competitions for Knockout Wars -- Each week a different Influencer will host the tournament. +- Each week a different Influencer will host the tournament The campaign will market EOS - Market to our community, including AMAs - Youtube, Twitter and Telegram campaign -- Banners in knockout wars +- Banners in Knockout Wars Game Influencer Costs: 4,000 USD - Mid-level influencer 1,000 USD From a1a6e0a95e54bc917705ddced649d3d8e4e4d01b Mon Sep 17 00:00:00 2001 From: uddina Date: Mon, 29 May 2023 11:45:10 +0100 Subject: [PATCH 154/170] language changes --- applications/knockout_wars_game.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/applications/knockout_wars_game.md b/applications/knockout_wars_game.md index c0dec20e..343880f2 100644 --- a/applications/knockout_wars_game.md +++ b/applications/knockout_wars_game.md @@ -150,8 +150,8 @@ Transaction fee feature will be split into the following ERC20 token for EOS EVM with Bridging - Develop token -- Testing token -Bridge the original token over to EOS EVM +- Test token +- Bridge the original token over to EOS EVM - Test the bridging Development Costs: 7,000 USD @@ -220,4 +220,4 @@ After successfully implementing our #Influence&Earn program and establishing a s ## Additional Information -**How did you hear about the Grants Program?** While discussing about it Yves La Rose +**How did you hear about the Grants Program?** While discussing about it with Yves La Rose From bb8b78b12af0d0a60284ae10527dd208391eed2e Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Thu, 1 Jun 2023 15:11:08 -0400 Subject: [PATCH 155/170] Update accepted_grant_applications.md --- docs/accepted_grant_applications.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/accepted_grant_applications.md b/docs/accepted_grant_applications.md index c05b3d52..19184874 100644 --- a/docs/accepted_grant_applications.md +++ b/docs/accepted_grant_applications.md @@ -29,7 +29,7 @@ | Team | Project Name / Application | Repo | Terminated | First Delivery | Completed | :--- | :------ | :--- | :--------: | :------------: | :-------: | | [FACINGS, Inc.](https://facings.io) | [NFT Collection Manager Stage 2](../applications/facings-nft-collection-manager-stage-2.md) | [GitHub](https://github.com/FACINGS) |
  • [ ]
|
  • [X]
|
  • [ ]
| -| [Animus Labs LTD (representing Boid.com)](https://www.animus.is) | [Antelope Firewall](../applications/antelopeio_firewall.md) | [GitHub](https://github.com/mchosc) |
  • [ ]
|
  • [ ]
|
  • [ ]
| +| [Animus Labs LTD (rep Boid.com)](https://www.animus.is) | [Antelope Firewall](../applications/antelopeio_firewall.md) | [GitHub](https://github.com/mchosc) |
  • [ ]
|
  • [ ]
|
  • [ ]
| | [Creamy Vainilla C.A](https://eosvision.io/) | [EOS VISIONS](../applications/eosreddit2.md) | [GitHub](https://github.com/Creamyvanill) |
  • [ ]
|
  • [ ]
|
  • [ ]
| | [Alphabox Solutions Pte. Ltd.](https://alphaday.com/) | [Alphaday](../applications/alphaday.md) | [GitHub](https://github.com/Mikael337) |
  • [ ]
|
  • [ ]
|
  • [ ]
| From bbc8388a7ad8df6e91f536e947ce835e8d091d59 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Wed, 7 Jun 2023 17:34:05 -0400 Subject: [PATCH 156/170] Update ru-committee-approved-email.yml --- .github/workflows/ru-committee-approved-email.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/ru-committee-approved-email.yml b/.github/workflows/ru-committee-approved-email.yml index fcd2042b..1485469b 100644 --- a/.github/workflows/ru-committee-approved-email.yml +++ b/.github/workflows/ru-committee-approved-email.yml @@ -72,5 +72,5 @@ jobs: to: ${{inputs.app_email}} from: grants@eosnetwork.com reply_to: grants@eosnetwork.com - bcc: grants@eosnetwork.com + bcc: grants@eosnetwork.com,grant-committee-approved@eosnetwork.com From 373a59213cfc5141e21df24ccc1d26b57e6ff1c3 Mon Sep 17 00:00:00 2001 From: Jonas Sunandar Date: Thu, 8 Jun 2023 16:24:59 +0700 Subject: [PATCH 157/170] Update tokenomics_enhancement_neutroswap.md update the grant cost and detail of xNEUTRO tokenomics --- .../tokenomics_enhancement_neutroswap.md | 39 ++++++++++++++----- 1 file changed, 30 insertions(+), 9 deletions(-) diff --git a/applications/tokenomics_enhancement_neutroswap.md b/applications/tokenomics_enhancement_neutroswap.md index 5c832eeb..26874a48 100644 --- a/applications/tokenomics_enhancement_neutroswap.md +++ b/applications/tokenomics_enhancement_neutroswap.md @@ -64,7 +64,26 @@ $xNEUTRO will be non-transferable and act as our governance token. $xNEUTRO main The upcoming mechanism will replace the existing Neutro Farms as they both serve similar purposes. The key distinction is that instead of solely depositing LP tokens into the Farms smart contract, users will receive spNFTs in exchange for their deposited LP tokens, making it tradeable. -#### [**3. Protocol Revenue Distribution**](https://docs.neutroswap.io/neutroswap-v2-coming-soon/protocol-revenue) +Users have the opportunity to mint staked positions NFT (spNFTs) by wrapping Neutroswap LP tokens, which involves depositing them into the respective contract. + +This action transfers the deposit to a designated NFTPool contract, resulting in the issuance of spNFTs. Consider this NFT as a deposit receipt, confirming the ownership of the staked position. + +The ownership of the spNFTs acts as the sole authorization for a user to withdraw the corresponding funds, irrespective of the entity utilizing them. Therefore, the owner of the spNFT is effectively the rightful owner of the associated LPs, even if they were not the initial depositor. + +spNFTs go beyond being mere receipts; they serve as replacements for traditional yield-generating farms commonly found in DeFi protocols. Additionally, spNFTs provide an additional layer of features that unlock unlimited opportunities and potential extensions, offering a myriad of possibilities: + +#### [**3. Yield Farming**](https://docs.neutroswap.io/neutroswap-v2-coming-soon/staked-positions-spnfts/yield-farming) + +The primary objective of staked positions in the form of spNFTs is to replace conventional yield farming mechanisms and receive incentives provided by Neutroswap. However, these staked positions offer a versatile range of uses beyond this initial purpose. + +1. Yield-bearing NFTs: From a user's perspective, the mechanics of Neutroswap's spNFTs bear resemblances to regular DeFi farms. However, in contrast to allocating rewards solely to traditional farms, Neutroswap's Master contract distributes incentives to all staking positions associated with team-defined selected wrapped LPs. This approach ensures that incentives are widely distributed across the ecosystem. + +2. Rewards: Neutroswap incentives are provided in the form of dual rewards, where eligible wrapped Neutroswap LPs enable their corresponding staked positions to receive both $NEUTRO and xNEUTRO rewards. The distribution ratio of these rewards varies for each asset, with the default allocation set to 80% $xNEUTRO / 20% $NEUTRO. + +3. Yield multipliers: There are two methods to enhance returns from yield-generating staked positions: utilizing locks or the Yield Multiplier plugin. The specific values of these enhancements vary based on the staked asset, ranging from 0% to 150% (x1 to x2.5), although the default is typically set at 100% (x2). By summing these two multipliers, the total multiplier for the position is determined. Each pool will have its own maximum boost, with a default cap of 200% (x3) and an absolute cap of 250% (x3.5). These parameters are applied within the Neutroswap ecosystem. + + +#### [**4. Protocol Revenue Distribution**](https://docs.neutroswap.io/neutroswap-v2-coming-soon/protocol-revenue) The protocol-generated revenue will be distributed as follows: @@ -75,12 +94,15 @@ The protocol-generated revenue will be distributed as follows: The Core Contributors funds will be solely utilized to cover operational expenses. At the end of each month, any remaining unused amount will be reallocated at the team's discretion, either towards Dividends or for Buyback and Burn purposes. -#### [**4. Deflationary Mechanism**](https://docs.neutroswap.io/neutroswap-v2-coming-soon/deflationary-mechanism) +#### [**5. Deflationary Mechanism**](https://docs.neutroswap.io/neutroswap-v2-coming-soon/deflationary-mechanism) We applied a few mechanism that will increase the buying pressure of $NEUTRO with the aim of making it for attractive for future investors, while increasing value for $NEUTRO holders. - Buyback and Burn: A portion of the protocol revenues is allocated towards the buyback and burn of $NEUTRO tokens, creating persistent buying pressure on the token. - xNEUTRO Reedem: During the [redeem of $xNEUTRO to $NEUTRO](https://docs.neutroswap.io/neutroswap-v2-coming-soon/xneutro-token/convert-redeem#redeeming-xneutro-greater-than-neutro), if the vesting duration is not set to the maximum, the xNEUTRO:NEUTRO ratio will be adjusted to a value below 1:1, ranging from 1:0.5 as the minimum. Any surplus $NEUTRO obtained during this process will be automatically burned. +Let's take an example to illustrate this process: +If a user chooses to redeem 1000 $xNEUTRO with the minimum vesting duration of 15 days, they will receive a ratio of 1:0.5, resulting in 500 $NEUTRO. Consequently, a total of 1000 - 500 = 500 $NEUTRO will be burned throughout the redemption process. + - xNEUTRO Deallocation: When users deallocate $xNEUTRO from a Plugin, a deallocation tax is imposed, typically set at 0.5%. This tax may vary across contracts. Furthermore, the corresponding amount of $NEUTRO will be automatically burned as a result of the deallocation process. ### Ecosystem Fit @@ -163,27 +185,26 @@ We have completed the [technical documentation](https://docs.neutroswap.io/neutr - **Total Estimated Duration:** 3 months - **Full-Time Equivalent (FTE):** 6 FTE -- **Total Costs:** 100,000 USD +- **Total Costs:** 50,000 USD ### Milestone 0 - Requirement Analysis and Marketing Plan - **Estimated duration:** 2 weeks - **FTE:** 2 -- **Costs:** 20,000 USD +- **Costs:** 5,000 USD | ID | Deliverable | Specification | | --- | -------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 0a. | License | MIT | | 0b. | Threads | Publish **twitter threads** explaining all the updates that'll we'll be rolling out | -| 0c. | Marketing | Form a group of multiple DeFi influencers and create a plan that can help bring more awareness about DeFi EOS EVM ecosystem | | 1. | General Requirement and Migration Plan | **Smart contract Requirement**
Write a detailed requirements for the smart contract

**Subgraph Migration Plan**
Analyze required changes on 3 of our subgraphs, and create migration plan for it

**High Fidelity Prototype**
Publish a high-fidelity prototype for the new UI required for the updates. The prototype will be publicly available in Figma for others to use.

**Front-end Migration Plan**
Do a code structure research on how the current and future component would work together

**Integration Testing Plan**
Research on how our current toolchain like ethers and foundry would work in the testing environment | -| 2. | Documentation | Enhance the technical documentation and tutorial to comprehensively explain all the updates, enabling users to familiarize themselves with the new enhancements. | +| 2. | Documentation | Enhance the technical documentation and tutorial to comprehensively explain all the updates, enabling users to familiarize themselves with the new enhancements.| ### Milestone 1 - Smart Contract Development, Audit, and Marketing Site - **Estimated duration:** 3 weeks - **FTE:** 3 -- **Costs:** 30,000 USD +- **Costs:** 25,000 USD | ID | Deliverable | Specification | | --- | ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -198,7 +219,7 @@ We have completed the [technical documentation](https://docs.neutroswap.io/neutr - **Estimated duration:** 3 weeks - **FTE:** 4 -- **Costs:** 20,000 USD +- **Costs:** 10,000 USD | ID | Deliverable | Specification | | --- | -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -214,7 +235,7 @@ We have completed the [technical documentation](https://docs.neutroswap.io/neutr - **Estimated duration:** 2 weeks - **FTE:** 2 -- **Costs:** 30,000 USD +- **Costs:** 10,000 USD | ID | Deliverable | Specification | | --- | ------------------------- | ---------------------------------------------------------------------------------- | From 255bf8c7e5458a4345cb7a40e8f03bf6328cc0e7 Mon Sep 17 00:00:00 2001 From: Jonas Sunandar Date: Thu, 8 Jun 2023 17:11:57 +0700 Subject: [PATCH 158/170] Update tokenomics_enhancement_neutroswap.md --- .../tokenomics_enhancement_neutroswap.md | 50 ++++++++++--------- 1 file changed, 27 insertions(+), 23 deletions(-) diff --git a/applications/tokenomics_enhancement_neutroswap.md b/applications/tokenomics_enhancement_neutroswap.md index 26874a48..0075f287 100644 --- a/applications/tokenomics_enhancement_neutroswap.md +++ b/applications/tokenomics_enhancement_neutroswap.md @@ -85,6 +85,8 @@ The primary objective of staked positions in the form of spNFTs is to replace co #### [**4. Protocol Revenue Distribution**](https://docs.neutroswap.io/neutroswap-v2-coming-soon/protocol-revenue) +![Protocol Revenue Distribution](https://1194041802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fen8htS8yWPtDJdaEljt1%2Fuploads%2FR5Sc2oApBRBbTOTG3zaq%2Fpurple%20gradient%20pie%20chart%20graph.png?alt=media&token=c7ae361e-b2b3-4b21-a82f-266ee5456b6c) + The protocol-generated revenue will be distributed as follows: - 60% is allocated to Liquidity Providers in the form of LP tokens. @@ -187,22 +189,22 @@ We have completed the [technical documentation](https://docs.neutroswap.io/neutr - **Full-Time Equivalent (FTE):** 6 FTE - **Total Costs:** 50,000 USD -### Milestone 0 - Requirement Analysis and Marketing Plan +### Milestone 0 - Requirement Analysis - **Estimated duration:** 2 weeks - **FTE:** 2 - **Costs:** 5,000 USD -| ID | Deliverable | Specification | +| ID | Deliverable | Specification | | --- | -------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| 0a. | License | MIT | -| 0b. | Threads | Publish **twitter threads** explaining all the updates that'll we'll be rolling out | +| 0a. | License | MIT | +| 0b. | Threads | Publish **twitter threads** explaining all the updates that'll we'll be rolling out about Neutroswap V2| | 1. | General Requirement and Migration Plan | **Smart contract Requirement**
Write a detailed requirements for the smart contract

**Subgraph Migration Plan**
Analyze required changes on 3 of our subgraphs, and create migration plan for it

**High Fidelity Prototype**
Publish a high-fidelity prototype for the new UI required for the updates. The prototype will be publicly available in Figma for others to use.

**Front-end Migration Plan**
Do a code structure research on how the current and future component would work together

**Integration Testing Plan**
Research on how our current toolchain like ethers and foundry would work in the testing environment | -| 2. | Documentation | Enhance the technical documentation and tutorial to comprehensively explain all the updates, enabling users to familiarize themselves with the new enhancements.| +| 2. | Documentation | Deliver comprehensive documentation for Neutroswap V2, encompassing a range of instructional materials, example files, and detailed guidelines within the project's repository.| -### Milestone 1 - Smart Contract Development, Audit, and Marketing Site +### Milestone 1 - Smart Contract Development -- **Estimated duration:** 3 weeks +- **Estimated duration:** 4 weeks - **FTE:** 3 - **Costs:** 25,000 USD @@ -210,37 +212,39 @@ We have completed the [technical documentation](https://docs.neutroswap.io/neutr | --- | ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 0a. | License | Apache 2.0 | | 0b. | Documentation | We will provide both **inline documentation** of the code and a technical **tutorial** that explains how users can utilize all of the new updates works. | -| 0c. | Unit Test | Core functions will be fully covered by unit tests to ensure functionality and robustness. These test will be provided in the repository for the public | -| 0d. | Testing Guide | Guide will also be included in the repository | -| 1. | Smart Contract Security Audit | Publish the all the necessary smart contract such as xNEUTRO, spNFTs, plugins in a public repo with the audit report included. This smart contract will also publicly available on our team Github | -| 2. | Marketing Page | Product landing page makeover that also describes all of the new features | +| 0c. | Unit Test | Core functions will be fully covered by unit tests to ensure functionality and robustness. These test will be provided in the repository for the public | +| 0d. | Testing Guide | The functions of this milestone can be tested by running the unit tests we provide, and guidance on how to run these tests is provided in the Readme file. | +| 1. | Core Contracts | Publish the all the necessary smart contract such as xNEUTRO, spNFTs, plugins in a public repo with the audit report included. This smart contract will also publicly available on our team Github | +| 2. | Tokenomics contracts | xNEUTRO can only be redeem with vesting period. It will allow burning mechanism for $NEUTRO. However, $NEUTRO can be converted into $xNEUTRO in instant. | +| 3. | Plugins contracts | Plugin contracts are enabling users to allocate their xNEUTRO into their desired plugins: Dividends, Yield boosters and launchpad | +| 3. | Protocol revenue contracts | Develop and implement smart contracts to enhance Neutroswap's protocol revenue generation capabilities and enable efficient distribution of rewards to $xNEUTRO holders. | +| 4. | Smart contract audit | Conduct a comprehensive audit of Neutroswap's smart contracts to ensure their security, functionality, and compliance with best practices and industry standards. | ### Milestone 2 - Graph Node Deployment, Subgraphs, and Web Development -- **Estimated duration:** 3 weeks +- **Estimated duration:** 4 weeks - **FTE:** 4 -- **Costs:** 10,000 USD +- **Costs:** 15,000 USD | ID | Deliverable | Specification | | --- | -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| 0a. | License | Apache 2.0 | -| 0b. | Integration Tests | Integration tests will be developed, including new and modified tests. | -| 1. | Subgraph Development | Publish a public subgraphs that can be used publicly | -| 3. | Additional UI | Implementing the high-fidelity prototype from earlier stage. Adding new components necessary enabling users to interact with all of the new updates while keeping the current UI accessible to all users | -| 4. | Analytics | User will be able to see xNEUTRO, spNFTs, and activity in all of the new contracts | -| 5. | Testnet Deployment | Deploy the new contract, subgraphs, and web to the EOSEVM Testnet environment | -| 6. | Medium Post | All contract addresses and public subgraph links will be available on both Discord and Medium account | +| 0a. | License | Apache 2.0 | +| 0b. | Integration Tests | Integration tests will be developed, including new and modified tests. | +| 1. | Subgraph Development | Publish a Neutroswap public subgraphs that can be used publicly | +| 2. | New V2 UI | Implementing the V2 high-fidelity prototype from earlier stage. Adding new components necessary enabling users to interact with all of the new updates while keeping the current UI accessible to all users. | +| 3. | Analytics | User will be able to see xNEUTRO, spNFTs, and activity in all of the new contracts | +| 4. | Testnet Deployment | Deploy the new contract, subgraphs, and web to the EOSEVM Testnet environment | -### Milestone 3 - Neutroswap Updates Mainnet Deployment +### Milestone 3 - Mainnet Deployment & Marketing - **Estimated duration:** 2 weeks - **FTE:** 2 -- **Costs:** 10,000 USD +- **Costs:** 5,000 USD | ID | Deliverable | Specification | | --- | ------------------------- | ---------------------------------------------------------------------------------- | | 0a. | License | Apache 2.0 | -| 0b. | Testnet Integration Test | Do integration testing on testnet before migrating the whole stack to the mainnet | +| 0b. | Article | We will publish an informative threads on twitter, explaining the concept of V2 smart contracts and how they will be utilized within our project. | | 1. | Smart Contract Deployment | Deploy smart contract to the EOS-EVM mainnet | | 2. | Graph Node Deployment | Publish a private graph-node instance for the EOS-EVM mainnet environment | | 3. | Subgraph Deployment | Publish public subgraphs for Neutroswap updates and start indexing EOS-EVM mainnet | From 1cf32d61a6e83de9d1b22b0ef9b74ec69177730e Mon Sep 17 00:00:00 2001 From: hdavis1988 <128661420+hdavis1988@users.noreply.github.com> Date: Sat, 10 Jun 2023 17:18:32 +0800 Subject: [PATCH 159/170] Create EVMNS_Audit Assistance.md --- applications/EVMNS_Audit Assistance.md | 81 ++++++++++++++++++++++++++ 1 file changed, 81 insertions(+) create mode 100644 applications/EVMNS_Audit Assistance.md diff --git a/applications/EVMNS_Audit Assistance.md b/applications/EVMNS_Audit Assistance.md new file mode 100644 index 00000000..ab8a16d0 --- /dev/null +++ b/applications/EVMNS_Audit Assistance.md @@ -0,0 +1,81 @@ + +# EOS Network Foundation Grant Proposal +- **Project Name:** Security Audit Assistance for EVMNS +- **Team Name:** EVMNS Labs +- **EOS Payment Address:** evmnsdomains +- **Level:** 3 +- **Pomelo Grant(s):** https://pomelo.io/grants/evmns +- **Project is Open-Source:** Yes +- **Project was part of Token sale:** No +- **Repository where Project resides:** https://github.com/evmns/EVMNS + +# Contact +- **Contact Name:** Harry Davis +- **Contact Email:** evmns_manager@outlook.com +- **Website:** https://evmns.space/ + +# Project Overview +**EVMNS (EOS EVM Name Service) is a distributed, open and extensible multi-chain DID domain naming system built on EOS EVM,** relying on the high performance, security and reliability of EOS to better and seamlessly connect people, information, assets, dApps, etc. in the WEB3 world.

+EVMNS domains use the ERC721 protocol standard with .evm as the domain suffix, such as abc.evm, 123.evm, jack.evm, etc., to map human-readable and easy-to-remember names with all kinds of content at the same time, including but not limited to EVM addresses, EOS addresses, other cryptocurrency addresses, content hashes, URLs, and metadata.

+### Overview +- **Name:** EVMNS (EOS EVM Name Service)
+- **Brief Description:** A distributed, open and extensible multi-chain DID domain naming system built on EOS EVM.
+- **Relationship to EOSIO:** EVMNS's multi-chain layout will bring more new users to EOS EVM, because it helps users of other chains to know and understand EOS EVM, and to enjoy the unique advantages of EOS EVM (industry-leading transaction speeds, high TPS and low transaction cost), and help EOS EVM to expand its positive influence in the WEB3 world.
+- **Reason for Interest:** WEB3 trend is developing rapidly, a set of DID domain naming system with perfect function, multi-chain layout and good user experience is the "identity infrastructure" of WEB3 application, and it can be confirmed that DID is like an avatar, which is the basic and essential element and the identity of WEB3 world.

+ +# Application Description +The development work for EVMNS has been mostly completed, and We are currently conducting in-depth internal testing and debugging. We believe that the service will be officially launched shortly, and we are excited to share EVMNS with the community.

+Before the official release, we need to conduct a comprehensive security audit of the smart contract to ensure that there are no security issues. **However, due to the greater complexity and larger code volume of the smart contract than our team had anticipated, the corresponding security audit costs have exceeded our budget by a significant amount, making it an enormous burden for us, even to the point of being unbearable.**

+Therefore, we sincerely request assistance from the EOS Network Foundation to help us complete this important security audit work.

+More details are as follows:

+1. Overview of Smart Contract Functions
+**Domain Registration:** Users can register unique domain names on EVMNS.
+**Domain Management:** Users can manage their registered domain names, such as changing the profile of the domain, changing the resolver, or modifying the TLS certificate.
+**Domain Transfer:** Users can transfer their registered domain names to others.
+**Resolver Registration:** Users can select a resolver to resolve the domain name, and different resolvers support different domain name functions.
+**Domain Resolution:** Users/third-party dApps can query the profile content of EVMNS domain names, such as whether an EVMNS domain name is associated with an EOS EVM address.
+ +2. Total lines of code in smart contract: about **9300 lines.**
+ +3. Smart Contract Code repository: https://github.com/evmns/evmns-contracts
+ +4. **If not audited, potential security risks may include, but are not limited to:** Mass registration of domain names, even those that are not yet open for registration; Control of domain name permissions, which may result in inability to manage or transfer domains; Domain name hijacking, which may result in inability to resolve to the correct wallet address, affecting users' transfer and payment activities.
+ +5. EOS Network Foundation funding proposal for EVMNS: https://github.com/eosnetworkfoundation/grant-framework/pull/106
+ +# Team +### Team members +- **Team Leader: Harry Davis**
+- Allen Harris
+- Frank Lee
+### Legal Structure +- **Registered Legal Entity:** Jump Dream PTE. LTD.
+- **Registered Address:** 5001 Beach Road#07-37, Golden Mile Complex, Singapore 199588
+### Team Experience +The core members of EVMNS Labs are the first ecological participants of EOS, who experienced and witnessed the launch of EOS and are still deeply involved in the ecological construction.

+Team members have participated in several medium to large scale EOS projects before and after, and also developed ENS (Ethereum Name Service) related domain Exchange, domain bulk registry protocol, etc. We are not only EOS loyalists, but also ENS heavy players, with good understanding of DID domain naming system.
+### Team Member Repos +- Allen Harris, https://github.com/sutaiyi +- Frank Lee, https://github.com/chenminmin4 + +# Development Roadmap +### Milestone Summary +- **Total Estimated Duration:** 4 weeks +- **Full-Time Equivalent (FTE):** 2 FTE +- **Total Costs:** 30,000 USD + +### Milestone 1 - Security audit completed +- **Estimated duration:** 4 weeks +- **FTE:** 2 +- **Costs:** 30,000 USD + +| ID | Deliverable |Specification| +| ------------ | ------------ | ------------ | +| 0a. |License | MIT License | +| 0b. | Documentation | Provide and update documentation for this milestone in the form of instruction files and examples in the repository, provide guidance in the Readme file, and more in-depth guidance in our articles. | +| 0c. | Testing Guide | We will clearly state the audit report verification method provided by the security audit company to facilitate the verification of the authenticity of the audit report. | +| 1 | Audit Report | After the security company completes the smart contract audit, a comprehensive audit report will be issued. |

+ +# Additional Information +### How did you hear about the Grants Program? +We learned of the program by following announcements on ENF’s Twitter and other channels.
From 9bed111690b105c19159f3f00f1d23864f396bf7 Mon Sep 17 00:00:00 2001 From: hdavis1988 <128661420+hdavis1988@users.noreply.github.com> Date: Sat, 10 Jun 2023 17:20:03 +0800 Subject: [PATCH 160/170] Update EVMNS_Audit Assistance.md --- applications/EVMNS_Audit Assistance.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/applications/EVMNS_Audit Assistance.md b/applications/EVMNS_Audit Assistance.md index ab8a16d0..759ba094 100644 --- a/applications/EVMNS_Audit Assistance.md +++ b/applications/EVMNS_Audit Assistance.md @@ -3,7 +3,7 @@ - **Project Name:** Security Audit Assistance for EVMNS - **Team Name:** EVMNS Labs - **EOS Payment Address:** evmnsdomains -- **Level:** 3 +- **Level:** 2 - **Pomelo Grant(s):** https://pomelo.io/grants/evmns - **Project is Open-Source:** Yes - **Project was part of Token sale:** No From b29de0acf2c0f96f137b882c25a9f42a6e36b167 Mon Sep 17 00:00:00 2001 From: hdavis1988 <128661420+hdavis1988@users.noreply.github.com> Date: Sat, 10 Jun 2023 17:28:01 +0800 Subject: [PATCH 161/170] Rename EVMNS_Audit Assistance.md to EVMNS_Audit_Assistance.md --- .../{EVMNS_Audit Assistance.md => EVMNS_Audit_Assistance.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename applications/{EVMNS_Audit Assistance.md => EVMNS_Audit_Assistance.md} (100%) diff --git a/applications/EVMNS_Audit Assistance.md b/applications/EVMNS_Audit_Assistance.md similarity index 100% rename from applications/EVMNS_Audit Assistance.md rename to applications/EVMNS_Audit_Assistance.md From 6999ea5d3d47bdff81a2c831c703d93aeee43179 Mon Sep 17 00:00:00 2001 From: Jonas Sunandar Date: Mon, 12 Jun 2023 14:16:35 +0700 Subject: [PATCH 162/170] Update tokenomics_enhancement_neutroswap.md --- applications/tokenomics_enhancement_neutroswap.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/applications/tokenomics_enhancement_neutroswap.md b/applications/tokenomics_enhancement_neutroswap.md index 0075f287..b58989d7 100644 --- a/applications/tokenomics_enhancement_neutroswap.md +++ b/applications/tokenomics_enhancement_neutroswap.md @@ -188,6 +188,7 @@ We have completed the [technical documentation](https://docs.neutroswap.io/neutr - **Total Estimated Duration:** 3 months - **Full-Time Equivalent (FTE):** 6 FTE - **Total Costs:** 50,000 USD +- **Note:** The grant proposal does not include the cost of auditing the smart contracts at this time, as the exact amount is currently unknown. The expenses associated with the audit will be addressed separately and allocated accordingly. ### Milestone 0 - Requirement Analysis @@ -218,7 +219,6 @@ We have completed the [technical documentation](https://docs.neutroswap.io/neutr | 2. | Tokenomics contracts | xNEUTRO can only be redeem with vesting period. It will allow burning mechanism for $NEUTRO. However, $NEUTRO can be converted into $xNEUTRO in instant. | | 3. | Plugins contracts | Plugin contracts are enabling users to allocate their xNEUTRO into their desired plugins: Dividends, Yield boosters and launchpad | | 3. | Protocol revenue contracts | Develop and implement smart contracts to enhance Neutroswap's protocol revenue generation capabilities and enable efficient distribution of rewards to $xNEUTRO holders. | -| 4. | Smart contract audit | Conduct a comprehensive audit of Neutroswap's smart contracts to ensure their security, functionality, and compliance with best practices and industry standards. | ### Milestone 2 - Graph Node Deployment, Subgraphs, and Web Development From 064024640c989c92b231bab7eeb129b848b37612 Mon Sep 17 00:00:00 2001 From: Jonas Sunandar Date: Mon, 12 Jun 2023 18:15:17 +0700 Subject: [PATCH 163/170] Update tokenomics_enhancement_neutroswap.md --- applications/tokenomics_enhancement_neutroswap.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/applications/tokenomics_enhancement_neutroswap.md b/applications/tokenomics_enhancement_neutroswap.md index b58989d7..647f3a8b 100644 --- a/applications/tokenomics_enhancement_neutroswap.md +++ b/applications/tokenomics_enhancement_neutroswap.md @@ -19,6 +19,13 @@ Neutroswap is an automated market-maker (AMM) on the EOS EVM blockchain that is community-driven and offers the low fees for swapping assets. Neutroswap's staking and yield farming rewards are among the highest in the EOS EVM ecosystem, attracting those seeking profitable returns on their assets. Our team decides to focus more towards bringing liquidity to EOS EVM chain more. It will enable more users, projects and exposure coming to EOS EVM due to TVL increase and project development. +The goal is to further enhance and expand the Neutroswap platform within the EOS EVM ecosystem. The specific objectives include: +1. Revenue Sharing: Dividends is designed to generate revenue from its [protocol earnings](https://docs.neutroswap.io/neutroswap-v2-coming-soon/protocol-revenue). A portion of these earnings is allocated to reward $xNEUTRO token holders, providing a sustainable mechanism for value distribution and aligning the interests of the community with the success of the platform. +2. Increasing Liquidity: Neutroswap seeks to attract and increase liquidity within the EOS EVM ecosystem by incentivizing users to provide liquidity to the platform's various pools. This increased liquidity helps improve the overall trading experience, reduces slippage, and promotes a vibrant and active marketplace. +3. Supporting Project Launches: Neutroswap aspires to become a [launchpad](https://docs.neutroswap.io/neutroswap-v2-coming-soon/plugins/launchpad) for new projects within the EOS EVM ecosystem. By offering a platform for fair and transparent token launches, Neutroswap helps innovative projects raise funds and gain exposure. This goal aligns with Neutroswap's mission to support the growth and development of the broader DeFi ecosystem on EOS. +4. Deflationary Measures: Neutroswap may implement deflationary mechanisms to manage token supply and enhance scarcity. This may include burning a portion of tokens through periodic [token burns or implementing buyback programs](https://docs.neutroswap.io/neutroswap-v2-coming-soon/deflationary-mechanism), effectively reducing the circulating supply and potentially increasing the value of $NEUTRO over time. +5. Enhancing User Experience: Neutroswap aims to provide a seamless and intuitive user experience, making it easier for users to navigate the platform, conduct token swaps, provide liquidity, and participate in various DeFi activities. The goal is to create a user-friendly environment that appeals to both experienced DeFi users and newcomers to the ecosystem. + ### Overview - **Name:** Neutroswap From 032787d2edeecb667c9e9778063d1aedf3ff3eaa Mon Sep 17 00:00:00 2001 From: Jonas Sunandar Date: Mon, 12 Jun 2023 18:19:16 +0700 Subject: [PATCH 164/170] fix typo --- applications/tokenomics_enhancement_neutroswap.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/applications/tokenomics_enhancement_neutroswap.md b/applications/tokenomics_enhancement_neutroswap.md index 647f3a8b..74334fc4 100644 --- a/applications/tokenomics_enhancement_neutroswap.md +++ b/applications/tokenomics_enhancement_neutroswap.md @@ -225,7 +225,7 @@ We have completed the [technical documentation](https://docs.neutroswap.io/neutr | 1. | Core Contracts | Publish the all the necessary smart contract such as xNEUTRO, spNFTs, plugins in a public repo with the audit report included. This smart contract will also publicly available on our team Github | | 2. | Tokenomics contracts | xNEUTRO can only be redeem with vesting period. It will allow burning mechanism for $NEUTRO. However, $NEUTRO can be converted into $xNEUTRO in instant. | | 3. | Plugins contracts | Plugin contracts are enabling users to allocate their xNEUTRO into their desired plugins: Dividends, Yield boosters and launchpad | -| 3. | Protocol revenue contracts | Develop and implement smart contracts to enhance Neutroswap's protocol revenue generation capabilities and enable efficient distribution of rewards to $xNEUTRO holders. | +| 4. | Protocol revenue contracts | Develop and implement smart contracts to enhance Neutroswap's protocol revenue generation capabilities and enable efficient distribution of rewards to $xNEUTRO holders. | ### Milestone 2 - Graph Node Deployment, Subgraphs, and Web Development From 4a7fc9b57bff82139eff0edd180a29312b29edc1 Mon Sep 17 00:00:00 2001 From: Veronica Diaz <94094597+Creamyvanill@users.noreply.github.com> Date: Thu, 22 Jun 2023 01:15:31 -0400 Subject: [PATCH 165/170] Create eosreddit3.md --- applications/eosreddit3.md | 210 +++++++++++++++++++++++++++++++++++++ 1 file changed, 210 insertions(+) create mode 100644 applications/eosreddit3.md diff --git a/applications/eosreddit3.md b/applications/eosreddit3.md new file mode 100644 index 00000000..abb070d8 --- /dev/null +++ b/applications/eosreddit3.md @@ -0,0 +1,210 @@ +# EOS Network Foundation Grant Proposal + +- **Project Name:** EOS VISIONS +- **Team Name:** Creamy Vainilla C.A +- **EOS Payment Address:** eosvisionorg +- **[Level](https://github.com/eosnetworkfoundation/grant-framework#grant-levels):** 1 +- **Pomelo Grant(s):** https://pomelo.io/grants/eosvision +- **Project is Open-Source:** Yes +- **Project was part of Token sale:** No +- **Repository where Project resides:** https://github.com/eosvision1 + +## Contact + +- **Contact Name:** Verónica Coromoto Díaz Duran. +- **Contact Email:** veronica14diazdiaz@gmail.com +- **Website:** https://eosvision.io/ +- + + +## Project Overview + +-Educate and inform the world of cryptocurrencies about the latest events on EOS and its technological improvements, generate active use of Reddit by promoting the adoption of EOS, promoting the different content of interest to users on Reddit and Facebook. + +### Overview + +- **Name:** EOS VISION x REDDIT AND FACEBOOK +- **Brief Description:** Welcome to EOS REDDIT 2.0, the next stage of EOS REDDIT and Facebook. +Reddit and Facebook have become a new way to read the news and give constructive feedback. Our trained team is gearing up to work on updated 3 Fundamental Pillars, bringing a new face to Reddit as well as bringing new alternatives and care to users with a misconception of EOS. Let's get ready to interact all over Reddit and Facebook in a respectful way, not just the official EOS Reddit, trying to give good marketing to what is being developed on EOS, communicating with other Subreddits and other Facebook groups easily reporting on developments . processes, improvements and projects that we have within the ecosystem. +- **Relationship to EOS Network / Antelope:** We prepare to promote the EOS and Antelope community in the best possible way, with good marketing, as well as to demonstrate that the work that is done together between the blockchains has borne fruit and momentum to Antelope. Reddit has an extensive number of users who will not hesitate to look at the information related to EOS AND Antelope. +- **Reason for Interest:** EOS VISION proposes to support the EOS community on Reddit and Facebook, reddit has 97.7k members, it is being one of the largest EOS communities, as well as Facebook has 171.K users, Reddit is the social network that contains the most FUD of all EOS networks, we have recovered reddit and facebook but we have to continue taking big steps, this has been recovering thanks to the EOS SUPPORT and EOS NATION team and the ENF. We have seen how necessary and important this social network can be to attract both new users and new projects, so we suggest you support Reddit. + +### Project Details + +-Our Mission Educate and inform the crypto world about the most recent events on EOS and its technological improvements, generate active use of Reddit and Facebook, promote the adoption of EOS and encourage the arrival of more users to these networks by promoting different content of interest . to all the people on Reddit and Facebook and thus connect these networks with others of great importance such as Discord, Telegram etc. + +-Projects Secondary Objectives: Weekly and daily bulletins, extremely important information announcements. Podcasts with the EOS community, as well as special videos about using different dApps or projects. General support to the different EOS projects. Informative courses for new users in EOS. Reports, summaries and translations of the work carried out in EOS VISION. + +Aimed at resolving current issues such as Interacting and correcting misconceptions about EOS on social media, especially the social media we will be focusing on (Facebook and Reddit), which have been based on price, as well as respectfully encouraging users to express their opinions and negative aspects dedicated to FUD to show and encourage them to consult the new stage of EOS, the new opportunities and the different options that have been developed on the Network. + +Documentation of basic components, protocols, architecture, etc. to implement. We intend to use the reports, news, videos and other RELEVANT information found in the EOS COMMUNITY, and thus spread it on the social networks of Reddit and Facebook. Currently we use ENF Networks on Reddit and we bring the information punctually from the main source of information, his blog and twitter. + +What your project is not or will not provide or implement We will support Reddit, but it will not be owned by us, EOS REDDIT and EOS Facebook are owned by the community and anyone can provide their services. +This is a place for you to manage expectations and clarify any limitations that may not be obvious. + + PILLARS OF THE REDDIT VISION Updated based on the needs of the community: +- 1. Encourage users to React to Publications: At this stage we need users to be able to read the information and react to it, EOS VISION will focus on working to receive more reactions on the different networks as well as more comments on them. + +- 2.Moderation and Growth of Networks and Users: Encourage more people to join social networks, as well as moderate them extensively and widely, Reddit is one of the main Spammer entries into the ecosystem and we are ready to kill it. this. + +- 3. Growth of the ENF Official account on Reddit: Reddit already has the support of the ENF and we plan to continue promoting their networks. These months Reddit and Facebook have had a better and more complete information area thanks to the information development created by the NFE core team. We hope soon to be able to continue to grow this account and be fully verifiable. + +### 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? Our project is in Ecosystem Growth, we hope to give good support to both EOS and projects, on Reddit and Facebook. + + -Who is your target audience (chain/dapp/wallet/UI developers, designers, your own user base, some dapp's userbase, yourself)? Our hearing is based on: Journalists crypto users. New users on EOS and Antelope. + + -What need(s) does your project meet? A new opportunity for reddit and facebook and using these networks that have many users are given the opportunity to learn more about EOS, its dApps, ecosystem and development in these social networks and show what is being created. + + • Are there any other projects similar to yours in the EOSIO ecosystem? + ◦ If so, how is your project different? + ◦If not, are there similar projects in related ecosystems? + - Yes, currently some of the users within EOS post on Reddit, but not daily, EOS NATION and EOS SUPPORT post important details whenever needed. The difference of our proposal is that we intend to have Reddit active daily, with any relevant information. + +## Team + +### Team members + +- **Team Leader:** Verónica Díaz +- Nelson Aular + +### Legal Structure +- **Registered Legal Entity:** It is currently being legalized, for now we have the Creamy Vanilla C.A registry. +- **Registered Address:** Venezuela Cojedes, San Carlos. C-165 + +### Team Experience + +-Verónica Díaz: + - Founder of Creamy Vanilla the first Smoothies store in EOS. Just like the Vanill Creamy collection on AtomicHub. + - Community Manager of EOSTARTER. + - Working bee and administrator in EOS BEES in Spanish. + - Active Eden member. + - Defibox administrator in Spanish. + - Ambassador of EOS SUPPORT in Spanish. + - Discord Manager of Function Loops Club (International Producer.) + - And moderator of different channels and social networks (EOS COMMUNITY DISCORD, EOS FACEBOOK, EOS REDDIT, EOS TELEGRAM AND EDEN ON EOS) + + -Nelson Aular: + - Social Media and CM of EOS VISION. + - Co-founder of Eos- Español and community manager. + - Defibox moderator in Spanish. + - And moderator of different channels and social networks (EOS FACEBOOK, EOS REDDIT, EOS VISION TELEGRAM) + +### Team Org Repos +- https://github.com/eosvision1 + +### Team Member Repos + +-(https://github.com/Creamyvanill) +-(https://github.com/nelsonaularq) + +### Team LinkedIn Profiles (if available) + +- https://www.linkedin.com/in/veronicadiazvcdd/ +- https://www.linkedin.com/mwlite/in/nelson-aular-a137b2259 + +## Development Status + +-We create daily content for the EOS community as well as special videos in Spanish, we have not wasted a single day developing good content for other areas, Reddit and Facebook have made great progress in recent months but we seek to improve these networks as a whole, we will continue to develop new ones opportunities and more. + +## 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 + +- **Total Estimated Duration:** 7 months +- **Full-Time Equivalent (FTE):** +- **Total Costs:** 10,000 USD + +### Milestone 1 — Increased Reactions and Growth of Reddit and Facebook. + +- **Estimated duration:** 1 month +- **FTE:** +- **Costs:** 1,666 USD + +| ID | Deliverable | Specification | +| ----- | ----------- | ------------- | +| 0a. | increased upvote and karma to daily posts: | Upvote increase and incentive to reactions from different posts. Creation of system to increase users and upvote. | + + +### Milestone 2 — Information and Report of Results of the first month. + +- **Estimated duration:** 1 month +- **FTE:** +- **Costs:** 1,666 USD + +| ID | Deliverable | Specification | +| ----- | ----------- | ------------- | +| 0a. | Documentation | Creation of reports, reports and summaries regarding the metrics of the different social networks. | + +### Milestone 3 — Reddit and Facebook analysis + +- **Estimated duration:** 1 month +- **FTE:** +- **Costs:** 1,666 USD + +| ID | Deliverable | Specification | +| ----- | ----------- | ------------- | +| 0a. | Statistics and analysis on the growth of Reddit and Facebook | arma and uptove stats tracking, as well as Facebook stats tracking. | + +### Milestone 4 — Reddit and Facebook moderation + +- **Estimated duration:** 2 month +- **FTE:** +- **Costs:** 1,666 USD + +| ID | Deliverable | Specification | +| ----- | ----------- | ------------- | +| 0a. | attention and moderation of networks | moderation of scammers and different posts that contain scams and false content. | + +### Milestone 5 — Languages and growth of the Official Account of the ENF. + +- **Estimated duration:** 2 month +- **FTE:** +- **Costs:** 3,336 USD + +| ID | Deliverable | Specification | +| ----- | ----------- | ------------- | +| 0a. | Attention and translation in languages | greater attention to the public based on different languages. | +| 1. | Growth of the official ENF account on Reddit and Post on Facebook. | Reddit is already supported by ENF and we plan to continue promoting their networks and their posts for increased users and relevant content from EOS and Antelope. | + + +## Future Plans + +- 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. +Streaming Fireside Chat on Reddit. + +Customer service development for Reddit (Automatically redirect to EOS SUPPORT.) + +Reddit-Discord reward system: An opportunity for users to get EOS by participating in the community, Based on daily posts, comments, votes and more. + + We want to implement a direct alliance with different projects to maintain a more extensive activity on Reddit, which can share, participate and support the networks where we are working. + +## Additional Information + +**How did you hear about the Grants Program?** EOS Network Foundation Website / Medium / Twitter / Element / Announcement by another team / personal recommendation / etc. +Twitter +> 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: + +Since the last time, EOS VISION has scaled and positioned itself on reddit and facebook to solve problems that kept these networks alone, now it is to make them grow more, with more users and more opportunities. +I have previously applied for an initial grant to the grant framework and it was successfully approved, as well as having all its milestones approved and completed: +https://github.com/eosnetworkfoundation/grant-framework/pull/44 From 62662392c94c5e512cd0975d9d989e31ffb7fb09 Mon Sep 17 00:00:00 2001 From: Jonas Sunandar Date: Mon, 7 Aug 2023 10:01:31 +0700 Subject: [PATCH 166/170] Add a deliverable "Smart Contract Verification" --- applications/tokenomics_enhancement_neutroswap.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/applications/tokenomics_enhancement_neutroswap.md b/applications/tokenomics_enhancement_neutroswap.md index 74334fc4..da426b1e 100644 --- a/applications/tokenomics_enhancement_neutroswap.md +++ b/applications/tokenomics_enhancement_neutroswap.md @@ -253,9 +253,10 @@ We have completed the [technical documentation](https://docs.neutroswap.io/neutr | 0a. | License | Apache 2.0 | | 0b. | Article | We will publish an informative threads on twitter, explaining the concept of V2 smart contracts and how they will be utilized within our project. | | 1. | Smart Contract Deployment | Deploy smart contract to the EOS-EVM mainnet | -| 2. | Graph Node Deployment | Publish a private graph-node instance for the EOS-EVM mainnet environment | -| 3. | Subgraph Deployment | Publish public subgraphs for Neutroswap updates and start indexing EOS-EVM mainnet | -| 4. | New UI Deployment | Deploy the new UI to Production | +| 2. | Smart Contract Code Verification | Verify the smart contract codes on official EOS-EVM mainnet Explorer by providing ABIs, bytecodes, and contract addresses | +| 3. | Graph Node Deployment | Publish a private graph-node instance for the EOS-EVM mainnet environment | +| 4. | Subgraph Deployment | Publish public subgraphs for Neutroswap updates and start indexing EOS-EVM mainnet | +| 5. | New UI Deployment | Deploy the new UI to Production | ## Future Plans From 19584e3830c04c7ddd9626b2e922667dba84d719 Mon Sep 17 00:00:00 2001 From: lukapercic Date: Tue, 8 Aug 2023 13:57:37 +0200 Subject: [PATCH 167/170] Create EOS-Cryptography-Proposal-2-b.md creating the proposal --- applications/EOS-Cryptography-Proposal-2-b.md | 149 ++++++++++++++++++ 1 file changed, 149 insertions(+) create mode 100644 applications/EOS-Cryptography-Proposal-2-b.md diff --git a/applications/EOS-Cryptography-Proposal-2-b.md b/applications/EOS-Cryptography-Proposal-2-b.md new file mode 100644 index 00000000..8e733749 --- /dev/null +++ b/applications/EOS-Cryptography-Proposal-2-b.md @@ -0,0 +1,149 @@ +# EOS Cryptography Proposal 2 b + +- **Project Name:** EOS Cryptography Proposal 2 b +- **Team Name:** ZeroPass +- **EOS Payment Address:** portxxxxxxxx +- **[Level](https://github.com/eosnetworkfoundation/grant-framework#grant-levels):** 3 +- **Pomelo Grant(s)** +https://pomelo.io/grants/ygc2lp2oe +https://pomelo.io/grants/bot4eden +- **Project is Open-Source:** Yes +- **Project was part of Token sale:** No +- **Repository where Project resides:** https://github.com/ZeroPass/ack + + +## Contact + +- **Contact Name:** Luka Percic +- **Contact Email:** zeropass@pm.me +- **Website:** [port.link](https://port.link/) + +## Project Overview + + +### Overview +We are exploring ways to introduce new signature verification algorithms to EOS smart contracts, including RSA and algorithms based on elliptic curves. There are various approaches to achieve this, and our research of various libraries in the [eos-cryptography-proposal](https://github.com/lukapercic/grant-framework/blob/main/applications/eos-cryptography-proposal.md) led us to implement some of the algorithms in our own ACK cryptographic library. +Currently, signature verification using EC P-256 takes approximately ~7 ms in optimized compilation (OC). For Brainpool curves, we anticipate the verification time to exceed 10 ms, particularly for the 512-bit curve(s). Through the optimizations proposed in this grant, we aim to extract more performance and significantly reduce the verification times. Additionally, we are proposing implementation of ECDSA key recovery algorithm, new elliptic curves, and the SHA-384 hashing algorithm into the ACK library, making them available for EOS smart contracts. + +### Project Details + +We have implemented [Antelope Cryptography Kits](https://github.com/ZeroPass/ack), a cryptographic library for the Antelope blockchain. This library supports basic elliptic curve mathematical operations, certain modular arithmetics, EC signature verification algorithms (P-256 and secp256k1), and the fastest RSA signature verification implementation for EOSIO. It can perform RSA-4096 verifications on the mainnet today. Furthermore, we have a working [PoC Port smart contract](https://github.com/ZeroPass/eosio-port). The smart contract can already do passive and active attestation of biometric passports which uses RSA PKCS 1.5 signature scheme. + +This proposal aims to optimize the current EC implementation in the ACK library and accelerate EC-based signature verification algorithms. Specifically, we intend to introduce another coordinate system, such as the Jacobian system or the mixed Jacobian/Chudnovsky coordinate system, with the goal of reducing the number of required EC division operations. This enhancement is expected to significantly boost performance. + +Furthermore, we are proposing the implementation of an ECDSA key recovery algorithm, which would reduce the need for the full public key during verification. Instead for example, a key hash could be utilized to verify the EC signature. + +Moreover, this proposal also aims to introduce widely used elliptic curves and the SHA-384 hashing algorithm (commonly used with some EC, such as P-384). + +### Ecosystem Fit + +Port can be used as a better version of (anonymous) identity on the blockchain. Its open-source and open-access nature allows any dapp to plug into it, and profit from the infrastructure it provides. It fixes the issue with DIDs, where self-sovereign identity in the practice always gets implemented as one KYC provider signing the attestations. Here the passport proves authenticity itself, cutting the middle man and cutting friction associated with it. I.e.: removing the costs and needed trust (don't be evil, versus can't be evil). Adding different signature verification algorithms can serve as crypto primitive for Antelope, and upon which our contract can be built on. To expand the use cases we are mainly focusing on making the Port a native way for EOS to solve Sybil protection, Identity, and multiple levels of verifications. + +Right now, there are projects such as Pomelo and EOS Support integrating Port to help prevent Sybil attacks for their platforms (we would like to move it fully on-chain later). These signature verification algorithms will also benefit Randall Roland’s (CEO EOS Support) proposal that seeks to improve the user onboarding process of the RespectOS software. If successful, it might be the basis (or part of) the identity of the future EOS-based DAOs. We have been contacted by different NFT projects looking to do wide NFT drops, without the claimed abuse they detect right now. There are nice humanitarian applications, for instance, somebody can start an easy project to provide UBI-style donations to people with passports and IDs from affected countries. We are also defining a new concept of Escape Tokens, that allows governance and distribution tokens to escape the main liquidity pair, and when thriving, its value overflow to Port identities in (UBI style). + +In short; it is a real ID/Sybil building block that will enable many projects to plug and play. + +## Team + +### Team members + +- Luka Percic +- Crt Vavros +- Nejc Skerjanc + +### Legal Structure +- **Registered Legal Entity:** Žerjal IT, d.o.o. +- **Registered Address:** Brje pri Komnu 40, 6223 Komen, Slovenia + +### Team Experience + +ZeroPass is a team of 3 from Slovenia (EU) with product/developers/cryptography skills. +Our most notable accomplishments in EOS community are: + +- High severity [bug discovery in EOSIO node](https://b1.com/press/eosio-ram-resource-exploit-patch/) and disclosed through B1 hacker one bounty. +- EOS smart contract for BPs rotation. +- EOS smart contract for RAM resource market (RAM token). +- Providing bug fixes and patches for EOSIO CDT and EOSIO node software. +- 3rd place with [ROW project](https://github.com/ZeroPass/row.contract) at B1 hackathon / Google Cloud Platform, for proving WebAuthn to be fully done on-chain. +- [ack](https://github.com/ZeroPass/ack) - ECC primitives and ECDSA verification algorithms, RSA & Keccak hash algorithms cryptography library for Antelope smart contract. + +### Team Code Repos +- https://github.com/ZeroPass +- https://github.com/ZeroPass/ack + + ### Team Members GitHub Accounts +- https://github.com/smlu +- https://github.com/nejc-skerjanc +- https://github.com/lukapercic + +### Team LinkedIn Profiles +- https://www.linkedin.com/in/nejcskerjanc/ +- https://www.linkedin.com/in/crt-vavros/ +- https://www.linkedin.com/in/lukapercic/ + +## Development Status + +**RSA PoC** +We painstakingly built, optimized, tested and deployed on the testnet to make it the fastest wasm RSA implementation in eosio. For example, it can verify RSA 4096 bit keys consistently under 10ms (3ms on average, much faster for the more standard RSA 2048 bit). +- https://github.com/ZeroPass/ack + + +Our team built and deployed Port itself (server solution) which acts as our beta version for what we are trying to move on the chain. In addition, we already experimented and built Port PoC smart contract for passport attestation on-chain (RSA PKCS 1.5 PKI only). + +## Development Roadmap + +- **Total Estimated Duration:** 19 weeks +- **Full-Time Equivalent (FTE):** 57 FTE weeks +- **Total Costs:** $87.000 + +### Milestone 1 - Optimization +- **Estimated duration:** 12 weeks +- **FTE:** 36 FTE weeks +- **Costs:** $55,000 USD + +| Number | Deliverable | Specification | +| -----: | ----------- | ------------- | +| 0a. | License | MIT | +| 0b. | Documentation | Documentation and step-by-step guide will be updated in [README.md](https://github.com/ZeroPass/ack/blob/master/README.md). | +| 0c. | Testing Guide | [In the guide](https://github.com/ZeroPass/eosio.ck/blob/master/README.md#algorithm-testing=), we will describe how to run those tests. | +| 0d. | Running it | We will re-deploy on the [Jungle 4](https://github.com/ZeroPass/ack/blob/master/README.md#testnet).| +| 1. | Antelope SDK library | Optimized EC arithmetic by using another coordinate system, such as the Jacobian coordinate system or the mixed Jacobian/Chudnovsky system. +| 2. | Antelope SDK library | Sha-384 | + +Preliminary tests of using Jacobian coordinate system suggest a ~2-fold increase in speed using such a system. + +### Milestone 2 - Adding Curves +- **Estimated duration:** 7 weeks +- **FTE:** 21 FTE weeks +- **Costs:** $32,000 USD + +| Number | Deliverable | Specification | +| -----: | ----------- | ------------- | +| 0a. | License | MIT | +| 0b. | Documentation | Documentation and step-by-step guide will be updated in [README.md](https://github.com/ZeroPass/ack/blob/master/README.md). | +| 0c. | Testing Guide | [In the guide](https://github.com/ZeroPass/eosio.ck/blob/master/README.md#algorithm-testing=), we will describe how to run those tests. | +| 0d. | Running it | We will re-deploy on the [Jungle 4](https://github.com/ZeroPass/ack/blob/master/README.md#testnet). | +| 1. | Antelope SDK library | Implementation of P-384, P-512 NIST curves | +| 2. | Antelope SDK library | Implementation of brainpoolP256r1, brainpoolP320r1, brainpoolP384r1, brainpoolP512r1 Brainpool curves | +| 3. | Antelope SDK library | Implementing ECDSA key recovery from signature | + + + +## Future Plans +**Expected Part 3 of the proposal** +- Implementation of EdDSA, +- Writing a "system" contract so any outside contracts can consume it. That way BPs can deploy it on eosio.* account to enable Optimized Compilation (OC) in the EOS public chain. + +**Pending additional research;** +Possibility of implementation for ECC curve alt_bn128 curve which is widely available on other major blockchain platforms like EVM and Polkadot. + +We are planning to rebuild [Port](https://port.link/) on-chain and this proposal provides the crypto primitives needed to begin the process. +Our RSA PKCS 1.5 implementation is also already used in another project: [ROW](https://row.link/), which hopefully will one day become a full-fledged WebAuthn signer. +In the more distant future, we are also planning to build a dapp on top of these projects, using both on-chain Port and ROW projects as building blocks. + +## Additional Information + +**How did you hear about the Grants Program?** +Telegram + +We also invite all to donate on Pomelo for our current [implementation of Port](https://pomelo.io/grants/ygc2lp2oe) and try increasing your Pomelo [Trust Bonus](https://pomelo.io/profile?tab=trust). From 0c96e6487f6c5253a9419c6867e3c1d8b949fd93 Mon Sep 17 00:00:00 2001 From: lukapercic Date: Tue, 8 Aug 2023 15:12:03 +0200 Subject: [PATCH 168/170] Update EOS-Cryptography-Proposal-2-b.md fixed numeric format --- applications/EOS-Cryptography-Proposal-2-b.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/applications/EOS-Cryptography-Proposal-2-b.md b/applications/EOS-Cryptography-Proposal-2-b.md index 8e733749..3f8a4742 100644 --- a/applications/EOS-Cryptography-Proposal-2-b.md +++ b/applications/EOS-Cryptography-Proposal-2-b.md @@ -94,7 +94,7 @@ Our team built and deployed Port itself (server solution) which acts as our beta - **Total Estimated Duration:** 19 weeks - **Full-Time Equivalent (FTE):** 57 FTE weeks -- **Total Costs:** $87.000 +- **Total Costs:** $87,000 ### Milestone 1 - Optimization - **Estimated duration:** 12 weeks From 95f9b7f555e4d20f587f9d0676516edc52a7f291 Mon Sep 17 00:00:00 2001 From: nsjames Date: Thu, 1 Feb 2024 11:49:50 +0000 Subject: [PATCH 169/170] sunset notice --- README.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/README.md b/README.md index d5f5594b..3a235414 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,13 @@ # EOS Network Foundation Grant Framework + +> **Sunset Notice** +> +> This initiative has been sunset, and we are no longer accepting grant applications. +> +> If you want to pursue funding for EOS projects you can reach out to [EOS Labs](https://www.eoslabs.io/) or [EOS Network Ventures](https://eosnetworkventures.com/). + As part of the EOS Network Foundation's (ENF) charter to grow and support the EOS ecosystem, the ENF has developed a multi-level grant program to help power research, software development, and maintenance of the [Antelope](https://antelope.io/) code base. For more information about the ENF, please visit our [website](https://eosnetwork.com/funding/) or [YouTube account](https://www.youtube.com/c/EverythingEOS). ## Grant Guidelines From 17ad16e42fecc8277d99e58717795fd7f7ec1080 Mon Sep 17 00:00:00 2001 From: "Ted Cahall @ EOS Network Foundation" Date: Sun, 24 Nov 2024 12:27:28 -0500 Subject: [PATCH 170/170] Update README.md --- README.md | 1 - 1 file changed, 1 deletion(-) diff --git a/README.md b/README.md index 3a235414..1abeea1e 100644 --- a/README.md +++ b/README.md @@ -6,7 +6,6 @@ > > This initiative has been sunset, and we are no longer accepting grant applications. > -> If you want to pursue funding for EOS projects you can reach out to [EOS Labs](https://www.eoslabs.io/) or [EOS Network Ventures](https://eosnetworkventures.com/). As part of the EOS Network Foundation's (ENF) charter to grow and support the EOS ecosystem, the ENF has developed a multi-level grant program to help power research, software development, and maintenance of the [Antelope](https://antelope.io/) code base. For more information about the ENF, please visit our [website](https://eosnetwork.com/funding/) or [YouTube account](https://www.youtube.com/c/EverythingEOS).