Topic: My Transaction Stuck already 4th Day - Please Help. (Read 336 times)

The best you can do is to rebroadcast the transaction, the transaction would have left mempool some weeks ago, it usually take two weeks for transaction to drop from mempool, but it might take before or longer but transaction of 6 to 7 weeks would have dropped from mempool. All you need to to is to spent the same transaction again or cancel it.

They aren't being shown by a block explorer. But they are still taking up space on the Trezor wallet to prohibit double spending. It's via the desktop-web browser.

I'll look into the trezor/electrum thing, thanks for the idea.

6 or 7 weeks? Are they still being shown on a block explorer?
If not, are you using trezor suite on your desktop, are are you using the web interface?

If it's the desktop version, maybe you can try opening your trezor with electrum... That way you should be able to re-spend the unspent outputs (you'll have to activate coin controll to select the unspent output tough).

Some more info, like the tx id, might help getting a better view of the situation: posting the tx id decreases your privacy but not the safety of your funds...

I've had two transactions stuck for nearly 6-7 weeks now from a Trezor. What can I do about this?

This is great, that means free acceleration still works, I have checked to know that the transaction was put in viabtc free acceleration. With the average mempool size we currently having, it is clear that viabtc really helped the transaction confirmed because the mempool is having many transactions to be confirmed which makes miners only to pick high fee ones.

See:
And:
block 670253: Miner ViaBTC

ViaBTC | Transaction Accelerator is the only one I know that really works:

Woow , thank you guys for all your Answers
Finally my Transaction was Confirmed

I don't know how but I am very Happy now
I just learned from all of You, about Bitcoin Transactions what is Great.

Have a Great Day and Weekend.

Kind Regards.
TheFoolIsBack

I can second this. The block explorer I use lately tells that the tx was received "2021-02-09 10:19:55 UTC", and that's about 3 days ago.
So I don't know what the wallet shows, but the chance it's re-broadcasting the tx is slim to none.

I ran exactly the same command and it looks like my node has that transaction in its mempool, so it hasn't been dropped completely yet.

I have no idear how breadwallet works... All i can say is that when i query my own node:


So, your transaction is not in my node's mempool... And my node has been running for months... So my node either rejected your transaction or it was already dropped from my mempool... Odds are BRD is not retransmitting it, otherwise i probably would have found it in my mempool...

@Charles-Tim and the Wallet will not retransmit every time I check the Transactions?

I mean if 14 Days over but I check my Wallet and it can be that the Wallet will resend the Transaction?
Because as I check my Transaction in BRD Wallet it always show me the current DateTime as Initialized DateTime for this Transacrion.

I wanted to add a little sidenote to this remark: those 14 days are not set in stone... They're not part of the bitcoin protocol.

There is no cental mempool, every node keeps unconfirmed transactions in it's own mempool for a certain amount of time. The default setting of bitcoin core nodes is 14 days (at least, it used to be 14 days IIRC), but every node can chose to set a higher or lower amount of time. Also, there are other node implementations (and i have no idear what their default setting is). On top of this, the mempool also has a maximum size, if it's full, transactions will be pruned from the node's mempool (so it's possible at times of mempool congestion that your tx is dropped from most mempools after less than 14 days).

Bottom line: after 14 days, an unconfirmed transaction will be dropped from the mempool of the majority of the nodes, but defenatly not all of them. It's possible to see a transaction be dropped from most mempools after 14 days, but still see it end up in a block after 31 days if the mining node was running with a non-standard setting... So, by just recreating the transaction without looking at the unspent outputs that were used in the dropped transaction, it's possible the receiver will end up being payed twice. This is why it's a good idear to re-use the same unspent output when re-creating a transaction that was dropped from most mempools...

It might sound really technical, but it's important to know the difference

With what I have just checked, TheFoolIsBack made a transaction from a legacy address with 2 inputs to pay for goods, he paid to two addresses. No any bitcoin went back to his address, the reason I noticed this is that, TheFoolIsBack used legacy address but the two address paid to are bech32 addresses.

You do not lose anything, you only just have to be patient for the mempool to be less congested, your transaction will be confirmed likely during this weekend if mempool become less congested. Even, if not confirmed within 14 days, the Bitcoin will be dropped from the mempool back into your wallet.

And how can I Recover this Transaction if ViaBTC will not proceed my Transaction because of low amount?
Is there another Option?
Is here https://bitcointalksearch.org/topic/freepay-bitcoin-transaction-accelerator-5034315 use the same Method with ViaBTC or other (should I post also there my Transaction ID)?

