Improved validator info by storing on chain

[Andrew-Pohl]

For scalability the validator info needs to be stored on chain at the point of creating a node.

Proposed solution:
Create a new contract "validator info contract" - this avoids changing the consensus contract. This new contract will store the names and contact info (telegram username, email, websites and so on) on chain. The fuseapp will be modified to take additional input variables for these names. The fuseapp will then write the info to the contract on start. To avoid excessive changes the sites which currently grab validator data (staking) can continue to function in the same way (by calling the bot api endpoints). But the bot will look for changes in the validator info periodically and update it's databases accordingly.

[mul53]

Hey @Andrew-Pohl maybe this might be of help https://github.com/poanetwork/poa-network-consensus-contracts/blob/master/contracts/ValidatorMetadata.sol

[Andrew-Pohl]

Hey @Andrew-Pohl maybe this might be of help https://github.com/poanetwork/poa-network-consensus-contracts/blob/master/contracts/ValidatorMetadata.sol

Hey @mul53 good spot! I started writing my own but might modify poa's one (take out some of the stuff which isn't relevant to us)

[henry-hz]

@Andrew-Pohl , I think that 'telegram username, email, websites and so on' data saved directly on chain raises issues with GDPR in Europe, LGPD in Brazil, etc... I think you touch a major issue, that internet was made for computers, not for people. Maybe, partner with another web3 ID solution, like ageify, keyp, WoTT, etc...

[Andrew-Pohl]

@Andrew-Pohl , I think that 'telegram username, email, websites and so on' data saved directly on chain raises issues with GDPR in Europe, LGPD in Brazil, etc... I think you touch a major issue, that internet was made for computers, not for people. Maybe, partner with another web3 ID solution, like ageify, keyp, WoTT, etc...

This is a difficult one GDPR is about personal information and being able to tie it back to an invidual by name/email address and so on. However in our case we are dealing with "company" information which is already made public (in most cases) go on staking site see company X open company X's website and you already have all the details. All the POS blockchains afaik store this data on chain. (I'm no European lawyer so I may be totally wrong here)

[Andrew-Pohl]

#100