Author Topic: Which data should a delegate publish together with his name ONCHAIN  (Read 508 times)

0 Members and 1 Guest are viewing this topic.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12896
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Those of you that registered a name on the blockchain might have noticed that you can store a JSON object associated with your registered name on the blockchain, such as website, mail, ...

I'd recommend we start a discussion about which data active delegates should publish together with their name. This would involve a (not-so-regular) update-transaction. Nothing to special.

Those are the fields I personally would like to see for active delegates:

- website (campaign for the delegate)
- pgp/gpg fingerprint
- mail
- scripthash for price feed script
- delegate slate
- maintainer TITAN address

optionally those keys could could also be published:
- skype
- icq
- twitter
...
- bitmessage
- donation TITAN address
- forum handle
...

What's your view on this? Do we need this? Not required? Should we someday adjust our votes to reflect those entries to?

Disclaimer: My public json data currently only contains the slateID!


Thoughts?
Give BitShares a try! Use the http://testnet.bitshares.eu provided by http://bitshares.eu powered by ChainSquad GmbH