MetaMask
Last updated
Last updated
The MetaMask browser extension is the most popular crypto app today - and we're proud to have become the third hardware wallet manufacturer whose devices can be connected to the extension via a direct integration.
Using MetaMask with the Lattice1 is almost the same as using the app without a hardware wallet - but when you connect your hardware to the extension, all transaction requests will now have to be signed on the Lattice1 and you will get to approve all of them on the device screen.
This also means that whatever you can do with MetaMask (this includes all chains other than Ethereum that are supported by the extension too!), you can do with the Lattice1.
MetaMask uses what they call Accounts - each account is basically an interface from which you control a single EVM address (public key). When you connect your Lattice to MetaMask, you can select the addresses from the wallet stored on your Lattice to be imported and each will then create a new MetaMask account with a Lattice1 tag next to it.
What's important to note is that each address that would create a account on MetaMask can only be added to the extension once and after a standalone account is created from it, you won't be able to add the address again via any means (such as importing it from its private key).
Signing transactions is done in a similar way you're used to with MetaMask hot wallets - you will approve the transaction on MetaMask - but, unlike with a hot wallet, you will then also have to approve the transaction directly on the Lattice screen for it to go through (this is because your private keys are on the Lattice and not stored on MetaMask as it is with hot wallets).
When you connect your Lattice to MetaMask, your private keys remain safely stored on the hardware wallet, which means signing transactions will require approval on both MetaMask and then the Lattice screen.
