MEV LabsApply
BSCComing soon

Searcher infrastructure
for EVM chains.

Orderflow streams and builder-agnostic bundle submission. Submit a backrun bundle once—we fan it out to every active builder on the chain in parallel. Inclusion odds scale with the whole builder market, not a single operator.

Stream regions
global edges
Stream latency p50
design target
Fanout latency p50
submit → builders
Beta launch
TBD
Products

Stream the signal. Route the bundle.

The orderflow stream feeds searchers the targets. Bundle submission fans your backrun to every active builder on the chain so inclusion isn't bottlenecked by a single operator.

Signal source

Orderflow Stream

Beta

Low-latency stream of signal transactions for backrun strategies. Multi-region endpoints, SSE and WebSocket transport, with desensitized payloads safe for searcher consumption.

  • Multi-region edges (Tokyo, Frankfurt, NYC, Singapore)
  • Sub-20ms p50 stream latency to subscribers
  • Bundle-format signal with target hash and metadata
  • Reconnect-safe with replay window for missed frames
Execution

Bundle Submission

Beta

Submit a backrun bundle once. We fan it out to every active builder on the chain in parallel. Whichever builder wins the slot includes your bundle—you don't bet on a single block producer.

  • Builder-agnostic — routed to all active builders simultaneously
  • Atomic execution with revert protection (revertingTxHashes)
  • Bid & refund mechanics aligned to on-chain auctions
  • maxBlockNumber expiry, target-hash binding, signed envelope
Why MEV Labs

Don't bet on a single builder.

Other infra services compete to be the builder—your inclusion is capped by their block share. We sit one layer above and route your bundle to every active builder in parallel. The whole builder market works for you.

Builder-agnostic by design

Other infra services are themselves builders—your inclusion is capped by their block share. We route to every active builder on the chain in parallel, so inclusion scales with the entire builder market, not one operator.

Atomic backrun bundles

Target a signal hash and append your transactions. Bundles execute in defined order or revert as a unit—no partial fills, no orphaned approvals, no leaked intent across blocks.

Exclusive orderflow surface

Aggregated signal stream from desensitized sources, normalized into a single bundle-format feed. Originators not visible in the public mempool—an edge that disappears the moment flow goes public.

Built-in bid & refund

proxyBid-style bidding with refund handling done at the protocol layer. Searchers compete on value, not infra plumbing. Future: native builder for vertical integration when economics justify it.

Chains

Launching on BSC first.

BSC has a mature builder market—exactly where fanout meaningfully beats single-builder dependency. Submission and stream are chain-agnostic; new chains are added as integrator demand and builder coverage make the math work.

BNB Smart ChainBSC
Coming soon
Block time450ms
BuildersAll active

Closed beta launching on BSC. Fanout architecture targets every active BSC builder; integrations underway.

Want a different chain prioritized? Tell us what you need.

Pipeline

Signal to fanout in milliseconds.

Stream a signal, build a backrun, submit once—we fan it to every active builder in parallel. You focus on strategy; we handle the network.

01

Stream signals

Subscribe to the orderflow stream over SSE or WebSocket. Each frame is a desensitized bundle-format signal with the target hash and metadata you need to plan a backrun.

02

Build backrun bundle

Reference the signal hash, append your tx(s), set revertingTxHashes and maxBlockNumber. Optionally include proxyBid for the auction lane.

03

Submit once

Post to a single MEV Labs endpoint. We validate, simulate, and prepare the bundle envelope for parallel fanout—you never manage builder lists yourself.

04

Builder fanout

Bundle is dispatched to every active builder on the chain simultaneously. Whichever builder wins the slot lands your bundle. Inclusion odds scale with the whole builder market.

Coverage

The builder market, fanned out.

We don't pick winners on the builder side. The submission layer targets every active builder so your bundle has the best possible chance of landing — no matter who wins the slot.

Builder marketFanout target
BSC · all active

Every active BSC builder.

  • 01fanout
  • 02fanout
  • 03fanout
  • 04fanout
  • 05fanout
  • 06fanout
  • ··and every other active builder on chain

No allowlist. No preferred operators. Bundles fan out to every active builder simultaneously — whichever wins the slot lands your transaction.

— Apply for closed beta —

Run on every builder. At once.

Closed beta on BSC. Onboarding searcher teams, market makers, and quantitative funds first. Applications open when we launch the beta.

Applications open when beta launches · mevlabs.xyz