Skip to content

Latest commit

 

History

History
48 lines (27 loc) · 2.36 KB

Provalidator.md

File metadata and controls

48 lines (27 loc) · 2.36 KB

Validator Directory: Provalidator

  1. The name of your validator
  • Provalidator
  1. Why you want to become a validator for GovGen and AtomOne
  • Provalidator has cast a ‘No with Veto’ vote on proposal #82 and a ‘No’ vote on proposal #848, reflecting our belief that these proposals diverge from the foundational principles of Cosmos and fall short of their intended objectives. In light of this, we are eager to collaborate with GovGen and AtomOne, contributing to the community with the aim of pooling our expertise. Together, we aspire to forge a path forward, leveraging our collective experience to realize shared goals.
  1. Brief history/ Intro to your validator
  1. Details of your validator (website and contact email)
  1. Team structure, roles, and Discord handles
  • Founder: Joon Park, provalidator
  • Technical Director: Zenon Baek, zenon_provalidator
  • Business Development: Brian Oh, brian_provalidator
  1. Link to your main social accounts
  1. Unique validator key to submit
  • TBD
  1. Region you and/or your validator is based (country)
  • South Korea
  1. Must replicate, understand, and validate the genesis distribution. (See atomone-hub/genesis#65 (review) (atomone-hub/genesis#65 (review)))

  2. Must contribute to the above to prove understanding of it by contributing to the code or creating a PR/PRs

  3. Must adhere to a global decentralization mandate and if required to cooperate in translation for an efficient global reach

  4. Must provide Transparency disclosures of associations among validators. (Also see Validators and KYC #75 (atomone-hub/genesis#75 (comment))).

  5. The Community will put together best practices for KYC-ing and approving validator submissions. The conversation can be followed here: (Validators and KYC #75) (atomone-hub/genesis#75 (comment)))