Kleros
Kleros
Token: PNK


The Blockchain Dispute Resolution Layer

ICO dates
Start date: 2018-05-15
End date:

Registrated in: France

Platform: Ethereum
Type: ERC20

PREMIUM ICO

Kleros categories
Business services Platform Smart Contract
Video
Kleros token sale
KYC passing required Yes | Whitelist No | Restriction for countries No
Token distribution in ICO
16%
16%
Acceppting ETH
Kleros news, social
Kleros search trends in Google
Random whitepaper excerpts

2 Previous Work: SchellingCoin mechanism
Game theorist Thomas Schelling developed the concept of Schelling Point (also known as Focal Points)
(18) as a solution that people tend to use to coordinate their behavior in the absence of communication,
because it seems natural or relevant to them. Schelling illustrated the concept with the following
example: “Tomorrow you have to meet a stranger in NYC. Where and when do you meet him?”.
While any place and time in the city could be a solution, the most common answer is ”noon at the
information booth at Grand Central Terminal”. There is nothing that makes noon at Grand Central
Terminal a location with a higher payoff (any other place and time would be good, provided that both
agents coordinate there), but its tradition as a meeting place makes it a natural focal point.
Schelling points typically arise when communication is impossible, but also when, while commu-
nication is possible, no party can provide the other with a reason to believe that what he says is ...

What if the contract had a clause stating that, should a dispute arise, it would be solved by a
Kleros court? Kleros is a decentralized application built on Ethereum. After Bob stops answering her
email, Alice taps a button that says “Send to Kleros” and fills a simple form explaining her claim.
Thousands of miles away, in Nairobi, Chief is a software developer. In his “dead time” on the bus
commuting to his job, he is checking Kleros website to find some arbitration work. He makes a couple
thousand dollars a year on the side of his primary job by serving as a juror in software development
disputes between freelancers and their clients. He usually rules cases in the Website Quality subcourt.
This court requires skills in html, javascript and web design to solve disputes between freelancers and
their customers. Chief deposits 2 pinakion, the token used by Kleros to select jurors for disputes. The
more tokens he deposits, the more likely is that he will be selected as juror.
About an hour later, an email...

4.1.1 Options for jurors
Contracts will specify the options available for jurors to vote. In the introductory example, options
may be: “Reimburse Alice”, “Give Bob one extra week to finish the website” and “Pay Bob”.
The smart contract will also specify the behavior of the contract after the ruling is done. In the
example:

“Reimburse Alice” transfers funds to Alice’s address.

“Give Bob one extra week to finish the website” blocks new disputes for one week and removes
this option from further dispute.

