> For the complete documentation index, see [llms.txt](https://privacyoncoil.gitbook.io/coil-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://privacyoncoil.gitbook.io/coil-docs/using-coil/shielding-assets.md).

# Shielding Assets

Moving assets from a public wallet into Coil's private balance system.

Shielding is the process of moving assets from a public wallet into Coil's private balance system.

A shielding transaction begins on the public blockchain. The sending address, asset and amount are therefore observable at this boundary. Shielding does not erase the original transaction or make the public wallet's earlier history disappear.

The protocol records commitments representing the shielded assets. These commitments allow subsequent activity to be verified without publishing the underlying private information in the same form.

### How to shield

1. Select the correct blockchain in a compatible wallet.
2. Select a supported asset.
3. Review the amount and any required token approval.
4. Review the estimated transaction costs.
5. Submit the shielding transaction.
6. Wait for confirmation and wallet synchronization.
7. Check whether any additional spendability conditions apply.

**Note:** Asset support should always be confirmed in the wallet being used. A protocol's underlying capabilities and a particular application's available features are not necessarily identical.


---

# 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://privacyoncoil.gitbook.io/coil-docs/using-coil/shielding-assets.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.