# Rabby

<figure><img src="https://268056579-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZJQypB4fk8YIsDKCl_%2Fuploads%2FDXDa55MJMhV0e7pqPPzf%2Fimage.png?alt=media&#x26;token=750ae9c7-9d52-45b4-b38d-d2ecbdcb99e9" alt=""><figcaption></figcaption></figure>

Rabby wallet is a popular software wallet that comes both as a Chromium-based browser extension and also as a desktop app. You can connect your Lattice directly to Rabby without having to create a hot wallet first, so you can have just your Lattice addresses on the app just like with Frame, no need to use a hot address as 'account 1' as in MetaMask.\
\
Using Rabby with the Lattice1 is **almost the same** as using the wallet 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.

{% hint style="success" %}
This also means that whatever you can do with Rabby (this includes all chains other than Ethereum that are supported by the extension too!), **you can do with the Lattice1**.
{% endhint %}

**You can get Rabby here:**

{% embed url="<https://rabby.io/>" %}

### Rabby and Your Lattice

Rabby uses addresses **connected via your Lattice**. When you connect your Lattice to Rabby, you can select the addresses from the wallet stored on your Lattice to be imported and each will then create a **new Rabby account**.&#x20;

{% hint style="info" %}
You will only import your **addresses (public keys)** and create a communication channel between Rabby and your device, your **private keys** remain stored on the Lattice.&#x20;

This means that all transaction requests have to approved on Rabby like you're used to when using hot wallets, but then you will also have to confirm the transaction request approval **on the Lattice screen**.
{% endhint %}

<figure><img src="https://268056579-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZJQypB4fk8YIsDKCl_%2Fuploads%2FlYoxNhaqaNqcLj4YdVPd%2Fimage.png?alt=media&#x26;token=c8b693ad-e4b3-49e4-b555-6cd7ebf86140" alt=""><figcaption></figcaption></figure>