Skip to content

Latest commit

 

History

History
38 lines (26 loc) · 2.71 KB

TaxiStake.md

File metadata and controls

38 lines (26 loc) · 2.71 KB

  1. Why you want to become a validator for GovGen and AtomOne?

    1. TaxiStake manages the ShapeShift DAO and TaxiStake validators within the Cosmos ecosystem. ShapeShift DAO voted NO on proposal 848. AtomOne's focus on sovereignty, security, and decentralization is significant. As validators, we are devoted to fostering a robust and inclusive decentralized ecosystem. We do not reuse keys, but we can sign a transaction to verify the ownership of the ShapeShift Cosmos validator.

  2. Brief history/ Intro to your validator?

    1. TaxiStake validates on over 12 chains and is entrusted with over $20 million delegated to our infrastructure. The founders of TaxiStake have unique experience from their previous roles within a prominent cryptocurrency exchange. They have numerous years of experience in enterprise security across diverse sectors, including local and federal governments, traditional banking, startups, and managing the IT infrastructure around them. We have a multi-cloud technology and data center where we run our blockchain infrastructure. We utilize multi-cloud and bare metal hosted servers to maximize decentralization, security, and uptime.

  3. Details of your validator (website and contact email)

    1. https://taxistake.com/
    2. validators@taxistake.com

  4. Team structure, roles, and Discord handles

    1. Scott, Cofounder - COO, @scoh.taxistake
    2. Sean, Cofounder - CEO, @grithaxe

  5. Link to your main social accounts

    1. https://twitter.com/TaxiStake

  6. Unique validator key to submit (from Cosmos Hub):

    1. cosmosvaloper199mlc7fr6ll5t54w7tts7f4s0cvnqgc59nmuxf

  7. Region you and/or your validator is based (country)

    1. USA

  8. Must replicate, understand, and validate the genesis distribution. (See atomone-hub/genesis#65 (review))

    1. Acknowledged

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

    1. Acknowledged

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

    1. Acknowledged

  11. Must provide Transparency disclosures of associations among validators. (Also see Validators and KYC #75).

    1. Acknowledged

  12. The Community will put together best practices for KYC-ing and approving validator submissions. The conversation can be followed here: (Validators and KYC #75))

    1. Acknowledged