For institutional desks on public chains, a Private Relay is the production default for orders that must reach the chain: private RPCs and direct builder submission are mature and integrate with custody. OTC / Off-chain Matching suits size-sensitive trades, with Renegade and similar dark-pool venues offering ZK-backed matching. Encrypted Mempools win where builder or venue trust is unattractive and the chain supports threshold-encrypted ordering, which on Ethereum L1 waits for an enshrined design. Private Rollups are the suitable choice when privacy across mempool, state, and execution is required and the institution accepts the rollup operator model. The hybrid is to route by trade size and venue: large blocks through OTC; mid-size through a Private Relay, or an encrypted mempool on chains that run one; flow that needs full privacy through a private rollup.
A Private Relay is the lightest engineering integration: point the submission path at a private RPC or builder endpoint. OTC / Off-chain Matching adds a venue integration and ships signed bundles. Encrypted Mempools require a threshold network on the target chain (none on Ethereum L1 yet, and Gnosis archived its Shutter docs in September 2026) and tolerating the encrypt-decrypt round trip. Private Rollups are the heaviest commit: deploy or join a privacy-native rollup, integrate with its sequencer model, and accept the bridge boundary as a liquidity surface. None of the four offers cryptographic ordering atomicity across builders or rollups; cross-domain MEV remains an open frontier for chains that have multiple block builders or sequencers competing for inclusion.
This is a perspective for legal review by the deploying desk, not legal advice. OTC venues are typically classified under existing dark-pool frameworks; whether a specific venue triggers transaction-reporting or best-execution obligations is for counsel. Encrypted mempools delay disclosure rather than erase it; whether a post-decrypt audit trail satisfies a given reporting framework is a jurisdictional question. Private Rollups raise classification questions about the operator set and the disclosure interface; enterprise rollups (Prividium, Nightfall) are typically deployed in consortium structures, but acceptance varies by regulator. Cross-border deployment surfaces the question of whether a given regulator views encrypted-mempool ordering as compatible with its market-fairness rules; the document does not claim approval in any jurisdiction.
Requirements
- Hide transaction content (order side, size, target venue) before inclusion
- Mitigate MEV extraction (front-running, sandwiching, back-running)
- Preserve transaction validity and ordering guarantees
- Maintain audit trail for compliance and post-trade reporting
- Integrate with existing custody and execution workflows
Constraints
- Public mempool is the default; opting out incurs operational complexity
- Sequencer or builder trust is the typical price of privacy at this layer
- Cross-network coordination amplifies MEV exposure unless each leg is privatized
- On Ethereum L1 no encrypted mempool is live, and FOCIL's inclusion guarantee (Hegotá) covers only the public mempool
Architectural options
Recommended
For institutional desks on public chains, default to a Private Relay for orders that must reach the chain, and Renegade-class ZK dark-pool matching for size-sensitive trades. Pair with venue-side compliance reporting and custody integration. For chains with mature threshold-encrypted mempools (none on Ethereum L1 as of October 2026), layer Encrypted Mempools as the second-line protection for orders that must reach the public chain.
Side-by-side
| Axis | Private Relay | OTC / Off-chain Matching | Encrypted Mempools | Private Rollups |
|---|---|---|---|---|
| Maturity | production | production | prototyped | prototyped |
| Context | both | i2i | both | both |
| Trust model | Relay and builders | Venue or builder | Key holders (threshold committee) | Sequencer + bridge |
| Privacy scope | Pre-inclusion content, hidden from the public only | Pre-trade content only | Pre-inclusion content, hidden from builders too | Mempool + state + execution |
| Performance | Waits for a reached builder to win a slot | Minimal latency | Key-release step; next block in LUCID | L2-internal latency |
| Operator req. | Relay / builders | Venue / builder | Threshold network | Sequencer |
| Cost class | Low | Low | Low | Low (L2-internal) |
| Regulatory fit | Strong (unchanged on-chain record) | Strong (audit via venue) | Strong (post-decrypt audit) | Strong (per-rollup view keys) |
| Failure modes | Builder front-running; low builder coverage; public fallback | Venue compromise; builder centralization | Threshold compromise; liveness; key withholding | Sequencer outage; bridge exploit; operator capture (enterprise) |
Decision factors
- If venue trust is unacceptable and the chain supports threshold-encrypted ordering, choose Encrypted Mempools.
- If comprehensive privacy across mempool, state, and execution is required and the rollup operator model is acceptable, choose Private Rollups.
- If builders may see the order, a Private Relay is enough.
- If trading must remain on a public chain and threshold-encrypted ordering is unavailable, a Private Relay and OTC matching are the options in production; both trust builders or venues with the content.
Hybrid composition
Tier the privacy stack by trade size: large blocks (>EUR 5M-equivalent) through OTC; mid-size and time-sensitive flow through a Private Relay, or an encrypted mempool on chains that run one; comprehensive privacy flows (consortium or institutional desk) on a private rollup. Bridge balances out by routing all settlement to a shielded pool boundary so cross-tier movement does not re-expose history.
Open questions
- Regulatory acceptance. How do regulators view threshold-encrypted ordering and OTC routing relative to traditional mempool transparency?
- Market impact. Effects on price discovery and market structure as private broadcasting share grows.
- Cross-chain coordination. Maintaining privacy when broadcasting across multiple networks; cross-builder MEV is unresolved.
- Timing analysis. Sophisticated adversaries may still extract information from transaction-timing patterns even under encrypted mempools.
- Builder market structure. Concentration at the builder layer creates a censorship and copy-trading risk that economic competition alone may not bound.
- Inclusion or privacy. Until inclusion lists can carry sealed transactions, a private route gives up FOCIL's inclusion guarantee. How should a sender weigh that for compliance-critical transactions such as freezes?
- Key publishers. Who may hold decryption keys for regulated flow, and how is a key holder that withholds after seeing the ordering penalised?
- Permissioned operators. On a permissioned chain the operator that sequences sees every pending transaction. Encrypted submission hides it until ordering, not after. Is that enough without application-layer confidentiality?
Referenced by
Last reviewed