Linking Digital Assets

In the Immutable zkEVM ecosystem, linking digital assets (ERC20, ERC721, ERC1155) is essential for their authenticity, administration, and security. This process enables Immutable to verify the legitimacy of each asset, ensuring they originate from recognized sources.

This guide provides a detailed, step-by-step process for linking your digital assets through Immutable's Hub.

Sections

• Why link my assets?
• How do I link my assets?
• What about custom contracts?

---

Why link my assets?

Linking digital assets allows Immutable to associate the owner of the asset(s) with an acknowledged company or an organisation. This is important because linking allows Immutable to safeguard your digital assets against engagements of fraudulent and/or unauthorised actors.

Immutable protects your linked digital assets through a process called assets verification. This prevents the likelihood of unverified creators to imitate your digital assets.

On top of that, Linking also manages off chain authorization for all actions provided by our Immutable API and Immutable SDK suite. One example would be the metadata refresh.

How do I link my assets?

note

Assets deployed by using the Immutable Hub's contract deployment feature are linked automatically to your account, so there is no need to perform this process manually.

1. After deploying a contract, obtain the asset's contract address. It should look like this: 0xec1852d1ecaa54bfa96c50c43990e210edf09288
2. Verify you contracts source code on Immutables Explorer. Only verified contracts can be linked to Immutable Hub environments. (Immutable Hub will automatically verify your contracts when deploying from Hub).
3. Visit Immutable Hub and select your requisite project and environment. Then, go to the Tokens menu for ERC20 assets or the Collections menu for ERC721 assets on the left-hand sidebar.
4. Click Link Collection and/or Link Token Button:
5. Follow the instructions provided in the modal drawer. After signing a few steps, you should be done!

What about custom contracts?

For custom contracts, you must ensure that your contract is compatible with Immutable's linking process.

💡MANDATORY COMPLIANCE

To make sure that creators receive their hard earned loyalties, Immutable requires that all collections of ERC-721/1155s deployed on Immutable zkEVM implement the Operator Allowlist. Not implementing will have these effects for your collection (i.e. ERC-721/1155s):

1. You may forfeit any token grants you may have received.
2. Passport users will receive a warnings that your collection is likely to be counterfeit.
3. Your collection will not appear on any of the 3rd party marketplaces in our ecosystem.

For more information on the Operator Allowlist, please see this guide.

Custom collections

In order to link a custom collection, ensure that your contract implements one of the following functions:

1. OpenZeppelin's Ownership and Ownable
2. OpenZeppelin's Roles as specified by the specification here.

Custom tokens

For token contracts, these implementations are optional. If your contract doesn't implement OpenZeppelin's Ownable or RBAC methods, Immutable will query the block explorer to verify that the contract was deployed by the wallet linking the token.