Skip to content

Commit c74e7d3

Browse files
jrag0xgitbook-bot
authored andcommitted
GitBook: [master] 60 pages and 7 assets modified
1 parent 3dbfaae commit c74e7d3

File tree

13 files changed

+7
-9
lines changed

13 files changed

+7
-9
lines changed

.gitbook/assets/curate.png

495 KB
Loading
428 KB
Loading
1.17 MB
Loading
405 KB
Loading

.gitbook/assets/pnk-token.png

471 KB
Loading

.gitbook/assets/pnk.png

244 KB
Loading
630 KB
Loading

integrations/types-of-integrations/smart-contract-integration.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ description: >-
1818

1919
If you want to integrate with Kleros for dispute resolution, you will have to create an `Arbitrable` smart contract as per the[ Arbitration Standard](https://kleros.gitbook.io/docs/developer/erc-792-arbitration-standard) that will allow executing the following flow:
2020

21-
![Standard simplified flow between an Arbitrable and Arbitrator smart contract](../../.gitbook/assets/image%20%286%29.png)
21+
![](../../.gitbook/assets/flow_arbitrable-arbitrator-smart-contract.png)
2222

2323
In the `Arbitrable` contract, you will have to define at least:
2424

integrations/use-cases/defi-insurance.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ By doing this, an insurance project will simplify its development effort by focu
4242

4343
This contract would follow the standard request-challenge protocol with a crowdfunded appeal system, where the claim submitter registers the claim and anyone can challenge said claim thus creating a dispute in Kleros Court. An insuree would then be able to submit a claim using that contract and to provide the information related to his claim. If their claim is challenged, a dispute will be opened in the relevant Kleros Court. If not challenged, the claim will be considered valid and a payout will be triggered.
4444

45-
![How Kleros can be integrated into a DeFi Insurance product](../../.gitbook/assets/2.png)
45+
![](../../.gitbook/assets/defi-insurance-project.png)
4646

4747
To sum up: In the case of claim systems using Kleros as Claims arbitrator, the final ruling will be made if no claim challenge has been raised, if no appeal has been made after a previous decision by jurors or if a decision has been made in the General Court with no more appeal possible.
4848

pnk-token.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ PNK is used both to stake \(for the possibility to become a juror and to protect
2424
* **Voting Rights:** PNK is used for all governance decisions taken on the Kleros platform. Users can vote with their PNK in any related votes. We already use this mechanism in our token curated list and court governance decisions.
2525
* **Staking Rewards:** Users must stake PNK in order to be able to become jurors in disputes. The more PNK a user stakes, the more chance he has of being chosen as a juror in the selected court.
2626

27-
![](.gitbook/assets/image%20%285%29.png)
27+
![](.gitbook/assets/pnk-token.png)
2828

2929
{% hint style="info" %}
3030
**FAUCETS FOR TESTNET PNK**
@@ -74,7 +74,7 @@ On the other hand, an attack on Kleros would presumably not have that large of a
7474

7575
Finally, in the extreme case of a successful 51% attack, by having a native token, it is possible to perform a last-ditch defense of forking the system to remove the attackers’ holdings. Then the market would sort out which version of PNK should be used going forward. This would of course be highly disruptive as any pre-existing contracts designating Kleros as their arbitrator would continue to use the old version of PNK by default. Still, it would offer the community a path forward out of disaster that would not be available without a native token. This is similar to the [ultimate appeal mechanism of Augur](https://medium.com/kleros/kleros-and-augur-keeping-people-honest-on-ethereum-through-game-theory-56210457649c).
7676

77-
![](.gitbook/assets/1_cf2c4tphtq1h0dek4aa3yg.png)
77+
![](.gitbook/assets/pnk.png)
7878

7979
On the left, an attacker has managed a 51% attack and starts carrying out obvious miscarriages of justice. The community decides to fork the token removing the attackers’ holdings, and most of the users migrate to the new version of PNK.
8080

0 commit comments

Comments
 (0)