Private Crypto Swaps: What Shielding Actually Hides

Public blockchains are transparent by design, and that transparency has trade-offs. Every transfer, every counterparty, every balance sits in an open ledger that anyone can read with nothing more than an address. For auditability that is a feature. For a business whose treasury movements are visible to competitors, or an individual whose entire holdings become public the moment someone links an address to their name, it can create significant privacy concerns.

A wave of services now promises to address this, and many of them overstate what they provide. “Anonymous swaps” is often a marketing phrase rather than a precise technical description, and the gap between the two has led to users misunderstanding the protection on offer. The more useful question is narrower and more honest: what exactly gets hidden, from whom, and what stays visible regardless.

CryptoRoute has introduced private crypto swaps built on the NEAR Intents confidential relay. The notable aspect is how precisely the boundaries of the feature are defined.

Start with a standard cross-chain swap. Pull up the settlement record and it reads like an open book: the assets on both sides, the exact amount that went out, the exact amount that came in, and the market maker who filled the order. All of it, permanently, to anyone who looks. If you moved size, everyone knows you moved size. If you are a business, your counterparties and your flow are a matter of public record.

A private swap changes what that lookup returns. Instead of a readable token diff, an observer finds a shielding transfer from an opaque one-time account carrying an encrypted memo. No rate. No counter-asset. No counterparty. The trade happened, but it left no public trail describing itself.

How it works

The mechanism is straightforward once you remove the marketing language from the description.

You pick a route and get a quote as you would for any swap. According to CryptoRoute, for standard amounts no account or identity check is required. The difference is where settlement executes: instead of landing somewhere public indexers can watch, the swap runs on FAR, a permissioned private fork of NEAR operated for the NEAR Intents protocol. Balances and settlement details there are not exposed to public explorers. The output then arrives at your destination address like any other swap; the provider states that custody remains with the user throughout the flow.

The company states that the fee matches a standard CryptoRoute swap. Quotes can differ slightly, since confidential liquidity comes from a dedicated set of market makers rather than the general pool.

The part most services skip: what is not hidden

This is where clear engineering descriptions separate themselves from marketing, and it deserves stating plainly.

Your deposit on the origin chain is a normal public transaction. Your payout on the destination chain is a normal public transaction. Both remain fully visible on their respective chains, exactly as they always were. What gets shielded is the settlement in between: the amounts, the balances, the trade details on the private chain.

This is shielding from public view; it is not cryptographic anonymity. The private chain runs on a permissioned validator set, and those operators can see the transactions crossing it. Shielding from public explorers is a real and useful property, but it is categorically different from anonymity guarantees provided by cryptographic mixers or zero-knowledge designs.

Marketing that describes this class of product as “anonymous” may mislead users about the limits of the protection provided.

That precision matters more than it might seem. A user who believes they are anonymous will behave differently than a user who knows they are shielded from public explorers but visible to a permissioned operator. Presenting the former when the product provides the latter is how people can be exposed unexpectedly.

Where it fits, and where it does not

The legitimate demand here is not exotic. A company paying suppliers on-chain may not want its competitors reading its supplier list and volumes. A person receiving income to a known address may not want their annual earnings public to anyone who once obtained that address. Address transparency has real downstream consequences, including making holders visible targets. Desiring privacy similar to a bank statement is a common concern.

What shielding does not do is change your obligations. Skipping an identity check at the point of swap does not alter tax or reporting rules, which apply to these transactions as they do to other trades in the jurisdiction involved. Privacy from public surveillance and exemption from legal duties are unrelated things, and conflating them can have consequences.

It also will not protect you from operational errors. Reused addresses, poor on-ramp and off-ramp hygiene, or linking a shielded flow to an identified address on either end can undo the benefit entirely. The rail handles the settlement layer. It does not handle operational security.

Availability

The company states that private swaps are available on supported routes. On a supported route page, users can enable the “Private swap” option in the widget before confirming, and the swap is routed through the confidential rail instead of the public one. Coverage is expected to expand as confidential liquidity grows, so route support may broaden over time. According to CryptoRoute, other aspects remain unchanged: non-custodial operation, no account required, and the tracking page shows status, deposit and payout. One thing that will not be available is a public settlement trail, because there is no public settlement record for those steps.

The broader point is worth holding onto. Privacy on public chains is an engineering problem with partial solutions, and the industry would be better served by describing those solutions accurately than by selling anonymity that is not delivered. Knowing exactly what a tool hides, and exactly what it does not, is the only basis on which anyone can decide whether they need it.

---