IP Royalty Vault

Each IP Asset has an IP Royalty Vault, which acts as a pool for all monetary inflows related to an IP Asset’s commercial exploration or from minting licenses. Anyone who holds Royalty Tokens (defined below) has the right to claim their share of this pool.

​

Token Terminology

1. Royalty Tokens: the IP Royalty Vault contract is also the ERC-20 contract for the Royalty Tokens of each IP Asset. This means the address of the IP Royalty Vault for an IP Asset is also the ERC-20 token address of the Royalty Tokens. Each IP Asset has 100,000,000 Royalty Tokens associated, where each token represents 0.000001% of those gains. The holders of these Royalty Tokens can claim the Revenue Tokens (defined below) that are in the associated IP Royalty Vault.
2. Revenue Tokens: these are the tokens used for payment (ie. WIP). Royalty Tokens can be used to claim Revenue Tokens. Read below on whitelisting ⤵️

​

Whitelisted Revenue Tokens

An ERC-20 token must be whitelisted by our protocol in the RoyaltyModule.sol contract to be used as a Revenue Token. Here are the whitelisted tokens:

​

How to obtain Royalty Tokens?

When an IP Asset receives revenue, it is deposited into its IP Royalty Vault. In order to claim revenue from this vault, you must have the associated Royalty Tokens. Once any address owns Royalty Tokens of a given IP Asset, it is entitled to that % (% of the total supply of Royalty Tokens owned) of any future Revenue Token (that is whitelisted) received & in the IP Royalty Vault.

There are two ways that trigger the IP Royalty Vault deployment and make the initial Royalty Token distribution - whichever comes first:

1. A License Token is minted from an IP for the first time: the associated IP Account (the parent’s IP Account) receives 100% of the Royalty Tokens
2. An IP registers as a derivative: the associated IP Account (the child’s IP Account) receives 100% Royalty Tokens, and then distributes x% of it to ancestors based on the License Terms

Because Royalty Tokens are ERC-20, they can be transferred like any other token. Thus, the IP Account could send them to someone else, or even put them up for sale on the secondary market.

​

How Revenue Flows

This section will help explain how revenue flows from the time of payment to being claimed by the royalty token holder. For the purposes of explanation, we will use an example from the Liquid Absolute Percentage (LAP), but it is the same for any royalty policy.

Imagine we have a scenario where IPA4 tips IPA3 1M WIP by calling payRoyaltyOnBehalf.

1. Revenue Tokens flow to the Royalty Module contract. This contract then splits up the tokens based on the royalty stack on the receiving IPA. In this case, IPA3 has a royalty stack of 15%, so 850k tokens flow to IP Royalty Vault 3, and 150k tokens flow to the LAP contract.

2. The LAP contract separates the payment to the ancestors by calling transferToVault. In this case, IPA2 deserves 100k (10% of IPA3’s earnings) and IPA1 deserves 50k (5% of IPA3’s earnings).

3. Now that the Revenue Tokens are in the IP Royalty Vaults, the associated Royalty Token holders can claim from the vaults. Remember, the Revenue Tokens get claimed to whoever holds the Royalty Tokens. In the most common case, they are in the IP Account since that’s where they originate. To claim, you would call either claimRevenueOnBehalfByTokenBatch or claimRevenueOnBehalf.

​

External Royalty Policies

Revenue Tokens can also move from a vault to another vault via the functions claimByTokenBatchAsSelf located in the IpRoyaltyVault.sol contract. For this to be possible the vault that is claiming revenue tokens needs to own Royalty Tokens of the vault being claimed from. This can be particularly useful when used together with external royalty policies.

Vaults can only claim from other vaults if those other vaults belong to IPs in the same derivative chain. If a vault owns royalty tokens from an IP but it is not an ancestor of that IP, it is not possible to claim rewards with those royalty tokens.