# Speeding up or cancelling an Ethereum transaction

An Ethereum replacement uses the same sender and transaction nonce as a pending transaction while changing fields such as fees. Nodes apply their own transaction-pool replacement rules. The first valid competing transaction included consumes that nonce; a replacement cannot undo an already executed transaction.

Evidence: [Ethereum JSON-RPC](https://ethereum.org/en/developers/docs/apis/json-rpc/); [Ethereum transactions](https://ethereum.org/en/developers/docs/transactions/); [Geth command-line options](https://geth.ethereum.org/docs/fundamentals/command-line-options)

Canonical: https://degreesofsatoshi.com/encyclopedia/ethereum-transaction-replacement/
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

- **Competition:** The replacement and original compete for one sender nonce. ([Ethereum JSON-RPC](https://ethereum.org/en/developers/docs/apis/json-rpc/); [Ethereum accounts](https://ethereum.org/en/developers/docs/accounts/))
- **Hash:** Changing the signed transaction creates a different transaction identifier. ([Ethereum transactions](https://ethereum.org/en/developers/docs/transactions/))
- **Limits:** A same-nonce attempt cannot reverse a nonce already consumed in the accepted chain. ([Ethereum transactions](https://ethereum.org/en/developers/docs/transactions/))

## Speeding up usually preserves the intended action

A wallet can build a higher-fee attempt using the same recipient, value and call data. Both fee caps may matter under EIP-1559-style pricing, and exact admission thresholds depend on node software and configuration.

Inspect the final recipient, value, calldata and maximum fee. A familiar wallet label does not substitute for reviewing the transaction actually being signed.

Evidence: [Ethereum JSON-RPC](https://ethereum.org/en/developers/docs/apis/json-rpc/); [Fee market change for ETH 1.0 chain](https://eips.ethereum.org/EIPS/eip-1559); [Geth command-line options](https://geth.ethereum.org/docs/fundamentals/command-line-options); [Geth legacy-pool replacement checks](https://raw.githubusercontent.com/ethereum/go-ethereum/v1.15.11/core/txpool/legacypool/list.go)

## Cancellation is a race, not a command to validators

A wallet may attempt to occupy the nonce with a different operation instead of the original request. If that alternative is included first, the original cannot also consume the same sender nonce.

If the original is included first, the competing cancellation loses. For this reason, an interface must not describe submission of a cancel attempt as proof of cancellation.

Evidence: [Ethereum JSON-RPC](https://ethereum.org/en/developers/docs/apis/json-rpc/); [Ethereum transactions](https://ethereum.org/en/developers/docs/transactions/)

## After inclusion, inspect the winning receipt

Follow the hash of the transaction that actually entered the block. A replaced attempt can remain visible in a wallet history or external service without becoming the executed payment.

Once a transfer has executed, moving assets back generally requires a new authorized operation. Replacement is not a refund mechanism.

Evidence: [Ethereum JSON-RPC](https://ethereum.org/en/developers/docs/apis/json-rpc/); [Embedding transaction status code in receipts](https://eips.ethereum.org/EIPS/eip-658)

## Questions

### Does a higher fee guarantee my replacement wins?

No. Nodes must accept the replacement, it must reach block builders in time, and the original must not already have been included.

Evidence: [Ethereum JSON-RPC](https://ethereum.org/en/developers/docs/apis/json-rpc/); [Fee market change for ETH 1.0 chain](https://eips.ethereum.org/EIPS/eip-1559)

## Claims and scope

### ethereum-transaction-replacement-quick-answer

An Ethereum replacement uses the same sender and transaction nonce as a pending transaction while changing fields such as fees. Nodes apply their own transaction-pool replacement rules. The first valid competing transaction included consumes that nonce; a replacement cannot undo an already executed transaction.

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

### ethereum-transaction-replacement-fact-competition

Competition: The replacement and original compete for one sender nonce.

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

### ethereum-transaction-replacement-fact-hash

Hash: Changing the signed transaction creates a different transaction identifier.

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

### ethereum-transaction-replacement-fact-limits

Limits: A same-nonce attempt cannot reverse a nonce already consumed in the accepted chain.

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

## Sources

- [Ethereum JSON-RPC](https://ethereum.org/en/developers/docs/apis/json-rpc/) — ethereum.org contributors. RPC response fields, transaction receipts, call simulation and log filtering. Locator: eth_getTransactionByHash; eth_getTransactionReceipt; eth_call; eth_getLogs; eth_getCode; eth_estimateGas; eth_getBalance; eth_getStorageAt; eth_getTransactionCount; default block parameter. Retrieved: 2026-10-02T17:03:42.060Z.
- [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.
- [Geth command-line options](https://geth.ethereum.org/docs/fundamentals/command-line-options) — Go Ethereum. Implementation-configurable transaction replacement and local pool policies. Locator: txpool.pricebump; txpool.lifetime. Retrieved: 2026-10-02T17:25:58.872Z.
- [Ethereum accounts](https://ethereum.org/en/developers/docs/accounts/) — ethereum.org contributors. Key-controlled and code-controlled accounts, balances, nonces and storage. Locator: Account types; An account examined; Account creation. Retrieved: 2026-10-02T17:03:41.958Z.
- [Fee market change for ETH 1.0 chain](https://eips.ethereum.org/EIPS/eip-1559) — Ethereum Improvement Proposals. Base fees, fee caps, priority fees and effective transaction gas price. Locator: Specification. Retrieved: 2026-10-02T17:03:42.151Z.
- [Geth legacy-pool replacement checks](https://raw.githubusercontent.com/ethereum/go-ethereum/v1.15.11/core/txpool/legacypool/list.go) — Go Ethereum. Versioned same-nonce replacement policy and EIP-1559 fee-cap conditions. Locator: list.Add; gasFeeCap and gasTipCap replacement thresholds. Retrieved: 2026-10-02T17:55:17.128Z.
- [Embedding transaction status code in receipts](https://eips.ethereum.org/EIPS/eip-658) — Ethereum Improvement Proposals. Receipts report top-level execution success or failure. Locator: Specification. Retrieved: 2026-10-02T17:03:42.150Z.

## Revision history

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

## Cite this entry

Degrees of Satoshi editorial project. “Speeding up or cancelling an Ethereum transaction.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/ethereum-transaction-replacement/