Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better use of validator identity and description fields #99

kwunyeung opened this issue May 27, 2019 · 0 comments


Copy link

commented May 27, 2019

Currently the identity field of validator only be used for storing the keybase key suffix for crawling the profile picture. This not fully utilizing the field as the length of the identity field has 3000 characters limit which is 11x larger than the description field.

Although there were a TODO to change the validator info to be a JSON input, validators have already got used to the 4 different fields. Any changes on the struct will also break consensus. It's better to alter the usage of these fields rather than changing gaia for now.

Clearly the description field is already not enough for validator to describe themselves even though we have Markdown support on BD. It will be great if the validator page can be upgrade to be a channel to enhance the communications between validators and delegators.

What a validator would like to show

  1. Name
  2. Profile Picture (if keybase is not provided, this can be a pure url)
  3. Keybase key suffix for identity check
  4. Company details
  5. Staking T&C
  6. Contact Info (email / GH / TG)
  7. Location (it will be great if we can show a map of all validators)
  8. Team members (link to their Twitter account?)
  9. Awards with announcement links

These can all be formatted with a JSON by using the identity field. The field have to be backward compatible. If the validators don't want to give those details and keep putting the keybase key suffix, we still show the profile picture from Keybase.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
1 participant
You can’t perform that action at this time.