# Private transaction submission: hiding an order from which audience?

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.

Evidence: [Flashbots Protect overview](https://docs.flashbots.net/flashbots-protect/overview); [Maximal extractable value](https://ethereum.org/en/developers/docs/mev/)

Canonical: https://degreesofsatoshi.com/encyclopedia/private-transaction-submission/
Published: 2026-10-02
Substantively modified: 2026-10-02
Independently verified by an automated reviewer: 2026-10-02T18:15:18.493Z
Data current through: 2026-10-02

AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied.

## Key facts

- **Example:** Flashbots Protect describes a private submission path with configurable settings. ([Flashbots Protect overview](https://docs.flashbots.net/flashbots-protect/overview))
- **Visibility:** Avoiding public broadcast does not mean no intermediary sees the transaction. ([Flashbots Protect overview](https://docs.flashbots.net/flashbots-protect/overview))
- **Scope:** MEV includes more than one attack or extraction mechanism. ([Maximal extractable value](https://ethereum.org/en/developers/docs/mev/))

## 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.

Evidence: [Flashbots Protect overview](https://docs.flashbots.net/flashbots-protect/overview)

## 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.

Evidence: [Flashbots Protect overview](https://docs.flashbots.net/flashbots-protect/overview); [Ethereum transactions](https://ethereum.org/en/developers/docs/transactions/)

## 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.

Evidence: [Ethereum transactions](https://ethereum.org/en/developers/docs/transactions/); [Flashbots Protect overview](https://docs.flashbots.net/flashbots-protect/overview)

## Questions

### 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.

Evidence: [Ethereum transactions](https://ethereum.org/en/developers/docs/transactions/); [Flashbots Protect overview](https://docs.flashbots.net/flashbots-protect/overview)

## Claims and scope

### private-transaction-submission-quick-answer

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: {"collection":"defi","dataAsOf":"2026-10-02","blockHeight":null}

### private-transaction-submission-fact-example

Example: Flashbots Protect describes a private submission path with configurable settings.

Scope: {"collection":"defi","dataAsOf":"2026-10-02","blockHeight":null}

### private-transaction-submission-fact-visibility

Visibility: Avoiding public broadcast does not mean no intermediary sees the transaction.

Scope: {"collection":"defi","dataAsOf":"2026-10-02","blockHeight":null}

### private-transaction-submission-fact-scope

Scope: MEV includes more than one attack or extraction mechanism.

Scope: {"collection":"defi","dataAsOf":"2026-10-02","blockHeight":null}

## Sources

- [Flashbots Protect overview](https://docs.flashbots.net/flashbots-protect/overview) — Flashbots. 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.401Z.
- [Maximal extractable value](https://ethereum.org/en/developers/docs/mev/) — ethereum.org contributors. Ordering-dependent extraction and limits of private submission. Locator: Sandwich trading; MEV protection. Retrieved: 2026-10-02T17:03:45.625Z.
- [Ethereum transactions](https://ethereum.org/en/developers/docs/transactions/) — ethereum.org contributors. Signed transaction fields, nonces, propagation, inclusion and transaction types. Locator: The transaction lifecycle; Typed transaction envelope. Retrieved: 2026-10-02T17:03:41.854Z.

## Revision history

- 2026-10-02: First publication after primary-source research and independent automated verification.

## Cite this entry

Degrees 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/