# Creating Custom Address Tags

Address tags are a neat accessory to the [**automatic contract ABI definitions**](https://docs.gridplus.io/lattice1/how-the-lattice1-makes-transactions-readable-with-abi-decoding) as they allow your Lattice1 to **display a custom name** on the screen for any address - this address can be anything from your second wallet to a smart contract address and when you're signing a transaction, you will see the custom name under the **\[Contract]** parameter on your Lattice screen.

Let's have a look at how this works in practice - let's say you want to transfer **Dai to a friend's address**. Compare the two screenshots below.

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

{% hint style="success" %}
You can see a set of parameters about the transaction request - this is the result of the **auto ABI functions** loading as normally the transaction payload is just a long hex string.&#x20;

* **On the left**, you can clearly see the smart **contract address** being called - in the standard 0x ETH address format. You can also see the recipient's address on the bottom (under \[dst]).
* **On the right**, both the contract address and your friend's address are now displayed with a custom **address tag** which makes confirming if you're interacting with or sending to the correct address very easy.
  {% endhint %}

Using the Lattice1 with ABI function definitions and address tags really **unlocks the full potential of the device** and when you set them up, you get unrivaled security. It's practically impossible to send your funds to a malicious contract by mistake when you set them up. So, let's do that now.

### Creating and Deleting Address Tags

In the [**Lattice Manager**](https://lattice.gridplus.io), navigate to the menu on the left and select **Address Tags**. In this section, you can see the list of all saved address tags - both the contract address and the display name. Yours will be empty, but it's very easy to get started.

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

1\. First, click on **Add**.

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

2\. You can now **paste the address** you want to create a tag for and then type in the display name - we highly recommend you use [**Etherscan**](https://etherscan.io/) for exploring contracts - make sure to get the right ones!

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

3\. When you click on **Add**, you will have to **confirm** the new tag on your Lattice screen (because the tags are saved on the device).

**4. And you're done!**

5\. In case you want to delete any tags, just select the ones you want to get rid of and click on **Remove Selected.**&#x20;

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

### Exporting and Importing Address Tags

You **don't** have to create the address tags **one by one**, you can also **import them from a .csv file**.\
In order to do this your .csv file will need to have this format:

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

{% hint style="success" %}
As address tags are **deleted** when you **reset the system**, it's always good to keep a **backup file** and import all the tags into the device again after the reset in one action.
{% endhint %}

Just select the tags you want to export and click on **export**. If you then want to import the tags, click on **import**, select the file and the tags will be copied to your Lattice.

<figure><img src="/files/74llAK3jETwpbu4sxi5Q" alt=""><figcaption></figcaption></figure>


---

# 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/lattice-manager/address-tags.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.