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

# Your Sia Wallet

\
`walletd` is the Sia Foundation's standalone wallet for Siacoin (SC) and Siafunds. It can manage multiple wallets and supports Ledger hardware wallets, through either a command-line interface or a web interface.

`renterd`, `hostd`, and `indexd` each include a built-in wallet for the coins they spend. `walletd` is the separate, general-purpose wallet for holding and moving your own Siacoin, independent of those services.

`walletd` can index either just your own addresses or the entire chain, and it can hold your seed to send and receive or run watch-only — tracking addresses without access to private keys. Some of its features:

* Send, receive, and store Siacoins and Siafunds.
* Manage multiple wallets, including watch-only and Ledger hardware wallets.
* Track wallet balances and transaction history.
* Monitor the blockchain for activity on specific addresses.

{% hint style="info" %}

#### **Getting Started with `walletd`**

Start storing your Siacoins on Sia by downloading the official [`walletd` software](https://sia.tech/software/walletd) and exploring our step-by-step [Setting up walletd](/wallet/setting-up-walletd.md) guide.
{% 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://docs.sia.tech/wallet/wallet-overview.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.