New transaction accelerator on the market - mempool.space

[xixou]

I still see
You are currently on the waitlist. You will get notified once you are granted access.
Do you know how much time it takes to get access to the accelerator?
I have set a way to low fee and turned off RBF ... What a mess, there is no confirmation after 1 month ...

[ABCbits]

I still see
You are currently on the waitlist. You will get notified once you are granted access.
Do you know how much time it takes to get access to the accelerator?
I have set a way to low fee and turned off RBF ... What a mess, there is no confirmation after 1 month ...

If 1 month already passed, most node already drop your transaction from it's node. Depending on which wallet software you use, you can "delete" that unconfirmed transaction and create new ones with better fee rate.

[xixou]

I still see
You are currently on the waitlist. You will get notified once you are granted access.
Do you know how much time it takes to get access to the accelerator?
I have set a way to low fee and turned off RBF ... What a mess, there is no confirmation after 1 month ...

If 1 month already passed, most node already drop your transaction from it's node. Depending on which wallet software you use, you can "delete" that unconfirmed transaction and create new ones with better fee rate.

I use bitcoin core QT.
I do not see delete transaction when right clicking on it. (abandon transaction and increase fee (RBF was off) are grayed out)
Transaction is here:
https://mempool.space/tx/42888c7b1540f8d5b9e074d15c2d86d7b03878adf6f173c7316f09910c2dabd9
If I delete, will my sat be back in the wallet?

[LoyceV]

