FLUX Book

Documentation for FLUX users and developers.

FLUX is a hosted MEV trading platform. You claim a tier, deploy your own contract, fund it, and the bot runs. Trades happen automatically, profits accumulate in your contract, and you withdraw to any chain when you want.

That is the whole product.

What you actually do

The flow is the same on every tier. You pick a tier. You claim a whitelist spot by sending crypto to a generated address. The system deploys a smart contract in your name and registers it with the bot’s execution mesh. You fund the contract with the working capital the bot trades against. You start the bot. Trades happen. You withdraw profits to any address on any chain.

The tiers differ in what the bot can do once it is running. The lower tier is a front-runner on a single chain. The middle tier adds cross-chain arbitrage, copy-trading, sandwich, liquidations, gas spoofing, and a private RPC mesh. The top tier extends the same execution into centralized exchange and traditional FX rails. Each tier up is more strategies, more chains, more markets, and a tighter execution path.

What the bot does for you. Front-running, sandwich, arbitrage, copy-trading of high-performing wallets, liquidation targeting, pre-launch sniping, cross-chain execution, and on the top tier, CEX and FX market access. The bot watches the mempool and the order books, scores opportunities, encodes them, and submits signed transactions. You do not write a strategy. You do not approve trades. You do not manage the submission path. You fund the contract and read the dashboard.

What you keep

Your funds stay in your contract. FLUX does not hold a balance for you. The withdrawal flow sends from your contract to any address you specify, on any chain you specify, regardless of which chain the contract is deployed on. The contract is yours. The keys are yours. The balance is yours to query and yours to withdraw at any time.

The platform takes a small cut of profitable trades as the operational fee. The cut is visible in the deploy step before you confirm. There is no charge on deposits, no charge on withdrawals, no charge for the bot to be idle. You only pay when the bot makes money, and the fee is taken out of the same transaction.

Who is this for

People who want a structural edge in MEV and do not want to run the infrastructure themselves.

The current users are mostly people who would otherwise be writing their own bots from scratch. They come to FLUX because running a competitive MEV setup from home takes a dedicated team and dedicated hardware. The platform replaces that with a deploy step and a dashboard. A smaller group are users who already run a bot and want a second execution path they can compare against. The strategy suite is configurable from the post-deploy dashboard if you want to tune the bot’s behavior, but the defaults are tuned by people who have been doing this longer than most.

You will get the most out of FLUX if you can read a transaction trace, understand what gas and slippage do to a profitable trade, and know what a sandwich attack looks like. You do not need to be able to write one. The bot writes them. You read the dashboard.

What FLUX is not. FLUX is not a research tool, not a data pipeline, not a backtesting framework, and not a hosted RPC service. The system exists to run trades against the strategies that ship with each tier. If you want to write your own MEV strategies and run them in production, the upstream open-source FLUX codebase is a reasonable starting point; this hosted product is the consumer version of that work.

On the execution path

The FLUX edge is in the execution path. The bot watches pending transactions on every supported chain, scores them against the enabled strategy set, encodes the profitable subset, and submits through a private RPC mesh with priority lane access. The middle tier adds a private mempool that other bots do not see. The top tier adds the same execution against centralized exchange and FX order books, with cross-market interpolation between the on-chain and off-chain books.

The platform is built on top of Reth. The data layer is the same one the open-source FLUX project uses for MEV classification. The hosted version adds the private infrastructure and the trade-execution layer on top of that classification, which is what makes the difference between a research dataset and a running bot.

Navigating This Book

• Installation: Get started with our step-by-step guide
• Running FLUX: Follow our quick-start instructions
• Under the Hood: Explore FLUX’ architecture
• MEV Identification: Dive into our mev-inspector methodologies

Licensing and Community

FLUX is developed and maintained by FluxLabs. The hosted platform is a paid product with tiered whitelist access. The underlying analyzer and classifier code is open source under Apache and MIT and welcomes contributions.

The private execution layer, the strategy set, and the cross-market routing are proprietary to FluxLabs and run inside the hosted product. Researchers and academics interested in the classification work can use the open-source codebase directly; users who want the running bot use the hosted product.