> For the complete documentation index, see [llms.txt](https://docs.gridplus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gridplus.io/apps-and-integrations/mycrypto/connecting-to-mycrypto.md).

# Connecting to MyCrypto

If you'd like to try **MyCrypto** out and see all the features the dashboard app has to offer, connecting your Lattice to it is very easy and will take just a minute or two.

### Step-By-Step Guide

1. In the MyCrypto app, go to the **Add** tab on the left or [**this link**](https://app.mycrypto.com/add-account/:walletId) and select **GridPlus**. On the next screen, select the chain you want to use and hit **Next.**

<figure><img src="/files/ej66G2XL1vyI3ChjjRg0" alt=""><figcaption></figcaption></figure>

2. Make sure your Lattice is online and unlocked and on the next step, simply click on **Connect to GridPlus** to initiate the pairing process.

<figure><img src="/files/tZxOqIWGKvGVJtu6lkg7" alt=""><figcaption></figcaption></figure>

3. You will be taken to the **Lattice Connector** module, where you will need to input your **device ID** and create a password. You can find your device ID as the last item on the Lattice homescreen. \
   \
   The **password** can be anything and it is saved in the permission this pairing process will create on your device. To reset the password, you can delete the MyCrypto permission from your Lattice under permission, but please note you'll then have to re-connect to the app.\
   \
   After you type both of these in, click on **Connect**.

<figure><img src="/files/pkZwod8JtB1Jr8FQ97W7" alt=""><figcaption></figcaption></figure>

4. A secret code will then be generated on your Lattice screen, which you will have to type in the Lattice Manager window in order to connect your Lattice to MyCrypto.

<figure><img src="/files/EGFxhSBkn2VFFDGQH24c" alt=""><figcaption></figcaption></figure>

5. If you type in the code correctly, your Lattice will show a successfully connected message and you will be taken back to MyCrypto to the **Select an Account** screen.\
   \
   Here you can rename the **newly connected accounts** you're importing to MyCrypto (but you can also do that later).\
   \
   If the wallet you have on the Lattice or an active SafeCard was created on a Ledger device, you will not see your balance and the addresses will be different from the ones you're used to using, this is because Ledger uses non-standard [**derivation paths**](https://docs.gridplus.io/blockchain-basics/wallets).\
   \
   In order to fix this, you will have to switch the derivation path to a custom one by clicking on **add a custom derivation path**. You can find an explanation of Ledger's derivation paths [**here**](https://blog.ledger.com/understanding-crypto-addresses-and-derivation-paths/).\
   \
   Then just click on **Add x Accounts** and you're done!

<figure><img src="/files/D3rRT5Wt19n478ju5z73" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.gridplus.io/apps-and-integrations/mycrypto/connecting-to-mycrypto.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
