operator-filter-registry So whats with the latest changes? Is this operator filter still needed?

Confused af .......

https://twitter.com/opensea/status/1626682043655507969

Feb 18 '23 01:02 kabaluyot

https://github.com/ProjectOpenSea/operator-filter-registry/commit/b490f22be54b69a45f4dce516370fa433b0144d8

so who controls the list now?

Feb 20 '23 04:02 irreverent-eth

What's the status of this?

Mar 01 '23 00:03 nidhhoggr

"9/ Second – We’re moving to a minimum 0.5% creator earnings model, with the option for sellers to pay more. This applies to all collections that do not use on-chain enforcement (old and new)."

This means implementing this is unnecessary to earn creator fees in OpenSea. Correct?!?!

Mar 01 '23 00:03 nidhhoggr

"9/ Second – We’re moving to a minimum 0.5% creator earnings model, with the option for sellers to pay more. This applies to all collections that do not use on-chain enforcement (old and new)."

This means implementing this is unnecessary to earn creator fees in OpenSea. Correct?!?!

I assume this is not required anymore. It backfired to opensea ..

Mar 01 '23 01:03 kabaluyot

I assume this is not required anymore. It backfired to opensea ..

While I appreciate your assumption, I would appreciate that confirmation coming from the horses mouth and not have to rely on deciphering cryptic marketing lingo only for them to change the requirement for onchain enforcement for the umpteenth time.

Mar 01 '23 04:03 nidhhoggr

I have been trying for 4 days to get an Answer from Opensea Discord dev support channels and no one has been bothered to answer me bar some scammers and one community member.

OpenSea support sucks.

Mar 16 '23 08:03 null-prophet

finally got some one from support to confirm this is still needed.

Mar 23 '23 07:03 null-prophet

What? But they said from their announcement that force implementation of this is not anymore required no?

Mar 23 '23 08:03 kabaluyot

From the horses mouth:

🐴 👄

Norman (OpenSea)

Mar 16, 2023, 23:59 UTC

Hi there,
 
Thanks for reaching out. I can share more about OpenSea’s current creator earnings policy. 
 
For collections that don’t contain an on-chain enforcement method, we’ll enforce 0.5% creator earnings, and sellers can choose to pay additional optional creator earnings. This applies to all listings and offers created after 3:30 pm ET on February 17, 2023.
 
Collections that choose to use the [Operator Filter](https://github.com/ProjectOpenSea/operator-filter-registry), or another on-chain enforcement method, will have their full creator earnings enforced. This is also the case for any collections created using OpenSea’s shared storefront. You can set creator earnings by following the steps in this [help guide](https://support.opensea.io/hc/articles/14069267158035).
 
I’m here to help if you have additional questions.
Customer Experience Associate

Norman

So there you go.

Mar 23 '23 09:03 null-prophet

~~Seems they will enforce royalties if your contract has ERC-2981~~

that was polygon

Mar 23 '23 14:03 irreverent-eth

Seems they will enforce royalties if your contract has ERC-2981

where is the proof in this statement? Show me Opensea explicitly saying this otherwise it's just your opinion.

Mar 23 '23 20:03 null-prophet

Seems they will enforce royalties if your contract has ERC-2981

that's most likely not the case. They are pretty clear about this in the Readme that it's basically just a recommendation that most marketplaces disregard. Taken directly from the README of this repo:

Note on EIP-2981

Implementing EIP-2981 is not sufficient for a token to be eligible for creator earnings on OpenSea.

While sometimes described as "on-chain," EIP-2981 only provides a method to determine what the appropriate creator earnings should be for a sale. EIP-2981 does not provide any mechanism of on-chain enforcement of those earnings.

Mar 23 '23 21:03 nidhhoggr

~~I deployed contracts with ERC-2981 support and royalties are enforced for it on OpenSea~~

sorry this was polygon

Mar 23 '23 23:03 irreverent-eth

I deployed contracts with ERC-2981 support and royalties are enforced for it on OpenSea

Do you have the address?

And you had no operator filterer added?

And setting a royalty in OS above 0.5% worked?

Mar 24 '23 00:03 null-prophet

OK, my bad, seems that it was only the case for polygon collections

Mar 24 '23 08:03 irreverent-eth

OK, my bad, seems that it was only the case for polygon collections

@irreverent-eth show the contract address or it didn't happen. If that was the case OpenSea should have indicated such in the support response provided above.

Mar 26 '23 02:03 nidhhoggr

cost like less than a dollar to test

https://polygonscan.com/address/0xf605e6efaeb8933297f14442855ed78c7f6b30c5

@nidhhoggr

Mar 26 '23 15:03 irreverent-eth

@irreverent-eth While it appears creator fees are working on that collection have you tried a purchase transaction to see whether or not they are only optional? Screen Shot 2023-03-26 at 2 03 19 PM

Mar 26 '23 21:03 nidhhoggr

@nidhhoggr

Mar 26 '23 22:03 irreverent-eth

@irreverent-eth That shows what the seller sees. What does it look like from the buyers end when they are making the purchase? Is there an option or is it required to pay the full %6.9?

Mar 26 '23 22:03 nidhhoggr

@irreverent-eth this is what it looks like if the collection doesn't have royalties enforced

I am not sure if you're getting what I'm trying to say, but my mistake was to assume that OpenSea treats eth and polygon the same but they do not. It looks to me that operator filter is not required for polygon for royalties enforcement at the moment

Mar 26 '23 23:03 irreverent-eth

Screen Shot 2023-03-26 at 8 33 03 PM

Mar 27 '23 03:03 nidhhoggr

That's exactly what I'm saying?

I guess the answer is that for ETH we would still need this

Mar 27 '23 03:03 irreverent-eth