<!-- tempo-docs-context -->
> Source: [/docs/protocol/transactions/eip-4337](https://tempo.com/developers/docs/protocol/transactions/eip-4337.md)
> Section: [Tempo EVM](https://tempo.com/developers/docs/development.md). Build on Tempo EVM: wallets and keys, payments, transactions and fees, TIP-20 Tokens, contracts, exchange, network details, nodes, protocol specifications, and changelog.
> [Documentation index](https://tempo.com/developers/llms.txt) · [Docs skill](https://tempo.com/developers/SKILL.md)

> Tempo MCP: Use `search`, `find_pages`, `read_page`, and `code` at `https://mcp.tempo.xyz` for Tempo and related documentation.
> If an indexed page is missing or reflects an older site, read this site’s [documentation index](https://tempo.com/developers/llms.txt) and Markdown pages directly.

# Comparing Tempo Transactions and EIP-4337

[EIP-4337](https://eips.ethereum.org/EIPS/eip-4337) uses smart accounts, an EntryPoint, and bundlers; paymasters are optional. Tempo Transactions implement common account features natively. They support fixed protocol signature schemes rather than arbitrary user-defined validation logic.

## EIP-4337 Design Goals

EIP-4337 enables several key capabilities for Ethereum accounts:

* **Fee sponsorship**: Third parties can pay gas fees on behalf of users
* **Batched operations**: Multiple calls can execute atomically in one transaction
* **Alternative signatures**: Accounts can use signature schemes beyond secp256k1
* **Custom validation**: Accounts can define arbitrary validation logic

## How Tempo Achieves These Goals

Tempo Transactions natively support sponsorship, batching, and supported alternative signatures. Custom validation remains a smart-contract design decision.

### Fee Sponsorship

On Ethereum, an EIP-4337 paymaster sponsors operations using its EntryPoint ETH deposit. Applications may use existing paymaster and bundler services.

Tempo Transactions include a `fee_payer_signature` field directly in the transaction. A sponsor signs the transaction to agree to pay fees. The protocol validates both signatures and deducts fees from the sponsor. No paymaster contract or bundler is required; the sponsor still needs a signer and a submission path. See the [fee sponsorship guide](https://tempo.com/developers/docs/api/fee-payer) for implementation details.

### Batched Operations

A bundler includes UserOperations in an EntryPoint transaction. One UserOperation can execute an atomic batch when the account supports it.

Tempo Transactions include a native `calls` array. Multiple contract calls execute atomically in a single transaction. The protocol handles execution directly without external services.

### Alternative Signatures

EIP-4337 accounts implement signature validation in contract code, which may be shared across accounts.

Tempo Transactions natively support secp256k1, P256, and WebAuthn signatures. The protocol verifies these signatures directly, so passkey authentication works without custom contracts.

### Gas Token Flexibility

Ethereum paymasters may charge other tokens, but settlement with EntryPoint uses ETH. Conversion need not happen inside the paymaster or during each operation.

Tempo Transactions pay fees directly in any USD stablecoin that has liquidity on the Fee AMM. No conversion infrastructure is needed. See the [stablecoin fees guide](https://tempo.com/developers/docs/guide/payments/pay-fees-in-any-stablecoin) for implementation details.

## Integration Comparison

| Aspect | EIP-4337 | Tempo Transactions |
|--------|----------|-------------------|
| Contracts used | EntryPoint and smart account; optional paymaster | None required for native features |
| Submission | Bundler (self-hosted or provided) | Standard RPC; sponsor signer if sponsored |
| Fee payment | ETH deposit on Ethereum; optional token charging by a paymaster | Eligible USD TIP-20 token |
| Signature verification | Custom validation contract | Protocol-native |

## When to Use EIP-4337 on Tempo

For an existing EIP-4337 integration, verify your provider's Tempo-compatible EntryPoint, account implementation, bundler, and fee handling. Prefer native Tempo Transactions when their built-in features meet your requirements.

## Start with Tempo Transactions

To start using Tempo Transactions, see the [Tempo Transactions guide](https://tempo.com/developers/docs/guide/tempo-transaction) for SDK integration in TypeScript, Rust, Go, and Python. For the full technical specification, see the [Tempo Transaction Specification](https://tempo.com/developers/docs/protocol/transactions/spec-tempo-transaction).
