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.
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.
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.
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.
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.
16+
years in software delivery
7+
years in blockchain
120+
delivered projects
EVM, Rust and ZK-snark
expertise
Architecture, consulting
and delivery ownership
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.

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

Enable compliant shielded trading with ZK-SNARK-based privacy, existing AMM liquidity, and selective disclosure for MiCA/AML auditability.

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.