Delegating a wallet

Click the searchbar or the "Delegate assets" link on the main page to get started. It'll open up this modal window.

What if I already delegated on Registry V1?

If you already delegated using V1, that data is in the V1 contract. Over time, projects will migrate to V2 and it's important you migrate your delegation to V2 if you want it to be recognized by these newer projects. The default delegation on the portal is now V2.

You can migrate your delegation by clicking on the migration banner when you connect your wallet if you have existing V1 delegations in place.

Clicking the migrate button will populate all your V1 delegations into one V2 batch call so you can easily re-delegate in the more powerful V2 contract to ensure projects which support the latest contract will recognize the delegation.

What is the difference between Wallet, Contact, and Asset delegation?

We offer several permissioning options to customize what parts of your wallet you want to delegate. Most users delegate their entire wallet or a specific contract, but we enable more powerful granularity for those who need it.

  • Wallet: This will delegate your entire wallet, all contracts and assets within it.

  • Contract: Will only delegate a specific contract. Other contracts/assets remain undelegated.

  • Asset: Will only delegate a specific tokenId and/or amount of tokens on a specific contract. Autodetects whether a contract address is ERC20, ERC721, or ERC1155. For ERC20 you delegate an amount, for ERC721 you delegate a tokenId, for ERC1155 you delegate a tokenId and amount.

These work from a top down approach. For example, if you delegate your entire wallet, when someone checks if you have a specific contract or token delegated, it will return true.

Same thing for delegating a specific contract. When you check if a specific token is delegated, it will return true as well.

Last updated