For most of crypto’s history, the industry has focused on making transactions possible.
First it was sending assets. Then came smart contracts. Then bridges, rollups, intent systems, and increasingly sophisticated infrastructure for moving value across chains.
Each wave made crypto more usable. Assets became easier to transfer, applications became easier to build, and liquidity became easier to access.
But as the industry optimized for efficiency, scalability, and interoperability, another question received far less attention:
What information becomes visible every time a transaction takes place? As crypto evolves from a speculative asset class into a foundation for real economic activity, that question is becoming increasingly important.
Cross-Chain Swaps Got Easier. Privacy Didn’t.
Cross-chain swaps have come a long way. A few years ago, moving assets between ecosystems was often frustrating, expensive, and risky. Today, we have bridges, aggregators, intent systems, and increasingly polished user experiences. For the most part, the industry has figured out how to move value between chains.
What it hasn’t figured out is privacy.
Every swap leaves behind a trail. Not just of where funds came from and where they ended up, but of how you use crypto. Which chains you prefer, when you move assets, how often you trade, and which protocols you interact with. Over time, those activities become patterns, and those patterns become profiles.
Most people don’t think much about this because public blockchains have conditioned us to accept transparency as the default. The assumption is that if transactions are verifiable, then everything about them should be visible. But those are two different ideas.
The Real Problem Isn’t Transparency
One of the most important innovations introduced by blockchains is the ability to independently verify state. Anyone can audit transactions, verify balances, and validate that the system behaves as expected. That transparency creates trust at the network level.
The problem is that transparency at the network level often spills over into the user experience.
As crypto becomes less about speculation and more about real economic activity, that distinction starts to matter. Businesses don’t want every treasury movement exposed. Individuals don’t necessarily want their financial behavior mapped forever. Future AI agents acting on behalf of users will generate even larger amounts of transactional activity, making execution data increasingly valuable to observe and analyze.
Verifiability vs. Visibility
The question is no longer whether systems should be verifiable. The question is whether every action performed inside those systems needs to become part of a permanent public record.
This is where our thinking around privacy has gradually shifted.
Many privacy discussions focus on balances. Can someone see how much I own? Can someone identify my wallet? Those questions matter, but they don’t fully capture the problem.
Execution Reveals More Than Balances
In practice, execution often reveals far more than balances ever could.
When someone performs a swap, their goal is simple: they want one asset to become another. They don’t necessarily want the route, timing, counterparties, chain preferences, and execution details to become publicly observable in the process. Yet this is exactly how most cross-chain infrastructure works today.
The Thinking Behind Curvy Swap
If we’re building infrastructure for private and compliant transaction execution, swaps are a natural place to apply it.
But as we started thinking about the product, we found ourselves asking a different question. Why does almost every swap begin by asking users to connect a wallet?
In most cases, the user hasn’t even defined what they’re trying to do yet. The first interaction is immediately technical: connect a wallet, approve permissions, switch networks, sign transactions, and only then begin the actual process.
We wanted to explore a different approach.
Start With Intent, Not Wallets
With Curvy Swap, the process starts with intent. Users choose what they’re sending, what they want to receive, and where the funds should ultimately arrive. Once those details are known, Curvy generates a one-time deposit address for the transaction.
The user deposits funds, and everything else happens in the background.
Routing. Shielding. Swapping. Delivery.
The objective isn’t to remove complexity from the system. The objective is to remove complexity from the user experience.
Users shouldn’t need to understand privacy sets, aggregation mechanisms, bridge routes, or zero-knowledge proofs. They should simply be able to define an outcome and let the infrastructure handle the work required to get there.
That’s the experience we wanted to build.
What Actually Happens During a Curvy Swap?
The flow is intentionally simple.
A user selects the asset they’re sending, the asset they want to receive, and the destination address where the funds should ultimately arrive. Based on those inputs, Curvy generates a one-time deposit address.
Step 1: Deposit
Once funds are deposited, the transaction moves through several stages behind the scenes.
First comes the deposit. Funds enter Curvy’s privacy infrastructure and are committed into the shared privacy set.
Step 2: Shielding
Next comes shielding. At this stage, the relationship between the deposit and the eventual destination is separated from the public execution path.
Step 3: Validation
A zero-knowledge proof is then used to validate the transaction without revealing a direct source-to-destination link.
Step 4: Routing and Swapping
Once the transaction has been validated, Curvy performs the required routing and swap operations. Depending on the assets and chains involved, this may involve bridging, asset conversion, or multiple execution steps happening behind the scenes.
Step 5: Delivery
Finally, the assets are delivered to the destination address specified at the beginning of the process.
The User Experience
From the user’s perspective, the flow looks like this:
- Select the asset you’re sending.
- Select the asset you want to receive.
- Enter the destination address.
- Deposit funds to the generated address.
- Receive the swapped assets.
The complexity still exists. It simply lives inside the infrastructure rather than inside the user experience.
Privacy Should Be Part of the Infrastructure
Over the years, privacy has often been treated as a separate category of product. Something users need to consciously seek out, configure, and manage themselves. In practice, that approach rarely scales beyond a relatively small group of highly motivated users.
We think privacy works better when it becomes part of the infrastructure itself.
Not a special mode. Not a separate application. Not an advanced setting hidden behind additional complexity.
Just a property of how transactions are executed.
What Comes Next?
Curvy Swap is one example of what that looks like in practice. The more interesting question is what comes next.
Beyond Swaps
Swaps are only one type of transaction. The same execution challenges increasingly appear in payments, treasury operations, business workflows, and eventually agent-driven financial systems.
Privacy as Infrastructure
As more economic activity becomes automated, privacy can no longer be treated as an optional feature sitting on top of the stack.
It becomes part of the stack itself.
Curvy Swap Is Live
Curvy Swap is now live: https://swap.curvy.box