Files
pezkuwi-sdk/pezkuwi/roadmap/implementers-guide/src/node/disputes
pezkuwichain 379cb741ed feat: Rebrand Polkadot/Substrate references to PezkuwiChain
This commit systematically rebrands various references from Parity Technologies'
Polkadot/Substrate ecosystem to PezkuwiChain within the kurdistan-sdk.

Key changes include:
- Updated external repository URLs (zombienet-sdk, parity-db, parity-scale-codec, wasm-instrument) to point to pezkuwichain forks.
- Modified internal documentation and code comments to reflect PezkuwiChain naming and structure.
- Replaced direct references to  with  or specific paths within the  for XCM, Pezkuwi, and other modules.
- Cleaned up deprecated  issue and PR references in various  and  files, particularly in  and  modules.
- Adjusted image and logo URLs in documentation to point to PezkuwiChain assets.
- Removed or rephrased comments related to external Polkadot/Substrate PRs and issues.

This is a significant step towards fully customizing the SDK for the PezkuwiChain ecosystem.
2025-12-14 00:04:10 +03:00
..

Disputes Subsystems

If approval voting finds an invalid candidate, a dispute is raised. The disputes subsystems are concerned with the following:

  1. Disputes can be raised
  2. Disputes (votes) get propagated to all other validators
  3. Votes get recorded as necessary
  4. Nodes will participate in disputes in a sensible fashion
  5. Finality is stopped while a candidate is being disputed on chain
  6. Chains can be reverted in case a dispute concludes invalid
  7. Votes are provided to the provisioner for importing on chain, in order for slashing to work.

The dispute-coordinator subsystem interfaces with the provisioner and chain selection to make the bulk of this possible. dispute-distribution is concerned with getting votes out to other validators and receiving them in a spam resilient way.