An arbitrator is responsible for providing a final answer to a question when there is a dispute, in exchange for a fee. If the arbitrator is untrustworthy, the system cannot be relied on to provide accurate answers.

Any contract address can be set as the arbitrator. Our dapp currently lists only the Reality Keys trusted arbitrator contract, but others can be entered manually. We can add other contract addresses on request.

Since arbitration is expensive, it will usually only be requested after parties have posted bonds, and the bonds have escalated to a level where the bond you stand to gain by paying for arbitration is higher than the fee. Accordingly, arbitrators should feel free to set fairly high fees that will adequately cover the cost of a thorough arbitration process.

Arbitration Models


Kleros provide a decentralized court system that is integrated with reality.eth and has been used successfully for high-stakes settlement.

Stakeholder voting

Where a consumer contract has their own token, they may choose to provide their own arbitrator contract allowing their own stakeholders to vote. Alternatively, it is possible to deploy a reality.eth contract using the token in question for bonds, then create questions without a registered arbitrator. That way the side able to martial the greatest amount of the token will prevail.


We are developing a forkable Layer 2 ledger where issues can be decided by the subjective choice of users to operate as an arbitration backstop.

Creating and using an arbitration contract

Arbitrator contracts should expose the following functions to users:

  • function getDisputeFee(bytes32 question_id) constant returns (uint256)

  • function requestArbitration(bytes32 question_id)

When requestArbitration() is called with a sufficient fee, they should call the following against the Reality.eth contract:

  • notifyOfArbitrationRequest(bytes32 question_id, address requester)

When they produce an answer, they should settle the contract with:

  • submitAnswerByArbitrator(bytes32 question_id, bytes32 answer, address answerer)

If the result of arbitration is to affirm the answer given by the final answerer, the person who gave that answer should be supplied as answerer. If the result of arbitration is to change the final answer, the answerer supplied should be the user who paid for arbitration. Since version 2.1, this behaviour can be enforced by a contract by instead using

assignWinnerAndSubmitAnswerByArbitrator(bytes32 question_id, bytes32 answer, address payee_if_wrong, bytes32 last_history_hash, bytes32 last_answer_or_commitment_id, address last_answerer)

The last 3 arguments can be extracted from event logs and supplied by the user sending the transaction, and are verified by the contract.


Sometimes the answer the arbitrator finalizes on will already have been given earlier, but with a lower bond. It may appear fairer to some for the arbitrator to set the answerer as the person who previously gave that answer, not the person who paid. However, for all we know the person who gave the correct answer could be a sock puppet belonging to the person who gave the final, wrong answer. Rewarding them would remove the disincentive to lie. For the system the incentive system to work correctly, it is essential that the arbitrator choose the person who paid them as the answerer, unless the pre-existing final answer was correct.

Getting information about the arbitrator

  • function realitio() should provide the address of the Reality.eth contract to which the arbitrator responds.

  • function metadata() should provide a string of json-encoded metadata. It may contain the following properties

    • tos: A URI representing the location of a terms-of-service document for the arbitrator. Should be a URI, either a standard https:// URL or ipfs://

    • foreignProxy: true: This signals that the contract requires users to request arbitration on another chain, as with the Kleros cross-chain proxy. The contract will call additional methods against the contract to get the details of the foreign proxy.

    • template_hashes: [Not yet implemented] An array of hashes of templates supported by the arbitrator, if you want to limit usage of the arbitrator to specified templates. If you have a numerical ID for a template registered with Reality.eth, you can look up this hash by calling the Reality.eth template_hashes() function.

See an Arbitrator contract example to show you how to set the metadata.