Kleros
Kleros.ioGithub
  • Introduction to Kleros
  • Kleros FAQ
  • Governance
  • PNK Token
  • They talk about Kleros
  • Products
    • Court
      • Kleros Juror Tutorial
      • Famous Kleros Cases
      • What happens during a dispute?
      • Kleros & Credible Neutrality
    • Court V2
    • Proof of Humanity
      • Proof of Humanity 2.0 Tutorial: (Register & Vouch)
      • Proof of Humanity 2.0 Tutorial (Remove & Challenge)
      • Proof of Humanity 2.0 Tutorial (Transferring a Profile)
      • Proof of Humanity 2.0 Integration Guide
      • Proof of Humanity FAQ
        • Proof of Humanity 2.0 launch FAQ
    • Curate
      • Kleros Curate Tutorial
      • Kleros Scout
        • Tutorial
        • Earn With Kleros Scout
        • Partnerships
        • Kleros Scout - Metamask Snaps
          • Knowledge Base
        • FAQs
    • Oracle
    • Governor
    • Escrow
      • Kleros Escrow Tutorial
      • Kleros Escrow Specifications
    • Linguo
      • Kleros Linguo Tutorial
      • Step-by-step Tutorial
        • Requesting translations
        • Working as a translator
        • Reviewing translations
      • F.A.Q
      • High-level Overview
    • Moderate
      • Susie
        • Getting Started
          • Add Susie
          • Start Susie
        • Basics
          • Welcome
          • Language
          • Notifications
        • Rules
        • Reports
        • Evidence
        • Federations
  • INTEGRATIONS
    • Overview
    • Industry use cases
    • Types of Integrations
      • 1. Dispute resolution integration plan
        • Smart contract integration with Kleros Court (Arbitrator)
        • Use Cases
          • DeFi Insurance
          • Gaming
          • Recognition of Jurisdiction Integration
            • Integración por Reconocimiento de Jurisdicción
        • Channel partners
          • How to use Reality.eth + Kleros as an oracle
          • Safe Zodiac integration
          • Kleros Reality Module
        • Integration Tools
          • Centralized Arbitrator
          • Dispute Resolver
      • 2. Curated-data integration plan
        • Retrieving information from Kleros Dapps
    • Policy writing guide
    • Live & Upcoming Integrations
    • Kleros Analytics
    • Scalability & Cross-chain
      • Using Kleros arbitration for Dapps on xDai/Gnosis
    • Integrations FAQ
  • Developers
    • Arbitration Development
      • ERC-792: Arbitration Standard
      • ERC 1497: Evidence Standard
      • Arbitrable Proxy
    • Arbitration by Example
      • ArbitrableDeposit.sol
      • TwoPartyArbitrable.sol
      • Rental.sol
      • ArbitrableTransaction.sol
      • MultipleArbitrableTransaction.sol
      • MultipleArbitrableTokenTransaction.sol
    • Deployment Addresses
    • Curate Classic: Integration for Devs
    • Light Curate: Integration for Devs
    • Guide for Preparing Transactions
  • Contribution Guidelines
    • Overview
    • General Dev. Workflow
      • Task Tracking & Lifecycle
      • Releases
    • Smart Contract Workflow
      • Task Tracking & Lifecycle
      • RAB - Review, Audit, Bounty
      • RABd (+ Deploy)
      • Reporting Vulnerabilities
    • Code Style and Guidelines
      • Git
      • Solidity
      • Web Languages
    • License & Code of Conduct
      • License
      • Code of Conduct
  • Additional Resources
    • Discord
    • Telegram
    • Governance Forum
    • Twitter
    • Blog
    • Reddit
    • Github
    • Slack
Powered by GitBook
On this page
  • Introduction
  • Key integration steps
  • 1. Determine your data requirements
  • 2. Determine the method for data retrieval
  • 3. Build your frontend (if applicable)
  • 4. Communicate all the above to your users

Was this helpful?

Edit on GitHub
  1. INTEGRATIONS
  2. Types of Integrations

2. Curated-data integration plan

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

PreviousDispute ResolverNextRetrieving information from Kleros Dapps

Last updated 3 months ago

Was this helpful?

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

  • Identity registries

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

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 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

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

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

2. Determine the method for data retrieval

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. 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!

The 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.

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

Save time and avoid omissions by using our

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

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

Educating them on how to to the curated registries in question.

Kleros Curate
Tokens registry
Address tags registry
Contract-Domain Name (CDN) registry
NFT registries
Proof-of-Humanity
here
here
main page
Tokens registry
Address tag registry
Contract-Domain Name mappings
Proof-of-Humanity project
model TCR acceptance policy here!
here
The Graph's
submit and challenge entries