(abandon transaction and increase fee (RBF was off) are grayed out

I've often noticed that too. I'm not sure when this feature can be used.

If I delete, will my sat be back in the wallet?

Yes.

After a month, Bitcoin Core should be able to forget this 1 sat/vbyte transaction. It's even under the purge limit.
Alternatively, you could probably import the private key into Electrum and create a new transaction there, but try first to wipe this transaction from your Bitcoin Core.

[xixou]

Could it be that the delete transaction can only be done if you still have BTC in you wallet?
I get 0 for now.

[dkbit98]

Could it be that the delete transaction can only be done if you still have BTC in you wallet?
I get 0 for now.

Silly question to ask... it's impossible to make any transaction in bitcoin blockchain if you have ZER0 coins in your wallet, and zero really needs to be 0, not 0.00012 or similar.
You can't get in negative balance with bitcoin, like you can do with fiat currencies and banks accounts.

[xixou]

I made the payment to empty my wallet, this is why it is at 0 At the moment.
It was not the case before of course.

[dkbit98]

I made the payment to empty my wallet, this is why it is at 0 At the moment.
It was not the case before of course.

Yeah, I see you tried to do, but older format addresses you used needs higher fees.
You can wait a very long time for confirmation with minimal 1.00 sat/vB fee that you used, but you can always send more coins to your wallet and accelerate transaction if you are in a hurry.
Next time make sure to check mempool.space before making any (consolidation) transactions.

[Synchronice]

If I delete, will my sat be back in the wallet?

Yes.

After a month, Bitcoin Core should be able to forget this 1 sat/vbyte transaction. It's even under the purge limit.
Alternatively, you could probably import the private key into Electrum and create a new transaction there, but try first to wipe this transaction from your Bitcoin Core.

Just want to confirm this. As far as I understood, if you post in public the transaction that you want to accelerate, you might be in trouble because if you don't accelerate it and will hope that nodes will forget your transaction soon, then there might come someone evil who will push nodes to broadcast your transaction and it will be unconfirmed till the day recommended fees match to your TX fees.

You can wait a very long time for confirmation with minimal 1.00 sat/vB fee that you used

That might not happen for months in the best case, years in the good case and never in the worst case.

[LoyceV]

if you post in public the transaction that you want to accelerate, you might be in trouble because if you don't accelerate it and will hope that nodes will forget your transaction soon, then there might come someone evil who will push nodes to broadcast your transaction and it will be unconfirmed till the day recommended fees match to your TX fees.

No need to post anything: the moment you broadcast a transaction, it's public knowledge. "Someone evil" can just be a node with very large mempool. But for most other nodes, 1 sat/vbyte is still under the purge limit, so they won't even remember it.
The only way to make a signed transaction invalid is by moving at least one of the inputs (with a higher fee).

[xixou]

My transaction is still in mempool for 3 months now ...
Why is it not getting out of the mempool?

[LoyceV]

My transaction is still in mempool for 3 months now ...

I assume you're talking about this transaction: 42888c7b1540f8d5b9e074d15c2d86d7b03878adf6f173c7316f09910c2dabd9.

Why is it not getting out of the mempool?

There is no "one mempool". Anyone can keep that transaction as long as it's valid. Easy fix: move one of the inputs.
For example, (check and if you like it) sign this transaction:

Code:

01000000010481a776ff31478b8b967e15a9e68f78f4cd06b156a5d12910f72d8885147e95020000001976a914367ca154148ceabbcfc3b6c6167f512bb4f9c23388acfdffffff01b88800000000000017a914e09aa133479cff513578a460c606ba504fd761a68700000000

This takes your smallest input, adds a higher fee, and sends it to your destination address. I used coinb.in to create this unsigned transaction.
Once this is confirmed, your months-old transaction is no longer valid.

[dkbit98]

My transaction is still in mempool for 3 months now ...
Why is it not getting out of the mempool?

It's been 4 months actually, but this is because you used minimal fee 1.00 sat/vB so transaction can't be confirmed and I honestly don't remember last time we saw fees getting that low.
Don't expect it to see fees go down that level any time soon, so better do what LoyceV suggested above.

[NotATether]

First is the limits that have killed the demand, Viabtc has really half closed to gate, so you have to pay 20sat/vb to be sure and keep your tx under 0.5kb, plus of course no unconfirmed parents, so there are times when there are simply no tx out there that match the requirements, as for the next block issue, it happens when ViaBTC has really bad luck and is not getting enough blocks spread across the day, they offer 100tx every hour but sometimes they don't mine a block for 6-7 hours, so not to fill the whole block with cheap tx they postpone a few of them to the next one, I read once something about a 500 cap but don't know how accurate that claim was, probably it's more about size than raw numbers.

All signs point too the fact that ViaBTC is winding down on its operations or is at least falling on hard times. If it's not finding blocks at the rate it used to be, then clearly the first thing that is going to be axed are the free transaction accelerator because it has to get as much BTC as possible to survive. I am actually quite surprise that they haven't killed yet if it's not very useful anymore.

[stompix]

All signs point too the fact that ViaBTC is winding down on its operations or is at least falling on hard times. If it's not finding blocks at the rate it used to be, then clearly the first thing that is going to be axed are the free transaction accelerator because it has to get as much BTC as possible to survive. I am actually quite surprise that they haven't killed yet if it's not very useful anymore.

What signs?
They had an 11.30% share over a year and a 13.70% share over the last month is not like they are losing anything significant!
That was a purely economic decision, it made sense at the time and it makes sense for every mining pool, you're giving away better rewards and you also make the income of your miners smaller compared to other pools,  we all love cheap stuff but a company isn't run on appreciations! You don't have to be near bankruptcy to do it!

[xixou]

My transaction is still in mempool for 3 months now ...

I assume you're talking about this transaction: 42888c7b1540f8d5b9e074d15c2d86d7b03878adf6f173c7316f09910c2dabd9.

Why is it not getting out of the mempool?

There is no "one mempool". Anyone can keep that transaction as long as it's valid. Easy fix: move one of the inputs.
For example, (check and if you like it) sign this transaction:

Code:

01000000010481a776ff31478b8b967e15a9e68f78f4cd06b156a5d12910f72d8885147e95020000001976a914367ca154148ceabbcfc3b6c6167f512bb4f9c23388acfdffffff01b88800000000000017a914e09aa133479cff513578a460c606ba504fd761a68700000000

This takes your smallest input, adds a higher fee, and sends it to your destination address. I used coinb.in to create this unsigned transaction.
Once this is confirmed, your months-old transaction is no longer valid.

Thanks for your help but this is too complicated for me.

[LoyceV]

Thanks for your help but this is too complicated for me.

Export private key, import it into Electrum, click "Tools > Load transaction", sign it, broadcast it.
Or just convince Bitcoin Core to drop your transaction. Maybe upgrade to the latest version first, I don't know if that would help.

[nc50lc]

-snip-

Thanks for your help but this is too complicated for me.

I use bitcoin core QT.

You can also (temporarily) set mempoolfullrbf=1 option to let your node accept replacement to transactions without opt-in rbf flag.
Sign the transaction LoyceV provided you (output checks out), then broadcast it to your node's mempool.

Follow these simple steps:

• Go to "Settings->Options...", click "Open Configuration File" and your 'bitcoin.conf' file should open with your text editor.
• In your config file, type: mempoolfullrbf=1 in a new line and save the changes, then close the text editor.
• Close Bitcoin Core, wait for it to properly close, then launch it again.
• Once running, Open Core's console in "Window->Console", make sure that the correct wallet is selected in the console's drop-down menu;
  In that console window, type the command: signrawtransactionwithwallet "unsigned_raw_transaction" to sign the (unsigned_raw_transaction) LoyceV's transaction above.
• Copy the resulting signed raw transaction hex and use the command: sendrawtransaction "signed_raw_transaction" to broadcast it to your node and relay it to your peers.

Once done, you may disable the 'fullrbf' setting if you do not want to use it.

[xixou]

Thanks for your help but this is too complicated for me.

Export private key, import it into Electrum, click "Tools > Load transaction", sign it, broadcast it.
Or just convince Bitcoin Core to drop your transaction. Maybe upgrade to the latest version first, I don't know if that would help.

Broadcasting won't help as the fee is too low.
I just tried latest Bitcoin Core 27.0,
option to cancel the transaction is still grayed out (wallet is synced).


https://zupimages.net/up/24/24/t852.png

[LoyceV]

Export private key, import it into Electrum, click "Tools > Load transaction", sign it, broadcast it.

option to cancel the transaction is still grayed out (wallet is synced).

Try the above. Or nc50lc's solution.