Bitcoin Forum

Hey I have a tx stuck in mempool its custodial wallet unfortunately and sender is Mia.  Please any ideas to bump fee? Or cpfp way without keys?
Tx#
3fc2ebf7dd2ce21a8b7a68545942c0d1b8f0f141f8a4c91865031eb65a5e4209

Thank you  ;D

The transaction support replace-by-fee, you can increase the fee.

Or you can wait for the next hour and submit the txid on ViaBTC free accelerator https://www.viabtc.com/tools/txaccelerator/ so that the transaction would be included in a block mined next by ViaBTC.

Edit:
It is from Custodial wallet, follow what hosseinimr93 posted if you can not wait and use ViaBTC accelerator. If you can wait, I can help you submit the txid in some minutes time.

Do you have control over the receiving address? If so, you can do CPFP.

To do CPFP, you should spend the fund received in the unconfirmed transaction in a new transaction with a high fee.
If the fee paid for the new transaction is high enough for both transactions, miners will include them in the same block.

In the case your wallet doesn't allow you to spend unconfirmed coins, you should import your seed phrase/private key in a wallet which allow you to do so. A good option is electrum.

Successfully submitted:

https://www.talkimg.com/images/2023/11/17/F6Q4q.jpeg

If ViaBTC mine the next block, the transaction will be confirmed.

You can know newly mined block here: https://mempool.space/blocks

I tried to check the TXID you provided above the transaction was made 2 weeks ago and the transaction was already rejected by other nodes so you should be able to recreate a new transaction I don't think CPFP will work you need to contact the sender Mia if the sent amount is already rejected or if it's funded back to her account. Ask her to make a new transaction once again with enough fee if it was already rejected.

If this transaction is broadcasted again then you will need to wait again for 2 weeks until the transaction is rejected again by the mempool because the fee used in this transaction is around 17sat/vB which is far from the current recommended fee by mempool.space. However, you can do what hosseinimr93 suggested above if you have full control of your wallet but if it is also an exchange then you don't have any other choice but to wait again for 2 weeks

He should let ViaBTC mine a block and the transaction would be confirmed.

I was unable to check it from blockchair.com, but I saw it on https://www.blockchain.com/explorer and https://blockstream.info.

https://blockstream.info/tx/3fc2ebf7dd2ce21a8b7a68545942c0d1b8f0f141f8a4c91865031eb65a5e4209
https://www.blockchain.com/explorer/transactions/btc/3fc2ebf7dd2ce21a8b7a68545942c0d1b8f0f141f8a4c91865031eb65a5e4209

Which means it has not been dropped from nodes of some mempool and also not displayed to be invalid on ViaBTC accelerator and can still be confirmed and it will not take up to 4 to 5 hours before ViaBTC will mine the next block.

The mempool is over 170 sat/vbyte and not worth to rebroadcast the coins. Also the sender's wallet is not his, although I doubt if it is from a custodial wallet as it is of low fee and also supporting replace-by-fee.

Edit:
ViaBTC mined block 817095 and the transaction has been confirmed.

you did good work. at op try to get a trezor.io wallet hardware and use rbf to fix issues.

I have a similar situation but a bit higher fee. Still my transaction has been sitting in the mempool for like two weeks or so. ViaBTC refuses to accelerate my transaction as they seem to have some size limit and my transaction obviously exceeds that limit. Any suggestions?

P.S. I'm not going to do RBF because I refuse to fuel this monkey token craziness. This is not an emergency, so I can wait.  8)

if you can wait wait.

what did you pay?

60 sat 80 sat ?

https://mempool.jhoenicke.de/#BTC,1w,weight

looks like 60 should be okay

If you don't want to use rbf to bump your transaction and you don't meet ViaBTC's requirements, then there is no suggestion we can give you other than for you to wait, since you said it is not an emergency and you are willing to wait, then wait. By the way, what fee rate did you attach to your transaction, and since it has been in the mempool for more than two weeks as you said, most nodes that use the default time of 14 days must have dropped it out of their mempool.

The fee is around 30sat/byte if I remember correctly... I said two weeks because the OP mentioned similar time period but it can as well be 12 or 13 days, I'm not sure. When nodes give up, transaction status turns to "local" in my wallet so there's a chance still...