“Pay Bob” transfers funds to Bob’s address.
4.1.2 Privacy
Solving disputes may require parties to disclose privileged information with jurors. In order to prevent
outside observers from accessing this information, the natural language contracts (English or other)
and the labels of the jurors voting options are not put on the blockchain. When the contract is
created, the creator submits hash
(
contract text
, ...

Second, pinakion provides jurors the incentive to vote honestly
4
by making incoherent jurors pay
part of their deposit to coherent ones.
4.2.2 Jury selection
After candidates have self-selected specific courts and deposited their tokens, the final selection of
jurors is done randomly. The probability to be drawn as a juror is proportional to the amount of
deposited tokens. Theoretically, a candidate may be drawn more than once for a specific dispute
(but in practice it is unlikely). The amount of times a user is drawn for a dispute (called its weight)
determines the number of votes he will get in the dispute and the amount of tokens he will win or lose
during the token redistribution.
Imagine that 6 token owners signed up for the dispute and deposited 10,000 in total with the
following distribution:
Token Owner Activated Start End Weight
A
1000
0 999 0
B
1500 1000 2499 1
C
500 2500 2999 1
D
3000 3000 5999 2
E
1...

Random numbers are generated with sequential proof of work (10) using a scheme similar to Bu¨nz
et al. (11) adapted to also work for Proof-Of-Stake blockchains
5
.
1.
Initialization
: We start with seed=blockhash and let all parties input a value localRandom to
change the seed such that seed=hash(seed,localRandom). This allows any party to change the
seed. We want the seed to not be chosen by any one party. This way every party can change
the seed, but not choose it, because choosing a particular seedAttack would require the attacker
to determine localRandom such that hash(seed,localRandom)=seedAttack which is difficult due
to the preimage resistance of cryptographic hash functions.
2.
Computing the master random value
: Every party who has a stake in the random number
runs sequential proof of work on the seed. Starting with
h
0
=
seed, they compute
h
n
+
1
=
hash
(
h
n
)...

prevent the use of rainbow tables. The address is the Ethereum address of the juror, it is required
in order to make the commitment of each juror different, thus preventing a juror from copying the
commitment of another. When the vote is over, they reveal
{
vote
,
salt
}
, and a Kleros smart contract
verifies that it matches the commitment. Jurors failing to reveal their vote are penalized (see Incentive
System section).
After a juror has made a commitment, his vote cannot be changed. But it is still not visible to
other jurors or to the parties. This prevents the vote of a juror from influencing the vote of other
jurors.
Jurors can still declare that they voted in a certain way, but they cannot provide other jurors a
reason to think that what they say is true. This is an important feature for the Schelling Point to
arise. If jurors knew the votes of others jurors, they could vote like them instead of voting for the
Schelling Point.
We let any party ab...


In appeals, both parties have to deposit the arbitration fees. The appellant also has to deposit
an extra stake proportional to the appeal fees which will be given to the party winning the
dispute. This way if a party makes frivolous appeals to harm the opposing party, the opposing
party will get a compensation for the time loss, while if the appeals are finally ruled to be legit,
the stake will be returned to the appellant
8
.
A discussion about the fee structure defined by arbitrable smart contracts will be part of future
work.
4.5 Appeals
If, after the jury has reached a decision, a party is not satisfied (because it thinks the result was
unfair), it can appeal and have the dispute ruled again. Each new appeal instance will have twice the
previous number of jurors plus one. Due to the increased number of jurors, appeal fees must be paid
(appeal fees
=
new amount jurors

fee per juror

fee already paid).
If a verd...

Figure 4: Token redistribution after the vote with seven jurors. Tokens are redistributed from jurors
who voted incoherently to jurors who voted coherently. Bob lost the dispute and pays the arbitration
fees. The other deposits are refunded.
revealing one’s vote is twice as large than the penalty for voting incoherently (2

α

min activate

weight).
This incentivizes jurors to always reveal their vote.
In case of appeal, the tokens are redistributed at each level according to the result of the final
appeal. If at one level no one voted coherently, the tokens are given to the winning party.
When there is no attack, parties are incentivized to vote what they think, other parties think, other
parties think. . . is honest and fair. In Kleros, the Schelling Point is honesty and fairness. One could
argue that those decisions being subjective (for example, compared to a Schelling Coin mechanism
for a prediction market), no Schelling Point would arise. In (18), the ...

Kleros Roadmap

1
April 2018
MVP of Kleros released on the test net
2
May 2018
ICO
3
July 2018
Start of the first pilot
4
October 2018
Full version with real use cases
5
April 2019
Release of version with miltiple subcourts
Federico Ast
Federico Ast CEO & Co-founder

Clément Lesaege
Clément Lesaege CTO & Co-Founder

Nicolas Wagner
Nicolas Wagner Co-founder, WEB3 Developer

Sam Vitello
Sam Vitello Dapp Developer

Romina Kavcic
Romina Kavcic Design Lead

Stuart James
Stuart James Community Manager

Enrique Piqueras
Enrique Piqueras Dapp Developer

William George
William George Cryptoeconomics Researcher

Jérome de Tychey
Jérome de Tychey
Mitchell Loureiro
Mitchell Loureiro
Marketing Strategy, VP of Marketing at Steemit
Marketing Advisor
Marketing Lead
Advisor, Strategy and Marketing
Nicolas Wagner
Nicolas Wagner
Co-founder, WEB3 Developer
Blockchain Developer
Romina Kavčič
Romina Kavčič