# Bitcoin (Replace by Fee)

Everything in [For Operators](/helpcenter2/for-operators/operators-overview.md) applies to Bitcoin. The one addition is **Replace by Fee (RBF)**, a way to deal with a Bitcoin transaction that's been broadcast but is stuck waiting for confirmation, by replacing it with a higher-fee version.

RBF lets you do one of two things with such a transaction:

* **Speed it up**: rebroadcast it with a higher fee so it confirms sooner, or
* **Cancel it**: replace it with a transaction that returns the funds to your own account.

> **Important:** A network fee applies in **both** cases, including cancellation. Replacing a transaction means broadcasting a new one.

## When RBF is available

The **Speed-up** and **Cancel** actions appear only while a transaction can still be replaced, that is, when the request has executed but its outgoing transaction is still **submitted** (broadcast to the network's mempool, not yet confirmed). Once it confirms (or is otherwise no longer submitted), the actions disappear.

You'll find **Speed-up** and **Cancel** on the request, both in the actions on the Requests table and inside the request's side sheet.

## Speed up a transaction

Choosing **Speed-up** opens the standard [send screen](/helpcenter2/for-operators/sending-assets.md), titled *Speed-up transaction (Replace by Fee)*, pre-filled with the **same recipient and amount** as the original and a freshly computed fee. You can adjust the recipient, amount, fee strategy, and note before submitting. The same warnings and errors as a normal send apply, and you authorise it on your device the same way.

## Cancel a transaction

Choosing **Cancel** opens the send screen titled *Cancel transaction (Replace by Fee)*. To cancel, the transaction is redirected back to your own account: the **recipient is replaced by your sender address**, the amount stays the same, and a new fee is computed. Only the **fee strategy and note** can be changed. A warning reminds you that proceeding cancels the transaction and that the fee is still charged.

## What happens to the original

When a replacement (speed-up or cancel) goes through:

* the original request's status becomes **Cancelled**;
* its approval information is **unchanged** (it was legitimately approved), and the side sheet notes it was superseded, with a link to the replacement request;
* the original produces **no operation** in the [operations history](/helpcenter2/for-operators/operations-history-and-statuses.md); only the new replacement transaction appears there once confirmed.

When the replacement confirms, the account's balances and operations history update.

> **Note:** On Ledger Stax and in the app, an RBF request is reviewed like a standard send with one extra detail, the hash of the transaction being replaced, so approvers can see exactly what's being superseded.

**Related:** Ethereum has an equivalent for nonce-based networks. See [Ethereum: staking & Replace by Nonce](/helpcenter2/network-specific-guidance/ethereum-staking-and-replace-by-nonce.md).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.enterprise.ledger.com/helpcenter2/network-specific-guidance/bitcoin-replace-by-fee.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.