Now I lost again my Hope

I am familiar with the BRD wallet but I think the RBF is not set as the default just like we have on Electrum and by the look of the situation there's no way for the OP to bump up the transaction fee unless he's going to use the paid service offer by ViaBTC which is the best option cause ViaBtc free service accelerator see to work for the transaction with at least 0.0001BTC/kb or 10k sat/kb

Transaction easily get confirmation when there's no congestion and it better you use tx fee estimator as advised.

Let me get this straight: you bought something, paid for it, then in another transaction paid 0.00003850 BTC more (for shipping). So the 0.00099878 BTC BTC went back to your own wallet?
If that's the case, you should have used only 1 instead of 2 inputs (I prefer to use wallets that allow coin control, so I get to manually pick which funds to spend). It would have made your transaction smaller, and the fee lower. Or even better: avoid paying such small amounts of Bitcoin, the webshop itself can barely use it because of transaction fees. It would be great if the webshop can accept Bitcoin Lightning Network for this.

@loyceV  0.00003850 BTC this amount was added the Webshop where I Purchased as Shipping cost

So than now I know this was their Fault not mine.
They should include in price of the goods not separate.

Or am I wrong?

Woow thank you guys for your replies

I will take in consideration all your advises in the Future of my Transactions using Bitcoin
And I will give a shot to BRD and if facing again the same Situation I will change my Wallet.
I am using this Wallet since a while now and never had issues like this. BRD has no option to manual enter a Transaction Fee ... it offers me economy regular and fast.

Kind Regards

I recently used it, and it worked. You have to enter it at exactly the beginning of the hour (say: 10:00:00) to stand a chance.

If ViaBTC doesn't mine it, my guess is it will confirm on Sunday indeed.

For future transactions, you should avoid sending 0.00003850 BTC to change addresses. At current transaction fees, this is worthless dust. You would have been better off adding this amount to the transaction fee.

Breadwallet

@mocacinno Thanks for your tips

BRD is on Playstore and AppStore present Wallet.
I will give a last chance to use it onward and see if SegWit Option Help or not

You can try to make use of fee estimators and compare it with your wallet fee estimator, you will be able to know the fee you can pay that will include your transaction into a block fast. But, there are times the fee can be very high, this depends on the mempool. I do notice on weekend fee of 5 satoshi/vbyte (that does not mean though, depending on the mempool), but this is increased during week days, but what is causing it is when people are making much of transaction, in which there are a lot of transaction on the mempool, miners will first take up the ones with high fee, that is why the ones with low fee will not confirmed during the time. So, the fee depends on the mempool.

Paying from segwit to segwit address do have a low fee, there was a fee I checked yesterday on fee estimator, comparing segwit to legacy, the fee for legacy was about $8 while the fee for segwit was about $6. Using segwit will let you pay lower fee of up to 40% lower or more reduction. Also using segwit to pay to nested segwit and legacy is still higher in fee compared to paying from segwit to segwit. But, paying from legacy to legacy is much higher, in fact, it has the highest fee. So, using segwit will help you reduce the fee.

Using segwit will make your transaction fee to be reduced as explained above, but there are still possibilities you pay much lower fee in which transaction can be stuck in mempool. But, having the knowledge about fee estimation can help, also your wallet fee estimator or online fee estimators can help to determine this. Also, paying high priority fee will make your transaction confirmed in time.

Lastly, I will advice you to make use of wallet that support replace-by-fee, which can be used to pump the fee in time like this, provided if you want to. Electrum wallet supoot replace-by-fee.

I am not familiar with BRD wallet.

If your address starts with 1 it's not SegWit. If it starts with 3 it's SegWit compatible, if it starts with bc1 then it's native SegWit address. If you don't know what you do, I recommend 3* SegWit compatible, since many services still cannot send money to native segwit address. How to achieve that? I don't know, but BDR does offer SegWit, but I don't know how.

SegWit allows lower fee indeed, but that doesn't mean you'll pick lower number of satoshi/vbyte, instead the number of vbytes will be smaller.

Tips:
* from what I've read, BRD should allow better fee structure than "low, max,..." but if you cannot find any option to pick more exactly the fee, try another wallet https://bitcoin.org/en/choose-your-wallet
* before sending a transaction take a look at sites like https://mempool.space/ or https://btc.com/stats/unconfirmed-tx and decide better what fee to use.
* if you are not in a hurry, try to send transactions in the week-ends.

