<blockquote>
  <p>I send all the btc in one wallet to another wallet of my own, so as i didn´t have a rush i put a small fee, too low to be honest.</p>
</blockquote>

<p>That's a known problem : when mempool median feerate spikes after you broadcast your transaction, or in your case doesn't lower as you may have expected.</p>

<p>That's the reason why marking transactions as <a href="https://en.bitcoin.it/wiki/Replace_by_fee" rel="nofollow noreferrer">replaceable</a> is useful in the first place: if a transaction gets stuck, it enables you to replace the already broadcast transaction with a new one paying more fees. This is not permitted for transactions that do not signal replaceability.</p>

<p>What wallet did you use ? Most wallets today offer the possibility to signal for RBF (<strong>*</strong>), and you may just be able to replace your low-feerate transaction.</p>

<blockquote>
  <p>Can anybody tell me certainly how much time take to a transaction to be forgoten?</p>
</blockquote>

<p>The default for nodes on the network is set to 336 hours (<code>bitcoind</code>'s <code>-mempoolexpiry</code> option).</p>

<p>EDIT : As <a href="https://bitcoin.stackexchange.com/users/5406/murch">@Murch</a> pointed out in the comments, you can also try CPFP on the receiver side, i.e. spend the unconfirmed transaction with a high-fee transaction to bump the overall feerate of the "package" (we call "package" the unconfirmed transaction chain).</p>

<p>(<strong>*</strong>) Was grossly "most wallet signal RBF" before EDIT, which is wrong and <a href="https://transactionfee.info/charts/transactions-signaling-explicit-rbf/" rel="nofollow noreferrer">reflected by the mempool</a> (corrected by @Murch, thanks!).</p>

CC BY-SA 4.0
2020-05-19T14:51:54.090Z
2020-05-22T09:53:26.630Z
2020-05-22T09:53:26.630Z
Antoine Poinsot
<p>Try speeding it up instead, <a href="https://coinbaseaccelerator.com" rel="nofollow noreferrer">Coinbase Accelerator</a> worked for me.</p>

CC BY-SA 4.0
2021-04-05T14:07:58.080Z
2021-04-05T14:07:58.080Z
Ophrenne
<p>I send all the btc in one wallet to another wallet of my own, so as i didn´t have a rush i put a small fee, too low to be honest. I´ve read that eventually the transaction will be forgoten and returned to original wallet, but I also read about transaction being stuck for months. Anyone can help me or give more information about it? Can anybody tell me certainly how much time take to a transaction to be forgoten? 
Thanks a lot..</p>

CC BY-SA 4.0
2020-05-19T14:17:15.157Z
Do you know what you had your fee set at? How many satoshis per byte was your transaction? Depending what your fee was set at it might just take some time before it goes through.
m1xolyd1an
CC BY-SA 4.0
2020-05-19T15:34:54.273Z
Does this answer your question? [Why is my transaction not getting confirmed and what can I do about it?](https://bitcoin.stackexchange.com/questions/9046/why-is-my-transaction-not-getting-confirmed-and-what-can-i-do-about-it)
MCCCS
<transactions>
Stuck transaction
Martin
# Stuck transaction

(Asked by: username_0 on 2020-05-19)

I send all the btc in one wallet to another wallet of my own, so as i didn´t have a rush i put a small fee, too low to be honest. I´ve read that eventually the transaction will be forgoten and returned to original wallet, but I also read about transaction being stuck for months. Anyone can help me or give more information about it? Can anybody tell me certainly how much time take to a transaction to be forgoten?
Thanks a lot..

**Tags:** transactions

> **Comments:**
> **username_1**: Do you know what you had your fee set at? How many satoshis per byte was your transaction? Depending what your fee was set at it might just take some time before it goes through.  
> **username_2**: Does this answer your question? [Why is my transaction not getting confirmed and what can I do about it?](https://bitcoin.stackexchange.com/questions/9046/why-is-my-transaction-not-getting-confirmed-and-what-can-i-do-about-it)  

---

## 2 answers

### Answer by username_3 on 2020-05-19. Score: 1

> I send all the btc in one wallet to another wallet of my own, so as i didn´t have a rush i put a small fee, too low to be honest.

That's a known problem : when mempool median feerate spikes after you broadcast your transaction, or in your case doesn't lower as you may have expected.

That's the reason why marking transactions as [replaceable](https://en.bitcoin.it/wiki/Replace_by_fee) is useful in the first place: if a transaction gets stuck, it enables you to replace the already broadcast transaction with a new one paying more fees. This is not permitted for transactions that do not signal replaceability.

What wallet did you use ? Most wallets today offer the possibility to signal for RBF (**\***), and you may just be able to replace your low-feerate transaction.

> Can anybody tell me certainly how much time take to a transaction to be forgoten?

The default for nodes on the network is set to 336 hours (`bitcoind`'s `-mempoolexpiry` option).

EDIT : As [@Murch](https://bitcoin.stackexchange.com/users/5406/murch) pointed out in the comments, you can also try CPFP on the receiver side, i.e. spend the unconfirmed transaction with a high-fee transaction to bump the overall feerate of the "package" (we call "package" the unconfirmed transaction chain).

(**\***) Was grossly "most wallet signal RBF" before EDIT, which is wrong and [reflected by the mempool](https://transactionfee.info/charts/transactions-signaling-explicit-rbf/) (corrected by @Murch, thanks!).


---

### Answer by username_4 on 2021-04-05. Score: 0

Try speeding it up instead, [Coinbase Accelerator](https://coinbaseaccelerator.com) worked for me.


---

