Standard Block Producer Information Model

This proposal is a collaboration between: HKEOS, EOS Tribe, SW/Eden, CryptoLions and EOS Rio

The goal is to define a structured way for Block Producer Candidades to publish information about themselves using the regproducer action on the eosio.system contract. Having a standard will allow compatibility between apps and interfaces that require information about any block producer.

Current ABI snippet for the regproducer action:

{
      "name": "regproducer",
      "base": "",
      "fields": [
        {"name":"producer",     "type":"account_name"},
        {"name":"producer_key", "type":"public_key"},
        {"name":"url",          "type":"string"},
        {"name":"location",     "type":"uint16"}
      ]
}

When registering their info on the blockchain, a block producer candidate should define the url field above with a link to the JSON file he is responsible for hosting. We encourage BPs to use some platform where the data can be signed and publicly verified, for instance keybase's KBFS public folder. Example: https://igorls.keybase.pub/eosrio.json

The current standard resides on: https://github.com/eosrio/bp-info-standard

As of 16/05/2018 the format was:

UPDATE: Format upgraded to JSON-schema Draft-v7 at https://github.com/eosrio/bp-info-standard/blob/master/schema.json

We are open for any changes the community deem required. Please create an issue on github.

Go EOS!

EOS New York supports this information model and will adopt this method.

I like the idea, the trick is to coordinate all BP candidates to implement it.
EOSTribe will adopt this approach.

This is awesome! One good idea is to specify a JSON schema to validate it.

Makes sense and obviously will evolve. Therefore having fields such as SBPIM version number and last updated timestamp will be important to allow information portals to identify the version of the information model and whether they have the most recent information.