Encyclopedia DeFi · Entry 163
Private transaction submission: hiding an order from which audience?
In this article
At a glance
Key facts
| Fact | Detail | Source |
|---|---|---|
| Example | Flashbots Protect describes a private submission path with configurable settings. | [1] |
| Visibility | Avoiding public broadcast does not mean no intermediary sees the transaction. | [1] |
| Scope | MEV includes more than one attack or extraction mechanism. | [2] |
Identify who receives the signed transaction
A wallet sends the transaction to a particular RPC or relay endpoint, which follows its configured submission path. That path can differ from ordinary peer-to-peer mempool propagation.
The endpoint, builder sharing and privacy settings are part of the security assumptions. “Private” without a named mechanism is incomplete.
Service policies are not consensus guarantees
Flashbots documents policies intended to avoid including reverting transactions through its service. Those are service-specific properties, not a rule that Ethereum universally refuses to charge for failed transactions.
A private transaction can also remain unincluded. Keep submission, inclusion and execution outcome separate.
A retry can change the disclosure model
If a wallet later broadcasts the same transaction publicly, its information becomes available through that path. A user should know whether fallback is automatic or explicit.
Private submission does not replace reviewing the destination, calldata, permissions and minimum output. It changes delivery, not the meaning of the signed authorization.
Direct answers
Questions people ask
Does private submission make the transaction invisible after it confirms?
No. An ordinary transaction included on a public chain remains publicly inspectable. The privacy mechanism concerns its submission and pre-inclusion exposure.
Inspect the evidence
The answer and key facts have stable claim links. These records retain the scope and qualification when reused.
Private transaction submission sends a transaction through a service or builder path instead of ordinary public-mempool broadcasting. It can reduce exposure to some frontrunning strategies, but the service and relevant downstream participants still receive information. Privacy, failure handling, inclusion and fallback behavior depend on the route used.
Scope: DeFi · data through 2026-10-02. Verification: verified · 2026-10-02T18:15:18.493Z.
Link to this claimExample: Flashbots Protect describes a private submission path with configurable settings.
Scope: DeFi · data through 2026-10-02. Verification: verified · 2026-10-02T18:15:18.493Z.
Link to this claimVisibility: Avoiding public broadcast does not mean no intermediary sees the transaction.
Scope: DeFi · data through 2026-10-02. Verification: verified · 2026-10-02T18:15:18.493Z.
Link to this claimScope: MEV includes more than one attack or extraction mechanism.
Scope: DeFi · data through 2026-10-02. Verification: verified · 2026-10-02T18:15:18.493Z.
Link to this claimRevision history
- — First publication after primary-source research and independent automated verification.
Source register
Sources and references
Retrieval dates and locators are recorded individually.- Flashbots Protect overviewFlashbots
Private submission changes who receives a transaction and depends on relay and builder behavior.
Locator: MEV protection; Privacy; How it works · Retrieved: 2026-10-02T17:03:45.401ZOpen source - Maximal extractable valueethereum.org contributors
Ordering-dependent extraction and limits of private submission.
Locator: Sandwich trading; MEV protection · Retrieved: 2026-10-02T17:03:45.625ZOpen source - Ethereum transactionsethereum.org contributors
Signed transaction fields, nonces, propagation, inclusion and transaction types.
Locator: The transaction lifecycle; Typed transaction envelope · Retrieved: 2026-10-02T17:03:41.854ZOpen source
Research and drafting use AI assistance. A separate automated review checks claims against primary sources; no external expert or named human review is implied. Publication, substantive editing, source retrieval and verification are recorded separately. This version was independently checked by an automated reviewer on 2 October 2026.
Editorial method and correctionsDegrees of Satoshi editorial project. “Private transaction submission: hiding an order from which audience?.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/private-transaction-submission/