2. Curated-data integration plan

Solution plan for using the data from curated data registries created using Kleros

Introduction

While resolving disputes is the most direct way to integrate with Kleros, the Court can also be used to power the decentralized curation of information.

Here are a few examples:

• Contract metadata registries built with Kleros Curate

  • Tokens registry

  • Address tags registry

  • Contract-Domain Name (CDN) registry

• NFT registries

• Identity registries

  • Proof-of-Humanity

A full list of Kleros's existing integrations and partnerships can be found here.

Using Kleros's curated data registries always consists of the following steps, which are outlined below.

To help you keep track of your integration process, click here to make a copy of our Curated Data model integration plan!

Key integration steps

Following these steps in sequence will ensure that your integration is secure and runs smoothly for both you and your users.

1. Determine your data requirements

Each curated registry of Kleros has a unique acceptance policy and field set for each entry onto the list. You can use one of the ready-made registries if it fits your needs. Otherwise, feel free to create your own list from scratch.

1.1 Using one of the existing registries

The main page of Kleros Curate features a number of existing curated registries that have met certain quality standards in their policy and format. Note that the registries are specific to a chain, and you will see different lists on xDai/Gnosis chain than on Ethereum Mainnet.

A few of the most important lists that are related to contract security metadata are:

1. Tokens registry

2. Address tag registry

3. Contract-Domain Name mappings

There is also the Proof-of-Humanity project, which is a Sybil resistant curated registry of real humans (linked to their ETH addresses) on the Ethereum blockchain.

1.2 Creating your own TCR

If none of the lists mentioned in the links above suit your needs, feel free to create your own registry by following the instructions here:

Kleros Curate Tutorial

Save time and avoid omissions by using our model TCR acceptance policy here!

Refer to the policy writing guide here if you need help adjusting it to your use case.

2. Determine the method for data retrieval

We recommend using one of the subgraphs built using The Graph's technology to query for the information one of the existing curated lists.

Retrieving information from Kleros Dapps

3. Build your frontend (if applicable)

Once the curated registry has been decided/created, and the query for retrieving the data is settled, you can proceed to creating the frontend to display the information (if applicable for your use case).

4. Communicate all the above to your users

Once all the above are done, it is time to communicate the involvement of Kleros in the dispute resolution processes of your platform to reduce any potential confusion around the processes. This includes but is not limited to:

1. Educating them on the decentralized nature of the curated registries, that the data is not under the control of Kleros (the organisation).

2. Educating them on how to submit and challenge entries to the curated registries in question.

3. Communicating the process for them to submit additional evidence and raise appeals (if supported).

Once all the above are done, you are ready to go live with Kleros!