Default speed
Bundles fan out to all five builders. Reverts allowed — fastest possible inclusion for everyday trades.
Ethereum private RPC
Send transactions like nobody’s watching.
ZeroMEV wraps every Ethereum transaction as a private bundle and fans it out to five top builders. Sandwich bots get nothing. You stay protected — and earn rebates.
- 1Add the ZeroMEV RPC endpoint to your wallet.
- 2Sign and send transactions like normal — we handle the rest.
- 3Land MEV-free and collect rebates straight from builders.
5
builders fanned out per bundle
100%
private bundles — never in the public mempool
0
wallet leaks. ever.
Three flavors
Pick the endpoint that fits your trade.
Same wallet, same signing flow — three privacy / inclusion trade-offs to choose from. Click the copy button to grab the URL.
No reverts allowed
Same five-builder fanout, but the bundle dies if your transaction would revert. No wasted gas, ever.
Maximum privacy
Routed only through BuilderNet's Trusted Execution Environment. One builder. Zero leaks. Pure stealth mode.
Under the hood
Your transaction. Our sleight of hand.
The mechanics that keep MEV bots out, your wallet UI clean, and rebates flowing back to you.
-
1
Your wallet calls our RPC.
Whatever wallet you use — MetaMask, Rabby, Frame — it just sees a normal Ethereum endpoint speaking
eth_sendRawTransaction. -
2
We wrap it as a private bundle.
Your raw transaction is packaged with builder-specific payloads and a refund recipient field, then dispatched in parallel.
-
3
We submit privately, then keep trying.
Your bundle goes out for the next block. If it misses, we keep retrying privately — never touching the public mempool.
-
4
Clean fail if it never lands.
If your bundle exhausts the retry window, your wallet sees a terminal failure — no zombie pending transactions clogging the UI.
Get paid for protection
Builders rebate. We route it home.
When a builder profits from including your bundle, they refund a slice of those proceeds. ZeroMEV polls BuilderNet's refund API, tracks credits, and sends them straight to your wallet.
How do refunds work?
FAQ
Questions, answered.
Quick answers to the things people ask before adding ZeroMEV to their wallet.
What is MEV, and why should I care?
MEV ("maximum extractable value") is the profit specialized bots earn by reordering or sandwiching transactions in a block. If you're trading on Uniswap or any DEX, MEV bots can detect your transaction in the public mempool and front-run it — you get a worse price; they pocket the difference. ZeroMEV stops that by sending your transaction privately, never exposing it to the mempool.
Is ZeroMEV custodial?
Nope. Your wallet keeps your signing keys — ZeroMEV only sees signed transactions. We forward those bundles to builders. We never hold funds and we never have the ability to move them.
What happens if my transaction would revert?
It depends which endpoint you use. /fast allows reverts — your tx may land on-chain even if it fails (you still pay gas). /noreverts kills the bundle the moment a revert is detected, so you never pay gas for a failed trade. /fullprivacy behaves like /fast but stays inside the BuilderNet TEE.
How exactly do refunds work?
Builders that profit from your bundle's MEV can refund a portion of that profit to a recipient address you specify. ZeroMEV's refund poller continuously fetches refund records from BuilderNet's API and persists them. Refund credits accrue and pay out automatically — no claim flow, no extra signature.
Which networks does ZeroMEV support?
Ethereum mainnet first, with the same builder fanout pattern. The chain ID is configured per-deployment, and the RPC supports the standard MetaMask read methods (eth_getBalance, eth_call, eth_estimateGas, etc.) by proxying to a trusted upstream node.
Is ZeroMEV open source?
Yes. The forwarder is written in Rust and dual-licensed Apache-2.0 / MIT. Health and Prometheus metrics are exposed at /health and /metrics for self-hosters who want visibility into chain status, the latest block, and refund-poller liveness.