InstaSwap × DZap Is Live: Privacy Should Never Cost You Execution

InstaSwap × DZap is live, and it runs in both directions.

On-chain, nothing is ever really over. Every swap you have ever made still points back to you — sitting in a public ledger, indexed, permanent, and available to anyone who cares to look. That is the problem this integration is aimed at, and the reason two protocols decided to plug into each other rather than compete.

What DZap users get

Private swaps on DZap now settle on InstaSwap infrastructure.

That means a DZap user reaching for privacy gets our settlement layer underneath: decentralized, non-custodial, no KYC, and 66+ chains supported natively. Native is the operative word — real assets on real chains, not wrapped IOUs passing through a custodian while the trade is in flight.

Nothing about the DZap experience changes except what happens under the hood when privacy is switched on. No new account, no separate flow, no bridge to trust.

What InstaSwap users get

DZap's routing engine now powers Split Swap on InstaSwap.

Split Swap is the feature that takes a single deposit and fans it out to as many as 100 wallets, each with its own amount. It is the most execution-sensitive thing we do: every leg needs a route, and a bad route on any one of them shows up as slippage the user did not agree to.

DZap's routing engine is built for exactly that problem — finding the best path across a fragmented multi-chain liquidity landscape. Putting it behind Split Swap means better fills on every leg of a fan-out, without you changing a thing about how you use it.

Two protocols, one idea

The idea both sides signed up to is short enough to fit on a slide: privacy should never cost you execution.

This is worth stating plainly, because the usual trade-off in this space is grim. Privacy tooling has historically meant accepting worse rates, thinner liquidity, longer waits, and a much smaller set of supported assets — a tax you pay for not wanting your finances public. Plenty of people looked at that bill and decided transparency was cheaper.

That trade-off is not a law of nature. It exists because privacy layers and routing layers were built by different people solving different problems, and nobody put them in the same stack. This integration puts them in the same stack: DZap brings the execution quality, InstaSwap brings the private, non-custodial settlement, and neither side has to be sacrificed for the other.

What stays the same

Everything that matters about the custody model:

• Decentralized. No central operator standing between you and the fill.
• Non-custodial. Funds settle to the address you nominate.
• No KYC, no account. Nothing to sign up for, nothing held against your name.
• Native across 66+ chains. Real assets, real chains, no wrapped representations in the middle.

New here?

If the privacy side of this is unfamiliar, two explainers cover the mechanics: What Is a Private Swap? walks through intent-based settlement and why there is no on-chain link between what you sent and what you received, and What Is a ZK Private Swap? covers the zero-knowledge shielded route and Proof of Innocence.

Frequently asked questions

Do I need to do anything to use this?

No. Both sides of the integration are live and automatic. DZap's private swaps route to our infrastructure, and Split Swap uses DZap's routing engine, with no action required from you.

Does this change custody in any way?

No. Both protocols are non-custodial. Neither takes possession of your funds at any point in the flow.

Which chains are covered?

66+ chains natively on the InstaSwap settlement side.

Is Split Swap still private?

Yes. DZap's engine changes how each leg is routed and priced, not whether the operation settles privately.

Try it

Both sides are live now. Run a private swap or a Split Swap at app.instaswap.com, and find DZap at @dzap_io.