SUAVE: Research, Evidence and Execution Boundaries
SUAVE is a Flashbots research initiative for programmable MEV applications and confidential execution. Its proposal, protocol specifications and experimental client are different kinds of evidence. They do not establish a released FRB integration, a working production endpoint or measured trading results. This guide explains what to verify before treating a research design as an execution workflow.
Research design is not release evidence
The official specifications repository was archived on May 12, 2025; its README describes an alpha protocol. The client README describes work in progress. These are source-specific observations, not a claim that every related project or endpoint has stopped. Check current release artifacts and operating conditions independently.
What each source can tell you
| Source or product | Evidence it provides | What it does not establish |
|---|---|---|
| SUAVE proposal | Flashbots’ motivation and architectural direction | Production readiness, a release date or a shipped FRB feature |
| Specifications and client | Protocol concepts and experimental implementation references | A supported endpoint, service terms or reproducible latency/inclusion measurements |
| FRB release documentation | Published Windows software scope and release verification details | SUAVE support merely because this guide discusses SUAVE |
Developer verification checklist
Establish provenance
Record the repository, release or commit, documentation date, network and client version. Distinguish historical specifications from an active implementation.
Review trust and permissions
Identify who receives transaction data, who executes it and what permissions are requested. Confidential-computation design does not remove the need to inspect implementation assumptions.
Use an isolated test environment
Confirm prerequisites and testnet or devnet configuration. Do not reuse production secrets in examples or infer readiness from a demo.
Verify the whole execution path
Distinguish simulation output, submission acknowledgement and the final on-chain result. Publish a measurement only with its method, sample and limits.
Where FRB fits
FRB is a non-custodial Windows execution assistant with local signing keys, simulation-first review and supported private-bundle workflows. This page does not claim shipped SUAVE integration. Verify the installed build and current documentation before relying on a particular network, provider or route.
Primary sources and limits
Sources checked:
Frequently asked questions
Is SUAVE the same as Flashbots Protect?
No. The SUAVE sources discuss programmable MEV applications and confidential execution; they are not evidence that a private-transaction RPC is a SUAVE deployment. Read the documentation for the actual service you intend to use.
Does this guide prove FRB has SUAVE integration?
No. A research article is not release evidence. Check the installed build, release notes and documented provider/network support before selecting an execution route.
Are the figures on this page benchmark results?
No benchmark, inclusion percentage or latency result is published here. Use a reproducible method and actual observations for any performance comparison.
Does an archived repository prove every SUAVE endpoint is unavailable?
No. Archival describes that repository. The current status and trust conditions of any implementation or endpoint need separate verification.