The registry contract shows this was a real policy primitive, not just public marketplace rhetoric. Collections or owners could register, filter operator addresses, filter contract code hashes, subscribe to another registrant’s list, or copy another registrant’s entries once and then diverge.
OperatorFilterer.sol is the main mechanism page in code form: token contracts are meant to inherit transfer and approval modifiers that query the registry and revert when an operator is disallowed. This is transfer admission control, not only offchain royalty signaling.
DefaultOperatorFilterer.sol is especially revealing because it auto-subscribes inheriting token contracts to OpenSea’s canonical subscription. That exposes the real control surface very clearly: whoever curates the canonical list can shape many collections’ effective marketplace policy.
RevokableOperatorFilterer.sol matters because it bakes in the possibility of exit. The comments note that OpenSea may stop enforcing creator earnings if the registry is revoked or bypassed, which shows the mechanism always depended on marketplace cooperation in addition to token-side checks.
The official README now consists mainly of a deprecation notice pointing readers to a creator-fees update, which is itself useful evidence: the mechanism was retired rather than becoming a permanent shared industry standard.
OpenSea’s August 2023 announcement says the Operator Filter was launched so creators could restrict secondary sales to marketplaces that enforce creator fees, but was being sunset because ecosystem-wide buy-in did not happen. That makes the project a strong historical case study in the limits of unilateral marketplace-led royalty enforcement.
The current creator-fee-enforcement docs are useful as a successor comparison point because they move to Seaport hooks, transfer validators, and signed authorizer zones. The control surface shifts from blacklist publication toward validator configuration and order authorization.
Why it matters for the corpus
It gives the corpus a clean mechanism page for NFT royalty enforcement infrastructure instead of leaving the topic as blog-level culture-war memory.
It also creates a bridge between older blacklist-style enforcement and newer validator/zone-based enforcement models like ERC721-C-style transfer validation.
The most reusable question it raises is where creator-fee control really lives: royalty metadata, marketplace policy, shared operator blocklists, token-level transfer validators, or order-authorizer zones.
Follow-up comparison threads
Compare Operator Filter Registry directly against Royalty Registry so offchain royalty signaling and onchain transfer blocking do not get flattened together.
Compare Operator Filter Registry directly against ERC721-C / transfer-validator / SignedZone flows so shared blocklist publication, token-level validation, marketplace authorization, and collection-owner override power do not get flattened into one generic creator fees bucket.