| Secret Network Developer DAO (Secret Dev DAO)
| ## Project Description
We intend to create a Developer DAO on Secret.
|
| We are a Developer DAO currently deployed on Harmony. We want to build on Secret and support the Secret Network ecosystem. We believe privacy is the future and want to be part of it. We also love Rust and want to focus on the project building the best Rust-based dApps out there. Here are the links to the Harmony Dev DAO to show you who we are: Telegram: https://t.me/+e44CHO1hNqBiOTRhDiscord: https://discord.gg/MswWavU228Github: https://github.com/harmony-devdaoTwitter: https://mobile.twitter.com/harmony_dev_daoLinkedIn (optional):Please link to any public projects you (or your team) have built: Examples of projects created include https://fishfight.one/ a game built using the VRF-function on Harmony. It shows how VRF can be used in a gamefi project. Additional projects include supporting Validators on the Harmony blockchain through improving their voting system, as well as maintaining the testnet. We have other projects as well, including https://harmony-devdao.github.io/wallet-integration-mm/ Which is a wallet integration. Tutorial-related content from the DAO is unique as well. This includes tutorials on how to de-code issues with code, such as this.
|
| ## Problem / Solution
| The problem is that Devs want to be able to interact with other Devs. Either by asking them in the #devassist channel or by asking them Q/As during a Townhall. This also includes issues like Bug Bounties on DeWork, use of Commonwealth to get feedback, and many other examples of DAO-tooling support ecosystem growth. The solution is a Developer DAO devoted to supporting Devs; utilizing the latest DAO-tooling to enable this.
|
| ## Detailed product description
| Dev DAO Tooling
This would include Aragon to build Governance Infrastructure
Expand DeWork to enable bounty creation to support the Secret Ecosystem. This prioritizes bug fixes, dev retention, and dev interaction on Secret, and task management. Clickup/Jiro for clearly organizing the work of the DAO
Documentation like How to Integrate a Project: FishFight
How to integrate FishFight on SecretOffering the video and content integration documentation of FishFight as a project Community Support ContentOffer Dev Support in Discord,
Telegram to support Dev-related issuesTelegram/Twitter AMAs to build community interactionMonthly Dev Town Halls so devs can learn from each other’s experiences
Aragon to build Governance Infrastructure | Expand DeWork to enable bounty creation to support the Secret Ecosystem. This prioritizes bug fixes, dev retention, and dev interaction on Secret, and task management.
Clickup/Jiro for clearly organizing the work of the DAO | How to integrate FishFight on Secret
Offering the video and content integration documentation of FishFight as a project
Offer Dev Support in Discord, Telegram to support Dev-related issues
Telegram/Twitter AMAs to build community interaction
Monthly Dev Town Halls so devs can learn from each other’s experiences
| ## Go-to-Market plan:
The DAO has previously worked with Solidity for the EVM-compatible Harmony chain. But we are also equally capable of building in Rust.The DAO governors are also familiar with Typescript -- useful for calling the APIs in Secret’s library (like griptape). Additionally, for SecretPy Library, we want to help build the documentation there as well. The DAO contains governors from a variety of front-end and back-end backgrounds. From video game development (i.e. Ed Noris’s FishFight) to front-end and back-end development.
|
|
| ## Value capture for Secret Network ecosystem
| The main KPIs we are looking to are 1000 Discord members, 1000 Twitter followers, Twitter Spaces with at least 30 listeners, Dev Townhalls on Discord with at least 30 Devs. This would be followed by the documentation on Notion/Gitbooks for Secret Network growing with contributions as well. In addition, there would be 3 videos a month for documentation purposes.
|
| ## Team members
Sev: Dev Support (https://github.com/Severino)
Krueger: Content Creation and Dev Support, Operations https://github.com/y04nqt
Toni: Dev Support and Social Media (https://twitter.com/toni_x_coder and https://github.com/toniton)
George: Operations and Social Media
Markus: Content Creation and Tutorials
Ed Noris: Content Creation (https://trustlessteam.one/ and creator of https://fishfight.one/ and https://github.com/twobitEDDVicta: Content Creation (https://github.com/sprect8)
|
| ## Team Website
| https://harmonydevdao.carrd.co/
|
| ## Team's experience
|
| The team has an average of 8 years of coding experience. Check our linkedin and githubs for more info.
|
| We have been a team for more than a year now.
Harmony ONE tokens dropped 90% in value from March, 2022 to July, 2022. The hack also meant any stablecoins -- on Harmony’s Horizon Bridge -- became virtually worthless due to the subsequent de-peg. Price link. However, DevDAO operations still continue, and the past 12 months have been an incredibly productive time for the DAO.
Unfortunately, the price downturn due to the 29th of June Hack has created headwinds for the Harmony Development Ecosystem. The potential challenges Harmony faces in the near-term means it would be prudent to begin a new DAO with many of the same governors and DAO tooling as before. In essence, turning our experiences into the building blocks for Secret.
|
| ## Team Code Repos
| https://github.com/harmony-devdao
|
| ## Team LinkedIn Profiles
|
| Sev: Dev Support (https://github.com/Severino)Krueger: Content Creation and Dev Support, Operations https://github.com/y04nqtToni: Dev Support and Social Media (https://twitter.com/toni_x_coder and https://github.com/toniton)George: Operations and Social MediaMarkus: Content Creation and Tutorials Ed Noris: Content Creation (https://trustlessteam.one/ and creator of https://fishfight.one/ and https://github.com/twobitEDDVicta: Content Creation (https://github.com/sprect8)
|
|
| ## Development Roadmap
| 18-month Roadmap
Our 18-month roadmap would be split into 3 parts and each would be 6 months long. 1) Content 2) Dev Support 3) Community Building and AdvisoryFirst 6 months The first term will be devoted to content and supporting the expansion of Secret’s documentation. This will include interacting with developers to support adding to the knowledgebase.
This is primarily due to the gradual increase in projects coming to Secret. Naturally, projects will expect a lot of documentation before spending resources to integrate with Secret. Additionally, video and other kinds of content will be produced generally following the below guidance. Content and Educational Roadmap and our Term 1 Objectives
The content will have an emphasis on solidity and typescript, preventing exploits, creating contracts, and general good practices. Examples will include but are not limited to: Video Content- Smart contract storage addressing:How variables are stored in virtual memory and how to find and access given data.
This could be useful for accessing unexported variables.- Secret codebase: An overview of the structure and architecture of the codebase. Overview of how to search https://wiki.Secret.org/ and how to find the best documentation. This would be especially graphic heavy with lots of topology diagrams.- Transaction signing and RLP encoding: Not necessarily going too deep into the math of it, but explaining the general method and process of signing a transaction. What it means to have the private-key/public-key. How to verify transactions.
Explaining why this is so secure. When talking about this together with transactions RLP encoding can be explained and how it's used to send signed transactions.- Applications of existing private-key/public-key infrastructure:dApps don't necessarily need to do transactions.
For example, multisig and snapshot where you can take advantage of everyone having a private-key/public-key and not needing to pay gas. What this is all about and what this is and could be used for.
This might also serve for a general cleanup of misconceptions about what a blockchain actually is i.e.: Blockchain != Cryptocurrency. Cryptocurrency is just one good application of this concept.
Written Content:Creating a Knowledge Base for Developers on Notion to act as a Developer Repository. This will also allow new Devs to grab boilerplate code and build from there. How to set up a local work environment to make it super clearly explained; this will easily avoid bottlenecks.
Second 6 months... after the first phase, we will move on to the second phase of scaling the DAO. This phase will focus on creating a self-sustaining DAO and building the tooling necessary for this. In addition, it will create the right tooling and incentive structures to support on-boarding and developer support for Secret. We will still continue to create Content and Community Support. However, an emphasis will be on Developer Support Support with the expectation that there will be more projects on Secret. Doing so, this alleviates the burden of the original team behind Secret to answer all questions from the devs.
The Developer DAO transitions to fill the gap between the original Secret team and the wider Secret dev community. Create a new category of DAO members called DAO supporters. These supporters will gradually take more responsibility for the operational management of the DAO from the DAO governors. Offer 48-hour ticket tournament for answerable support tickets. Users can connect to the knowledgebase like https://wiki.Secret.org/ and submit tickets there or on Discord.Push partnerships for projects across Secret in order to have monthly Dev Townhalls so devs can learn from each other’s experiences
During the Third period of 6 months... the effort will be made to make the DAO self-sustaining and totally community managed and operated. Add more community-related tooling like Aragon for DAO tokens
DAO Governors transition into signatories. Create DAO IOUs for work rendered by supporters. These tokens are for offering work so that governors can become signatories and empower individual community members to participate in the DAO. DAO tokens would become an IOU for anyone contributing to the DAO. The IOU would mean it could be cashed in for an equivalent amount of stablecoins after a vote on the completion of the work.
This way, new members can contribute to the DAO and be paid for the work Make the Developer DAO self-sustaining about offering paid-advisory support for projects | Video Content | - Smart contract storage addressing:How variables are stored in virtual memory and how to find and access given data.
This could be useful for accessing unexported variables.
|
| Example milestones:
| We are open to discussing this. We thought for the first 4 months, there would be an initial funding amount of approximately 30,000 USD -- similar to how we helped build the Harmony Developer DAO. However, we are open to feedback on this as we understand there’s a lot of sensitivity around throwing money at a DAO -- especially a DAO coming from the Harmony ecosystem.
The DAO has previously worked with Solidity for the EVM-compatible Harmony chain. But we are also equally capable of building in Rust.The DAO governors are also familiar with Typescript -- useful for calling the APIs in Secret’s library (like griptape). Additionally, for SecretPy Library, we want to help build the documentation there as well. The DAO contains governors from a variety of front-end and back-end backgrounds. From video game development (i.e. Ed Noris’s FishFight) to front-end and back-end development. | | | ## Value capture for Secret Network ecosystem | The main KPIs we are looking to are 1000 Discord members, 1000 Twitter followers, Twitter Spaces with at least 30 listeners, Dev Townhalls on Discord with at least 30 Devs. This would be followed by the documentation on Notion/Gitbooks for Secret Network growing with contributions as well. In addition, there would be 3 videos a month for documentation purposes. | | ## Team members Sev: Dev Support (https://github.com/Severino) Krueger: Content Creation and Dev Support, Operations https://github.com/y04nqt Toni: Dev Support and Social Media (https://twitter.com/toni_x_coder and https://github.com/toniton) George: Operations and Social Media Markus: Content Creation and Tutorials Ed Noris: Content Creation (https://trustlessteam.one/ and creator of https://fishfight.one/ and https://github.com/twobitEDDVicta: Content Creation (https://github.com/sprect8) | | ## Team Website | https://harmonydevdao.carrd.co/ | | ## Team's experience | | The team has an average of 8 years of coding experience. Check our linkedin and githubs for more info. | | We have been a team for more than a year now.
Created by Harmony in September 2021: https://talk.harmony.one/t/developer-dao-mandates-deliverables/2145
Supported by Harmony Co-Founder, Stephen Tse: https://twitter.com/stse/status/1433525374227415040?s=20&t=-1LACMkxjqVPsSofFGfCVw Funded by Harmony for 100,000 USD worth of ONE (in ONE tokens only) in March, 2022 by Harmony: https://talk.harmony.one/t/developer-dao-funding-request/9804
Harmony ONE tokens dropped 90% in value from March, 2022 to July, 2022. The hack also meant any stablecoins -- on Harmony’s Horizon Bridge -- became virtually worthless due to the subsequent de-peg. Price link. However, DevDAO operations still continue, and the past 12 months have been an incredibly productive time for the DAO.
Unfortunately, the price downturn due to the 29th of June Hack has created headwinds for the Harmony Development Ecosystem. The potential challenges Harmony faces in the near-term means it would be prudent to begin a new DAO with many of the same governors and DAO tooling as before. In essence, turning our experiences into the building blocks for Secret. | | ## Team Code Repos | https://github.com/harmony-devdao | | ## Team LinkedIn Profiles | | Sev: Dev Support (https://github.com/Severino)Krueger: Content Creation and Dev Support, Operations https://github.com/y04nqtToni: Dev Support and Social Media (https://twitter.com/toni_x_coder and https://github.com/toniton)George: Operations and Social MediaMarkus: Content Creation and Tutorials Ed Noris: Content Creation (https://trustlessteam.one/ and creator of https://fishfight.one/ and https://github.com/twobitEDDVicta: Content Creation (https://github.com/sprect8) | | | ## Development Roadmap | 18-month Roadmap Our 18-month roadmap would be split into 3 parts and each would be 6 months long. 1) Content 2) Dev Support 3) Community Building and AdvisoryFirst 6 months The first term will be devoted to content and supporting the expansion of Secret’s documentation. This will include interacting with developers to support adding to the knowledgebase.
This is primarily due to the gradual increase in projects coming to Secret. Naturally, projects will expect a lot of documentation before spending resources to integrate with Secret. Additionally, video and other kinds of content will be produced generally following the below guidance. Content and Educational Roadmap and our Term 1 Objectives
The content will have an emphasis on solidity and typescript, preventing exploits, creating contracts, and general good practices. Examples will include but are not limited to: Video Content- Smart contract storage addressing:How variables are stored in virtual memory and how to find and access given data.
This could be useful for accessing unexported variables.- Secret codebase: An overview of the structure and architecture of the codebase. Overview of how to search https://wiki.Secret.org/ and how to find the best documentation. This would be especially graphic heavy with lots of topology diagrams.- Transaction signing and RLP encoding: Not necessarily going too deep into the math of it, but explaining the general method and process of signing a transaction. What it means to have the private-key/public-key. How to verify transactions.
Explaining why this is so secure. When talking about this together with transactions RLP encoding can be explained and how it's used to send signed transactions.- Applications of existing private-key/public-key infrastructure:dApps don't necessarily need to do transactions.
For example, multisig and snapshot where you can take advantage of everyone having a private-key/public-key and not needing to pay gas. What this is all about and what this is and could be used for.
This might also serve for a general cleanup of misconceptions about what a blockchain actually is i.e.: Blockchain != Cryptocurrency. Cryptocurrency is just one good application of this concept.
Written Content:Creating a Knowledge Base for Developers on Notion to act as a Developer Repository. This will also allow new Devs to grab boilerplate code and build from there. How to set up a local work environment to make it super clearly explained; this will easily avoid bottlenecks.
Second 6 months... after the first phase, we will move on to the second phase of scaling the DAO. This phase will focus on creating a self-sustaining DAO and building the tooling necessary for this. In addition, it will create the right tooling and incentive structures to support on-boarding and developer support for Secret. We will still continue to create Content and Community Support. However, an emphasis will be on Developer Support Support with the expectation that there will be more projects on Secret. Doing so, this alleviates the burden of the original team behind Secret to answer all questions from the devs.
The Developer DAO transitions to fill the gap between the original Secret team and the wider Secret dev community. Create a new category of DAO members called DAO supporters. These supporters will gradually take more responsibility for the operational management of the DAO from the DAO governors. Offer 48-hour ticket tournament for answerable support tickets. Users can connect to the knowledgebase like https://wiki.Secret.org/ and submit tickets there or on Discord.Push partnerships for projects across Secret in order to have monthly Dev Townhalls so devs can learn from each other’s experiences
During the Third period of 6 months... the effort will be made to make the DAO self-sustaining and totally community managed and operated. Add more community-related tooling like Aragon for DAO tokens
DAO Governors transition into signatories. Create DAO IOUs for work rendered by supporters. These tokens are for offering work so that governors can become signatories and empower individual community members to participate in the DAO. DAO tokens would become an IOU for anyone contributing to the DAO. The IOU would mean it could be cashed in for an equivalent amount of stablecoins after a vote on the completion of the work.
This way, new members can contribute to the DAO and be paid for the work Make the Developer DAO self-sustaining about offering paid-advisory support for projects | Video Content | - Smart contract storage addressing:How variables are stored in virtual memory and how to find and access given data.
This could be useful for accessing unexported variables. | | Example milestones: | We are open to discussing this. We thought for the first 4 months, there would be an initial funding amount of approximately 30,000 USD -- similar to how we helped build the Harmony Developer DAO. However, we are open to feedback on this as we understand there’s a lot of sensitivity around throwing money at a DAO -- especially a DAO coming from the Harmony ecosystem.