> For the complete documentation index, see [llms.txt](https://docs.clore.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.clore.ai/wallet.md).

# Wallet

CLORE is an ERC-20 token on the Ethereum network. You can store and manage your CLORE tokens using any wallet that supports Ethereum and ERC-20 tokens.

## CLORE Token Details

| Property | Value                                        |
| -------- | -------------------------------------------- |
| Network  | Ethereum (ERC-20)                            |
| Contract | `0xe60201989b8628f43dc0605f585a72bcf1f1e977` |
| Symbol   | CLORE                                        |
| Decimals | 18                                           |

## Compatible Wallets

Since CLORE is an ERC-20 token, you can use any Ethereum-compatible wallet.

### Browser Extension Wallets

| Wallet              | Description                                          | Link                                                   |
| ------------------- | ---------------------------------------------------- | ------------------------------------------------------ |
| **MetaMask**        | The most popular Web3 wallet with 30M+ monthly users | [metamask.io](https://metamask.io)                     |
| **Rabby Wallet**    | Security-focused with clear transaction previews     | [rabby.io](https://rabby.io)                           |
| **Coinbase Wallet** | Self-custody wallet by Coinbase with easy onboarding | [coinbase.com/wallet](https://www.coinbase.com/wallet) |
| **Phantom**         | Clean interface with built-in swap and NFT features  | [phantom.app](https://phantom.app)                     |
| **Frame**           | Privacy-focused desktop wallet with hardware support | [frame.sh](https://frame.sh)                           |
| **OKX Wallet**      | Multi-chain wallet supporting 80+ networks           | [okx.com/wallet](https://www.okx.com/wallet)           |
| **Rainbow**         | Beautiful wallet designed for NFT collectors         | [rainbow.me](https://rainbow.me)                       |

### Mobile Wallets

| Wallet              | Description                                             | Link                                                   |
| ------------------- | ------------------------------------------------------- | ------------------------------------------------------ |
| **MetaMask**        | Mobile version with browser extension sync              | [metamask.io](https://metamask.io/download/)           |
| **Trust Wallet**    | Multi-chain wallet supporting 100+ blockchains          | [trustwallet.com](https://trustwallet.com)             |
| **Rainbow**         | Simple interface with L2 bridging and cross-chain swaps | [rainbow.me](https://rainbow.me)                       |
| **Zerion**          | DeFi-focused with comprehensive portfolio tracking      | [zerion.io](https://zerion.io)                         |
| **Coinbase Wallet** | Mobile wallet with easy access to DeFi and NFTs         | [coinbase.com/wallet](https://www.coinbase.com/wallet) |

### Hardware Wallets (Cold Storage)

For maximum security, use a hardware wallet:

| Wallet       | Description                                                 | Link                                   |
| ------------ | ----------------------------------------------------------- | -------------------------------------- |
| **Ledger**   | CC EAL5+ certified, supports 5,500+ cryptocurrencies        | [ledger.com](https://www.ledger.com)   |
| **Trezor**   | Open-source with touchscreen interface                      | [trezor.io](https://trezor.io)         |
| **Tangem**   | Card-shaped wallet, no charging needed, 25+ year durability | [tangem.com](https://tangem.com)       |
| **SafePal**  | Air-gapped with QR code signing, backed by Binance          | [safepal.com](https://www.safepal.com) |
| **Keystone** | Air-gapped with large touchscreen, open-source firmware     | [keyst.one](https://keyst.one)         |

### Desktop Wallets

| Wallet            | Description                                       | Link                                       |
| ----------------- | ------------------------------------------------- | ------------------------------------------ |
| **Exodus**        | Multi-platform with built-in exchange and staking | [exodus.com](https://www.exodus.com)       |
| **Atomic Wallet** | Decentralized with built-in atomic swap exchange  | [atomicwallet.io](https://atomicwallet.io) |

***

## Adding CLORE to Your Wallet

### MetaMask / Browser Wallets

1. Open your wallet
2. Click **Import Token** or **Add Token**
3. Select **Custom Token**
4. Enter contract address: `0xe60201989b8628f43dc0605f585a72bcf1f1e977`
5. Symbol and decimals should auto-fill (CLORE, 18)
6. Click **Add**

### Trust Wallet / Mobile

1. Open Trust Wallet
2. Tap the toggle icon (top right)
3. Search for "CLORE" or scroll to find it
4. If not found, tap **Add Custom Token**
5. Select **Ethereum** network
6. Paste contract: `0xe60201989b8628f43dc0605f585a72bcf1f1e977`
7. Save

***

## Troubleshooting

### Token Not Showing

1. Make sure you're on the Ethereum network (not BSC or other networks)
2. Verify the contract address is correct
3. Try adding as a custom token manually
4. Refresh your wallet or restart the app

### Wrong Network

CLORE is an **Ethereum (ERC-20)** token. Make sure you're sending to an Ethereum address, not BSC, Polygon, or other networks. Sending to the wrong network may result in lost funds.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.clore.ai/wallet.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
