The Validator Directory on the Evmos Network is a place for validators to share more insights to current and future delegators. This repo will be used on Evmos.org to help create an environment where stakers can choose a validator based on a wide gamut of inputs, e.g., contribution to the Evmos ecosystem. We hope to leverage the dataset here to improve our decentralization efforts. The base template provided by the Cosmos SDK has not been sufficient to quantitatively describe a validator. It is certainly advantageous for every validator to provide as much information as he/she/they can. If there are any fields that you feel we are missing, please do not hesitate to reach out to the Evmos team and we will do our best to accommodate. Additionally, we plan to leverage the data from: Eco-stake Validator Profile to further enrich our restaking features.

1. Go to your terminal and query for your validator details. You can do this also on our website here or interact with the /cosmos/staking/v1beta1/validators/{validator_addr}.
2. Copy the result over to your own editor and add/edit the fields listed below. In the end, the result should be similar to the validator.example.json.
3. Please fill out as much details as possible. If you have restaking feature enabled, please ensure you add the required details on the Eco-stake Validator Registry and make a PR request on there as well. We will look up your details via the moniker and address.
4. Make a PR request on Evmos Validator Directory and be sure to place your profile in the right folders: mainnet and/or testnet.

Please note that all fields are under description. If any fields are not described in the acceptable fields, we cannot accept the PR. Additionally, if you list more than 2 items in any array, we will show the first two. For example, Communities have several categories. If you fill out two per each categories (Community, Social, etc.), then only the first two are shown in the Evmos Staking Dashboard. An asterisk by the type represents a required type. We encourage validators to fill out the details field with a bit more about themselves. However, we encourage short, succinct responses.

SocialEntity : {
  "name": string*,
  "link": string*,
}

Collaborator: { // One can always add more collaborators
  "identifier": string*,
  "role": string,
  "relationship" string,
  "pubKey": {
    "@type": "/cosmos.crypto.ed25519.PubKey",
    "key": string
  }
}

Communities: [
  {
  "involvement_type": enum* // "Github | Community | Social | Other",
    "date_from": string* // "Feb 22, 2021",
    "date_to": string // "Present",
    "handle": string, // Can be a developer profile
    "description": string*,
    "link": "string", // Project link or developer profile link
    "contributions": [{
      "features": { // as Github
        "name": string*,
        "sha": string,
        "repo": string, // link/branch link or specific feature link
        "description": string,
      }
    }]
},
{
  "involvement_type": Social,
  "date_from": "September 2021",
  "date_to": "Present",
  "contributions": [{
    { //Community | Social | Other
        "name": string*,
        "description": string,
      },
  }]
}]

Infrastructures: [
  {
  "hosting_provider": string,
  "stack_details": string
  }
]

• social: SocialEntity[]
• collaborators: Collaborator[]
• communities: Community[]
• infrastructures: Infrastructure[Infrastructure] - there is no way for Evmos to validate these stack details however, we encourage our validators to be as descriptive as they can and talk about their stacks like hosting, is barebone setup, etc.
• offers_auto_compounding: boolean - default is false. If true, we will leverage the data on here which generates the h json data here.
• relayers: boolean - default is false
• is_recent: boolean - if the validator is formed in the last 3 months, it will be a true
• has_liquid_staking: boolean - default is false
• has_interchain_account: boolean - default is false