# Token & Network Basics

ELLIPAL supports 40+ blockchains and 10,000+ tokens, including BTC, ETH, SOL, USDT, USDC, and many others.

### Key Concepts

#### Native Coin vs Token vs Network

| Term        | Definition                                           | Examples                                   | Responsibility for Fees                  |
| ----------- | ---------------------------------------------------- | ------------------------------------------ | ---------------------------------------- |
| Native Coin | The main cryptocurrency of a blockchain              | BTC, ETH, SOL, BNB, ADA, XRP               | Pays transaction fees on its own network |
| Token       | Digital asset built on top of an existing blockchain | USDT, USDC, UNI, LINK                      | Paid using the network’s native coin     |
| Network     | The specific blockchain where the asset exists       | Ethereum, Tron, BNB Chain, Solana, Polygon | -                                        |

{% hint style="warning" %}
The same token can exist on multiple networks, such as USDT on Ethereum, Tron, BNB Chain, and Polygon. Always make sure you are using the correct network.
{% endhint %}

### Network-Specific Features

#### Bitcoin (BTC)

Bitcoin supports multiple address formats:

* `bc1q…` — Native SegWit, recommended, lowest fees
* `3…` — Nested SegWit
* `1…` — Legacy

ELLIPAL shows the most modern format by default.

***

#### EVM-Compatible Networks

EVM-compatible networks include Ethereum, BNB Chain, Polygon, Base, and many others.

These networks support ERC-20, BEP-20, and similar tokens.

Transactions require Gas paid in the network’s native coin, such as:

* ETH on Ethereum
* BNB on BNB Chain
* POL on Polygon

Gas Limit for standard token transfers is usually around `150,000`.

***

#### XRP Ledger (XRPL)

XRP addresses start with `r`.

ELLIPAL supports:

* BIP44 format — recommended
* Legacy format

Adding most XRP tokens requires creating a Trust Line on-chain. This action consumes a small amount of XRP.

XRP accounts require a minimum reserve of approximately `1 XRP`.

***

#### Stellar (XLM)

XLM accounts require a minimum reserve of approximately `1 XLM`.

***

#### Cardano (ADA)

Cardano has two main address formats:

* `addr1…` — Shelley format, current standard, supports staking
* `Ddz…` / `Ae2…` — Byron format, older format, does not support staking

***

#### XDC Network

XDC has two address formats:

* `xdc…` — Native format, recommended by ELLIPAL
* `0x…` — EVM-compatible format

You can manually convert the format by replacing the prefix when needed.

Example:

`xdc...` can be changed to `0x...`

{% hint style="warning" %}
**Note:** Only change the prefix for XDC addresses when a platform requires a different format.
{% endhint %}

***

### Memo / Destination Tag

Some networks, especially XRP and XLM, use a Memo or Destination Tag to identify the recipient when multiple users share the same address.

This is mainly required by exchanges. Personal wallet-to-wallet transfers usually do not need a Memo.

***

### FAQ

<details>

<summary><strong>Why do I need ETH to send USDT on Ethereum?</strong></summary>

USDT on Ethereum is a token. All transactions on the Ethereum network require ETH to pay for gas fees.

</details>

<details>

<summary><strong>Why can’t I send all my XRP or XLM?</strong></summary>

XRP and XLM require a minimum reserve balance to keep the account active.

The reserve is approximately:

* `1 XRP` for XRP
* `1 XLM` for XLM

</details>

<details>

<summary><strong>Why does adding an XRP token trigger a transaction?</strong></summary>

Adding a token creates a Trust Line on the XRP Ledger. This is an on-chain operation and requires a small fee.

</details>

<details>

<summary><strong>What is the difference between a Native Coin and a Token?</strong></summary>

Native coins have their own blockchain. Tokens are built on existing blockchains and depend on the native coin of that network to pay transaction fees.

</details>


---

# 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://support.ellipal.com/docs/features-and-advanced-usage/token-and-network-basics.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.