Topic: Beginner here with unconfirmed transaction. Please help (Read 329 times)

He just got lucky, the average mempool size suddenly dropped to 10+mb that made his 1sat/byte tx possible for a 12-24hours-confirmation just as I mentioned earlier.

---

@maxttilt You can now lock the topic (lower-left button) after editing the title like "[SOLVED] Title".

Thats correct since the price of tx are depend on the status of the mempool and I believe it will be better if Bitcoin core tx fee can have the same features like electrum. However, the transaction was confirmed 15 hours ago.



Wasn't aware of the situation. I mentioned the site because I used it last year with the viabtc and my transaction went through.

That seems to be a fairly accurate representation of how Bitcoin Core is currently setup... and should work.

Obviously, the tricky part is calculating the correct fee You really want to make sure you calculate it properly. If you're very desperate and you need a fast confirmation, overestimating is definitely better than underestimating... otherwise you might end up with TWO unconfirmed transactions left hanging!

Seems like your transaction confirmed  

In case you ever want to do a cpfp with bitcoin core qt the next time you run into problems:
*warning*: I don't use the QT wallet, and i don't wanted to stop my daemon, so i used an altcoin wallet for this semi-walktrough... I hope their QT gui layout is the same as bitcoin core's. I also didn't have any unspent outputs i could work with...
- go to settings
- open options
- go to the wallet-tab
- enable: "coin control features" and "spend unconfirmed change"
- click on the send tab
- click on the button under the title "coin controll features" that lets you select your inputs
- select the unconfirmed unspent output you received as change from the hanging transaction and one second confirmed unspent output (you'll need this second unspent output to have sufficient funds for a big enough fee... If the change is/was sufficient, you could have done a rbf instead of a cpfp)
- it doesn't matter which address you fund with this CPFP transaction, as long as you manually pick a fee that's calculated with the following formula: (new fee) >= (((fee for fast confirmation of hanging tx) + (fee for fast confirmation of CPFP transaction) ) - (fee already payed for the hanging transaction))

You can use this tool for a fee estimation of both the hanging and the cpfp tx: https://coinb.in/#fees

Damn... ConfirmTx? Really?

They were confirmed as a scam months ago (maybe even a year ago). I’m not even sure if they are still up.

Rebroadcasting is usually totally useless. All it does is add the tx to specific nodes mempool. If the tx is already there, it doesn’t do anything. The tx with higher fee will always get confirmed first. That’s is no way an “acceleration”.

I believe the above transaction accelerator or confirmtx which will allow the OP to pay some certain fee to miners if the previous is too small are the option the OP had since mocacinno believe rebroadcasting the transaction is not the best option.

Either you can try what mocacinno suggested, or you can make an account on Viabtc and see how much cost your transaction to accelerate on paid accelerator. Viabtc accept BCH for paid acceleration, i can't check right now how much is cost for your transaction but i don't think is so much.

Looks like they ask over 0.1BCH for it

Sometimes you can use ViaBTC accelerator to make the transaction pass by faster, but it won't work with really low fees

https://pool.viabtc.com/tools/txaccelerator/

nope, the change is insufficient to pull off a succesfull rbf. Even if he uses all change, the fee would only be bumped to ~3-4 sat/byte, which is insufficient at the moment.

@OP: i've had a rather busy day today, so i haven't answered you (yet), if nobody else explains how to do a CPFP by tomorrow, i'll try to schedule some time to make a small walktrough and post it in this thread

thanks for your reply. What do you suggest i do then? I dont mind upping the fee.

I set the fee at decent recommended setting for this transaction but no idea why comes up insufficient.

If the average mempool doesn't return to a low value of 10mb, transactions like yours will likely never get confirmed based on 2017's same scenario.
If it miraculously gone down to average of 10mb, you will only have to wait for about 12-24hours for it to get confirmed.

By saying "return to your wallet", you must be talking about how long will the nodes keep that tx in their mempool, answer: most nodes will drop it after 14days, but some may not.
If you haven't changed the -mempoolexpiry setting, it will "return" after 14 days after your last re-broadcast.

can i ask, what would the wait be like roughly? and also if it doesnt ever gets confirmed, how long does it take till it gets returned to my wallet in this current situation? thanks

sorry i cant reply ur pm, have a 2 PM/day restriction as a new user.

i am using the latest version of bitcoin core.

Given the current size of the mempool and the fees in play at the moment... the OP really has little option but to just sit and wait As calculated, the maximum fee they can possibly reach with RBF is only around 4 sat/vbyte total... and there are around ~25-30 blocks worth of transactions that have higher fees than that.

The only other option available would be a "Child Pays For Parent" (aka CPFP) transaction... whereby they spend that 0.00002376 BTC change output in a transaction that pays a comparatively HUGE fee (like 120+ sats/vbyte) to try and push both transactions through, or get the recipient of the ~1.52 BTC output to try the same.

Bitcoin Core has coin control, so creating a transaction that spends that change output should be relatively simple.

What I mean is the "additional fee" that he can use based from the available change.
But I think that it's not possible since the minimum sending amount is 546 Satoshis which also applies for the change... so the maximum fee that he can add is +3sat/b not 4 in my previous reply.

Still not worth the effort.

@nc50lc: i had never heared about a maximum increment... I have to admit i have only used rbf once (altough most of my transactions are opt-in rbf)...

I've just read bip125 again: https://github.com/bitcoin/bips/blob/master/bip-0125.mediawiki but i don't see a +4sat/byte maximum increment specified here either. Could you point me to the correct documentation?

The highest increment you can make using RBF is +4sat/byte and still not enough for a "regular speed" transaction at the moment.
It's based from the size of the transaction: 589 bytes (x4=2356) and the change amount: 2376 satoshi (I don't know if the network will allow a <10 satoshi change Haven't tried it, maybe not).
But were talking about a SegWit transaction and blockchain.com often fails to display the accurate data of a SegWit Tx, could be lower or higher.

Or if the sending amount isn't an issue, do a double spend attempt by enabling coin control and by deleting your mempool (warning: not beginner-friendly).
This way, you can re-spend the same inputs to make another transaction (with lower sending amount and higher fees)

The problem is that the change sent to your change address is only 2376 satoshi's, so that's the maximum amount you can increase the fee with... So if you do a RBF, the maximum fee for the rbf transaction is 0.00001103 + 0.00002376 = 0.00003479. This bump would increase the odds of your transaction ending up in a block, but not by that much... The fee would still be to low for a fast confirmation!

Also, like i said before, if you bump the fee up to 0.00003479, you no longer have the option to do a CPFP...

Personally, if i would have your problem, i'd be in one of these 2 situations:
1) there's a sense of urgency... You're paying somebody else and you cannot contact this person to explain the situation.
Sollutions:

