# Naming Conventions

## **SaveToken Names**

The SaveToken protocol makes it easy to create a SaveToken that wraps any interest-bearing **asset token** with any **insurance** **token** by depositing any given **underlying token** (e.g., DAI, USDC, USDT, etc).

The SaveToken protocol is meant to be as flexible as possible. Naming conventions are meant to highlight the different variations of SaveTokens including their asset and insurance token pairings as well as the insurance coverage expiration dates.

The convention is as follows:

{ **Save**UnderlyingToken }*{* Asset Token Protocol *}*{ Insurance Token Protocol }\_ { Coverage Expiration Date }

In the example `SaveDAI` SaveToken below:

* `DAI` is the underlying token deposited to mint SaveDAI
* Aave is the asset token protocol used to obtain the interest-bearing `aDAI` asset
* Cover is the insurance token protocol used to obtain `CLAIM` tokens and protect the underlying `aDAI` asset
* The coverage from the `CLAIM` tokens expires on September 1st, 2022.

| SaveToken                                   | Underlying | Interest-Bearing Token | Insurance Token |
| ------------------------------------------- | ---------- | ---------------------- | --------------- |
| SaveDAI\_Aave\_Cover\_Expires\_1\_Sep\_2022 | DAI        | aDAI                   | CLAIM           |

## **SaveToken Symbols**

Similarly, the convention used for SaveToken symbols is as follows:

{ **Save**UnderlyingToken }\_{ Coverage Expiration Date }

In the example `SaveDAI` SaveToken:

| SaveToken                                   | Symbol           |
| ------------------------------------------- | ---------------- |
| SaveDAI\_Aave\_Cover\_Expires\_1\_Sep\_2022 | SaveDAI\_SEP2022 |


---

# 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.savedai.xyz/savetoken/naming-conventions.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.