Why Confidential EVM
Every EVM chain broadcasts your inputs. The chain that ships your transaction to a block also ships the transaction's contents to every observer in the world — the function you called, the arguments you passed, and the event log the contract emitted afterwards. That transparency is what makes public EVMs auditable. It is also what makes entire application categories impossible to build.
OXN keeps the audit trail but hides the contents. Below are the use cases that get unlocked.
Sealed-bid auctions
What breaks on public EVM. A "sealed-bid" auction on Ethereum is really a two-phase commit-reveal auction: bidders first publish keccak256(bid, salt) and only later reveal the actual bid. Three known problems: (1) bidders who don't reveal their winning bid at the end walk away with no penalty, (2) the commit hash reveals more than people think — given a small bid space, brute force is cheap, and (3) the whole design requires two on-chain transactions per bid.
What OXN enables. A single-transaction sealed bid. The bid amount lives in encrypted contract storage. Nobody — not the auctioneer, not other bidders, not a node operator — can read it before the reveal phase closes. When the reveal fires, the contract reads its own encrypted state and picks the winner. One transaction per bid, no commit hash, no reveal step.
Hidden orderbooks and MEV-resistant DEXes
What breaks on public EVM. Every limit order sitting in a public orderbook is visible to searchers who front-run it. Every AMM swap in the mempool triggers sandwich bots. MEV extracts billions per year from users on public EVM chains, and no amount of gas-policy tuning fully closes it.
What OXN enables. Orders posted with encrypted price and size. Matching happens inside the enclave against encrypted state. The clearing price and the winning matches are all a searcher sees — they cannot decompose the trade into individual orders to sandwich. A public settlement layer with a private matching engine, in the same contract.
Enterprise workflows and B2B settlement
What breaks on public EVM. A supplier invoicing $1.2M into a smart contract is telling every competitor, every counterparty, and every future negotiator the exact price paid. Enterprises that want blockchain auditability but cannot legally or commercially expose their numbers end up on private chains, losing the network effect.
What OXN enables. Invoice amounts, purchase orders, and settlement events stored encrypted. Auditors with the right key see everything. Everyone else sees that a transaction happened, between which addresses, and whether it succeeded — but not the amount or line items. Public chain, private data.
Voting and governance
What breaks on public EVM. When ballots are public, they can be bought. When ballots are pseudonymous but observable, they can be traced. Almost every on-chain governance vote today is effectively a public roll call, which distorts the tally by inviting coercion, bribery, and social pressure.
What OXN enables. Individual ballots encrypted per voter. Tallying happens inside the enclave against encrypted votes. The result — how many yes, how many no — is public, but individual ballots stay sealed. Combines the public accountability of the tally with the private conscience of the vote.
On-chain secrets, credentials, and off-chain identity
What breaks on public EVM. You cannot put a password on a public blockchain. You cannot put an API key. You cannot put a private key that a smart contract signs with, because the contract's storage is fully readable. Every "on-chain identity" scheme today ends up as a set of public commitments plus off-chain signature verification, because the actual secrets must live off-chain.
What OXN enables. Secrets that live inside contract storage, encrypted, usable only by the contract's own logic. A contract can hold an off-chain signing key, sign requests on behalf of authorized callers, and enforce access control — all without ever exposing the key. Real on-chain identity, not just on-chain proof of off-chain identity.
Games with hidden information
What breaks on public EVM. A poker contract cannot deal cards. A strategy game cannot fog of war. Anything with private per-player state has to lift the state off-chain, which defeats the point of running the game on-chain.
What OXN enables. Private per-player state stored encrypted in the contract, revealed only when the game logic dictates. Card games, strategy games, hidden-info auctions, blind draws — all become natural on-chain state machines.
What OXN does not try to do
Some things a chain cannot hide, regardless of technology:
- Who transacted with whom. Sender and recipient addresses are always visible — the chain has to route transactions somewhere. OXN does not obscure this. If you need transaction-graph privacy, layer a mixer on top.
- Gas paid. Gas is a public resource being consumed on public hardware. It is always visible.
- Contract bytecode. Deployed contract code is public and inspectable, exactly like on Ethereum. What is private is the state the code operates on and the inputs callers give it.
- Metadata that leaks by design. If your contract calls another contract at address
0xabc…and that other contract only handles USDC, the fact that USDC is involved is inferable regardless of encryption.
Confidentiality is a tool, not a magic wand. See Confidentiality Model for the full "what leaks" cheat sheet.