According to https://bitcoin.org/en/wallets/mobile/android/brd/ this wallet supports the RBF feature. Is there no option for you to "bump the fee"/"increase the fee" or something similar in your app?

I get the feeling that either you can enable it when you make a transaction or it is enabled by default but you turned it off somehow.

Well, you asked for tips  

1) I've never heared about the wallet you're using... I have no idear if it's a desktop wallet or an online wallet, or how it works or what their feature set is... Maybe it's a good idear to switch to a more common wallet instead? Electrum gives you the option to customise your fees and it has opt-in rbf and CPFP built in to the gui. This means electrum is well equiped to give you complete controll over your fees (while giving you all the information you need to make the decission) AND it's setup to help you get transactions unstuck by bumping the fee (with opt-in RBF tx's) or by creating a CPFP (in case you're the receiver, or if you opted out RBF). Wasabi wallet is another good alternative with a similar feature set (at least when it comes to not getting your tx's stuck). Both wallets can be coupled to the most popular hardware wallets to, so if you ever decide you need more security, you won't have to climb a new learning curve since you can just use a ledger or a trezor hw wallet using exactly the same electrum or wasabi gui.

2) instead of thinking in dollars and euro's, think in transaction size. The fee is calculated in satoshi per vByte... Not in satoshi per transacted FIAT equivalent

3) learn how to use sites like this one: https://jochen-hoenicke.de/queue/#0,24h . If you have opted in rbf and you use a wallet that shows you the transaction size and lets you pick the fee, this site helps you to set the correct fees

4) learn that, as long as there is trust between the sender and the receiver, nothing really bad can happen. A transaction either confirms, or it gets pruned from the mempool of most nodes after a couple of weeks... As long as there is trust between the sender and the receiver, the worst that can happen is that the sender has to re-send the funds after a couple of weeks... As long as you both have controll over your wallets, and you used the correct addresses on the correct network, nothing really bad can happen. Things are different when you pay somebody and there's a time limit (like for example, if you pay in an online shop): in this case you might want to overpay a little, so you don't get into troubles if your tx doesn't confirm on time.

@NeuroticFish thanks for your reply and I will considering in Future the Thread you mentioned.

And right just now pushed again my Transaction ID and  I've got the answer "This transaction is being accelerated."
But this wasn't me because before I always got the message "try agaian later"

Thanks again for you too
Regarding to my other Questions do you have some Tipps for me?

Kind Regards.

1. I think that either me, either somebody else added your TX to ViaBTC free accelerator, I've got the answer "This transaction is being accelerated."
I didn't use the accelerator for long time, but since the time was right, I gave it a shot.
Keep in mind that this doesn't mean that next block will have your tx, instead one of the next blocks mined by ViaBTC will have it.

2. If I am wrong, or for next time you are in a trouble, I think that this thread may worth a try: https://bitcointalksearch.org/topic/freepay-bitcoin-transaction-accelerator-5034315

@Charles-Tim Thanks for your quick Reply

Understand, than I will wait to see if this Weekend will be accepted.

Regarding to my Transactions in Future what should I do? Always set the Maximum Fee? (is this not stupid?)
till now every time worked Regular Fee

Yesterday just enabled on my BRD Wallet the SegWit Option...
Is this would Help me in Future for my Transactions not to stuck?

Thanks again

The transaction fee used is 20.552 sat/vbyte, but at the moment, the transaction fee that can possibly make miner to put your transaction into next block is around 102 Satoshi/vbyte. Also, the mempool is congested for now. The transaction is not replace-by-fee supported, which means you can not also pump the transaction. Also the transaction likely not having UTXO back into your wallet. Which means you have no option than to just wait for the mempool to be less congested, the mempool will probably be less congested during this weekend.

Hello Dear Community,

My Wallet is BRD, I have contacted the support but their Answer was with predefined Text "I have to wait and can do nothing." ;(

To mention that I chosen the Regular Fee as always before and never had issues like this.
The transferred amount is 40 Euro and found some Acceleration tolls witch offer acceleration but for 140$

ViaBTC never worked for me ... tried 1000 times at Begining of Hour , End, Middle .. Random and never accepted

My Transaction ID:
f0e7532301b5c5cdc3b7a14f214df91a92223baa1e750d940a8ed2627a8ebbd5

Please someone if can Help me

Kind Regards.