Setting royalties as per EIP2981 / ERC2981

[it-is-zods]

a small tweak to implement EIP2981 to set royalties.
I understand it is up to the marketplace to honour it (e.g. OpenSea and Rarible have their own "hack" for royalties) but it seems the EIP2981 is starting to be adopted by newer marketplaces and hopefully the dinosaurs will eventually follow.
these changes are small and hopefully make this contract future proof

as per Liarco suggestion, I've created a way to set royalties at any time, but have a default open in the construct

*note: I've only used this in a couple of test contracts, so please do your own tests and submit any feedback and/or tweaks here

[it-is-zods]

it looks like mammoth OpenSea is looking into EIP2891 as well :)
https://twitter.com/Slokh/status/1530298054057897987?s=20&t=ccZIrE4HxhNs5KbDRxJwOQ

[liarco]

Hi @it-is-zods,
Thank you for this, as I said for #302, this won't be included in v2, but I will take this into consideration for v3. I'll keep this open as a reminder since this has a higher priority IMHO.

[W-Lefebvre]

Hi @liarco,
I see that under your comments there is a message saying "This branch has conflicts that must be resolved".

Does this mean that the function suggested by @it-is-zods conflicts with the rest of the code you created? So is it risky to integrate it now in the current state of the code?

thanks for the answer guys

[vincio71]

Hi @liarco
when do you think will be available this feature?
Thanks in advance