<\/p>\n
Yesterday, NFT marketplace Blur<\/a> finally allowed users to redeem care packages for $BLUR, the platform\u2019s native token. The event was highly anticipated and resulted in a significant market surge over the last month. Ultimately, the\u00a0royalties-optional marketplace secured over\u00a0$430 million in trading volume<\/a>\u00a0in the last 30 days. And yesterday, the money continued to flow.<\/p>\n The event saw several top traders rake in more than $1 million<\/a> worth of tokens. According to data from\u00a0DappRadar<\/a>, Blur\u2019s 24-hour trading volume was around $9.5 million, making it second only to OpenSea, whose trading volume was approximately $12 million.<\/p>\n Now, it seems that Blur is going toe-to-toe with OpenSea in a new chapter of the Web3 royalty wars<\/a>. <\/p>\n In a blog post published this afternoon<\/a> (Feb. 15), the Blur team told users that they should block OpenSea\u2019s NFT marketplace. Why? Because creators currently can\u2019t earn full royalties on both Blur and OpenSea. Instead, they need to choose one to earn full royalties on \u2014 OpenSea or Blur, but not both. <\/p>\n This happens because OpenSea automatically sets royalties to optional when they detect trading on Blur. According to OpenSea<\/a>, they have this policy to protect both creators and their own bottom line.<\/p>\n In a series of tweets posted in November 2022, OpenSea company outlined its rationale for banning royalty-optional marketplaces like Blur. <\/p>\n \u201cIn the economic downturn, many of those looking to sell their NFTs are trying to sell them for as much as they can. Moving their listings to marketplaces that don\u2019t enforce fees is one way to do this. For collectors, this means NFTs they really want are increasingly likely to be listed on marketplaces that don\u2019t enforce creator fees. Even if these collectors say they want to pay creator fees, they\u2019re becoming more and more prone to buying on those marketplaces\u2026.Unless something changes soon, this space is trending toward significantly fewer fees paid to creators.\u201d \u2014 OpenSea<\/a><\/em><\/p>\n OpenSea\u2019s answer to this problem is to encourage individuals to prevent their NFTs from being traded on royalty-optional platforms. How do they do so?<\/p>\n In order for full creator fees to be enforced on OpenSea\u2019s platform, individuals who created smart contracts after January 2, 2023, must take on-chain action to make royalties enforceable. In other words, OpenSea requires creators to use on-chain tools that prevent the sale of NFTs on marketplaces that don\u2019t enforce creator royalties. Blur is a royalty-optional platform. As a result, users must block their NFTs from being sold on Blur in order to earn full royalties on OpenSea. If an individual opts not<\/em> to do this, OpenSea automatically sets royalties to \u201coptional\u201d on these collections. <\/p>\n In short, royalty-optional platforms like Blur must be blocked or OpenSea makes royalties optional. <\/p>\n Blur takes issue with this stance, claiming that creators should be the ones to decide where and how their items are sold \u2014 not companies. \u201cOur preference is that creators should be able to earn royalties on all marketplaces that they whitelist, rather than being forced to choose. To encourage this, Blur enforces full royalties on collections that block trading on OpenSea,\u201d they wrote in the blog post. <\/p>\n They continued, \u201cOpenSea has primarily cited Blur\u2019s policy on old collections without filters as the reason for why Blur should still be filtered by new collections. Their proposed solution, however, has serious flaws\u2026.which is why Blur has taken a different approach that has a better chance of solving the issue for good.\u201d<\/p>\n The response to the post was swift. Many members of the Web3 community took to Twitter and began posting about a new era in the royalty wars. It remains to be seen who will win this war. But for now, one thing is clear \u2014 creators are caught in the middle. <\/p>\nBlur vs OpenSea explained<\/h2>\n