Hi Flashbots team,
I operate AdValorem’s block builder (rbuilder) on Ethereum mainnet. We’re a production builder submitting to Flashbots, Titan, Aestus, and Agnostic relays. Looking to open two questions about receiving flow from Flashbots-operated services.
- MEV-Share downstream forwarding
Our understanding from docs.flashbots.net is that MEV-Share’s matchmaker forwards completed bundles to a small set of downstream builders (Flashbots’ own builder and BuilderNet operators). We’d like to request inclusion.
Questions:
- Is third-party builder inclusion in the MEV-Share downstream list an available path outside the BuilderNet consortium?
If yes, what’s the qualification process? SLA, integration test, historical performance thresholds?
If no, is BuilderNet operator status a precondition, or is the list fully Flashbots-curated?
- builder.flashbots.net / Protect private-tx routing
Some Flashbots-routed private-tx flow reaches Titan and BeaverBuild. Is that via direct-to-builder relationships that a new builder can apply for, or is it exclusively through BuilderNet consortium?
Our profile:
Builder RPC: https://builder.advalorem.io/rpc (Flashbots-compatible; eth_sendBundle, eth_sendPrivateRawTransaction)
Coinbase: 0x17D6d6658F0072A22fD80e7b896d95F0CBb6F119
Extra data: AdValorem
Uptime: 99.9%+
Relay coverage: Flashbots, Titan, Aestus, Agnostic
Bundle formats: v0.1, v0.2
Signature: honors x-flashbots-signature, tracks searcher reputation
Production timeline: currently live, running rbuilder-based fork with (fill in commit ref)
We’re aware that Flashbots deliberately curates downstream forwarding to protect matchmaker economics; happy to satisfy whatever standard applies. Open to a call if easier than async.
Thanks —
ValK