CIP 68 Royalties - Collaborator Discussion

[SamDelaney]

This thread is intended to gather input from developers who are already working on CIP 68-based royalty implementations or have similar vested interest, to make sure we consider all existing use cases before submitting the PR to the CF repository for general review. Interested in any & all input at this point.

The specification is based on the royalty specification in Nebula, with a couple key departures:

1. The royalty token is recommended to be locked at a script address, rather than stored in the user's wallet. This encourages projects to guarantee royalties won't change by sending their royalties to an always-fails (or similar) script address, but still allows for creative royalty schemes and minimizes disruption to existing projects.
2. The policyId of the royalty NFT must match that of the reference NFT. This enables lookups based on the user token in the same way as is done for the other tokens specified in CIP 68.

The specification here is made to be as minimal as possible. This is done with expediency in mind and the expectation that additional changes to the specification may be made in the future. The sooner we have a standard established, the sooner we can make use of it. Rather than attempting to anticipate all use cases, we specify with forward-compatibility in mind.

If you're interested in Ikigai's internal discussion that preceded this, check out #1.

[SamDelaney]

Closing in favor of pull 551 in the CF CIPs repository.