Grassroots Economics are working on components and steps to announce token registration metadata in a decentralized manner, for new token/converter pairs created on our Bancor network.
The aim is to arrive at a protocol which fulfills the needs of any agent/client that seeks to interact with the network.
We'd love some discussion around it.
Although registering a new token on the Bancor contracts will emit events upon which CIC client code can act upon, the information available is limited to the token itself and the exchange only. Therefore, a way to specify additional metadata for the entity that should be associated with the token must be provided.
The proposal consists of two smart contracts and a metadata schema. The schema describes the actual metadata, and the contracts provide the announcement of the token metadata availability, and a mechanism to locate where the metadata can be retrieved from.
A separate, more formal document will be written as a request for comment for decentralized metadata dissemination for institutionally identifiable information.
DecentralizedStorageResolver contract facilitates multiplexing of data resource locations across web2 and web3 networks. It is a separately maintained project with its own documentation. Its utility here is to let an entity specify one or more locations where the metadata for the registration can be retrieved.
CICRegistration contract announces the availability of metadata for a given token. In essence it is a simple chain of mappings (names do not match contract properties):
resolver_type is a sha256 hash of a custom resolver id. The only three recognized values at current time are:
sha256(DecentralizedStorageResolver), the resolver mentioned above
sha256(ENS1) - first generation ENS
sha256(ENS2) - second generation ENS , which refers to the aforementioned contract.
resolver_chain is a custom chain identifier string, which identifies which and what type of decentralized consensus resource holds the resolver record. It has the following format:
Example values are:
The schema defines how the metadata must be formatted. The data type is json, and has the following layout:
(TODO: write in official schema spec language instead if exists)
"default": "<rfc-2426, must be unencrypted>",
"[recipient_hint]": "<rfc-2426, optionally encrypted>",
 = optional value
<hex> = 0x-prefixed hexadecimal value
[recipient_hint] = (optional) arbitrary value that can be announced off-band to specific consumers, in order to instruct how to decrypt the values. Cannot be "default"
<entity> = arbitrary string specifying an organisation or person to associate with the token.
The actual organisation and person detail records are given in RFC-6350 vcard format. The MINIMUM amount of data the default entity can contain is:
X-COUNTRY-CODE: <ISO 639-1 country_ode>