> For the complete documentation index, see [llms.txt](https://docs.nulth.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nulth.xyz/reference/nulth-and-confidential-tokens.md).

# Nulth + Confidential Tokens

Stellar's **Confidential Tokens** and Nulth solve *different* privacy problems. They compose.

## The two layers

| Layer                   | What it hides                                          | What stays visible                 |
| ----------------------- | ------------------------------------------------------ | ---------------------------------- |
| **Confidential Tokens** | balances + transfer **amounts**                        | sender / recipient addresses       |
| **Nulth**               | the **authorization policy** — caps, allowlists, rules | the payment (amount + destination) |

> **Confidential Tokens hide the amounts. Nulth hides the rules.**

A normal Nulth account hides *why* a payment was allowed but not *how much* moved. A Confidential Token hides *how much* moved but not the *rules* behind it. Put them together and you get both.

## What composition looks like

A Nulth account whose pinned asset is a Confidential Token would authorize spends the same way — a ZK proof that the payment obeys a hidden policy — while the amount itself is confidential. The result:

* **hidden amount** (Confidential Token),
* **hidden policy** — cap, allowlist (Nulth),
* **provable compliance** to an auditor (Nulth disclosure proofs),
* addresses public, as today.

That is the shape institutional settlement actually wants: confidential values, confidential controls, and selective, verifiable disclosure to a regulator.

## Status — honest

This is a **composition on the roadmap, not a shipped feature.** Nulth today pins canonical testnet USDC. Confidential Tokens are themselves a testnet developer preview. When both are mainnet-ready, pinning a Confidential Token is a configuration of the same primitive, not a redesign — Nulth's authorization model is asset-agnostic. See the [roadmap](/trust-and-security/roadmap.md).


---

# 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.nulth.xyz/reference/nulth-and-confidential-tokens.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.