Base Playbook: From Demo to First Private Bundle

Answer first — The path from zero to your first live Base bundle runs through four gates: environment verification, endpoint benchmarking, 24-hour simulation, and canary deployment at 10% allocation. Skipping any gate increases the probability of a failed first session, which usually costs more in gas and opportunity than the time saved. This playbook gives you the exact steps for each gate, with specific metrics to hit before advancing.

Mastery Path: Layer 2 Mastery

• Arbitrum MEV Latency
• Base MEV Strategies
• Optimism Playbook
• Reth RPC Mastery
• Base Playbook (Current)

Why Base Requires a Distinct Playbook

Base shares Ethereum's EVM compatibility and smart contract tooling, but its sequencer model makes MEV execution meaningfully different from Ethereum L1.

No traditional private bundle market — Base uses a Coinbase-operated sequencer that orders transactions by priority fee and arrival time, not by a competitive builder market. Flashbots-style private relays don't exist for Base in 2026. Your transaction ordering advantage comes from physical proximity to the sequencer (AWS us-east-1) and a well-calibrated priority fee bid, not from private relay submission.

Faster block production — Base targets approximately 2-second block times. The detection-to-submission window is shorter than Ethereum L1, which means your execution infrastructure needs lower latency to capture contested opportunities.

Aerodrome as the dominant venue — Aerodrome Finance (a Velodrome fork with Coinbase backing) commands the majority of Base DEX volume. Most profitable arbitrage on Base involves Aerodrome as at least one leg of the trade. Understanding Aerodrome's weekly epoch mechanics and gauge vote distribution is important context before running automated strategies.

Gate 1: Environment Verification

Before touching capital or submitting any transactions, complete this checklist.

FRB Agent installation:

• [ ] Download from the official URL at /install
• [ ] Verify SHA-256: run Get-FileHash and confirm it matches the value published on the Download page
• [ ] Verify SHA-256 hash against the hash published on the download page
• [ ] Install to %LOCALAPPDATA%\FRB (default path — avoid system paths that require elevated permissions for frequent log writes)

System prerequisites:

