About the integration of ZERO and MetaMask

MetaMask and ZERO work according to the same principles as the LIQUID app and ZERO: 

  • Just like in the LIQUID app, you can see an overview of your portfolio in MetaMask and you can initiate and broadcast transactions from MetaMask.
  • Your private keys always remain on ZERO. As a consequence, you will always need to sign any transaction with ZERO.

One important difference between using the LIQUID app and MetaMask is that with MetaMask you choose which coins and accounts you want to synchronize. So, contrary to the LIQUID app, MetaMask may not display your full portfolio.

What can I do with the MetaMask integration?

You can use your ZERO with the MetaMask extension and with the MetaMask app. All functionality of MetaMask is supported, from sending and receiving transactions to signing messages and smart contracts.

This includes coins and chains that are not natively supported on ZERO.
ZERO will be able to show the most common chain and coin details.

What can't be done with the MetaMask integration?

All functionality of MetaMask is supported, except for signing Typed Data (EIP712). This will be added in the next firmware release of ZERO.

Besides that, there are some limitations and general differences with the LIQUID app.

Synchronize multiple wallets

You can synchronize multiple accounts with MetaMask, but only from one wallet. If you have your main wallet synced with MetaMask and you want to additionally synchronize a passphrase wallet, you need to unsync the main wallet first.

See:

Easily verify transaction details

The LIQUID app displays your unsigned transaction QR-code together with the transaction details. This makes it easy to verify the transaction details on ZERO before signing it.

MetaMask doesn't show the transaction details, just the QR-code. This makes it more difficult to verify the transaction details. You need to make a note or remember the transaction details to verify them on your ZERO. The most important thing you want to verify that it hasn't been modified is the receiver's address.

Only EVM-based chains

MetaMask has the option to extend its functionality with 'snaps'. These are not supported in this integration. You can only use EVM-based chains; These are based on Ethereum and use the same address format, starting with '0x'.