Skip to content
This repository has been archived by the owner on Apr 30, 2024. It is now read-only.

Dispute and licensing integration #93

Merged
merged 14 commits into from
Feb 17, 2024

Conversation

Ramarti
Copy link
Contributor

@Ramarti Ramarti commented Feb 15, 2024

Changes

This PR integrates the states of the Dispute Module into the Licensing pipeline.

  • If an IP asset has a dispute tag, it can no longer add a policy, mint a license, or link to parents.
  • Licenses of a dispute-tagged IP asset are considered "revoked" and are non-transferable and non-linkable (they still exist in the same form).

Note that a dispute tag gets attached only if a judge decides on the request for arbitration. Anyone can initiate an arbitration, which costs money, against an IP asset. The arbitration initiator can "settle" the dispute, which removes the tag from the IP asset.

Misc.

The license NFT metadata has been updated to include more information, including the revoked status.

@Ramarti Ramarti force-pushed the integration_licensing_disputes branch from 6b48854 to 9f11574 Compare February 15, 2024 18:48
@jdubpark jdubpark marked this pull request as ready for review February 16, 2024 03:23
@jdubpark jdubpark requested a review from a team February 16, 2024 03:23
@LeoHChen LeoHChen force-pushed the integration_licensing_disputes branch from 83550a1 to 2d69669 Compare February 16, 2024 19:08
Copy link
Member

@LeoHChen LeoHChen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM overall, many todo items, need to revisit post-beta.
In the documentation, we have to make it clear about the current limitation of the dispute and tag module. @Spablob

Also, please try not to combine changes all in one PR.

@LeoHChen LeoHChen merged commit e3918a8 into storyprotocol:main Feb 17, 2024
1 check passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants