No. The initial model is designed as a non-invasive proxy layer that routes into existing public liquidity rather than forcing a core AMM redesign.
Zero Knowledge Proof Blockchain Privacy for EVM DEXs
Enable compliant shielded trading with ZK-SNARK-based privacy, existing AMM liquidity, and selective disclosure for MiCA/AML auditability.
16+
years in software delivery
7+
years in blockchain
120+
delivered projects
EVM, Rust and ZK-snark
expertise
Architecture, consulting
and delivery ownership
Public DeFi is transparent by design. Institutional trading is not.
For larger traders, public blockchain execution creates a structural problem. Balances, positions, and trade behavior become visible on-chain. That exposes alpha, invites copy-trading, and makes serious execution harder to protect. A zero knowledge proof privacy layer can help reduce this exposure without moving liquidity away from public DEX infrastructure.
Public execution exposes alpha
Large wallets and institutional traders do not want their balances, positions, and trading patterns visible on-chain.
Anonymous privacy is not institution-ready
Classic mixers are not a viable path for regulated entities operating under AML and MiCA constraints.
DEXs lose high-value order flow
When privacy is missing, serious flow moves to OTC desks, internalized routes, or private arrangements instead of public liquidity venues.
Full private trading infrastructure is too invasive
Most protocols do not want to redesign the whole AMM or create separate shielded pools that split liquidity.
A ZK-SNARK Privacy Layer for Institutional Flow, Without Changing Your Core DEX Engine
Neti delivers a Shielded Trading Proxy that allows institutions to execute private trades through existing public DEX liquidity. The model is non-invasive: a proxy layer, frontend SDK, or API integrates with your current trading flow, while zero knowledge proof generation and selective disclosure mechanisms preserve privacy and regulatory auditability.
What Happens If Your DEX Lacks Privacy for Institutional Flow
- Larger traders keep using OTC desks or private execution paths.
- Your DEX keeps public liquidity, but misses privacy-sensitive order flow.
- Privacy remains a growth blocker instead of becoming a competitive advantage.
- Competitors with compliant blockchain privacy can become more attractive to institutional participants.
See the Zero Knowledge Proof Trading Flow in Practice
We can walk your team through the architecture, privacy model, and integration logic behind the Shielded Trading Proxy, including ZK-SNARK proof generation, relayed execution, DEX router integration, and selective disclosure.
Who it's for
- building or operating an EVM DEX
- exploring institutional or larger trader participation
- trying to protect users from public execution exposure
- looking for privacy without abandoning auditability
- evaluating privacy without redesigning the full protocol
- Avoiding deep AMM redesign or shielded liquidity fragmentation
How shielded execution works
Intent (Off-chain ZK)
User's device generates a ZK proof of intent and derives a stealth address off-chain. Keys never leave the client.
Why Zero Knowledge Proof Privacy Matters Commercially
.png&w=96&q=75){kind=small}
Attract larger traders without forcing them into public exposure
Protect trading strategies from copy-traders and MEV bots
Expand toward institutional participants without abandoning compliance
Turn blockchain privacy into a growth lever, not just a technical featur
Who Needs Zero Knowledge Proof Privacy for EVM DeFi
building or operating an EVM DEX
running an AMM or perpetual DEX on an L2
exploring institutional or larger trader participation
trying to protect users from public execution exposure
looking for privacy without abandoning auditability
avoiding deep AMM redesign or shielded liquidity fragmentation
evaluating ZK-SNARK privacy before changing your protocol architecture
Why Neti for Zero Knowledge Proof Blockchain Privacy
We design around protocol constraints, not just product requirements.
.png&w=96&q=75){kind=small}
We think in architecture, compliance, and delivery risk.
We help teams assess what can be added without destabilizing the protocol.
.webp&w=96&q=75){kind=small}
We work as a partner responsible for architecture and delivery, not isolated tasks.
We combine EVM, Rust, ZK-SNARK, and production blockchain delivery experience.
FAQs
No. The concept is specifically built to avoid separate empty shielded pools and preserve access to existing order books.
The architecture is designed around selective disclosure, allowing specific fund flows to be reviewed when needed rather than making all activity publicly visible.
Neti already has working demo-level mechanics and prior R&D/implementation work in privacy-oriented ZK infrastructure, even if some client references remain limited by NDA.
This version is designed to solve the most immediate privacy problems for larger traders and institutions using public DEX infrastructure. It focuses first on: strategy privacy balance privacy selective disclosure for specific flows stronger confidentiality for privacy-sensitive execution In practice, it is especially relevant where public execution visibility creates copy-trading risk or discourages larger participants from using public liquidity.
Not fully in the first version. The current model is strongest for privacy, reduced strategy exposure, and protection against copy-trading. Because execution still interacts with public liquidity infrastructure, it does not fully eliminate all MEV or front-running vectors. A more complete protection model would require deeper protocol-level changes in the DEX architecture and execution environment.
Exploring privacy for your DEX? Discuss your privacy architecture
We can help you assess whether shielded execution makes sense for your protocol, where the integration risk sits, and what can be delivered without breaking liquidity, composability, or compliance assumptions.