Worked example · 2023-08
OpenSea Operator Filter Registry sunset — Ethereum + multi-chain — 2023-08-17 (announcement) to 2024-02-29 (grace-period end)
Summary
OpenSea launched the Operator Filter Registry on 2022-11-08 as a creator-side enforcement mechanism in response to the broader 2022 marketplace-policy realignment on Ethereum NFT royalty enforcement. The mechanism's design was a creator-controlled allowlist contract: collections opting in could specify which marketplace operator contracts they wanted their NFTs traded through, and transfers to non-allowlisted operators would revert at the contract layer. The intent was to give creators a way to refuse listing on royalty-optional marketplaces (X2Y2, LooksRare with their 2022 royalty-policy adjustments, Blur with its customisable-royalty mechanism) and thereby protect royalty income at the marketplace-policy layer rather than depending on the ERC-2981 standard's voluntary-payment posture.
In early 2023, OpenSea transferred ownership of the Operator Filter Registry contracts to a multisig held by the Creator Ownership Research Institute (CORI). The transfer was framed as decentralising the enforcement mechanism so that no single marketplace operator (including OpenSea itself) controlled the registry's policy decisions. CORI's stated role was to operate the registry contracts on behalf of the broader creator community, with policy decisions about which marketplace operators to filter made through CORI governance rather than unilaterally by OpenSea.
On 2023-08-17, OpenSea announced via official marketplace communications that it was sunsetting its enforcement of the Operator Filter on its own marketplace effective 2023-08-31. New collections would no longer have their Operator Filter status enforced by OpenSea's listing logic; collections that had already opted in pre-sunset would continue to have their enforcement honoured by OpenSea on Ethereum during a grace period that ran through 2024-02-29. After the grace period end, OpenSea-side enforcement of the Operator Filter ended on Ethereum. CORI continued to operate the registry contracts post-sunset for collections that elected to maintain the on-chain enforcement leg (the contract-level revert on transfers to non-allowlisted operators), but OpenSea's marketplace-side honouring of the registry was retired.
The sunset announcement framed the change as responding to creator and trader feedback about the Operator Filter's effectiveness — the registry's listing-allowlist approach had been substantially defeated through 2022–2023 by traders routing through alternative paths (direct on-chain transfers, marketplace routers that bypassed the gating predicate, marketplaces that did not interact with the registry). OpenSea's framing was that the Operator Filter had become an ineffective enforcement mechanism in practice and that the marketplace-policy posture should adjust accordingly. The creator-side response to the announcement was mixed; collections that had bet on the Operator Filter as their primary royalty-enforcement mechanism faced a deployment-strategy reset, while collections that had used ERC-721C-style enforcement coupling or that had not opted into the Operator Filter were less affected.
For OAK's purposes, the sunset is the canonical worked example for the policy-defection-completion leg of the 2022–2024 Ethereum NFT marketplace-policy realignment on royalty enforcement. The event closes the cycle that began with the X2Y2 + LooksRare 2022 royalty-optionality shifts and the Blur 2022-10-19 launch: the marketplace-side defection from royalty enforcement was followed by the creator-side Operator-Filter response, and the sunset completed the cycle by retiring the marketplace-side honouring of that creator-side response. The cycle's completion converted ERC-2981's standard-vs-enforcement gap from a contested marketplace-policy question into a settled marketplace-policy posture on Ethereum NFT trading: realised royalty payment is voluntary on the taker side absent ERC-721C-style hard-coupled enforcement at the collection contract layer.
Timeline (UTC)
| When | Event | OAK ref |
|---|---|---|
| 2021-07 | ERC-2981 finalised as Final | (standard precedent) |
| 2022-08 | X2Y2 royalty-optionality shift; LooksRare parallel adjustments (see examples/2022-11-x2y2-looksrare-royalty-optional.md) |
T12.003 cohort antecedent |
| 2022-10-19 | Blur launches with customisable-royalty mechanism (third leg of the 2022 cohort) | T12.003 cohort antecedent |
| 2022-11-08 | OpenSea launches the Operator Filter Registry as a creator-side enforcement mechanism | T12.003 creator-side response |
| 2022-11 — 2023 (early) | Hundreds of NFT collections opt into the Operator Filter Registry; on-chain enforcement at the contract-level revert layer becomes operative | (cohort enrolment) |
| 2023 (early) | OpenSea transfers Operator Filter Registry ownership to the CORI multisig; framed as decentralising enforcement governance | (governance handoff) |
| 2022 — 2023 | Traders route around the Operator Filter via direct transfers, marketplace routers that bypass the gating predicate, and marketplaces that do not interact with the registry; enforcement effectiveness erodes through the cohort window | (effectiveness erosion) |
| 2023-08-17 | OpenSea announces sunset of Operator Filter enforcement effective 2023-08-31 for new collections; grace period continues enforcement for already-opted-in Ethereum collections through 2024-02-29 | T12.003 policy-defection completion (announcement) |
| 2023-08-31 | Sunset effective for new collections | T12.003 policy-defection completion (effective) |
| 2023-08 — 2024-02 | Grace period for already-opted-in Ethereum collections | (grace-period window) |
| 2024-02-29 | Grace period ends; OpenSea-side enforcement of the Operator Filter on Ethereum complete | T12.003 policy-defection completion (final) |
| 2024-02-29 onward | CORI continues to operate the registry contracts for collections electing to maintain on-chain contract-level enforcement; OpenSea no longer honours the registry on Ethereum | (post-sunset state) |
What defenders observed
- The on-chain enforcement leg and the marketplace-side enforcement leg are separable. The Operator Filter Registry has two enforcement components: the on-chain contract-level revert on transfers to non-allowlisted operators (technically operative as long as collections retain the OperatorFilterer-imported pattern in their contract code) and the marketplace-side honouring of the registry (a marketplace deciding to refuse listing or transfer on collections whose registry status flags the marketplace's own operator address). The OpenSea sunset retired the second leg on OpenSea but did not retire the first leg; collections that retained the on-chain pattern and held the relevant operator addresses on the filter list continued to have transfers revert to those operators post-sunset. This is the load-bearing analytical observation for defenders evaluating the sunset's per-collection consequences.
- Per-collection effective royalty rate is the load-bearing detection signal post-sunset. A defender (or a creator) tracking realised royalty income post-sunset observes the rate evolving as a function of (a) the collection's pre-sunset volume mix across marketplaces, (b) whether the collection retained on-chain contract-level enforcement post-sunset, and (c) the post-sunset evolution of trader behaviour now that OpenSea no longer honours the registry. NFT-analytics platforms (Nansen, Chainalysis, dappradar, bitsCrunch) published per-collection effective-royalty-rate metrics across the post-sunset window; the load-bearing collection-level signal is the divergence between the nominal stated rate and the realised rate weighted by per-marketplace volume share.
- The Mitigation surface for creators after the sunset is at deployment time and at contract-level enforcement. Creators deploying new collections post-sunset face a deployment-time decision: ship with ERC-2981 metadata only (and accept that royalty payment is voluntary on the taker side and that no marketplace-side enforcement layer remains on OpenSea), use ERC-721C-style enforcement coupling at the collection contract layer (LimitBreak's approach, hard-coupling transfer to a payment predicate), or adopt a successor-standard approach (proposals to ERC-2981 that bind taker-side payment, contract-level metadata standards such as EIP-7572 that improve marketplace-side policy interpretation). The OpenSea sunset event is the dated marketplace-policy change that creators must plan against in the post-2024-02-29 deployment environment.
- The sunset event is a structural completion of the 2022 cohort, not a single isolated marketplace decision. Reading the sunset in isolation would miss the cohort trajectory that produced it. The 2022-08 X2Y2 + LooksRare royalty-optionality shifts started the cohort; the 2022-10-19 Blur launch with customisable-royalty extended it; OpenSea's November 2022 Operator Filter response was the creator-side enforcement attempt; the August 2023 sunset announcement and the 2024-02-29 grace-period end completed the cycle. The cohort-trajectory framing is the load-bearing analytical context for the sunset event.
- CORI's continuing operation of the registry is the residual enforcement leg. CORI continued to operate the registry contracts post-sunset, and collections electing to maintain the on-chain contract-level enforcement leg (transfers reverting to non-allowlisted operators) retain that enforcement post-sunset on Ethereum. Defenders advising creators on residual royalty-enforcement options post-sunset should treat the on-chain leg + CORI registry continuity as the residual Operator-Filter-class enforcement path, distinct from the OpenSea-side honouring that ended at the grace-period end.
What this example tells contributors writing future Technique pages
- Marketplace-policy events have multi-layer enforcement consequences that a single-event read misses. The Operator Filter Registry was a two-layer enforcement mechanism (on-chain contract-level + marketplace-side honouring). The OpenSea sunset retired one layer on one marketplace; the other layer on the same marketplace and both layers on other marketplaces (where applicable) operate independently. Contributors writing future T12.003 worked examples should be explicit about which enforcement layer the event affects and which layers continue to operate.
- Creator-side deployment-time decisions are a discrete defender practice and warrant explicit Mitigation entries. The post-sunset deployment environment for new NFT collections requires explicit decisions about royalty-enforcement strategy that did not apply pre-2022. Contributors writing the v0.x Mitigation entries for T12.003 should consider an explicit creator-deployment-time-decision Mitigation that points back at this sunset event as the dated marketplace-policy realignment creators must plan against.
- Marketplace public communications are the load-bearing attribution anchor for marketplace-policy events. OpenSea's 2023-08-17 sunset announcement is publicly attributed via official marketplace communications, as are the 2022-08 X2Y2 + LooksRare royalty-optionality shifts. T12.003 worked examples should treat marketplace-public-statements as the load-bearing attribution evidence at the policy-event layer; on-chain forensics and per-incident technical evidence are not the appropriate attribution anchors for events of this class.
- Policy-event cohort trajectories should be documented as cohorts. The 2022–2024 Ethereum NFT marketplace-policy realignment on royalty enforcement is a multi-event cohort: the X2Y2 + LooksRare 2022 antecedents, the Blur 2022 launch, the OpenSea Operator Filter response, and the OpenSea sunset together form the trajectory. Each event is documented separately in the OAK examples corpus, but contributors writing future T12.003 worked examples should reference the trajectory as the load-bearing structural framing rather than treating any single event as standalone. The T12.003 Real-world examples section in
techniques/T12.003-royalty-bypass-marketplace-manipulation.mdis the canonical map between cohort events.
Public references
[openseaoperatorfilter2022]— OpenSea Operator Filter Registry GitHub project; documents launch, CORI multisig transfer, August 2023 sunset announcement effective 2023-08-31, and grace-period end 2024-02-29.[openseasunsetannouncement2023]— OpenSea's August 17 2023 announcement of the Operator Filter sunset and grace-period framework.[corimultisigregistry]— CORI's continuing operation of the Operator Filter Registry contracts post-sunset.[blurzeroroyalty2022]— Blur launch documentation; cohort antecedent context.[eip2981]— ERC-2981 NFT Royalty Standard text; structural antecedent.[chainalysis2022nft]— primary NFT industry retrospective; cohort-scale framing for the broader Ethereum NFT marketplace volume mix.
Citations
[openseaoperatorfilter2022]— Operator Filter Registry GitHub project; primary marketplace-side technical documentation.[openseasunsetannouncement2023]— OpenSea sunset announcement; primary attribution source for the policy-event layer.[corimultisigregistry]— CORI continuing operation of the registry contracts post-sunset.[blurzeroroyalty2022]— Blur launch documentation.[eip2981]— ERC-2981 standard.[chainalysis2022nft]— primary NFT retrospective.
Discussion
The OpenSea Operator Filter Registry sunset is OAK's canonical worked example for the policy-defection-completion leg of the 2022–2024 Ethereum NFT marketplace-policy realignment on royalty enforcement. The event closes the cohort cycle that began with the 2022-08 X2Y2 + LooksRare royalty-optionality shifts and the 2022-10-19 Blur launch with customisable-royalty mechanism: the marketplace-side defection from royalty enforcement provoked the creator-side Operator-Filter response, and the sunset completed the cycle by retiring the marketplace-side honouring of that creator-side response on Ethereum.
The cohort completion converted ERC-2981's standard-vs-enforcement gap from a contested marketplace-policy question into a settled marketplace-policy posture on Ethereum NFT trading. After 2024-02-29, realised royalty payment on Ethereum NFT trades is voluntary on the taker side absent ERC-721C-style hard-coupled enforcement at the collection contract layer. The on-chain Operator Filter contract-level revert remains technically operative for collections that retain the OperatorFilterer-imported pattern, and CORI continues to operate the registry contracts; but the marketplace-side honouring leg on OpenSea — the load-bearing leg for collections that bet on Operator-Filter-as-primary-enforcement — is retired.
For OAK's purposes, the sunset event is analytically important beyond the per-event detail. The cohort trajectory it completes — X2Y2 + LooksRare royalty-optionality (defection antecedent), Blur launch (cohort extension), Operator Filter Registry (creator-side enforcement response), sunset (defection completion) — is the canonical structural narrative for T12.003. Contributors writing future T12.003 worked examples should preserve this trajectory as the load-bearing context, treating any single event as a leg of the broader cohort rather than as a standalone incident. The sunset is the terminal leg of the trajectory; whether subsequent marketplace-policy events (post-2024 successor enforcement standards, ERC-2981 successor proposals binding taker-side payment, EIP-7572-class contract-level metadata adoption) form a new trajectory is a contributor target for v0.x updates.
The case also sits at the intersection of OAK's non-partisan editorial framing for T12.003. The sunset announcement framed the change as responding to enforcement-effectiveness erosion through 2022–2023; creator-side responses framed the sunset as completing a coordinated marketplace defection from royalty enforcement. Both framings are coherent within their respective premise sets. OAK documents the case because the defensive question for creators is real in the post-sunset environment regardless of how the underlying policy debate is resolved: a creator deploying a new collection in 2024 onward needs to make an explicit deployment-time decision about which royalty-enforcement strategy their revenue assumptions depend on, and the sunset is the dated marketplace-policy event that defines the constraints of that decision.
The pairing with examples/2022-11-x2y2-looksrare-royalty-optional.md is the most useful within-OAK cross-reference for the T12.003 cohort trajectory. The two examples together bracket the 2022–2024 marketplace-policy realignment: X2Y2 + LooksRare 2022 is the antecedent, the OpenSea sunset is the completion, and the Blur 2022-10-19 launch (referenced in the T12.003 technique page Real-world examples section) is the cohort extension between them. Contributors writing future T12.003 examples should preserve the trajectory across all three legs and should not collapse the cohort into any single dated event.