• [ ] Windows 10 21H2+ or Windows 11
• [ ] 16 GB RAM minimum (FRB's simulation engine is memory-intensive during peak simulation periods)
• [ ] SSD storage for log and state cache files
• [ ] Ethernet connection — Wi-Fi adds jitter that compounds across many bundle submissions per session

Ops Pulse setup:

• [ ] Create an Ops Pulse account and link it to your FRB Agent
• [ ] Configure at least one alert: gas spend > 150% of session baseline
• [ ] Confirm alerts are reaching you (test by triggering a manual alert from the FRB dashboard)

Store your completed checklist with timestamp in your internal knowledge base. This creates an audit trail for compliance and serves as a reference if the setup needs to be reproduced on a new machine.

Gate 2: Endpoint Benchmarking

Your WSS endpoint is the connection between FRB Agent and the Base chain. Its latency determines your reaction time for new transactions and your submission speed for priority fee bidding.

Minimum requirements for Base execution:

• P50 (median) latency: < 120 ms from your machine to the Base WSS endpoint
• P95 latency: < 200 ms — this is what you experience during contested windows when opportunities are active
• Jitter (standard deviation): < 20 ms — high jitter causes unpredictable reaction times

How to benchmark:

1. Open the FRB Dashboard → Tools → WSS Latency Tester
2. Add your primary endpoint URL
3. Run a 10-minute benchmark session — this captures at least 100 samples
4. Review the P50/P95 metrics and jitter value

If your endpoint fails the threshold: Try a different provider or different regional node. For Base, the provider's US-East endpoint will typically have lower latency than their European nodes for sequencer submission. Common providers with Base support: Alchemy (Base-specific tier), QuickNode (Base dedicated nodes), Infura.

Benchmark a backup endpoint before you need it. Know that if your primary endpoint starts throttling, switching to your backup takes under 60 seconds in FRB settings. Have the backup endpoint's credentials stored somewhere accessible — not only in the FRB configuration.

Document your results: Record P50/P95/jitter in your internal runbook with the date and time of the benchmark. Endpoint performance varies over time — your benchmark from today may not reflect performance three months from now.

Gate 3: 24-Hour Simulation

Simulation is the most important gate because it validates your strategy configuration against real market conditions without risking capital.

What FRB simulation does:

• Monitors the Base mempool in real time for opportunities matching your strategy configuration
• Simulates each potential trade against a local fork of current on-chain state
• Records projected PnL, gas consumption, and inclusion probability for each simulated opportunity
• Produces a 24-hour Ops Pulse report at session end

What to look for in simulation results:

Inclusion rate target: > 60% of simulated opportunities should meet the profitability threshold after accounting for your configured gas cap and slippage limits. If inclusion rate is much lower, your spread thresholds may be set too conservatively, or your gas cap is too low to compete.

Gas/profit ratio: Simulated gas cost should be < 35% of simulated gross profit per trade. If the ratio is higher, either your gas cap needs adjustment or the strategy is targeting opportunities too small for your cost structure.

Frequency: If simulation produces fewer than 5 opportunity candidates per day, either the market is quiet or your thresholds are too restrictive. Fewer than 5 candidates/day means your first live session may be long without any execution — adjust thresholds if needed.

Red flags in simulation:

• Any trade where simulated PnL is negative but inclusion threshold was passed (indicates a simulation bug or misconfigured spread calculation)
• Sudden spikes in simulated gas consumption on specific token pairs (may indicate honeypot contracts in your monitoring scope)
• Inclusion rate > 95% (usually indicates thresholds are too permissive and you'd be submitting many unprofitable live bundles)

Simulation duration: Run for at least 24 continuous hours. Base strategy profitability varies by time of day (US market hours produce more retail flow on Aerodrome; Asian sessions produce different patterns). A 24-hour window captures the full daily cycle.

Gate 4: Canary Deployment

After passing simulation, your first live deployment uses 10% of your intended allocation. This is not optional — it's how you validate that simulation results translate to real execution.

Canary configuration:

Session budget: 10% of intended allocation
Per-trade gas cap: 80% of simulated average gas cost
Refund guard: pause after 3 consecutive misses
Max concurrent strategies: 1 (your highest-confidence pair from simulation)
Copy

What to monitor during canary:

• Actual inclusion rate vs. simulated inclusion rate — target within 20% of simulation
• Actual gas consumption vs. simulated — target within 30%
• Any unexpected token pairs appearing in execution (may indicate monitoring scope is too broad)
• Ops Pulse alerts firing — if any alert triggers, pause and investigate before continuing

Canary success criteria before scaling:

• Minimum 50 execution attempts (or 48 hours elapsed, whichever comes later)
• Actual inclusion rate > 55%
• No individual trade producing a loss larger than 50% of average simulated gain
• No unexplained gas anomalies

Documentation required before advancing: Write a brief canary summary (2–3 paragraphs is sufficient) covering: what pairs you ran, inclusion rate, any unexpected behavior, and your decision to scale or pause. Store this in your internal knowledge base linked to your original checklist from Gate 1.

Scaling Beyond Canary

After a successful canary phase, scale in 25% increments with documented reviews:

Scale from 10% to 25%:

• Add the second-highest-confidence pair from simulation (if not already running)
• Increase session budget proportionally
• Keep gas cap and refund guard unchanged — these should be recalibrated based on canary data, not relaxed

Scale from 25% to 50%:

• Minimum 2 weeks of documented execution data at 25%
• Include stakeholder review if this is a team operation
• Ensure Ops Pulse monitoring covers all active pairs

Scale from 50% to full allocation:

• Minimum 4 weeks of documented execution data at 50%
• Consider whether the strategy has sufficient capacity at full allocation — some Base pairs don't have enough volume to absorb large order sizes without affecting your own execution

Reporting Templates

Daily summary (5 minutes):

• Session date and duration
• Bundles submitted / successful inclusions / refunds
• Total gas spent / total gross profit
• Any anomalies or alerts

Weekly summary (15 minutes):

• Aggregate daily stats for the week
• Endpoint performance notes (any rotations performed)
• Parameter changes made and rationale
• Comparison to simulation baseline

Monthly review (1 hour):

• Full PnL analysis vs. month-1 simulation projections
• Strategy assessment: continue, adjust, or pause
• Infrastructure cost accounting (RPC fees, VPS costs)
• Updated allocation decision for next month

Share weekly summaries with relevant team members and link them from your Chain MEV runbook so the context stays associated with the strategy configuration.

FAQ

How long should the canary phase last? At least 50 successful attempts or 48 hours, whichever takes longer. Short canaries with few data points don't give you enough signal to validate simulation results.

Can I reuse my Ethereum configuration on Base? No — gas multipliers, slippage thresholds, and fee parameters are different for Base's sequencer model. Start from scratch with Base-specific simulation rather than porting Ethereum configs.

What if refunds spike during canary? Pause the strategy immediately. Review Ops Pulse for the pattern (gas too low? slippage threshold too tight? specific pairs causing failures?). Fix the root cause in simulation before resuming. Do not simply increase the gas cap as a first response — understand why the refunds happened.

Do I need automated alerts for canary? Yes. Wire FRB telemetry into email or mobile notifications so budget overruns, latency spikes, or refund guard triggers reach you within minutes. A canary session that fails silently overnight is worse than one that alerts you immediately.

What's the minimum capital for this playbook to make sense? At canary size (10% of intended allocation), you need enough capital to cover gas costs across 50+ attempts plus enough inventory to capture meaningful arb margins on Aerodrome. Practical minimum for Base: $2,000 total allocation ($200 canary phase). Below this, gas costs per trade may consume the margin.

For a broader look at Base MEV opportunities and configuration reference, see the Base MEV Strategies guide and the Base ecosystem page.