It is worth mentioning that your transaction would only turn to 'local transaction' if the node or server that you are connected to drops your transaction out of their mempool, and then you can spend the input in another transaction.
Fee rate in the mempool (https://mempool.space/) isn't as high as it was days ago, fee rate is dropping and as i type this the fee rate for high priority tx's is ~ 38 sat/vbyte. So if truly your fee rate is ~ 30 sat/vbyte, it may be confirmed sometime soon if the fee rate continues to drop like this.

As long as either you're the sender, or you trust the sender enough to keep broadcasting the transaction, you can wait as long as it takes for fees to drop.

Depending on your wallet, you can broadcast it again. If you're the sender, none of this is relevant.

Yes, I'm both the sender and the receiver.  ;D

Just for info, this transaction still hasn't been processed. It's sitting there in the mempool ~30MB from tip. The fee is worth ~$5-6 in fiat which is a lot of money for a moderate amount I'm trying to send. 

Are you trying to consolidate some inputs? Then it is worth waiting till the fee drops. You can keep LoyceV's thread (https://bitcointalk.org/index.php?topic=2848987.0) in the watching list or a telegram bot for tracking the fees; for example- @BitcoinFeesAlert_bot. You can set alert there.

Then there's nothing to worry about :) I've had transactions that took months to confirm. As long as you don't need the funds, just let your wallet broadcast it until it gets confirmed.

This happened to me 2 or 3 years ago. I waited or almost 3 months before my unconfirmed transaction was confirmed. But when I have been using Electrum wallet, it will not take more than 3 weeks before I will see the coin back on my wallet and I will spend it again. I did not like what happened when my coin was unconfirmed for almost 3 months but I was the sender and the receiver and I did not panic becuase of it.

It depends on your wallet. I think Bitcoin Core keeps broadcasting it if I don't abandon the transaction, so even if the fee is under the minimum, it will be picked up by other nodes whenever fees drops low enough.

How long it will take a transaction to be dropped when using Electrum depends entirely on the Electrum servers you are connect to. Some will run with the default of two weeks, some will run with higher limits, and some will run with virtually no limit at all. If you are still seeing your unconfirmed transaction on Electrum after several months, you can try swapping to different servers to see if you can find one which has already dropped it.

Alternatively just make a full RBF replacement.

If I'd be a miner, I'd want to keep all valid transactions forever. As long as the inputs still exist, there's still money to be made when transaction fees drop.
The only way to be sure the transaction won't confirm later, is by spending at least one of the inputs by yourself in another transaction.

The best alternative to me is to never make a transaction that does not have RBF. If my transaction has RBF, all I will do after frustration of stuck transaction is to just increase the fee. I will prefer this than full RBF that I will be looking for a node that is supporting it to rebroadcast my transaction because all nodes are supporting the old and still existing RBF. But if a transaction is not supporting RBF, the person that make the transaction will have no other option than to go for your suggestion.

I try to avoid small change, so whenever possible, I send the full amount. The one time I did RBF in Bitcoin Core, it added another input, without giving me the chance to use Coin Control. So apart from being bad for privacy, the transaction size also doubled.

which is why I use trezor it allows rbf

with good management you can greatly reduce fees.

and I am not a "coin racist" so I do keep LTC and Doge on hand as they are the superior coins for smaller sends.

I'm witnessing a sharp drop in fees lately. Idiots running out of monkey pics I presume or?

The transaction I mentioned in my previous posts went up from ~25-30sat/mb to just ~5-6sat/mb from tip. Perhaps time to consolidate small inputs is near?

I see 25 sats and up not 5-6

I have a 22 sat that is 30 hours old and not going anywhere.

https://btc5.trezor.io/tx/b020a419353a421e9394d635df4d3cafa00fbd447e42a3b757af1bf633b47b9f

I'm sorry if my post was misleading, what I meant was "5-6mb from tip" not 5-6sat/mb fee. It's a value my wallet is estimating, the position of transaction in mempool. 5-6sat/mb is definitely unrealistic atm.

We are currently mining transactions at 23 sats/vbyte, so you might get lucky over the next couple of hours.

We are also around 23 blocks behinds where we "should" be in this difficult epoch, which doesn't help. Those 23 blocks would clear us out to around 11 sats/vbyte.

I guess the whole stuff is making sense to me now it's a direct variation  the transaction fee decreases in accordance to the block ruminant