The Parity team has a simple content hash to github repo (and/or url) mapping contract available. Parity has the ability to, given the content hash, do a reverse lookup against the contract and to retrieve the associated data.
This registering with the dapp and/or contract allows any URL be be identified by a hash of its content. For example, a dapp developer may want to associate an image with his dapp or a token developer may want to associate an image with his token that is to be displayed on the Parity UI. In addition, the registry is useful for developers to register versions of their dapps, the content of their manifests, etc.
Images are an important part of both the Token and dapp ecosystem. It allows for unique visual identification of the token/dapp. To support the registration of images, the Github Hint dapp has a url -> contentHash mode. Steps to registration -
For file registration, any type of URL is supported, it doesn’t have to reside on Github.
Dapp developers can register their
manifest.json files with the same steps as they would do for images.
To load dapps from the network, the GHH dapp can be used to register a specific commit. Once the dapp is requested, Parity UI will download a .zip of the repo in the background and serve the content. Unlike file registration (images and/or manifests), the underlying contract currently only supports github with a specific commit. Steps to registration -
gavofyork/gavcoin) as well as the specific commit (example