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

Was this helpful?

Edit on GitHub
  1. Products
  2. Court

Kleros & Credible Neutrality

How Kleros implements Credibly Neutrality in the context of decentralized dispute resolution.

PreviousWhat happens during a dispute?NextCourt V2

Last updated 3 months ago

Was this helpful?

'Credible Neutrality' is a concept introduced by Vitalik Buterin in an , where it was said that "a mechanism is credibly neutral if just by looking at the mechanism’s design, it is easy to see that the mechanism does not discriminate for or against any specific people". 4 primary rules were mentioned as fundamental to any credibly neutral mechanism:

  1. Don’t write specific people or specific outcomes into the mechanism

  2. Open source and publicly verifiable execution

  3. Keep it simple

  4. Don’t change it too often

Kleros has implemented these principles in the design of its Court, and added additional provisions to enhance its credible neutrality in the area of decentralized dispute resolution.

Rule 1: Don’t write specific people or specific outcomes into the mechanism

  • Kleros utilizes sortition (selection by the random drawing of lots) in the juror selection process, making it very difficult for disputants and voters to collude.

  • As an independent arbitration service, Kleros has no direct interest in the outcome of a dispute. This is especially relevant in high-value or DAO governance disputes.

Rule 2: Open source and publicly verifiable execution

  • The Kleros Court's code base is entirely open source and verifiable, and all evidences and voting activity within the Kleros Courts are publicly accessible.

  • All the processes in Kleros Court (e.g. dispute initiation, evidence submission, ruling challenge, participation in the jury) are trustless and permissionless, allowing anyone to participate, engage and influence the course of a dispute.

Rule 3: Keep it simple

  • The purpose-specificity of Kleros (i.e. the focus on dispute resolution) prevents community voting fatigue within DAOs and prevents the crypto-economic design of the DAO's governance setup to interfere with the dispute resolution process.

Rule 4: Don't change it too often

  • The settings determining the rules and crypto-economics of Kleros Court are adjustable only by governance votes.

  • The policy for each dispute are immutable after a dispute has been initiated, preventing the rules of a dispute to change during the course of a dispute.

Additional safeguards

Kleros Court has an appeal system that allows anyone who disagrees with a ruling to challenge it. This prevents random voting, 51% attacks and attacks from involving a larger pool of jurors and allowing more evidence and arguments to be presented.

inaugural blog post on Nakamoto in 2020
insurance
P + epsilon