Expectations for Registrar Candidates on Kusama Network: Some Recommendations
It is everyone's expectation for the community to welcome new Registrar candidacies aiming to decentralize the role as much as possible. Given the last discussions regarding this type of proposals, we expect those who want to become Registrars to explain their intentions and plans beforehand, and once the proposal is in the queue ask the community to second it to move forward to the referenda queue.
Make sure to be active on all channels and talk to your council members and the community in general about your proposal. To do this, share this information on the Kusama Direction Channel and on any of the forums available for the Community.
In order to keep candidacies organised and to make sure the community has full information, we encourage all candidates to follow these recommendations:
-
Registrars should be known: some kind of identity linked to the address should be available for the community to communicate with the proposer, and at least two communication channels should be in place in the on-chain identity for a registrar to show availability.
-
Registrars should publish what the requirements are for the judgement levels available and what the registrar fee is.
-
Specifics on infrastructure used (in particular backend architecture and any custom code) should be published and kept up to date. The candidate should explain the code and design on the proposal, if any. **There should always be room for differentiation: ** innovation is always welcomed, but remember a price-sensitive strategy can also be attractive to the community. A Registrar should know what differentiates their approach from others.
The Registrar's design should deliver efficiently.
- The proposer should provide timely responses to the community in the Kusama Direction channel or in the forum where the discussion is happening, as well as make sure that communication channels on their on-chain identity are up to date.
It is essential for a Registrar to respond fast in the eventuality of a blacklist event if needed: for this, efficient communication is important to the role.
- Registrar should prove some kind of experience related to the candidacy and involvement in the community. Explain in your proposal what is the reason for your candidacy, in which way have you been involved in the Kusama Community up to now, if any, and what is in your perspective the role of the Registrar.
Check the Kusama Wiki page to learn more about how to become a registrar and how to set an identity.
Comments (3)
A while back I tried and failed to register an application-specific registrar. I would like to try this again one of these days, having learned much since then, but I believe these guidelines should accommodate such non-standard registrars. Can we start a discussion around that as well?
@bruno: definitely, what changes do you envision on the guidelines or what to add in order to accommodate non-standard registrars focusing on specific apps? and when you talk about these type of candidates: how do you define them? I believe the current guidelines should also apply to these registrars, but happy to add more thinking about these specifically. I think it'd make sense to present it once chirp is out and running for people to actually use the registrar, or do you prefer to have it in place already?