Royalty Registry Lookup-and-Enforce Tool

WHAT IT DOES

This tool enables NFT marketplaces, dApp operators, and royalty enforcement services to look up royalty information from on-chain royalty registries for any token ID and sale price. It connects to your wallet and reads the token contract address, token ID, sale price, registry contract address, registered recipients, basis points, royalty amounts, lookup history, and timestamps. The tool is read-only — it does not sign any transactions — and provides a clear breakdown of who should receive royalties and how much they should receive based on the configured registry. This is essential for marketplaces that want to enforce creator royalties at the point of sale.

HOW TO USE

1. Connect your wallet using the wallet bridge (supports MetaMask, WalletConnect, and other EVM-compatible wallets).

2. Select the target network that matches your royalty registry and token contract deployment.

3. Enter the registry contract address and click "fetch registry details" to load the registry owner and verify the contract is accessible.

4. Enter the token contract address, token ID, and sale price (in native token) you want to check.

5. Click "look up royalty info" to query the registry and retrieve the complete royalty breakdown.

6. Review the results panel which displays:

- Registry address and owner

- Token contract and token ID

- Sale price and total royalty percentage

- Detailed breakdown of each recipient with their basis points and calculated royalty amount

7. The lookup history section shows your recent queries for quick reference.

TECHNICAL MECHANISM

The tool uses ethers.js v5.7.2 to interact with any EVM-compatible royalty registry contract that implements a standard interface (owner() view, getRecipients() view, getBasisPoints() view, getTokens() view, royaltyInfo(uint256, uint256) view). The royaltyInfo function takes a token ID and sale price, and returns two arrays: recipient addresses and their corresponding royalty amounts. The tool calculates the total royalty percentage by summing all basis points and displays each recipient's share in both percentage and native token terms. The lookup is read-only and requires no gas fees from the user (only RPC node access). The tool handles all integer conversions from the contract's wei units to human-readable decimal amounts using ethers.utils.formatEther, and tracks lookup history locally for audit convenience. The registry's getTokens() function can be used to optionally filter which token contracts the registry applies to, though the tool displays all registered recipients regardless of token filtering.

WHAT IT CANNOT SEE

This tool operates purely on-chain and cannot verify off-chain royalty agreements — it does not check that recipients actually hold rights to the royalties they are claiming. It cannot validate recipient entitlement — the tool cannot confirm that recipients created the works, hold copyrights, or are otherwise entitled to the royalty streams. It cannot detect disputes — if multiple parties claim the same rights or there are unresolved royalty conflicts, the tool cannot identify or resolve them. It cannot ensure fair distribution — the tool does not verify that the basis points are appropriate or that the splits are equitable based on contribution or rights ownership. The tool also cannot verify that recipients actually hold the rights they claim to have — all registry data is accepted as configured, and the tool does not cross-reference with on-chain identity or rights registries. Users are responsible for ensuring that the registry data is accurate and legally enforceable.

PLEASE NOTE

This tool works exclusively with EVM-compatible blockchain networks (Ethereum, Polygon, Arbitrum, Optimism, Base, etc.). It is read-only and requires no transaction fees from the user — only RPC node access is needed. The tool maintains no persistent storage — all state is refreshed from the blockchain on each session. For production use, ensure your registry contract implements the standard interface described above and that the registry data has been verified through appropriate on-chain or off-chain validation processes. Always verify that the registry address is correct and that the registry owner is a trusted party before relying on the lookup results for business operations.