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
  • Disambiguation
  • Clarifying the usage of modal verbs
  • Make explicit what is allowed and not allowed
  • When it comes to choices, less is more

Was this helpful?

Edit on GitHub
  1. INTEGRATIONS

Policy writing guide

A well-written policy is the cornerstone of an effective and secure dispute resolution setup

Here are a number of tips on how to write a fair, clear and secure policy for your curated registry or dispute resolution process:

Disambiguation

If there are several parties involved in a dispute, it is important to define the terms used to refer to each of them at the start of the policy.

Example: "For the purposes of this document, the party that purchases a service or goods will be referred to as the Client and the counter-party that offers the service or goods will be referred to as the Provider."

Clarifying the usage of modal verbs

Define how modal verbs should be interpreted in the context of the dispute, as they can lead to ambiguity around obligations and permissions.

Example: "The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119."

Make explicit what is allowed and not allowed

Be clear and specific about what should and should not be admissible. If the policy is for a curated registry, also state what are the criteria for removing an entry from the list, as there might be other reasons (other than the absence of the criteria for inclusion) that needs to be made explicit.

Where possible, give examples.

Example: "Submissions on either chain must be considered independently and on their own merits. To be explicit, each pair of submissions in the following two examples must not be considered duplicates:

  • Tagging 0xdc6…3A35 as “Curve.fi: EURS/sEUR” on ETH Mainnet and in Gnosis.

  • Tagging 0xdc6…3A35 as “Curve.fi: EURS/sEUR v2” on ETH Mainnet and “Curve.fi: EURS/sEUR (v2)” on Gnosis."

When it comes to choices, less is more

To reduce the chances of vote-splitting, it is important to reduce the number of choices available for jurors to pick. If possible, limit it to just 2 for most cases.

PreviousRetrieving information from Kleros DappsNextLive & Upcoming Integrations

Last updated 3 months ago

Was this helpful?