Skip to main content

For Searchers

You extract MEV from the Solana validator network — sandwich, JIT, atomic arb, liquidations, expirations. You play closer to the metal than bots: you care about pre-leader transaction visibility and about timing your submissions to highest-priority lanes.

What you'll use​

Relayer/TPU

MEV mempool plus direct TPU submission. Stream pre-leader transactions to a gRPC Block Engine you operate; ship winning bundles direct to the validator TPU in the ~250ms priority window. Pay-on-profit.

~250ms TPU window · pay-on-profit

Relayer/TPU is the searcher-side counterpart to the validator product Searcher Connection — validators publish their TPU traffic; you consume it and submit bundles back through the TPU adapter.

How it works end-to-end​

Relayer  →  detect pending tx  →  build response bundle
                                              │
                                              ▼
                                    TPU adapter → land in the next leader slot

The Relayer half streams incoming transactions before they're sequenced; you identify arb opportunities or signals, then the TPU-adapter half ships your response bundle directly to the validator's TPU in the ~250ms window. You only pay if your bundle is profitable.

Searcher vs Bot stack​

A pure searcher stack (this page) reads pending transactions and times submissions to specific upcoming leaders. A bot stack (for bots) reads post-sequencing shreds to track in-flight pool state. The two are complementary; mature operators often run both.

Pricing​

Pay-on-profit on the TPU adapter; the Relayer half is application-based. Live terms in the dashboard or via support-blockspace@everstake.one.

Get started​

  1. Apply via support-blockspace@everstake.one or in the dashboard.
  2. Read the Relayer/TPU quickstart — gRPC Block Engine receive + TPU-direct bundle submit, both covered.
  3. Pair with SWQOS or ShredStream if your strategy needs them too.