> For the complete documentation index, see [llms.txt](https://docs.tornadoeth.cash/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tornadoeth.cash/tornado-cash-nova/shielded-transfers-on-nova.md).

# Shielded transfers on Nova

Learn how to perform shielded transfers on Tornado Cash Nova for enhanced privacy and security in your transactions

One of the specificity of Tornado Cash Nova is the introduction of shielded transfers. It allows shielded transactions of deposited tokens while staying within the pool.

So far, to transfer the custody of deposited funds, tokens needed to be withdrawn first. With Nova, you will be able to transfer a chosen amount of your shielded balance (not necessarily all of it) to another address without needing to withdraw them from the pool.

<figure><img src="https://2754767501-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FW3U990Qef6L7w7eSM7Iw%2Fuploads%2FO630zrse5dPVwaUDXXHk%2F8.gif?alt=media&#x26;token=56c68aff-6c04-4b58-a94b-0c8f4b89e4a9" alt=""><figcaption><p>TORNADO CASH - NOVA</p></figcaption></figure>

These shielded transfers can be made to any address of your choice, as long as this address is shielded (i.e. already registered to Tornado Cash Nova pool).

As a reminder, a shielded address is registered either through the `Set up account` action or alongside an initial deposit from a wallet address.

We advise you to double-check the shielded address to which you transfer tokens as this action is irreversible.


---

# 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.tornadoeth.cash/tornado-cash-nova/shielded-transfers-on-nova.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.