restake wallet verification about validator-registry HOT 2 OPEN

Great suggestion and I completely agree something is needed here for verification. I like the idea of a blockchain based solution but I also want to make it as easy as possible. Ultimately the issue lies in who is allowed to make updates to this repository - we could go with a simpler solution where each validator can specify an array of github usernames in profile.json or authors.json who can make changes. We would then implement a CI workflow to check the user against this array if it exists, and fail any PR which doesn't match.

The initial submission of this list will have potential for abuse, but after that only users who are already in the list would be authorised to change it (unless special circumstances dealt with manually), which at least gives us some author control.

What do you think about that? Potentially in addition to some form of second verification layer like you outlined.

from validator-registry.

Defining specific GitHub accounts for making changes to existing entries should be sufficient.

For the initial entry, I suggest using keybase as a form of validation. Many validators use keybase identity already as the identity field stored on-chain. Github accounts can be verified as well so it should be relatively seamless for validators who already have this setup.

from validator-registry.