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
Shall we shall support EIP-2981 for Royalty in our NFT or create separate mechanism to handle royalty?
My thinking would be support EIP-2981 for NFT that are 1st party NFT created in our platform. But for some NFT has not EIP-2981 supported, we shall support another way of the royalty in the protocol.
The text was updated successfully, but these errors were encountered:
EIP-2981 is meant to signal royalties for NFT sales on markets. IMO this was made with art NFT/PFPs in mind, I'm not really sure if it matches IPAsset holder's use case, since I would expect them to want to hold the NFT (IP Rights) and license some rights to it, with earnings coming from other medium than sales. I expect our case to be more complex/dynamic that setting a % royalties fee.
There is also the issue of several NFT markets flat out refusing to to honor royalties.
My thinking here is to prioritize defining the IP framework and what a transfer means for IP Assets, then we could add EIP-2981 "on top" of our royalty price mechanism, to help with compatibility in markets that support it.
It's more about external collaboration and support. I am thinking if creators created pfp/art NFT on our platform using some factory, we can provide this option in our factory contract.
Shall we shall support EIP-2981 for Royalty in our NFT or create separate mechanism to handle royalty?
My thinking would be support EIP-2981 for NFT that are 1st party NFT created in our platform. But for some NFT has not EIP-2981 supported, we shall support another way of the royalty in the protocol.
The text was updated successfully, but these errors were encountered: