🔗 govgen-1
Directory for GovGen and AtomOne Validators
The GovGen and AtomOne Validators directory is a space to build a registry of GovGen and AtomOne validators for the community. A comprehensive list of validators, with information on who they are and how to get in touch, will make it easier for the validators community to engage directly with one another, coordinate upcoming tasks, and collaborate more efficiently. This directory is also a great space to discuss validated proposals in regard to operating requirements, upcoming issues, implementation ideas, or proposed solutions.
All validators who have voted NO or NWV on CosmosHub proposal #848 are invited to submit their request for participation through a pull request to this repository.
The Validators directory of the AtomOne repo is an initiative to help serve as a guide to:
- make it easier for existing projects, newcomers and community members to identify the approved validators
- for validators to coordinate on upcoming tasks and issues related to their operating activity as well as share valuable resource
- find development synergies and implementations
- make introductions to potential partners
- get plugged into the ecosystem
—--------------------------------------
AtomOne Validator Application Template:
Welcome. If you are a validator and would like to submit your application to join the AtomOne GovGen Validator Directory, please use this template to submit a pull request. You can tag it with "validators directory"
- The name of your validator
- Why you want to become a validator for GovGen and AtomOne
- Brief history/ Intro to your validator
- Details of your validator (website and contact email)
- Team structure, roles, and Discord handles
- Link to your main social accounts
- Unique validator key to submit
- Region you and/or your validator is based (country)
In order for the application to be approved by the community, all AtomOne/GovGen Validators:
- Must replicate, understand, and validate the genesis distribution. (See atomone-hub/genesis#65 (review))
- Must contribute to the above to prove understanding of it by contributing to the code or creating a PR/PRs
- Must adhere to a global decentralization mandate and if required to cooperate in translation for an efficient global reach
- Must provide Transparency disclosures of associations among validators. (Also see Validators and KYC #75).
- The Community will put together best practices for KYC-ing and approving validator submissions. The conversation can be followed here: (Validators and KYC #75))