X1 Privacy Review: Confidential XNT and USDC.x Transfers With the Amounts Hidden On-Chain

Every balance on X1 is public. Look up an address on an explorer and you can see what it holds and every amount it has ever sent. X1 Privacy changes that for two tokens. You wrap XNT or USDC.x into a confidential version, send it with the amount encrypted on-chain, and unwrap it back one for one whenever you like.

It went live on X1 mainnet on October 2, 2026. We read the whitepaper and the integration guide, used the app, and checked the reserves on-chain ourselves. This is our review.

Short version: X1 Privacy does one job and is honest about it. It hides amounts and balances, not who is paying whom. Every confidential token we checked is backed by the exact same amount in its reserve, exits are free, and nobody can freeze a balance. The main thing you are trusting is the upgrade key, and the whitepaper says so plainly. Usage is still small.

At a glance

How it works

The app is one page with three actions, and the whole flow is wrap, send, unwrap.

• Create an account. Your first step is a confidential token account. Its encryption keys come from a signature your wallet makes over a fixed message, computed in your browser and held only in memory. There is no extra seed phrase to back up: the same wallet can rebuild the keys at any time.
• Wrap. XNT goes from your wallet into the program’s reserve, and the same amount of cXNT, minus the 0.39% fee, is minted to your confidential account. For XNT the native coin is wrapped in the same transaction, so you just spend XNT from your wallet.
• Send privately. You pay the recipient’s confidential account address, or a wallet address that already has one. Your browser builds three zero-knowledge proofs: that your new balance is consistent, that the amount was encrypted correctly for both sides, and that nothing went negative. The chain checks the proofs, not the numbers.
• Unwrap. You prove your encrypted balance covers the amount, the cXNT is burned, and the same amount of XNT comes back from the reserve. No protocol fee.

Incoming payments land as a pending balance. The app folds them into your spendable balance the next time you send or unwrap, under the same wallet approval, so in practice you see one total.

None of this is new cryptography. X1 Privacy is a small program sitting on top of two things the chain already has: Token-2022 confidential balances, which store a balance as ElGamal ciphertext and update it without decrypting, and the native zero-knowledge proof program. We looked at that same machinery in August, when Jack Levin’s Project Custard demo sent a confidential transfer whose amount appeared nowhere in the transaction bytes. Custard showed it could be done. X1 Privacy turns it into something anyone can use with XNT and USDC.x.

What is private, and what is not

This is the most important section of the whitepaper, and the app repeats it on its front page: X1 Privacy gives you confidentiality of amounts, not anonymity.

So an observer can see that A paid B, but not how much, and cannot tell what either one holds. The whitepaper also points out the obvious leak: wrap a distinctive amount and unwrap the same amount soon after from a related address, and the two can be linked by amount and timing. Privacy comes from keeping funds wrapped and paying in confidential form. Each transfer uses fresh randomness, so two equal payments never produce the same ciphertext.

There is no auditor or viewing key. Nobody but the account owner can decrypt a balance, including the team. The integration guide even tells wallet builders not to describe the system as anonymous, which is the right call.

Is it fully backed? We checked

The program keeps one reserve per token and enforces one rule: the reserve must cover the confidential supply. cXNT can only be minted inside a deposit after the reserve is checked, backing only leaves after the burn is checked, and the program re-checks the reserve after every wrap and unwrap. The confidential mints have no freeze authority.

We read the accounts directly from the X1 mainnet RPC on October 15, 2026:

All three numbers match to the last unit for both tokens. The supply cap on both is set to the maximum possible value, so there is no artificial ceiling on how much can be wrapped.

Usage so far

The project publishes its own statistics page, counted from public chain history. Wrap and unwrap amounts are public by design, so they are exact. Transfers are counted, but their amounts are encrypted and the page cannot read them either.

These are early numbers. A dozen wallets and about 21 XNT wrapped is a launch, not adoption yet. Most of the wrapping so far happened on a single day in the second week of October. Wrap fees so far total 0.1533 XNT, which matches 0.39% of everything wrapped.

What you are trusting

The whitepaper has a section called “What is not permissionless today”, and it is worth reading because it names the trust point instead of hiding it.

• Using it needs no permission. Any wallet can create an account, wrap, send, receive and unwrap. Accounts are approved automatically. There is no pause instruction, no freeze and no instruction that moves or burns a user’s balance.
• The exit is unconditional. Unwrapping touches only the reserve and your own accounts and costs no protocol fee. The fee is charged on the way in precisely so that anyone paid in cXNT can always redeem it in full.
• The upgrade key is the trust point. Adding a new token, lowering a supply cap and upgrading the program are all controlled by the program’s upgrade authority. On-chain that is one address today, 9PvUEbUuZPH2eu7K3WGuwiAXa3jMHs4y8LqfWYYDjXrF. Lowering a cap can stop new wraps but never transfers or unwraps. An upgrade, though, could change the rules, and the whitepaper says so directly: users rely on that authority acting honestly until its powers are reduced. Moving it to shared control is on the roadmap.
• Security review. The team says the code went through internal review and adversarial testing, then an independent review in October 2026 of both the program and the web client. That review reported no issue that would let a third party take funds from a reserve or a user, and the client fixes it suggested are live. It covered X1 Privacy’s code, not the chain’s own token and proof programs. Further audits are planned, with reports to be published in full.
• Your keys follow your wallet. Lose the wallet and you lose the ability to decrypt and spend. A compromised device can expose keys and balances.

For builders

X1 Privacy is meant to be built on, not just used through its website. The integration guide is unusually complete: every address, the account layouts, the exact key derivation, the instruction formats, compute-unit budgets per action and a table of error codes. The IDL is served at /idl.json and live addresses at /api/state. Confidential transfers are plain Token-2022 transactions, so the X1 Privacy program is not even involved in them. No key, registration or approval is needed to integrate.

The guide asks wallets to derive the keys inside the wallet and never expose them to a page, and to read the token list from the chain rather than hard-coding it, because more tokens are coming. Native support in X1 wallets is what would move this from a website people visit to a toggle people use.

What’s next

The roadmap lists more X1 tokens, each with its own verifiable reserve; confidential swaps, trading one confidential token for another without revealing amounts, which the team says will not ship until it is safe; further audits and a public disclosure channel; reducing the upgrade authority’s powers; and native wallet integration.

Verdict

What we liked

• A clear, narrow promise, kept: amounts and balances are hidden, and the docs never pretend it is more than that.
• Fully backed, and verifiably so. We matched supply to reserve to the last unit.
• No freeze, no pause, no viewing key, and a free exit.
• No new cryptography: it uses X1’s own Token-2022 and proof programs.
• Documentation good enough for a wallet team to integrate without asking anyone.

What to watch

• The single upgrade authority, until it moves to shared control.
• Metadata: who pays whom, and wrap and unwrap amounts, stay public.
• Small usage so far: 12 wallets and about 21 XNT wrapped two weeks in.
• Two tokens only, and no confidential swaps yet.

X1 Privacy is the first tool that lets ordinary X1 users keep their balances and payment amounts to themselves, and it does that without a custodian or new cryptography. The upgrade key and the public metadata are the honest limits, and the project names both itself. If wallets build it in and confidential swaps arrive, it could become a default part of using X1 rather than a separate site.

Try it at x1privacy.xyz.