Flashbots Auction primary sources
Collected: 2026-05-11 UTC
Primary sources reviewed
- https://docs.flashbots.net/flashbots-auction/overview
- Official overview page
- Used to confirm the project’s self-description, first-price sealed-bid framing, public-mempool critique, actor model, and PoS-era relationship to mev-boost
- https://docs.flashbots.net/flashbots-auction/quick-start
- Official searcher onboarding guide
- Used to confirm the builder / relay / validator path, the dedicated authentication-key model, and the practical hosted-relay interface
- https://docs.flashbots.net/flashbots-auction/advanced/rpc-endpoint
- Official RPC reference
- Used to confirm the exact
eth_sendBundleandeth_callBundlebundle format, builder allowlists, bundle replacement / cancellation hooks, and explicit rate / size limits at the relay edge
- https://docs.flashbots.net/flashbots-auction/advanced/reputation
- Official reputation-system documentation
- Used to confirm the high- versus low-reputation queue structure and the fact that operational admission is conditioned by historical landing performance
- https://raw.githubusercontent.com/flashbots/mev-relay-js/master/README.md
- Public relay repository README
- Used to confirm the relay as a hosted service and to ground the relay’s stated anti-DoS function
- https://raw.githubusercontent.com/flashbots-sdk/ethers-provider-flashbots-bundle/master/README.md
- Public provider README
- Used to confirm payload-signing requirements, non-standard RPC methods, conditional coinbase payment patterns, and the need for a parallel standard RPC provider alongside the Flashbots relay path
Notes
- Flashbots Auction’s key mechanism is a sealed-bid private bundle market, not merely a wallet privacy toggle. It restructured MEV competition by moving ordering preference expression off the public mempool and into a relay-mediated bundle path.
- The reputation system matters because it shows that practical access to “permissionless” private order flow is conditioned by infrastructure defense policy, not only by protocol rules.
- The relay and builder layers are the core analytical control surfaces: they can see raw transactions, simulate them, impose rate limits, and decide how bundle traffic reaches validators.
- This entry belongs in the active corpus because it is a historical baseline for almost every later Ethereum order-flow or block-building design: MEV-Share, mev-boost, BuilderNet, SUAVE, and preconfirmation systems all make more sense when compared against Flashbots Auction’s private relay and sealed-bid design.