finds.dev

flashbots/web3-flashbots

Web3.py plugin for using Flashbots' bundle APIs

View on GitHubHomepage ↗

★ 430PythonMITupdated Jul 2024

// the take

A thin Web3.py plugin that adds a `w3.flashbots` namespace for submitting and simulating transaction bundles (`eth_sendBundle`, `eth_callBundle`) to a Flashbots relay. It's for Ethereum devs building MEV-aware tooling - searchers, arbitrage bots, anyone who needs to submit a bundle instead of a plain transaction - who are already using web3.py.

Hooks in through web3.py's native middleware system instead of wrapping or forking the library, so it composes with whatever else is already on your `w3` instance. Setup is a single `flashbot(w3, signer)` call that then exposes `sendBundle`/`callBundle` directly on the instance, matching web3.py's own API shape. The middleware auto-signs requests with the flashbots signature header, so you're not hand-rolling relay auth yourself.

No commits since mid-2024, and that's a bigger problem here than usual: Ethereum's MEV pipeline moved to mev-boost/PBS after the merge, but the README still talks about sending bundles to `mev-geth` and "miners" - pre-merge language that may not match how relays actually behave on mainnet today. CI only runs ruff lint (`.github/workflows/ruff.yml`); there's no test workflow, so nothing verifies bundle submission logic against a live or mocked relay before a release. The testnet docs are inconsistent - the README's quickstart points at the now-deprecated Goerli relay while the example command in the same file uses Holesky, with no clear statement of which is actually supported. Forks (211) are nearly half the star count (430), which usually means people are patching their own copies rather than getting fixes merged upstream.

We read the README, the directory tree and a key source file in November 2026. Nobody pays to be listed. How we judge →

// at a glance

Stars
430
Forks
211
Language
Python
License
MIT
Last commit
31 Jul 2024

// nearby

If web3-flashbots isn't quite it.

All repos →