The general subnet s2 has been around in Commune for a while, but so far has not been properly utilized. The main reason for this is the lack of user interface and tooling. Today, this changes. We have developed a comprehensive web platform to realize the potential of s2, making it easy for Commune Stakeholders to interact with the subnet and for the s2 DAO to manage the continuous module curation process. Every type of interaction with the subnet can now be done through the web frontent.
This blogpost will explain how the general subnet and the Community Validator platform works and how you can participate.
The general subnet s2
This subnet is unique in that it has no consensus mechanism limiting it to a singular validation mechanism. Weights translate linearly to incentive, allowing users to manually decide which modules they’d like to incentivise. The subnet is fully flexible to any diverse set of modules. Modules can be anything that you can put behind an endpoint or link to an identifier. Any piece of software, compute, data or X account, community initiative etc.
The economy of the general subnet is simple. Modules can create a condition of how much stake-weight a key needs to allocate to it, in order to access it at a certain bandwidth. The more demand Stakeholders have for a Module, the higher its rewards.
S2 Module Curation DAO
In order to protect against dishonest weights on junk modules, we introduced the s2 Module Curation DAO. This DAO has to approve Module’s applications to join a “legit module“ whitelist, and can remove Modules from that whitelist anytime based on 2/3 majority rule. The DAO follows these evaluation criteria. Weights can only be set on whitelisted Modules, meaning other modules cannot receive rewards.
You can create a s2 Module application via the Governance Portal.
Propose Change → Create new S2 Application
You can also register a Module to s2 fully through the Governance Portal.
Propose Change → Register a Module → S2
The concept of the Community Validator is simple. Holders can delegate their stake to the community validator and fully control it through the user-friendly web frontent, to participate on the general subnet s2 and the rootnet s0.
This gives you the power to determine how your stake influences s2’s module landscape and the protocols subnet landscape. This works by obtaining the validator weights by merging user weights together weighted based on their delegated stake.
First you select which Modules and which Subnets you’d like to allocate any incentive at all. Then you determine how much % of your influence should be allocated to them.
You can see, how other users have allocated their influence.
When new human-centric subnets launch, we will expand the frontent to them.
Coming platform updates
Once Commune allows validators to delegate their weight setting on specific subnets to other validators (child keys in Bittensor), we can enable existing validators to delegate weight setting to the Community Validator on s2. This will enable their delegators to utilize the s2 platform without directly delegating stake to the Community Validator.
We will provide an API for s2 Modules allowing them to easily retrieve how much stake-weight delegating keys have set on their module. This will allow them to create a pricing model, limiting access based on stake-weight.
We will add a Module-idea section to the frontent, where potential modules can be suggested and users can allocate weight to them based on their real stake. This will allow people to express their interest for certain ideas, making it easier to gauge what will likely be successful and what not.