A piece of Intellectual Property is represented as an 🧩 IP Asset and its associated ⚙️ IP Account, a smart contract designed to serve as the core identity for each IP. We also have various 🧱 Modules to add functionality to IP Assets, like creating derivatives of them, disputing IP, and automating revenue flow between them.

Let’s briefly introduce the layers mentioned in the above diagram:

​
🧩 IP Asset

When you want to bring an IP on-chain, you mint an ERC-721 NFT. This NFT represents ownership over your IP.

Then, you register the NFT in our protocol through the IP Asset Registry. This deploys an ⚙️ IP Account, effectively creating an “IP Asset”. The address of that contract is the identifier for the IP Asset (the ipId).

The underlying NFT can be traded/sold like any other NFT, and the new owner will own the IP Asset and all revenue associated with it.

​
⚙️ IP Account

IP Accounts are smart contracts that are tied to an IP Asset, and do two main things:

  1. Store the associated IP Asset’s data, such as the associated licenses and royalties created from the IP
  2. Facilitates the utilization of this data by various modules. For example, licensing, revenue/royalty sharing, remixing, and other critical features are made possible due to the IP Account’s programmability.

The address of the IP Account is the IP Asset’s identifier (the ipId).

​
🧱 Modules

Modules are customizable smart contracts that define and extend the functionality of IP Accounts. Modules empower developers to create functions and interactions for each IP to make IPs truly programmable.

We already have a few core modules:

  1. 📜 Licensing Module: create parent<->child relationships between IPs, enabling derivatives of IPs that are restricted by the agreements in the license terms (must give attribution, share 10% revenue, etc)
  2. 💸 Royalty Module: automate revenue flow between IPs, abiding by the negotiated revenue sharing in license terms
  3. ❌ Dispute Module: facilitates the disputing and flagging of IP
  4. 👥 Grouping Module: allows for IPs to be grouped together

​
🗂️ Registry

The various registries on our protocol function as a primary directory/storage for the global states of the protocol. Unlike IP Accounts, which manage the state of specific IPs, a registry oversees the broader states of the protocol.

​
💊 Programmable IP License (PIL)

The PIL is a real, off-chain legal contract that defines certain License Terms for how an IP Asset can be legally licensed. For example, how an IP Asset is commercialized, remixed, or attributed, and who is allowed to do that and under what conditions.

We have mapped these same terms on-chain so you can easily attach terms to your IP Asset for others to seamlessly and transparently license your IP.