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

# Your Wallet

A wallet of your own, bound to your account at hero level 15.

{% hint style="warning" %}
**Coming in Phase 2.** See [Phases](https://electrum-decisions.gitbook.io/electrum-decisions-docs/getting-started/phases.md).
{% endhint %}

## Your wallet

* When your hero reaches **level 15**, the game creates a **wallet** with **thirdweb** and binds it to your account and your **e-mail**.
* It is **non-custodial**: the keys belong **only to you**. Neither the studio nor thirdweb keeps them.

{% hint style="info" %}
Add your e-mail in [Settings](https://electrum-decisions.gitbook.io/electrum-decisions-docs/community/settings-and-account.md) before level 15 — the wallet is bound to it.
{% endhint %}

## Transfers happen on the website, not in the game

The game apps cannot use crypto, so the game itself has **no transfers** and no Amber purchases. Everything Amber is done in your **personal cabinet on the website**. There you find how to:

1. connect an outside wallet such as MetaMask or Trust Wallet;
2. buy POL with a card;
3. swap it for Amber on a decentralised exchange;
4. send Amber to your game wallet — and back.

{% hint style="danger" %}
**You carry the responsibility** for what you do with your wallet and your Amber outside the game. Never share your keys or your password. The game staff will never ask for them.
{% endhint %}

{% hint style="info" %}
Items, Seals and castle resources still **cannot be passed between players** — see [Seals and Resources](https://electrum-decisions.gitbook.io/electrum-decisions-docs/economy/seals-and-resources.md). Wallets are only for Amber.
{% endhint %}


---

# 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://electrum-decisions.gitbook.io/electrum-decisions-docs/amber/your-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.
