# Smart-account bundlers: turning user operations into transactions

In ERC-4337, a bundler collects user operations and submits an Ethereum transaction that invokes the EntryPoint to process them. The account’s validation logic authorizes each operation. A bundler is an execution-submission participant, not a guarantee of inclusion or a replacement for the account’s signing and permission rules.

Evidence: [Account Abstraction Using Alt Mempool](https://eips.ethereum.org/EIPS/eip-4337)

Canonical: https://degreesofsatoshi.com/encyclopedia/smart-account-bundlers/
Published: 2026-10-02
Substantively modified: 2026-10-02
Independently verified by an automated reviewer: 2026-10-02T18:12:41.505Z
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

- **Object:** A user operation is distinct from the bundler’s enclosing network transaction. ([Account Abstraction Using Alt Mempool](https://eips.ethereum.org/EIPS/eip-4337))
- **Validation:** The account validates its requested operation through the EntryPoint flow. ([Account Abstraction Using Alt Mempool](https://eips.ethereum.org/EIPS/eip-4337))
- **Payment:** Accounts or paymasters must cover the operation’s applicable gas costs. ([Account Abstraction Using Alt Mempool](https://eips.ethereum.org/EIPS/eip-4337))

## Separate the user request from its carrier

A wallet constructs a user operation containing the account’s requested execution and validation data. A bundler evaluates whether it can safely include the operation and packages accepted work into a transaction.

The user-operation identifier and the enclosing transaction hash serve different tracking purposes. A wallet should expose enough information to follow actual inclusion.

Evidence: [Account Abstraction Using Alt Mempool](https://eips.ethereum.org/EIPS/eip-4337)

## Validation protects the submission process

Bundlers simulate validation and apply the specified rules to reduce the risk of submitting operations that cannot pay or cannot be processed. The rules include constraints beyond an ordinary method-call preview.

Passing a bundler’s checks does not mean the user’s requested business action is sensible or that future state cannot change. Account authorization and economic outcome remain separate.

Evidence: [Account Abstraction Using Alt Mempool](https://eips.ethereum.org/EIPS/eip-4337)

## A bundler can decline or delay an operation

Bundlers choose what to submit within their software and fee policies. Their availability and willingness affect the route from signed request to block inclusion.

Use the relevant EntryPoint version and account implementation when interpreting an operation. The standard describes the protocol flow; deployed account stacks can use different EntryPoint versions and account rules.

Evidence: [Account Abstraction Using Alt Mempool](https://eips.ethereum.org/EIPS/eip-4337)

## Questions

### Does a bundler need to know my private key?

The protocol flow uses the account’s signed or otherwise authorized operation, not disclosure of its private signing key. The account implementation determines acceptable authorization.

Evidence: [Account Abstraction Using Alt Mempool](https://eips.ethereum.org/EIPS/eip-4337)

## Claims and scope

### smart-account-bundlers-quick-answer

In ERC-4337, a bundler collects user operations and submits an Ethereum transaction that invokes the EntryPoint to process them. The account’s validation logic authorizes each operation. A bundler is an execution-submission participant, not a guarantee of inclusion or a replacement for the account’s signing and permission rules.

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

### smart-account-bundlers-fact-object

Object: A user operation is distinct from the bundler’s enclosing network transaction.

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

### smart-account-bundlers-fact-validation

Validation: The account validates its requested operation through the EntryPoint flow.

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

### smart-account-bundlers-fact-payment

Payment: Accounts or paymasters must cover the operation’s applicable gas costs.

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

## Sources

- [Account Abstraction Using Alt Mempool](https://eips.ethereum.org/EIPS/eip-4337) — Ethereum Improvement Proposals. User operations, bundler transaction submission and paymaster validation. Locator: Specification; Bundlers; Paymasters; Security Considerations. Retrieved: 2026-10-02T17:03:42.486Z.

## Revision history

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

## Cite this entry

Degrees of Satoshi editorial project. “Smart-account bundlers: turning user operations into transactions.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/smart-account-bundlers/