ERC-7548 An NFT-based open IP protocol (Open IP Protocol built on NFTs)

Draft · NFTs & multi-token · created 2023-10-31

A standard that mixes multiple NFTs as components to create a new derivative NFT (a combo) and records the relationship between the original and the derivative work on the blockchain so anyone can trace it.

Why it is needed

Under the traditional intellectual property (IP) system, registration requires long waiting periods and heavy paperwork, and licensing agreements must go through case-by-case negotiation and difficult legal language. Because content is created far faster than registration procedures can keep up, much digital content ends up unprotected, and creators find it hard to earn fair revenue even when their work spreads. NFTs are used as a means of representing creative works, but there is no standard way to obtain permission when using someone else's NFT as a component to create a new work, and no common on-chain record exists to confirm which originals a new work came from. This proposal aims to combine registration, licensing, derivative-work creation, and relationship tracking into a single protocol, built on the premise that owning an NFT means owning the IP.

What to implement

In depth

Premise: An NFT is the IP

This protocol is designed around the principle of "1 premise, 2 extensions, 1 invariant." The 1 premise is that a single NFT represents all the IP in the open IP ecosystem; holding the NFT is treated as holding the rights to that IP. Because of this premise, the whole protocol is designed as an extension protocol compatible with ERC-721. The 2 extensions refer to the diversification of licensing schemes and remix rules, and the 1 invariant refers to the fact that the IP relationship record is always public and unchangeable.

Remix module: minting combos

The remix module (IERC721X) extends ERC-721 to let multiple existing NFTs be mixed to create a new NFT. Components can be either ERC-721 or ERC-1155. A single component is represented by a Component struct, consisting of a Token (tokenAddress, tokenId) pointing to the NFT, an amount for the quantity used, and a licenseId pointing to the license used for verification. mint takes an array of components along with a hash, which represents the algorithm that mixes the components to generate the combo's metadata. Once minting completes, a ComboMinted event is emitted, and getComponents(comboId) can be used to look up which components were used.

License module: permission to use someone else's NFT

By default, users can only remix NFTs they own to create derivative works. The license module (ILicense) is the channel through which an NFT holder grants others permission to use their NFT as a remix component. verify(user, combo, components) checks, when a combo is minted, whether the minter is allowed to use the given components. The original text notes that licensing schemes can vary widely, from NFT delegation to usage-based pricing to price-discovery mechanisms like auctions or AMMs, so this module is designed to allow a variety of custom licensing schemes.

Network module: singleton relationship tracking

The network module (INFTNetIndexer) tracks all relationships between original NFTs and derivative works, following the singleton pattern. isParent(parent, child) checks whether the child was created from the parent as a component; isSibling(a, b) checks whether two NFTs share a common parent and returns the list of shared parents; getParents(token) returns all the parents used to create the given NFT. The reasoning behind the singleton design is that recording all IP relationships in the same database creates a massive IP network that other social or gaming dApps can leverage to build new user experiences.

Remix rules can differ across implementations

The original text notes that there is no fixed standard for remix rules either. Details such as whether to support ERC-1155, whether to restrict the range of NFTs that can be chosen as components, or whether component NFTs are consumed after remixing can all differ across implementations. For this reason, the remix module is designed to support custom remix rules. Regardless of which licensing scheme or remix rules are used, however, the fact that the relationship record between the original and the new IP is public and unchangeable remains constant.

Backward compatibility and proposal status

This proposal is fully backward compatible with the existing ERC-721 standard. It extends the standard by adding new functions that do not affect core functionality, and it requires ERC-165 and ERC-721. The proposal's status is Draft. Since it is still a draft proposal whose content may change, it is advisable to check the latest source text before implementing it.

Things to watch out for

Original ERC · ← ERCs