+
+
+---
+
+## [Why Kleros Needs a Native Token](https://medium.com/kleros/why-kleros-needs-a-native-token-5c6c6e39cdfe)
+
+PNK's design provides three layers of protection against a 51% [(Sybil) attack](https://en.wikipedia.org/wiki/Sybil_attack):
+
+1. **Market scarcity defense.** Acquiring 51% of PNK becomes economically prohibitive: large purchases exhaust available liquidity and drive the price up, unlike an attack denominated in ETH or another asset with vastly deeper markets.
+2. **Price impact risk.** A successful attack would substantially devalue PNK itself, imposing a massive cost on the attacker that does not exist when attacking with an external asset.
+3. **Fork capability.** As a last resort, the community can perform an emergency fork that removes the attacker's holdings, a recovery path unavailable with external tokens.
+
+
+---
+
+## How to Get PNK
+
+The fastest way is the [Buy PNK page of the Court](https://court.kleros.io/tokens), which routes to the exchanges listed there.
+
+| Venue type | Options |
+| --- | --- |
+| **DEX aggregators** (large trades) | Paraswap, 1inch |
+| **DEXs** (medium trades) | Uniswap, Sushiswap, Balancer |
+| **Centralized exchanges** | Bitfinex, Gate.io, OKX |
+| **Fiat onramp** | Guardarian |
+
+---
+
+## What's Next?
+
+
+
+
+| Aspect | Court V1 |
+| --- | --- |
+| **Network** | Ethereum L1 (also Gnosis Chain) |
+| **Core contract** | KlerosLiquid (monolithic) |
+| **Standards** | ERC-792 (arbitration), ERC-1497 (evidence) |
+| **Staking** | PNK stays in the juror's wallet |
+| **Voting** | Commit-reveal with plurality aggregation |
+| **RNG** | Blockhash-based |
+| **Courts** | Hierarchical subcourt tree with the General Court as root |
+
+Jurors stake PNK directly from their wallet in a subcourt, are drawn at random with probability proportional to their stake, then commit and reveal their votes on the submitted evidence. Coherent jurors are rewarded; incoherent jurors lose part of their stake.
+
+---
+
+## V2 - Next-Gen Upgrade
+
+Court V2 runs on Arbitrum L2 and replaces the monolithic contract with a modular design: **KlerosCore** coordinates disputes, the **SortitionModule** handles juror selection, and pluggable **DisputeKits** provide the resolution mechanism. Cross-chain disputes are relayed through the **VEA bridge**.
---
@@ -113,16 +137,17 @@ This creates a self-policing system where dishonest behavior is economically pun
---
-## V2 Improvements
+## What Changed in V2
-Kleros Court V2 represents a significant evolution from V1:
+V2 keeps the same crypto-economic model as V1 and changes how it is implemented and where it runs:
-| Feature | V1 | V2 |
+| Component | V1 | V2 |
| --- | --- | --- |
-| **Network** | Ethereum Mainnet | Arbitrum (lower gas costs) |
-| **Cross-Chain** | Single chain only | Multi-chain via Vea bridge |
-| **Dispute Kits** | Single mechanism | Modular, pluggable kits |
-| **Vote Privacy** | Basic commit-reveal | Shutter encryption (in testing) |
+| **Network** | Ethereum L1 | Arbitrum L2 |
+| **Core contract** | KlerosLiquid (monolithic) | KlerosCore (modular) |
+| **Juror selection** | Built into KlerosLiquid | SortitionModule (separate) |
+| **Dispute resolution** | Single mechanism | Pluggable DisputeKits (Classic, Shutter, Gated, GatedShutter) |
+| **Cross-chain** | Single chain | Multi-chain via VEA bridge |
| **Staking** | PNK stays in wallet | PNK transfers to contract |
| **RNG** | Single source | Enhanced with fallback mechanisms |
@@ -132,6 +157,17 @@ Kleros V2 is currently in beta with 100+ disputes successfully processed. The sy
---
+## Current Status
+
+As of the May 2026 development update:
+
+- **Court V2**: the partial-coherence dispute kit was merged, and contract simplification across dispute kits was merged (June 2026).
+- **Court V1**: April staking rewards were shipped in the rewards exporter.
+
+Follow development on the [Kleros blog - developer updates](https://blog.kleros.io/tag/developer/).
+
+---
+
## What's Next?
Monitoring registry events...
;
-}
-```
-
----
-
-## Complete Integration Example
-
-```tsx
-// pages/CuratePage.tsx
-import { useState } from 'react';
-import { Web3Provider, useWeb3 } from '../context/Web3Provider';
-import { useRegistry, useItem, useSubmitItem, useChallengeItem } from '../hooks';
-import { formatEther } from 'ethers';
-
-const CURATE_ADDRESS = '0x...'; // Your registry address
-const VIEW_ADDRESS = '0x...'; // CurateView address
-
-function CurateContent() {
- const { address, connect } = useWeb3();
- const [itemId, setItemId] = useState
-
-
- )}
-
- {/* Submit Item */}
-
-
-
- {/* Item Details */}
- {item && (
-
-
- )}
-
- );
-}
-
-export default function CuratePage() {
- return (
- Curate V2 Integration
- - {/* Registry Info */} - {registry && ( -Registry Configuration
-Submission Deposit: {formatEther(registry.submissionDeposit)} ETH
-Challenge Period: {Number(registry.challengePeriod) / 3600} hours
-Submit New Item
- -Item Details
-Status: {item.statusName}
-Disputed: {item.disputed ? 'Yes' : 'No'}
- - {item.status === 2 && !item.disputed && ( - - )} -- ",
+ "description": "Someone requested to add one
- ",
+ "rulingOptions": {
+ "titles": ["Yes, Add It", "No, Don't Add It"],
+ "descriptions": [
+ "Select this if the item complies with the required criteria and should be added.",
+ "Select this if the item does not comply and should not be added."
+ ]
+ },
+ "category": "Curated Lists",
+ "question": "Does the
- ",
+ "tcrDescription": "
Please connect your wallet
;
- }
-
- return (
-
-
-
-
- {/* View Transaction */}
- {transactionId && transaction && (
-
-
- )}
-
- );
-}
-```
-
----
-
-## Resources
-
-Escrow V2 Integration
- - {/* Create Transaction */} -Create New Escrow
- -Transaction Details
-Amount: {formatEther(transaction.amount)} ETH
-Status: {transaction.status}
-Deadline: {new Date(Number(transaction.deadline) * 1000).toLocaleString()}
-
+
+
+**Kleros Enterprise** is a neutral dispute resolution system for businesses and governments, designed for speed, fairness, and transparency. Companies, institutions, and governments use Kleros dispute resolution technology to resolve disputes within their own platforms or services. The blockchain complexity is abstracted away: neither the organization nor its users need to handle crypto or interact with smart contracts directly.
+
+
+ 
# Curate
-
+
# Escrow
-
+
+
+---
+
+## What Changed in V2
+
+| Feature | V1 | V2 |
+|---------|----|----|
+| Network | Ethereum Mainnet | Arbitrum One |
+| Token support | ETH + standard ERC-20 | ETH + any ERC-20 (via SafeERC20) |
+| Settlement | Basic | Structured proposal / counter-proposal |
+| Evidence & appeals | Handled by escrow contract | Handled by Court |
+| Platform fees | None | None |
+
+---
+
+## Current Status
+
+As of the May 2026 development update, Escrow completed its Atlas IPFS migration, with UX improvements to the agreement upload step.
+
+Follow development on the [Kleros blog - developer updates](https://blog.kleros.io/tag/developer/).
---
@@ -41,7 +79,7 @@ Traditional online transactions require trust between strangers, creating opport
-
-
+
+---
+
+## Get in Touch
+
+
+
+
+# Kleros Scout MetaMask Snap
+
+Kleros Scout is available as a **MetaMask Snap** that enables safer contract interactions by delivering community-curated insights about the contracts you interact with on the blockchain. With each transaction, a tab displays insights about the contract being interacted with.
+
+The Snap provides metadata from three decentralized registries:
+
+- [**Address Tags Registry**](https://curate.kleros.io/tcr/100/0x66260C69d03837016d88c9877e61e08Ef74C59F2): verified project names and contract tags
+- [**Contract-Domain Name Registry**](https://curate.kleros.io/tcr/100/0x957A53A994860BE4750810131d9c876b2f52d6E1): verified contract-to-domain pairings
+- [**Tokens Registry**](https://curate.kleros.io/tcr/100/0xeE1502e29795Ef6C2D60F8D7120596abE3baD990): ERC-20 token information
+
+---
+
+## Installation
+
+
+
+
+---
+## How to use the Snap's features?
+Once you install the Kleros Scout Snap, with every txn/contract interaction, you will see a tab which provides you with insights around the same. Upon installation, If you see this, you are already using community curated contract insights for secure dapp interaction - the most important feature of the Kleros Scout Snap.
+
+
+ 
+
+---
+## Limitations
+
+The Snap explicitly does **not**:
+
+- Endorse any contract interaction
+- Use centralized whitelisting: all data is community-curated
+- Guarantee 100% accuracy or accept liability for insights
+
+---
+
+## Knowledge Base
+
+
-
+
+ 
+
+ 
+
+
+---
+
+## Step 2: Submit the Payment
+
+
+
+ 
+
+ 
+
+
+---
+
+## Step 3: Execute the Payment
+
+After creation, both parties see a transaction summary with their available actions.
+
+
+ 
+
+
+### As the payment sender
+
+- **Make payment**: release funds to the receiver, in full or partially. Pay the full amount when the service or product was delivered as agreed. Pay a partial amount to settle a disagreement without a dispute; the remainder stays in escrow and can still be disputed.
+- **Raise dispute**: click if you are unsatisfied with the delivery. You are shown the arbitration cost (for example, 0.03 ETH) and deposit the fee to initiate. The fee is refunded if you win.
+
+ 
+
+
+### As the payment receiver
+
+- **Reimburse**: return funds to the sender, in full or partially. Reimburse the full amount if you cannot complete the delivery. Reimburse partially to keep payment for work completed; the remainder goes to you and the transaction closes.
+- **Raise dispute**: click if the sender refuses payment despite you completing the terms. The arbitration cost and process are the same for both parties.
+
+ 
+
+
+
+### Settlements through partial payments
+
+There is no separate settlement mode. When both parties agree to a compromise, one of them makes a partial payment or reimbursement:
+
+- **Sender initiates**: the sender pays a partial amount (for example, 0.7 of 1 ETH). It goes immediately to the receiver; 0.3 ETH remains in escrow. The receiver can accept, dispute the remainder, or reimburse some or all of it.
+- **Receiver initiates**: the receiver refunds a partial amount (for example, 0.4 of 1 ETH). It returns to the sender; 0.6 ETH remains.
+
+
+
+
+
+ 
+
+
+
+ 
+
+
+ 
+
+
+---
+
+## What's Next?
+
+
+
+
+---
+
+## Staking and Cases
+
+Match your expertise to the appropriate court:
+
+- **Onboarding Court**: for beginners
+- **Blockchain Non-Technical Court**: for basic blockchain knowledge
+- **English Court**: for language expertise
+
+
+
+ 
+
+ 
+
+ 
+
+
+
+
+
+---
+
+## What's Next?
+
+
+
+
+---
+
+## Staking Your PNK
+
+
+
+ 
+
+
+ 
+
+
+Things to know about V2 staking:
+
+- **Your PNK transfers to the KlerosCore contract** while staked (in V1 it stayed in your wallet). You can unstake anytime unless it is locked in an active case.
+- **You can stake in at most 4 courts** (a gas-efficiency limit), so plan your court selection.
+- **Timing matters**: the court cycles through Staking, Generating, and Drawing phases. Stake changes made during the Generating or Drawing phases are recorded but only take effect in the next Staking phase. The UI shows whether your stake is "Current" or "Delayed."
+
+---
+
+## Getting Selected
+
+Selection is random but stake-weighted: your probability per draw is your stake divided by the court's total stake (5,000 PNK in a court with 100,000 PNK staked gives you a 5% chance per draw). You can be drawn multiple times for the same case; each draw is one vote, and all your votes must be for the same choice.
+
+When drawn:
+
+- A portion of your stake is locked as collateral
+- The case appears in **My Cases**
+- You are notified in the interface (and by email if you enabled notifications in Settings, which is strongly recommended for deadline reminders)
+
+---
+
+## Handling Your First Dispute
+
+
+ 
+
+
+
+
+
+---
+
+## Appeals and Court Jumps
+
+- Appeal funding follows `feeForJuror × ((nbVotes × 2) + 1)`: the winning side must fund 1× the appeal cost and the challenging side 2×. With 3 jurors at 0.05 ETH, that is 0.35 ETH for the winner and 0.70 ETH for the challenger.
+- The challenger can only fund during the **first half** of the appeal period; the winner has the entire period.
+- Each appeal round increases the juror count (`n×2 + 1`). When the count reaches the court's `jurorsForCourtJump` threshold (for example, 511), the dispute escalates to the parent court, and juror numbers adjust to the new court's parameters. You may be drawn for jumped cases; expect them to be more complex.
+
+
+ 
+
+
+---
+
+## Cross-Chain Disputes
+
+V2 natively supports disputes originating on other EVM chains (Ethereum, Gnosis Chain, Polygon, Optimism, and more). As a juror, everything happens on Arbitrum: disputes are bridged in, evidence appears unified in the interface, and rulings are bridged back to the origin chain. The process is identical for you regardless of where the dispute came from.
+
+---
+
+## Troubleshooting
+
+| Problem | What to do |
+| --- | --- |
+| Wrong network error | Switch to Arbitrum One (Rabby prompts automatically) |
+| PNK not visible in wallet | Import the PNK token contract manually; verify the address from official sources |
+| Stake transaction fails | Check PNK balance, ETH for gas, and the court minimum |
+| Case not in My Cases | Confirm you were drawn, wait for confirmation, refresh |
+| Vote deadline passed | Late votes are never accepted; set multiple reminders next time |
+
+For help: [Discord](https://discord.gg/kleros), [Telegram](https://t.me/kleros), or support@kleros.io.
+
+---
+
+## What's Next?
+
+
+
+ 
+
+ 
+
+
+ 
+
+ 
+
+
+### From Needs Vouch to In Review
+
+To advance, your profile needs:
+
+- At least 1 vouch from a person with "Resolved Claim" status who knows you
+- Full deposit payment (100%)
+- Vouch initiation via **Advance**
+
+Vouches process sequentially, roughly 3.5 days per person. Multiple simultaneous vouches from one person delay processing for others. If you need to correct something, withdrawal is available only during the vouching phase.
+
+### From In Review to Verified Human
+
+A 3.5-day challenge period lets the community verify compliance:
+
+- **If challenged**: a Kleros Court dispute opens. Provide evidence defending your case. Appeals are available if you disagree with the ruling.
+- **If unchallenged**: click **Execute** after 3.5 days to finalize your registration. Any address can submit this transaction. Your deposit is refunded on completion.
+
+Once verified, you gain the ability to vouch for others.
+
+ 
+
+
+
+ 
+
+---
+
+## Phase 4: Vouch for Another Profile
+
+You must be connected to the app and have "Verified Human" status.
+
+
+
+
+ 
+
+ 
+
+
+ 
+
+ Detection tools that can help:
+
+ - [Deepware.ai](https://deepware.ai)
+ - [Sensity.ai](https://sensity.ai)
+ - Voice recognition software for computer-generated audio
+ 
+
+
+ 
+
+ 
+
+
+ 
+
+ 
+
+
+### Remove registered or Verified Human profiles
+
+1. Open the profile and click **Revoke**
+2. Lock a deposit (reimbursed if the removal succeeds)
+3. Optionally submit evidence supporting the revocation
+
+ 
+
+
+ 
+
+
+Example evidence submissions:
+
+- **Self-removal from the same address**: name it "Self-removal of submission" and confirm your submitter status via the address.
+- **Self-removal from a different address**: name it "Self-removal of submission" and include a video recording stating: "I want to revoke my own submission from the Proof of Humanity registry".
+- **Malicious submission removal**: name it "Removal of deepfake submission" and include deepfake analysis reports as evidence.
+
+
+ 
+
+### Remove in-review profiles
+
+Use the challenge process described above.
+
+---
+
+## Resubmit a Profile
+
+### From a new address
+
+1. Ensure the old profile shows **Revoked** status (check `https://v2.poh.id/PoHID`)
+2. Remove it if necessary using the steps above
+3. Connect the new address and submit a fresh profile
+
+ 
+
+
+### From the same address
+
+1. Verify the old profile is **Revoked**
+2. Remove it if needed
+3. Click the **Resubmit Profile** button at the bottom left of the profile
+
+### Reapply an expired or expiring profile
+
+Profiles expire two years after registration. Reapply to prove your continued existence and control of the address.
+
+ 
+
+---
+
+## What's Next?
+
+
+
+ 
+
+ 
+
+ 
+
+
+ 
+
+ 
+
---
## For Developers
@@ -144,7 +139,7 @@ Build trustless applications with decentralized dispute resolution.