-
Notifications
You must be signed in to change notification settings - Fork 81
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
validators directory: Add DokiaCapital (#6)
* validators directory: Add DokiaCapital * Update DokiaCapital.md
- Loading branch information
Showing
1 changed file
with
34 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,34 @@ | ||
## Validator Directory: DokiaCapital | ||
1) The name of your validator | ||
|
||
- DokiaCapital | ||
|
||
2) Why you want to become a validator for GovNo and AtomOne | ||
|
||
3) Brief history/ Intro to your validator | ||
Dokia Capital has been a Cosmos validator since Genesis. | ||
|
||
4) Details of your validator (website and contact email) | ||
https://dokia.capital | contact@dokia.capital | ||
|
||
5) Team structure, roles, and Discord handles | ||
|
||
6) Link to your main social accounts | ||
- Twitter: https://twitter.com/DokiaCapital | ||
|
||
7) Unique validator key to submit | ||
cosmosvaloper14lultfckehtszvzw4ehu0apvsr77afvyju5zzy | ||
We will be using a different key for AtomOne | ||
|
||
9) Region you and/or your validator is based (country) | ||
Romania | ||
|
||
10) Must replicate, understand, and validate the genesis distribution. (See https://github.com/atomone-hub/genesis/pull/65#pullrequestreview-1775992431) | ||
|
||
11) Must contribute to the above to prove understanding of it by contributing to the code or creating a PR/PRs | ||
|
||
12) Must adhere to a global decentralization mandate and if required to cooperate in translation for an efficient global reach | ||
|
||
13) Must contribute to build a fair validators distribution structure by building guidelines to include tiers, participation levels, and validators limitations and operating conditions | ||
|
||
14) Must provide Transparency disclosures of associations among validators. (Also see [Validators and KYC #75](https://github.com/atomone-hub/genesis/issues/75#issue-2034573094)). The AtomOne Community will put together best practices for KYC-ing and approving validator submissions. The conversation can be followed here: ([Validators and KYC #75)](https://github.com/atomone-hub/genesis/issues/75#issue-2034573094)) |