Jur Documentation Hub
  • 🎯Jur is building tools for the Network State Revolution
  • Key Notions
    • πŸ—ΊοΈState and Nation
    • 🌌Internet and Web3
    • πŸ›οΈWeb3 and Organizations
    • πŸ—½The Interaction of Society and Technology
    • β­•Web 3 is a Secure Social Operating System
  • 🌎The Network State
  • πŸ“‘Types of Network States
    • Ideologic and non-ideologic Network States
    • Nested Network States
    • Sovereign Network State
  • πŸ”The Balajian Definition of Network State
  • πŸ”˜Differences Between Network States And DAOs
  • πŸ‡ΊπŸ‡³ Nation-States and Network States Will Be Complementary
  • πŸͺŸThe Network State Wiki
  • 🏴The Lean Network State Model
    • 🧡Reinventing The Texture Of Societies
    • Overview of Jur Chain
  • 🧱Lean Network State Components
    • πŸ‘«Community
      • πŸ—£οΈOn-Chain Polls
      • πŸ”‘NFT Status
      • πŸ›£οΈA Web3 Citizen's Journey
    • πŸ’ΈTrustless Treasury
    • βš–οΈJudiciary
    • πŸ§™Oracle
  • ⏳Future Components
    • 🏦Government
    • ✍️Legislative
    • πŸ’²Finance
    • πŸ”ŒInteroperability
    • πŸ†”Limited Liability Entities
    • βš“Insurance
    • πŸ’Services
    • πŸ—οΈNesting
    • βž•Interstate
  • Architecture
    • πŸ”€Intro
    • πŸ”Overview
    • πŸ‘«Community Module
      • Community
      • Proposal
    • πŸ—οΈTreasury Module
      • Treasury
      • Project
    • πŸ§™β€β™€οΈOracle Module
      • Oracle
      • Assessment
    • βš–οΈDispute Resolution Module
      • Court
      • Dispute
      • Judgement
    • ⛓️Jur Chain
      • Benefits of an Autonomous Chain
    • πŸ’“Ethos Testnet
    • πŸ—³οΈGovernance
      • Forkless Upgrades
      • Progressive Decentralization
    • πŸ’±Token Swap
    • 🌐Running a Node
    • 🌳Ecosystem and Economy
      • 🟣Polkadot
      • πŸ–‡οΈParachain XCM Value
    • πŸ‘“Transparency
    • πŸ”Audit
  • JUR ECONOMY
    • πŸ’±$JUR Token Model
    • ⏳$JUR Deflationary Token Model
    • πŸ›οΈTransaction Fee Distribution
    • 🦹$JUR Staking: Meta-Citizenship
      • The $JUR Holder Journey
      • Stake $JUR, receive weJUR
      • weJUR score
      • $JUR Staking and the $DOT bonding for parachain slots
    • ❗Legal Disclaimer
    • πŸͺ™Tokenomics
      • Non-Staking Policy
      • Transparency Policy
  • More
    • πŸ™‹FAQ
    • ⏩Roadmap
    • πŸ”Versioning
    • πŸ”’Changelog
    • 🚩Milestones
    • β˜•About Us
      • ⚑Partners
    • 🌿About this documentation
  • Group 1
Powered by GitBook
On this page
  1. Architecture
  2. Dispute Resolution Module

Dispute

PreviousCourtNextJudgement

Last updated 1 year ago

The Dispute pallet provides all the information relevant to the dispute: plaintiff/defendant accounts, agreement hash, claim hash, resolution proof, resolution deadline, resolution method (e.g. arbitration) and other accessory fields.

This structure allows for a Court to provide different types of resolution according to the specific dispute’s needs. We don’t envision large claims in the beginning phase but this would allow the system to potentially handle larger disputes with an arbitration procedure that can be carried out, for example, through the Jur Arbitration Platform.

The aim is to keep things simple in order to iterate with real dispute’s data instead of over-engineering the infrastructure on day 1.

βš–οΈ
Page cover image