Affiliate disclosure: the offers above and the links in this article are affiliate links. KY Solutions K.K., the operator of this site, may earn a commission when you sign up through them. We are an independent affiliate and not the official site of any company shown. 【開示】上記のオファーおよび本記事内のリンクはアフィリエイトリンクです。当サイト運営者(KY Solutions株式会社)は報酬を受け取ることがあります。当サイトは掲載各社の公式サイトではありません。
An NFT royalty is a number the token can express, not a rule the blockchain applies. The contract records that the creator would like a share of every resale, and whether that share is actually paid depends on whichever piece of software executes the trade. Most of those venues have, at some point since 2022, chosen not to pay it. Royalty on an NFT is enforced at the marketplace layer rather than by the token standard, and that single distinction explains almost every unpleasant surprise creators have had in the last four years.
This article is a factual reference and does not constitute investment or financial advice. It stays with what can be read directly in the standards, in marketplace documentation, in peer reviewed measurement and in published law, and it marks the places where the public record is thin. The thinnest part of that record is the present. No primary source we could open measures what share of today's NFT trades actually pay a royalty, so this piece deliberately does not give that number.
What exactly is an NFT royalty?
It is a request for payment that the token can state but cannot collect. The base standard for Ethereum NFTs, ERC-721, has no concept of money at all. Its required interface covers ownership and movement only, through functions such as ownerOf, transferFrom, safeTransferFrom, approve and setApprovalForAll. There is no sale price parameter anywhere in it, and no royalty recipient.
The royalty signal arrives in a separate standard, ERC-2981, which is marked Final in the Ethereum standards registry and was created on 15 September 2020. It adds exactly one read only function:
royaltyInfo(uint256 _tokenId, uint256 _salePrice) external view returns (address receiver, uint256 royaltyAmount)
A caller supplies a token identifier and a sale price, and the contract returns an address and an amount. The standard requires that implementers "MUST calculate a percentage of the _salePrice" when working out the royalty. Nothing in the function moves money, and because it is a view function it cannot.
A second piece of infrastructure, the Royalty Registry maintained in the manifoldxyz/royalty-registry-solidity repository, exists because royalty data was scattered across incompatible formats. It provides, in its own words, "a common interface to unify the lookup for various royalty specifications currently in existence", covering Rarible, Foundation, Manifold and EIP-2981, and it lets legacy contracts add an override. It was developed in conjunction with Foundation, manifold.xyz, Nifty Gateway, OpenSea, Rarible, SuperRare and Zora. It is a lookup and override layer, and like the standards it indexes, it does not collect anything.
Does the token standard enforce royalty payment?
No, and ERC-2981 says so in its own text rather than leaving it to interpretation. The abstract states that "the royalty payment must be voluntary, as transfer mechanisms such as transferFrom() include NFT transfers between wallets, and executing them does not always imply a sale occurred". The rationale is blunter: "It is impossible to know which NFT transfers are the result of sales, and which are merely wallets moving or consolidating their NFTs. Therefore, we cannot force every transfer function to involve a royalty payment."
The standard then expresses its hope as a requirement on anyone who adopts it. "Marketplaces that support this standard MUST pay royalties no matter where the sale occurred or in what currency, including on-chain sales, over-the-counter (OTC) sales and off-chain sales." That MUST binds only those who choose to support the standard, and no code checks it. The authors wrote plainly that "we believe the NFT marketplace ecosystem will voluntarily implement this royalty payment standard to provide ongoing funding for artists/creators". Under Security Considerations the document says "there are no security considerations related directly to the implementation of this standard", which is consistent with a specification that never takes custody of a payment. A standard that never holds the money cannot lose it, and for the same reason cannot guarantee it arrives.
| Standard | Registry status | What it specifies | What it enforces by itself |
|---|---|---|---|
| ERC-721 | Final | Ownership and transfer functions | Nothing about price or royalty, which it never mentions |
| ERC-2981 | Final, created 2020-09-15 | A read only royaltyInfo lookup, percentage of sale price | Nothing, payment is described as voluntary in the text |
| ERC-4910 | Final, created 2022-03-14 | Buyer pays the token contract, royalty balances held in the contract | Payment on trades routed through that contract, and only those |
| ERC-5192 | Final, created 2022-07-01 | A locked() flag, after which all transfer functions must throw | Non transferability, which removes resale and the royalty with it |
| ERC-721C | Not in the registry, eips.ethereum.org/EIPS/eip-721c returns 404 | Creator defined transfer security profiles and operator allowlists | Which addresses are allowed to move the token |
| Metaplex programmable NFTs | Solana asset standard, not an ERC | Permanently frozen token accounts plus rule sets | Which programs are allowed to move the token |
| Open Creator Protocol | Solana, open source, not an ERC | A policy engine built on spl-managed-token | Which programs are allowed to move the token |
Why can a contract not tell a sale from a gift?
Because the only thing a transfer function receives is a sender, a receiver and a token identifier. A gift to a friend, a move between two wallets owned by the same person, a loan repayment and a sale all arrive at the contract in the same shape. Price lives outside the token, in whatever marketplace contract or private arrangement produced the trade, and a royalty expressed as a percentage of a reported sale price can only ever be a percentage of what someone chose to report.
That gap has been measured. In the peer reviewed study "Understanding Security Issues in the NFT Ecosystem" by Dipanjan Das, Priyanka Bose, Nicola Ruaro, Christopher Kruegel and Giovanni Vigna, presented at ACM CCS in Los Angeles on 7 to 11 November 2022, the authors looked for trades that bypassed marketplace machinery. Their heuristic counted cases where "an address (seller) S transferred the NFT to another address (buyer) B, and B sent a payment to S on-chain within 15 minutes (before or after) the transfer transaction". Across assets listed on seven venues they found 56,920 such instances for OpenSea, 2,777 for Rarible, 814 for CryptoPunks, 302 for SuperRare, 56 for Sorare, 5 for Foundation and none for Axie. The OpenSea portion of their dataset covered 12,215,650 NFTs over June to December 2021.
Two caveats belong next to those counts. The authors state their own: "this estimate is conservative, because the payment could be made either off-chain or outside the time window that we considered for our analysis." The second is ours. A transfer followed by a payment within fifteen minutes is a pattern consistent with fee and royalty avoidance, not a proof of intent, and the data is five years old. The honest reading is that the hole is structural and was being used at measurable scale, not that we know its current size.
How did marketplaces actually behave once they had the choice?
They competed on it. Once one venue dropped the royalty, sellers had a cheaper place to go, and the rest followed within a year. The sequence below is drawn from reporting that cites the venues' own announcements.
| Date | Venue | Change | Reported by |
|---|---|---|---|
| 4 February 2022 | X2Y2 | Launched with zero royalties, took 11.1 million dollars of volume that month against 3.59 billion for competitors | The Block, 12 November 2022 |
| 8 July 2022 | sudoswap sudoAMM | No royalties, 0.5 per cent protocol fee, 50 million dollars of volume inside two months | The Block, 12 November 2022 |
| 15 October 2022 | Magic Eden | Royalties made optional | The Block, 12 November 2022 |
| 27 October 2022 | LooksRare | Removed royalties, redirected 0.5 per cent of trading fees to creators | The Block, 12 November 2022 |
| 8 November 2022 | OpenSea | Launched the on-chain Operator Filter, restricting transfers to venues that paid royalties | The Block, 12 November 2022 |
| 2 December 2022 | Magic Eden | Launched Open Creator Protocol so new Solana collections could opt into enforcement, royalties stayed optional for those that did not adopt it | Magic Eden press release, 1 December 2022 |
| 17 February 2023 | OpenSea | Trading fee to zero for a limited time, optional creator earnings with a 0.5 per cent minimum across all collections | Fortune, 26 February 2023 |
| 17 August 2023 | OpenSea | Operator Filter deprecated, creator fees optional for new collections from 31 August 2023, enforcement for existing filtered collections ending 29 February 2024 | The Block, 17 August 2023 |
| 1 September 2023 | OpenSea | operator-filter-registry repository archived and made read only on GitHub | GitHub repository state, read 10 November 2026 |
The competitive pressure was not subtle. Fortune reported on 26 February 2023 that Blur, which enforced only a 0.5 per cent minimum creator royalty and charged no trading fee, had taken 1.04 billion dollars of sales volume in the previous thirty days against OpenSea's 479 million, and that Blur had been telling creators to block trading on OpenSea in exchange for full royalty enforcement on Blur. Royalty policy had become a price war between venues, and the creator's share was the price being cut.
Did the operator filter work?
No. It was routed around, then withdrawn by the party that built it. The filter was a blocklist held in a registry contract, and collections that integrated it refused transfers initiated by operator addresses on the list. The weakness was that a blocklist has to name the thing it blocks. Blur integrated Seaport, the order settlement protocol OpenSea itself published, so trades on Blur arrived at filtered collections through the same contract OpenSea used. As The Defiant put it in the headline and standfirst of Owen Fernau's report, "Blur Adopts Seaport To Sidestep OpenSea Filter" and the "NFT Marketplace Will Enforce Royalties On Seaport Listings". Blocking Seaport would have meant blocking OpenSea.
Worth stating against our own argument: that particular bypass was not royalty theft. Blur said it would enforce royalties on those Seaport listings. What collapsed was the venue restriction, which was the only lever the filter actually pulled. OpenSea's own explanation when it deprecated the tool, quoted by The Block on 17 August 2023, was that the filter "was meant to empower creators with greater control over their web3 business models, but it required the buy-in of everyone in the web3 ecosystem, and unfortunately that has not happened".
Creators did push back. Yuga Labs chief executive Daniel Alegre said the company would "begin the process of sunsetting support for OpenSea's SeaPort for all upgradable contracts and any new collections, with the aim of this being complete in February 2024", adding that "Yuga believes in protecting creator royalties so creators are properly compensated for their work", as reported by The Block on 18 August 2023. A collection can withdraw from a venue, which is a real sanction, and it is still a commercial decision rather than a property of the token.
What do transfer restricted designs actually guarantee?
They guarantee which addresses may move the token. That is a conduit restriction, and it is not the same thing as verifying that a payment happened. The strongest current example on Ethereum is Limit Break's ERC-721C, which extends OpenZeppelin's ERC721 by "adding creator-definable transfer security profiles that are the foundation for enforceable, programmable royalties", with a CreatorTokenTransferValidator that lets creators "set transfer security levels, create and manage whitelists/contract receiver allow lists, and apply their creator-defined policies". Security level zero applies no caller or receiver constraints at all, and level one applies an operator allowlist that still enables over the counter transfers between wallets.
Payment is handled by a separate contract rather than by the token. Limit Break's Payment Processor documentation describes it as "a peer-to-peer NFT trading protocol" acting as "the blockchain execution layer for one or more off-chain order books and exchanges", and states that it "will NEVER withhold creator royalties when they are configured on-chain". It also lets creators restrict accepted payment currencies and "apply a minimum floor or maximum ceiling price at the individual token id or collection level". The documentation is candid about the dependency: a collection with no EIP-2981 support, no owner or access control and no backfilled royalty can only enforce payment through off-chain marketplace agreements.
Solana reached the same design from the other direction. Metaplex programmable NFTs keep token accounts permanently frozen at the SPL Token level so every operation must pass through the Token Metadata program, where rule sets evaluate allow and deny primitives such as ProgramOwnedList. The documentation states that "creators can design a Rule Set that ensures programs that do not enforce royalties are forbidden to perform transfers on their assets", and offers community rule sets so "any program that stops supporting royalties is immediately banned". Magic Eden's Open Creator Protocol takes the same route through spl-managed-token, describing itself as "an open protocol for creators to build utilities and the policy engine for their tokens".
Three limits apply to all of them. First, the allowlist is a governance object, so somebody curates it and that somebody becomes a dependency, which is the same centralisation trade-off that appears whenever crypto rails borrow an institutional gatekeeper, as in the debate over bank custody of digital assets. Second, ERC-721C is not a registered Ethereum standard. Its canonical registry page does not exist, and the reference implementation ships under an MIT licence that "disclaims all warranties in relation to the project". Third, and most important, none of it sees the money. ERC-4910, which goes furthest by making the buyer pay the token contract directly so royalties distribute inside it, concedes the ceiling in its own Security Considerations: "Exchanging a private key for money off chain cannot be prevented in any scenario." The spec also notes that smart contract wallet owners could settle internally and recommends barring contracts from owning the NFT unless whitelisted. Transfer restriction raises the cost of avoiding a royalty, it does not make payment a property of the asset.
| Route | Marketplace policy alone | Operator allowlist, ERC-721C style | Contract takes the payment, ERC-4910 style |
|---|---|---|---|
| Listing on a venue that treats royalty as optional | Not stopped, that is the venue's choice | Stopped, an unlisted operator cannot move the token | Stopped for trades routed through the contract |
| Wallet to wallet transfer with payment sent separately | Not stopped | Not stopped at security level one, which enables OTC by design | Not stopped, the contract never sees the separate payment |
| Reporting a token sale price and settling the rest off chain | Not stopped | Not stopped, the check is on who moves the token, not on price | Partly stopped, only the amount routed through the contract is visible |
| Selling the private key or the whole wallet | Not stopped | Not stopped, no transfer event occurs | Not stopped, and the spec says so explicitly |
| Moving the token into a wrapper contract that is allowlisted | Not stopped | Stopped only if receiver allow lists exclude the wrapper | Depends on how the wrapper settles |
| Changing control of a smart contract wallet that holds the token | Not stopped | Not stopped | Mitigated only by refusing contract ownership |
What does the measured record show about the money?
It shows a large cumulative figure and a steep decline, both measured on Ethereum, and both ending in 2023. Galaxy Digital research published in October 2022 by Sal Qadir and Gabe Parker, using Flipside Crypto data, put cumulative Ethereum creator royalties at 1.8 billion dollars, with the top ten issuers taking 27 per cent of that and 482 collections taking 80 per cent. The same work reported that average royalty rates on OpenSea had roughly doubled over the prior year, from about 3 per cent to about 6 per cent, and made the structural point directly, that royalties "are not actually programmed at the token/smart-contract level".
| Measure | Value | Source, method and conditions |
|---|---|---|
| Cumulative creator royalties to October 2022 | 1.8 billion dollars | Galaxy Digital research, October 2022, Flipside Crypto data, commercial research and not peer reviewed |
| Concentration of those royalties | Top 10 issuers 27 per cent, 482 collections 80 per cent | Same Galaxy work, same limitations |
| Peak weekly royalties | 28,000 ETH, nearly 76 million dollars, in one week of April 2022 | Nansen study reported by CoinDesk, Cam Thompson, 6 July 2023, methodology not published |
| Best week of June 2023 | 2,000 ETH, about 3.8 million dollars | Same Nansen study, denominated in ETH so dollar figures move with price |
| Average royalty rate requested | About 7.35 per cent across three major venues, around 10 per cent on Rarible | Falk, Gu, Tsoukalas and Zhang, arXiv 2212.00292, a preprint and not peer reviewed |
| Maximum royalty settable on OpenSea today | 10 per cent | OpenSea creator earnings help article, read 10 November 2026 |
| Share of trades paying a royalty in 2026 | Not stated here | No primary measurement found in this session, figures circulating on commercial market research pages could not be traced to a source |
One frequently repeated economic claim deserves a downgrade. The preprint by Brett Falk, Bin Gu, Gerry Tsoukalas and Niuniu Zhang reports that "higher royalty rates correlate with systematically lower initial sale prices", which is a correlation in a preprint rather than a causal result from peer reviewed work, and it should not be used as proof that charging a royalty costs a creator money at mint. The same paper is useful for a less contested observation, that "marketplace stances have ranged from full enforcement to outright bypass".
What venues say today can be read directly. OpenSea's current help documentation splits collections in two. Creator earnings are enforceable for "ERC721-C or ERC1155-C compatible custom smart contract" deployments and for OpenSea Studio collections created after 2 April 2024 at 10:00am PT. For everything else, "creators can specify their preferred creator earnings in their collection settings, but the NFT owner will ultimately choose whether to pay" them, with sellers toggling payment on when listing or accepting an offer. The ceiling is 10 per cent. Enforcement in 2026 is therefore a property of the individual contract and the individual venue, not of NFTs as a category.
If the code does not enforce it, does the law?
In the European Union there is a statutory resale royalty for physical original works of art, and in the United States there is none in federal copyright law. Directive 2001/84/EC of 27 September 2001 gives the author of an original work of art "an inalienable right, which cannot be waived, even in advance, to receive a royalty based on the sale price obtained for any resale of the work", and applies it to resales "involving as sellers, buyers or intermediaries art market professionals, such as salesrooms, art galleries and, in general, any dealers in works of art". Its Article 4 rates are 4 per cent up to 50,000 euro, 3 per cent to 200,000 euro, 1 per cent to 350,000 euro, 0.5 per cent to 500,000 euro and 0.25 per cent above that, with the total royalty capped at 12,500 euro.
Two features of that regime matter for tokens. The categories in Article 2 are physical, covering pictures, collages, paintings, drawings, engravings, prints, lithographs, sculptures, tapestries, ceramics, glassware and photographs made by the artist, so a token referencing a file is not obviously inside the definition. And the right attaches to professional intermediaries, which is precisely the role a permissionless settlement contract removes. The United States Copyright Office states that a resale royalty right is not part of current United States copyright law, and published "Resale Royalties: An Updated Analysis" on 13 December 2013 while studying whether Congress should create one.
Against our own case, one legal point we will not lean on. A 2018 Ninth Circuit decision in Close v. Sotheby's is widely described as holding the California Resale Royalty Act preempted by the 1976 Copyright Act, and the opinion is published by the court, but we could not open and read the opinion text in this session, so we make no claim about its holding. The safer statement is the one the Copyright Office makes itself.
Which leaves the NFT royalty where it started, as a contractual and commercial expectation rather than a statutory entitlement, resting on the terms of the venue and the configuration of the contract. That is a weaker foundation than many buyers assume, in the same way that the economics of fractional ownership of digital collectibles depends on platform terms rather than on anything the token does, and in the same way that the rules governing stablecoin issuance under Treasury guidelines sit outside the ledger that records the balances. We found no court decision in this session that enforced an NFT royalty against a non paying buyer or venue, and neither regime makes such a royalty self executing.
How strong is the evidence behind each claim in this article?
The spread is wide, and the weakest rows are the ones about current behaviour rather than about mechanism. Mechanism claims come from the specifications themselves, which is the strongest kind of evidence available for a technical question. Market behaviour claims come from trade press reporting venue announcements, which is adequate for dates and poor for magnitudes. Money claims come from commercial analytics with unpublished methods. The mechanism described here is well sourced, the magnitudes are weaker than they look, and the current rate of compliance is simply unknown.
| Claim | Evidence type | Strength |
|---|---|---|
| ERC-721 and ERC-2981 do not enforce payment | Primary specification text, read in session | Strong, the standard states it in its own abstract and rationale |
| Transfer restriction controls the conduit, not the payment | Vendor documentation plus ERC-4910 Security Considerations | Strong on mechanism, and the ERC-4910 text concedes the key sale case |
| Marketplace royalty policies changed on the dates given | Trade press reporting venue announcements, The Block, Fortune, press release | Moderate, dates are consistent across outlets but are not primary filings |
| Royalty avoidance happened at measurable scale | Peer reviewed, ACM CCS 2022, heuristic detection | Moderate, strong venue and an explicit conservative caveat, but 2021 data and a pattern rather than proven intent |
| Cumulative royalties reached 1.8 billion dollars | Commercial research on third party chain data | Weak to moderate, not peer reviewed, method not reproducible from the public write ups |
| Weekly royalties fell from 28,000 ETH to 2,000 ETH | Analytics firm study reported by trade press | Weak to moderate, no published methodology, and the comparison mixes ETH and dollar framing |
| Higher royalty rates go with lower mint prices | Preprint, correlational | Weak, we report it only as a correlation and recommend against acting on it |
| Current share of trades paying royalties | None found | Excluded, we could not verify any figure and have left the cell empty rather than estimate |
| ERC-721C adoption percentages circulating online | Commercial market research pages, no primary data | Rejected, these are not primary sources and we do not repeat their numbers |
| EU resale right rates and the United States position | Directive text and a government agency statement | Strong for the law as written, untested as applied to tokens |
What should a creator or a buyer check before assuming a royalty will be paid?
Check the contract first and the marketing second, because only one of them binds anyone. The following six checks can each be done in a few minutes.
- Read the token contract for a transfer validator or a frozen token account design. If every transfer is unconstrained, the royalty is a request.
- Check whether the collection appears as enforced or optional on each venue where it trades, because the answer differs by venue and by contract age, not by collection reputation.
- Treat the stated percentage as a ceiling. On optional collections the seller selects the amount, and paying above the minimum has been reported as uncommon.
- Assume wallet to wallet settlement exists. Operator allowlists at the common security level permit over the counter transfers by design.
- Ask who curates the allowlist and who can change it, because that party can change the economics of the collection without the creator acting.
- Do not assume statutory backing. The resale royalty in the European Union is written for physical art and professional intermediaries, and the United States has no federal equivalent.
The same discipline applies to every claim that a platform mechanism is automatic, whether the subject is royalties, the fee structures compared in work on social trading platform economics, or the screening promises behind sustainable digital asset funds. A rule that lives in a platform's policy can be changed by the platform, and the only rules that cannot are the ones a contract refuses to execute.
Frequently asked questions
Is EIP-2981 enforceable?
No. It defines a read only lookup that returns a recipient and an amount, and its own abstract states that "the royalty payment must be voluntary". Any payment happens because a marketplace contract chose to call the lookup and send the money.
Did OpenSea stop paying creator royalties?
It stopped enforcing them universally. From 31 August 2023 creator fees became optional for new collections, enforcement for collections using the Operator Filter ended on 29 February 2024, and today OpenSea documents earnings as enforceable only for ERC721-C and ERC1155-C compatible contracts and for Studio collections created after 2 April 2024. On other collections the owner chooses whether to pay, and the maximum settable rate is 10 per cent.
Can a creator force a royalty on every transfer?
Not without blocking transfers the creator does not like, which also blocks gifts, wallet consolidation and inheritance. The only fully enforceable rule is non transferability, as in ERC-5192, where a locked token makes every transfer function throw. That removes resale, and with it the royalty.
Do Solana NFTs enforce royalties better than Ethereum NFTs?
They use a stricter default. Programmable NFTs keep token accounts frozen so operations must pass through the Token Metadata program, where rule sets can forbid programs that do not enforce royalties. The guarantee is still about which program moves the asset, so an off chain payment with an allowlisted transfer remains possible.
Is an NFT royalty a copyright entitlement?
Not in the United States, where the Copyright Office states that a resale royalty right is not part of current copyright law. In the European Union there is an inalienable resale right under Directive 2001/84/EC, written for original works of art and resales involving art market professionals, and its application to tokens is untested in anything we could verify.
What is the single most reliable signal that a royalty will actually be paid?
That the sale is settled by a contract which looks up the royalty and pays it in the same transaction, on a collection whose transfers are restricted to such contracts. Limit Break's Payment Processor states that it "will NEVER withhold creator royalties when they are configured on-chain", which is a design property rather than a promise about any particular venue, and it only holds for trades that go through it.
Sources
- ERC-2981: NFT Royalty Standard, Ethereum Improvement Proposals, Final, created 15 September 2020
- ERC-721: Non-Fungible Token Standard, Ethereum Improvement Proposals
- ERC-4910: Royalty Bearing NFTs, Ethereum Improvement Proposals, created 14 March 2022
- ERC-5192: Minimal Soulbound NFTs, Ethereum Improvement Proposals, created 1 July 2022
- Das, Bose, Ruaro, Kruegel and Vigna, Understanding Security Issues in the NFT Ecosystem, ACM CCS 2022
- Falk, Gu, Tsoukalas and Zhang, Economics of NFTs: The Value of Creator Royalties, arXiv preprint
- Directive 2001/84/EC of 27 September 2001 on the resale right for the benefit of the author of an original work of art
- United States Copyright Office, Resale Royalty Right, including Resale Royalties: An Updated Analysis, 13 December 2013
- Royalty Registry and Royalty Engine, manifoldxyz/royalty-registry-solidity
- Limit Break, Creator Token Standards, ERC-721C reference implementation
- Payment Processor documentation, overview
- Metaplex, Programmable NFTs documentation
- Open Creator Protocol, magiceden-oss/open_creator_protocol
- Magic Eden, Open Creator Protocol press release, 1 December 2022
- OpenSea, operator-filter-registry, archived 1 September 2023
- OpenSea support, How do I set creator earnings on OpenSea
- MK Manoylov, NFT royalties: the story so far, The Block, 12 November 2022
- MK Manoylov, OpenSea disables royalty enforcement tool, The Block, 17 August 2023
- MK Manoylov, Yuga Labs slams OpenSea's shift to optional royalties, The Block, 18 August 2023
- Marco Quiroz-Gutierrez, Fortune, 26 February 2023
- Owen Fernau, Blur Adopts Seaport To Sidestep OpenSea Filter, The Defiant
- Cam Thompson, NFT Creator Royalty Payments Hit Two-Year Low, CoinDesk, 6 July 2023
- The Block on Galaxy Digital research, cumulative Ethereum NFT royalties, 21 October 2022



.png)



