Cowrie Research

royalty-registry

2 min read

Royalty Registry

  • Name: Royalty Registry
  • URL: https://royaltyregistry.xyz/
  • Category: NFT royalty-discovery registry / royalty-override middleware / multi-standard royalty lookup engine
  • Summary: Royalty Registry is royalty-discovery plumbing. It lets a collection point marketplaces at a royalty lookup contract and then normalizes the answer across the usual standards mess. Useful because it standardizes lookup; it does not block transfers or force anyone to pay.
  • What it does:
    • Lets a collection keep its token contract as the royalty source or point the ecosystem at a separate override contract through setRoyaltyLookupAddress
    • Gives older collections a way to add royalty data without redeploying the original NFT contract
    • Normalizes royalty lookups across several supported standards and project-specific formats through a shared RoyaltyEngine
    • Detects and caches the royalty spec used by a token’s chosen royalty-lookup address to reduce future lookup cost
    • Supports multi-recipient outputs instead of flattening everything to one payee
    • Ships public deployments and a public UI so marketplaces and collectors can inspect override state on multiple chains
  • Key claims:
    • The official README is clear about the job: backwards compatibility for older collections plus one common lookup surface across fragmented royalty standards. That is a narrower and more useful frame than treating it like an enforcement system.
    • RoyaltyRegistry.sol makes the real control point obvious. The important action is changing the lookup pointer with setRoyaltyLookupAddress, so practical power sits with whoever can repoint that address.
    • The permission model is opinionated rather than neutral. The registry recognizes several admin patterns, including Ownable, AccessControl, Manifold AdminControl, and some project-specific admin paths, which means governance recognition is part of the mechanism.
    • RoyaltyEngineV1.sol does more than pass through EIP-2981. It normalizes several royalty formats and fallback patterns, which is why marketplaces can query one surface instead of carrying the whole compatibility mess themselves.
    • The note matters as the clean baseline before the ecosystem moved toward transfer validators, authorizer zones, and marketplace-specific enforcement. Discovery is its lane; transfer control is not.
  • Whitepaper: No canonical standalone whitepaper surfaced in this pass. The strongest primary materials were the official README, Manifold documentation, the original launch post, and the RoyaltyRegistry.sol / RoyaltyEngineV1.sol contracts collected in ../../whitepapers/royalty-registry-primary-sources-2026-05-11.md.
  • Sources:

Internal linkages

Graph View

Backlinks