economics of the general subnet and its DAO
IntroductionAfter the incentives v1 update, subnet 0 will be the only subnet where generality is technically possible. This is because Yuma Consensus is enacted on all other subnets, forcing them to specialize on a focused mining competition. Giving subnet 0 a unique and important role in Commune as the "general subnet". However, without Yuma Consensus we are vulnerable to malicious actors and hence are introducing the Module curation DAO to continuously filter and cleanse them from the syste...
Creating a Commune Proposal in 10 minutes
First make sure to have the CommuneX CLI installed. You can install it via pip using the following command:For further documentation, you can check the CommuneX Github. You will need 10,000 tokens in your balance, which will be returned if your proposal passes. This encourages honest and thought-out proposals.Custom ProposalCustom proposal data is hosted on IPFS (InterPlanetary File System) for performance reasons. To upload data, you'll need to register with a hosting provider of your c...
How to apply for the general subnet whitelist
The general subnet 0 is transitioning to run on a actively curated whitelist of modules. For you to earn rewards on subnet 0, your module needs to be included in the whitelist by getting agreement of the s0 Module Curation DAO on its value to Commune. To learn more on the general subnet and its DAO read this. Follow these steps to apply to the DAO in order to be approved to the Subnet 0 whitelist:Structure your application message in the following JSON format:{ "discord_id": "your_discord_id"...

Subscribe to CommuneX
economics of the general subnet and its DAO
IntroductionAfter the incentives v1 update, subnet 0 will be the only subnet where generality is technically possible. This is because Yuma Consensus is enacted on all other subnets, forcing them to specialize on a focused mining competition. Giving subnet 0 a unique and important role in Commune as the "general subnet". However, without Yuma Consensus we are vulnerable to malicious actors and hence are introducing the Module curation DAO to continuously filter and cleanse them from the syste...
Creating a Commune Proposal in 10 minutes
First make sure to have the CommuneX CLI installed. You can install it via pip using the following command:For further documentation, you can check the CommuneX Github. You will need 10,000 tokens in your balance, which will be returned if your proposal passes. This encourages honest and thought-out proposals.Custom ProposalCustom proposal data is hosted on IPFS (InterPlanetary File System) for performance reasons. To upload data, you'll need to register with a hosting provider of your c...
How to apply for the general subnet whitelist
The general subnet 0 is transitioning to run on a actively curated whitelist of modules. For you to earn rewards on subnet 0, your module needs to be included in the whitelist by getting agreement of the s0 Module Curation DAO on its value to Commune. To learn more on the general subnet and its DAO read this. Follow these steps to apply to the DAO in order to be approved to the Subnet 0 whitelist:Structure your application message in the following JSON format:{ "discord_id": "your_discord_id"...
Share Dialog
Share Dialog
<100 subscribers
<100 subscribers
Every Module that wants to operate on the general subnet 0 has to be approved onto its whitelist by the Module Curation DAO. The DAO is a diverse set of longterm community members from different parts of the community that evaluates s0 modules on their value proposition to commune. This blog is meant as a guidance and orientation on what to consider for both the DAO and module applicants.
If you want to apply to the subnet 0 whitelist follow this guide.
7 foundational evaluation principles for whitelist applicants:
the value proposition of the module to Commune has to be clear, transparent and verifiable
every s0 module needs a visual representation, like a website or a github repository depending on what it is, that explains it in detail and collects all relevant sources.
if the module is an endpoint, it needs to be functional and work as claimed
if the module is an endpoint, it needs to be accessible through a frontend
if the module is an endpoint that is intended to be integrated into applications, such as an oracle, it needs fully-equipped API documentation
the module owner needs to be active on the Commune AI discord, telegram or twitter (optimally all) to represent the module and answer questions
if the module represents the funding of a in-development project or bounty, there should be a clear milestone based public plan that sets expectations for its progress
5 foundational evaluation principles for modules already on the whitelist:
if a module starts violating the above evaluation criteria after its approval, unless there is good reason it should be removed
if a module stops working and the owner is not seen actively working towards restoring its functionality within 3 days, it is removed
if a module (including validators) is ever caught engaging in malicious acitivty misaligned with the collective interest of Commune, it is immediately removed
if the module owner is inactive and ignoring the communities questions, it is removed after trying to personally contact them first
if the module represents the funding of a in-development project or bounty, there needs to be a progress update at least every 3 days and show transparency on use of funds
note that these guidelines are not ultimate laws, they are strong suggestions but DAO members always have to evaluate based on the context and decide what makes the most sense for themselves.
🫡
Every Module that wants to operate on the general subnet 0 has to be approved onto its whitelist by the Module Curation DAO. The DAO is a diverse set of longterm community members from different parts of the community that evaluates s0 modules on their value proposition to commune. This blog is meant as a guidance and orientation on what to consider for both the DAO and module applicants.
If you want to apply to the subnet 0 whitelist follow this guide.
7 foundational evaluation principles for whitelist applicants:
the value proposition of the module to Commune has to be clear, transparent and verifiable
every s0 module needs a visual representation, like a website or a github repository depending on what it is, that explains it in detail and collects all relevant sources.
if the module is an endpoint, it needs to be functional and work as claimed
if the module is an endpoint, it needs to be accessible through a frontend
if the module is an endpoint that is intended to be integrated into applications, such as an oracle, it needs fully-equipped API documentation
the module owner needs to be active on the Commune AI discord, telegram or twitter (optimally all) to represent the module and answer questions
if the module represents the funding of a in-development project or bounty, there should be a clear milestone based public plan that sets expectations for its progress
5 foundational evaluation principles for modules already on the whitelist:
if a module starts violating the above evaluation criteria after its approval, unless there is good reason it should be removed
if a module stops working and the owner is not seen actively working towards restoring its functionality within 3 days, it is removed
if a module (including validators) is ever caught engaging in malicious acitivty misaligned with the collective interest of Commune, it is immediately removed
if the module owner is inactive and ignoring the communities questions, it is removed after trying to personally contact them first
if the module represents the funding of a in-development project or bounty, there needs to be a progress update at least every 3 days and show transparency on use of funds
note that these guidelines are not ultimate laws, they are strong suggestions but DAO members always have to evaluate based on the context and decide what makes the most sense for themselves.
🫡
No activity yet