• Do a CPFP
• Find a mining pool operator and pay him
• expert, small odds of success: but you can also double spend the input in a brand new (non-rbf) transaction but use more unspent inputs so  you can pay for a much higher fee... The problem is that most nodes would reject this transaction, especially if sent within 2 days after the initial tx was broadcasted

2) there is no sense of urgency... You're moving funds between wallets, or you're paying somebody you can contact and explain the situation
Sollutions:

• Keep rebroadcasting the tx and wait it out
• Bump the fee up to 3479 satoshi's and keep rebroadcasting the tx and wait it out
• Do a CPFP
• Find a mining pool operator and pay him
• expert, small odds of success: but you can also double spend the input in a brand new (non-rbf) transaction but use more unspent inputs so  you can pay for a much higher fee... The problem is that most nodes would reject this transaction, especially if sent within 2 days after the initial tx was broadcasted

Can i ask how do i bump the fee when i keep getting this error message "Increasing transaction fee failed, (Change output is too small to bump the fee)" ?

i believe i have sufficient btc in my wallet

https://www.blockchain.com/btc/tx/1df2b339823d819caf5606b41338f7407e984bc3e29435a28c531e9006cb063f

Well, at first, it looks like the change is 0.00002376 BTC, so if you bump the fee, you can at least try to increase it by 2376 satoshi's...
You could also use the unconfirmed output to your change address as input for a new transaction with a fee high enough to cover both the initial and the CPFP transaction.

https://coinb.in/#fees tells me that at this point in time, this transaction would need a fee of: 0.00024628 BTC, since you payed only 0.00001103 BTC, you'll probably have to wait for a while... If you keep rebroadcasting your transaction, there's a reasonable chance it'll end up in a block even if you do nothing but rebroadcast...

To summarise, here are your options:

• Find a big mining pool operator that's willing to increase your tx's priority (either for free, or paying... But stay away from unknown miners, a single miner cannot just mine your transaction by himself)
• do a CPFP
• bump the fee
• keep rebroadcasting the transaction and wait it out

The first option is self-explanatory
The second option is using the unconfirmed unspent output funding the change address in a new transaction with a fee of: (0.00024628 BTC - 0.00001103 BTC) + a decent fee for the transaction itself
The thirth option is using the opt-in rbf that you probably opted into (since you already tried to bump the fee)... Altough bumping the fee with 2376 satoshi's probably won't suffice, and spending the complete change will exclude you from trying a CPFP
The last option is the easyest, but will probably take the most time... Just save the raw tx in hex format and keep rebroadcasting it using one of the many online forms...