> For the complete documentation index, see [llms.txt](https://guide.mochipool.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.mochipool.com/web3-wallets/how-wallets-work.md).

# How Wallets Work

## Keys & Cryptography

As mentioned earlier, Web3 wallets don't actually store your digital assets; they rather store keys which allow you to access and manage those assets which are stored on the blockchain itself. Every wallet has a unique public key/address and a private key. The public key acts like a bank account number, while the private key acts as the password or signature that allows you to access and manage your digital assets.

{% hint style="info" %}
While it is okay to share your public key, you must ensure that your private key is kept safe.
{% endhint %}

<figure><img src="/files/cM2EXg84s6wHgKctWlX2" alt=""><figcaption><p>Public &#x26; Private Keys. Source: crypto.com/university</p></figcaption></figure>

When you want to send digital assets, you initiate a transaction from your wallet by signing it with your private key. The transaction is then broadcast to the network and validated by the consensus mechanism we discussed earlier. Once the transaction is confirmed, the digital assets are transferred to the recipient's wallet.


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://guide.mochipool.com/web3-wallets/how-wallets-work.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.