You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current implementation of RoyaltyTokenDistributionWorkflows (introduced in PR #126) requires minting a license token to trigger the deployment of an IP royalty vault if one is not already deployed. This process imposes additional minting fees specified in the attached license terms, which are unnecessary overhead. Additionally, this approach requires extra signatures and introduces complexity, making it cumbersome for users.
Suggested solution
To streamline this process and avoid unnecessary costs:
The workflows contract will automatically attach a commercial license with a zero minting fee to the IP.
The license token will be minted using these zero-fee terms solely to trigger royalty vault deployment.
Once the vault deployment is completed, the workflow contract will immediately lock this license to ensure it cannot be misused.
This solution removes extra fees and simplifies the process, making the system more efficient and user-friendly.
The text was updated successfully, but these errors were encountered:
Description and context
The current implementation of
RoyaltyTokenDistributionWorkflows
(introduced in PR #126) requires minting a license token to trigger the deployment of an IP royalty vault if one is not already deployed. This process imposes additional minting fees specified in the attached license terms, which are unnecessary overhead. Additionally, this approach requires extra signatures and introduces complexity, making it cumbersome for users.Suggested solution
To streamline this process and avoid unnecessary costs:
This solution removes extra fees and simplifies the process, making the system more efficient and user-friendly.
The text was updated successfully, but these errors were encountered: