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

# Private Transfer

Private Transfer lets you send funds to any recipient without linking your wallet history to theirs. You sign once and USX.Capital handles the swap, bridge, and delivery. The recipient receives clean USX tokens with no visible connection to your address.

Everything happens at [usx.capital/transfer](https://usx.capital/transfer).

### How It Works

<figure><img src="https://3601501210-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdTt60r5om0G1pRfwMApK%2Fuploads%2F8yzUOxO2PvpZ0vdLa47h%2Fimage.png?alt=media&amp;token=60be920a-6cb0-49a0-b078-1b6871c9ecf5" alt=""><figcaption></figcaption></figure>

**What the blockchain sees:** a single encrypted cross-chain transaction payload. The link between sender and recipient is not visible on public block explorers.

**Delivery time:** under 10 minutes.

### Supported Networks and Assets

|                        | Supported                   |
| ---------------------- | --------------------------- |
| **Source chains**      | Ethereum, Base, Scroll, BNB |
| **Source assets**      | USX, USDC, ETH, USDT        |
| **Recipient receives** | USX (on Scroll)             |

### Steps

{% embed url="<https://player.vimeo.com/video/1181123383>" %}

1. Go to [usx.capital/transfer](https://usx.capital/transfer)
2. Connect your wallet
3. Select your source token and enter the recipient's wallet address
4. Sign once and the frontend automatically handles:
   * Swap (any token → USDC) via LiFi
   * Bridge to Scroll via Across
   * Mint USX 1:1 from USDC
   * Encrypted delivery through Scroll Cloak
5. The recipient receives USX in their wallet, with no visible link to your address

### Use Cases

* **Move to a clean wallet:** Transfer funds to a new wallet without linking it to your existing address or transaction history.
* **Protect trading activity:** Move profits from a DEX trade to a cold wallet or OTC desk without exposing your main address balance to on-chain analytics or "Smart Money" trackers.
* **Private batch payments:** Organizations can send payments to multiple recipients. Recipients receive their funds, but transaction amounts and sender history are not visible on public block explorers.

### Technical Details

* **Token routing and minting:** Users swap any token for USDC via LiFi. The USDC is then bridged from the source chain to Scroll via Across and minted 1:1 into USX.
* **Encrypted intent:** The user's transfer intent, i.e, amount, recipient address, and target chain is encrypted client-side before submission. On blockchain explorers, this appears only as a single encrypted cross-chain payload.
* **Delivery:** The USX backend decrypts the user's intent and sends the final USX to the recipient's address. The platform absorbs any short-window volatility risk during this process.
* **Liquidity:** USX liquidity in the Cloak contracts is manually funded on a set cycle. It is not automatically rebalanced from the treasury.

### Compliance

Private Transfer is designed to be private to the public, not to regulators. The architecture supports centralized auditing and view keys, enabling compliance with AML/CFT regulations. This is a deliberate design choice to avoid the regulatory issues associated with fully trustless mixers.

### Important Note

Although Cloak breaks the on-chain link between sender and receiver, observers may still make educated guesses by analyzing on-chain activity. For example, if a unique amount is deposited and the same amount is withdrawn shortly afterward. Avoid using round or identical amounts if this is a concern.

***

## Common Questions

**Q. What is Private Transfer?**&#x20;

A. Private Transfer lets you send USX to any recipient without creating a visible onchain link between your wallet and theirs. You sign once and then USX handles the swap, bridge, and encrypted delivery. The recipient gets clean USX with no visible connection to your address on public block explorers.

**Q. How is the sender-recipient link hidden?**&#x20;

A. Your transfer intent (amount, recipient address, and target chain) is encrypted client-side before it hits the blockchain. On the blockchain, it appears as a single encrypted cross-chain payload routed through Scroll Cloak. The USX backend then decrypts the intent and disburses from the vault, so no direct link between sender and receiver is written to a public ledger.

**Q. Is Private Transfer anonymous? What about compliance?**&#x20;

A. Private Transfer is private to the public, not to regulators. The architecture supports centralized auditing and view keys, so the platform can comply with AML/CFT obligations if required. This is a deliberate design choice, because unlike fully trustless mixers, USX avoids the legal and regulatory risks that come from having no way for regulators to review activity if required.

**Q. What tokens and chains are supported?**&#x20;

A. You can send from Ethereum, Base, Scroll, or BNB using USX, USDC, ETH, or USDT. The recipient always receives USX on Scroll. [LiFi](https://li.fi/) handles the swap and [Across](http://across.to/) handles the bridge. You don't need to manage any of the steps manually.

**Q. How long does a private transfer take, and are there any fees?**&#x20;

A. Delivery typically completes in under 10 minutes. USX **doesn't charge an additional fee** for privacy routing. Standard bridge and swap fees from LiFi and Across still apply.


---

# 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://docs.usx.capital/protocol/private-transfer.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.