I have a time-sensitive dilemma around Opensea’s royalty enforcement and am wondering if anyone who knows how Manifold is approaching this could shed some light. I’m working with an artist who needs to deploy a contract and mint a piece today, for a deadline. We had already decided to use Manifold, but given that there doesn’t seem to be an implementation of Opensea’s royalty enforcement blocklist for Manifold yet, we’re not sure what to do. If we knew that Manifold’s solution for this is something that could be added later, once it’s ready, to an already-deployed contract (using an extension?), we’d feel fine about deploying a Manifold contract (we don’t need royalty enforcement right away, but need to know we can implement it in the future). If the solution is something that has to be added when a contract is deployed, then we may need to plan on deploying today and redeploying later, or look into other contracts we can use today.
Opensea royalty enforcement / blocklist - can solution be added to existing contracts?
You should be good to go. We’ve been in touch with OpenSea and are building an extension to enable what you’re describing now.
edit 11/22: we are working to support this but an extension will likely not work, unfortunately.
Thanks for your reply! Sounds great
Any time estimate on this? Currently recent manifold contracts show 0% royalties and it’s a no-go for artists.
It’s a priority. 2-3 weeks.
@gorkulus @0x12389810weq I have some unfortunate news. An issue came up and it doesn’t look like this can be done with an extension anymore.
Sorry, this caught us off guard. There are a few ways forward, I will share updates when I can.
Thanks for the update. That is unfortunate - we went ahead and minted an artist’s first NFT on a Manifold contract based on this guidance, to be featured in a big show. It sounds like we will probably need to redeploy on a new contract at some point. Definitely would love any further updates as soon as you have them.
I know, I thought we were solid. Apologies. Will keep this thread up to date.
Major bummer. I know it’s a complex problem.
I was about to launch a Burn/Redeem with a royalty tomorrow. Should we wait until the plan is more full flushed out? If so, how would I delay a Burn/Redeem draft? Can I remove the start date if I have not Published yet?
Thanks, appreciate it! If deploying a new Manifold contract with the OS code (or similar) is a path forward and it could be done soon, we’d love that.
I just deployed our SC and NFT Collection via manifold and discovered that because manifold doesn’t include on-chain enforcement opensea won’t enforce royalties.
This is a major problem and, quite frankly, should have been disclosed prominently. Not buried in the FAQ and in the Forum.
What is really suprising is that manifold’s UI clearly implies that opensea royalties ARE supported
But when one clicks the link opensea shows the following.
Seems a bit deceptive…
I don’t know what to do at this point. Extremely disappointed.
Damn it. You’re right. The in-app messaging is not accurate for all contracts anymore . Will fix.
We’re working to give optionality for creators to support Opensea’s Operator Filters, but it is a moving target. If this is important to you–and you do not already have a manifold contract deployed prior to november 8th–I would use another contract provider right now.
Added a warn to the deploy screen.
We’re working actively on this and will have updates to share shortly.
May you provide some more clarity on “moving target” and how this differs from being a “priority. 2-3 weeks” which you have been stated 8d ago? I am closely working with an artist on a drop that will partly rely on secondary market royalties. Manifold is our preferred contract provider so an additional 1-2 weeks to wait would be fine. BR Nils
is there a possibility that it will not be solved?
We have a solution.
See public announcement here with more details: https://twitter.com/manifoldxyz/status/1598073648656822272
so if i make a new one contract today, after 1 dec, i will have royalties on OS?
Yes for contracts deployed from Dec 1st, you can go into studio, select your contract, then settings. There you can enable OpenSea’s marketplace blocker (and then have royalties enforced).
For contracts deployed from November 8th until Dec 1st, we’re working closely with OpenSea on a solution, hang tight.
For future updates, follow the pinned thread: [Release] Manifold Creator Core v2.0.0 Update🎉