Simplify Royalty Claims in RoyaltyWorkflows
and GroupingWorkflows
by Removing Snapshots
#118
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR simplifies
RoyaltyWorkflows
andGroupingWorkflows
to use the updated royalty vault API, introduced in PR#291 of the core protocol, which simplifies the royalty claiming process by removing the need for snapshots.Key Changes
RoyaltyWorkflows
:transferToVaultAndSnapshotAndClaimBySnapshotBatch
snapshotAndClaimBySnapshotBatch
snapshotAndClaimByTokenBatch
transferToVaultAndSnapshotAndClaimBySnapshotBatch
inRoyaltyWorkflows
to remove snapshot logic and renamed it totransferToVaultAndClaimByTokenBatch
.claimAllRevenue
inRoyaltyWorkflows
to allow claiming all available revenue for an ancestor IP.collectRoyaltiesAndClaimReward
inGroupingWorkflows
.Test Plan
New test cases were added for the
claimAllRevenue
function, and existing unit and integration tests forRoyaltyWorkflows
andGroupingWorkflows
were updated.Related Issue
RoyaltyWorkflows
andGroupingWorkflows
to Simplified Royalty Claiming Without Snapshots #112Notes
This PR introduces major interface changes to
RoyaltyWorkflows
.