Answers developer questions about integrating K2 V2 dispute resolution into smart contracts.
npx skills add https://github.com/kleros/docs --skill kleros-docs
Please help me install this Agent Skill. Skill: kleros-docs Source: https://github.com/kleros/docs/tree/main Command: npx skills add https://github.com/kleros/docs --skill kleros-docs
This AI Context skill helps developers quickly answer questions about integrating Kleros V2 dispute resolution into smart contracts.
Ask the AI to explain how to encode extraData for a General Court dispute (courtID 1) with 3 min jurors using abi.encodePacked.
High-intent search queries and answers about installing and using this skill.
Encoding extraData for a Kleros V2 General Court dispute uses abi.encodePacked to concatenate the courtID, minJurors, and other dispute parameters into a single bytes payload. For example, encoding courtID 1 with 3 min jurors requires packing these values for the IArbitratorV2 createDispute function.
IArbitrableV2 is implemented by smart contracts that can receive dispute rulings, while IArbitratorV2 is implemented by the KlerosCore arbitration protocol to create disputes and manage jurors. The AI context explains how these interfaces interact during the dispute resolution lifecycle.
Yes, Kleros V2 supports cross-chain dispute resolution through the Vea bridge, allowing disputes originating on other chains to be arbitrated on Arbitrum One where the KlerosCore contract is deployed. The AI context covers how to configure this cross-chain architecture.
Yes, the @kleros/kleros-sdk provides programmatic access to interact with Curate V2 for item curation and Escrow V2 for secure transactions. The AI context delivers guidance on using the SDK for these end-to-end integration scenarios.
Dispute templates in Kleros V2 define the structured metadata and question format presented to jurors during arbitration. You configure them within the extraData encoding when calling the createDispute function through the IArbitratorV2 interface.
Data mappings are required when integrating Proof of Humanity V2 to correctly route dispute identifiers and registry states between your IArbitrableV2 contract and the KlerosCore arbitrator. The AI context explains how to maintain these mappings for accurate dispute tracking.
CodestoneeCreate USDC escrow transactions between AI agents with layered verification.
aRustyDevApply RAII, ownership, and smart-pointer patterns to prevent memory bugs across Rust, C++, and C.
sendaifunConsolidate Solana perpetual futures liquidity across Drift, Flash, Adrena, and Jupiter.
sendaifunBridge assets and messages between Solana and EVM chains using the deBridge Solana SDK.
