Summary: Operator Filter Registry is best understood not as a generic NFT-royalties debate artifact, but as a concrete onchain policy layer for deciding which transfer operators a token contract will honor. Its core mechanism is a registry of blocked operator addresses and blocked code hashes, plus token-side helper contracts that apply those checks to transfers and approvals. The most important design move is the subscription model: a collection can maintain its own list, copy another list once, or automatically subscribe to a canonical OpenSea-managed list through DefaultOperatorFilterer. That makes the project a useful comparison class for Royalty Registry, ERC721-C transfer validators, and Seaport authorizer zones: the real question is whether creator-fee enforcement power sits in metadata signaling, in a shared blacklist publisher, in token-level transfer validation, or in marketplace-specific fulfillment rules.
What it does:
Lets token contracts or their owners register with a shared registry and filter specific operator addresses or contract code hashes
Supports subscription and copy semantics so one registrant can inherit another registrant’s blocklist instead of curating its own from scratch
Ships OperatorFilterer helper contracts that token contracts can inherit to gate transferFrom / safeTransferFrom and approval methods through the registry
Ships DefaultOperatorFilterer, which automatically subscribes a collection to OpenSea’s canonical subscription list
Ships revokable and updatable variants so owners can later bypass or re-point the registry logic
Is explicitly marked deprecated in the official repository, and OpenSea later said it was sunsetting the filter because unilateral marketplace blocking failed to gain ecosystem-wide buy-in
Key claims:
The registry contract shows the core mechanism is broader than a hand-maintained address blacklist. It lets registrants filter both individual operators and entire operator implementations by code hash, which is a much stronger control surface than simple metadata-based royalty preference signaling.
The subscription model is the analytically important piece. registerAndSubscribe() and DefaultOperatorFilterer mean many collections can inherit one publisher’s policy set, so the central question becomes who controls the canonical list and how downstream collections can exit it.
The OperatorFilterer helpers make the enforcement point explicit: the token contract itself is expected to revert transfers or approvals when an operator is disallowed. This is a transfer-admission mechanism, not merely an offchain marketplace preference flag.
RevokableOperatorFilterer is revealing because it bakes in the possibility that collections may want to permanently bypass the registry. Its comments also note that OpenSea may stop enforcing creator earnings if the registry is revoked or bypassed, which exposes the dependency on marketplace policy even when the blocking logic lives onchain.
The official repo README now says the system is deprecated, and OpenSea’s August 2023 announcement said it was sunsetting the Operator Filter because the approach required ecosystem-wide buy-in that did not materialize. That makes the project a useful historical baseline for how hard unilateral royalty enforcement is to sustain.
OpenSea’s newer creator-fee-enforcement docs are useful as a follow-on comparison because they move to Seaport hooks, transfer validators, and signed authorizer zones. That shows the control surface shifted from shared blocklists toward validator-and-zone-based transfer authorization.
Operator Filter Registry belongs in the active corpus because it gives the library a clean mechanism page for NFT-marketplace policy enforcement rather than flattening this whole episode into vague royalties drama.
Whitepaper: No canonical whitepaper or litepaper surfaced in this pass. The strongest primary materials were the official repository, the Solidity source files for the registry and helper contracts, the deprecation note, and OpenSea’s later fee-enforcement docs collected in ../whitepapers/operator-filter-registry-primary-sources-2026-05-11.md.