# Advanced Frame Setup

Frame puts the power of customizability back into the hands of the user and makes it simple. Don't want all your signed transactions routed via Infura? Change your RPC provider, even to a self-hosted full node! Want your Lattice transactions to be routed directly from your self-hosted Lattice transaction router? Enter the URL! And more...

### Adding More Chains/Layer 2s and Changing the RPC Provider

Adding chains and L2s to Frame is a couple of clicks away. Simply open the menu with the <img src="/files/sWtbFD9gXyQ9WesnkERf" alt="" data-size="line"> button and select the chains you would like to use under **Chains**.

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

{% hint style="success" %}
Other EVM-compatible chains can be added by clicking the **Add New Chain** button which you can find by scrolling to the bottom of the chain selection page.
{% endhint %}

You can also **change the RPC provider** for each chain in this menu, just click Pylon (which is Frame's own default RPC) and select either **Local** or **Custom** and fill in the details if needed.

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

### Transaction Routing

The Lattice1, by default, routes transaction requests via **GridPlus infrastructure** in a fully secure, encrypted way. We cannot see the details of your transaction - nobody can.

However, we do offer [**an open source tool**](https://docs.gridplus.io/lattice1-guides/connect-your-lattice-to-your-own-private-endpoint) that anyone can run that will route your tx requests locally. To use that tool to route your tx requests, you'll need to tell Frame how to route them.

**Here's how:** open the **Settings** menu by clicking on the menu button icon <img src="/files/pwtnvLKJqZBRVNTTK7GB" alt="" data-size="line"> and scroll down to **Lattice Relay** and switch it to your custom relay URL.

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

### Adding Custom Tokens

Frame will auto detect most ERC-20 tokens on its own, however - if you hold some nascent or unknown tokens, you can add them simply by clicking **More** at the bottom of your token list, then clicking **Add Token** and then filling in the relevant details for your custom tokens.

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

### Using Multiple Hardware Signers

{% hint style="info" %}
Let's say you have the same seed backed up on multiple hardware wallets - it's easy to switch between them and continue using your connected accounts without having to re-connect your hardware wallets!
{% endhint %}

Just go through the connection process you can starts in **Accounts→Add New Account** and select your addresses when you're done. If you're adding a Ledger wallet, make sure to have the correct deriv path for Ledger selected in Settings.

### Other Customizations

Frame is a powerful wallet with many more features - this list was just a short overview. Check out the other options in the **Settings menu**!

{% hint style="info" %}
If you have any specific questions, you can reach out to the [**Frame team**](https://discord.com/invite/UH7NGqY) on **Discord**.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.gridplus.io/apps-and-integrations/frame/advanced-frame-setup.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.