Base Playbook: From Demo to First Private Bundle

Checklist

• WSS latency and variance acceptable (< 150 ms median ideal).
• Router allowlists + token hygiene.
• Slippage/gas caps and session budget configured.

Steps

1. Start in simulation; confirm expected deltas.
2. Canary size 1/10th on first attempts.
3. Private bundles first; keep safe public fallback.
4. Record inclusion percent over 50–100 attempts and iterate.

Environment prep

Before touching live capital, inventory your stack. Run the FRB installer, confirm Windows updates, verify SHA-256 for the binary, and store the hash inside your internal KB. Pair one node client, label it clearly, and plug it into Ops Pulse so on-call teammates can see uptime.

Endpoint validation

• Benchmark two Base WSS providers with the FRB latency tool.
• Capture p50/p95 latency, jitter, and rejection codes for each.
• Rotate automatically if throttling persists for more than three blocks.

Simulation to canary flow

1. Capture at least 24 hours of synthetic orders.
2. Export telemetry to review profit deltas and failure reasons.
3. Promote to canary after documenting guardrails in your checklist.

Private bundle crafting

• Keep bundles compact (≤5 transactions) and reuse tested templates.
• Reserve a backup relay in case Coinbase sequencer variance spikes.
• Track gas multipliers; Base favors steady bids instead of last-minute surges.

Reporting & escalation

Document every decision in your desk notebook:

• Why you chose certain routers and liquidity tiers.
• Which budgets applied (session, per-pair, refund thresholds).
• Who approved the move from canary to production.

Share a summary with stakeholders plus links to /base-mev, Chain MEV hub, and /support so everyone knows where to look when questions arise.

Playbook timeline (example)

Keeping a living timeline helps compliance follow along without wading through raw telemetry.

Ops notes your team should standardize

• Endpoint memo: who owns each API key, rotation date, and POP.
• Guardrail summary: session cap, per-trade gas limit, refund trigger.
• Escalation tree: who to ping if refunds spike or inclusion dips below target.

Update this note weekly and paste it into the Knowledge Base so every operator sings from the same sheet.

FAQ

How long should the canary phase last?
At least 50 successful attempts or two calendar days—whichever takes longer.

Can I reuse Ethereum configs on Base?
Only after trimming gas multipliers and revalidating endpoints; treat Base as its own venue.

What if refunds spike?
Pause the route, analyze Ops Pulse, and downshift to simulation until the cause is resolved.

Do I need automated alerts?
Yes—wire FRB telemetry into your alerting stack so budget overruns, latency spikes, or guardrail hits page the on-call operator immediately.