KOR Protocol Developer Docs
  • KOR Protocol: Introduction
    • Overview
    • Partners
  • Overview of KOR SDK
    • Notable Features
    • Merits of using KOR SDK
    • Use Cases
  • SDK Reference
    • Introduction
    • SDK Installation
    • SDK Initialization
    • Client Methods
      • Asset
      • NFT
      • On-Chain IP
      • On-Chain License
      • Royalty Distribution
      • Conflict Management
    • Tutorials
      • Pre-requisites
      • Mint and Register in Own Collection
      • Mint in KOR Collection and Register
      • Register Existing Minted Token as IP
      • Launch 100-Song Album via IPFS
      • Launch 5-Song Album via AWS S3
      • Register Asset as Derivative
      • Update License Terms of Existing IP
      • Raise, resolve and cancel conflicts
      • Create a copy NFT of an IP
    • Releases
    • Deployed Smart Contracts
  • Essential Business Flows
  • Architecture
    • Overview
    • Event Listener
    • Modules
      • Asset Module
      • NFT Module
      • On-Chain IP Module
      • On-Chain License Module
      • Royalty Distribution Module
      • Conflict Management Module
  • Key Definitions
  • Community
Powered by GitBook
On this page
  • Raise Conflict
  • Resolve Conflict
  1. Architecture
  2. Modules

Conflict Management Module

PreviousRoyalty Distribution ModuleNextKey Definitions

Last updated 5 months ago

The Conflict Management Module handles the conflict related tasks in the protocol allowing users to:

  • Raise Conflicts

  • Resolve Conflicts

  • Get Conflict details

  • Arbitrator management

  • Conflict fee management

Raise Conflict

To raise a Conflict, a user has to provide the following:

  1. Conflict Evidence Link

  2. A Conflict Tier

  3. Stake the tokens based on the Tier.

Once the above is provided the IP is marked as Conflicted and further derivatives cannot be created until the conflict is resolved.

Resolve Conflict

Conflict can only be resolved by an Arbitrator. The Arbitrator reviews the Conflict Evidence and based on that checks the validity of the conflict. If the Conflict is valid, the remaining staked tokens are transferred back to the Conflict raiser and the IP is Locked. If the conflict is not valid then the remaining tokens are used by the platform and IP is no longer tagged as conflicted.