@dabs, if you're not in a rush I'd suggest just leaving it to its thing...
According to electrum, it should take 1.1 sats per byte to confirm in 5 hours (25 blocks) so give it up to about 8 hours and it should confirm.
Topic: [Aug 2022] Mempool empty! Use this opportunity to Consolidate your small inputs! - page 54. (Read 88546 times)
October 17, 2019, 11:32:26 AM
October 17, 2019, 10:15:48 AM
Just did a transaction a couple hours ago, and paid 1/sat. Still not confirmed, but monitoring it, it should confirm by the end of the day.
So it's even less than 1 sat/B ... all inputs are segwit. May have to wait a little longer than I expected. Hopefully 24 hours should be enough.
Quote
Summary
Size 510 (bytes)
Weight 1071
Received Time 2019-10-17 12:23:14
Lock Time Block: 599766
Inputs and Outputs
Fees 0.00000268 BTC
Fee per byte 0.525 sat/B
Fee per weight unit 0.25 sat/WU
Size 510 (bytes)
Weight 1071
Received Time 2019-10-17 12:23:14
Lock Time Block: 599766
Inputs and Outputs
Fees 0.00000268 BTC
Fee per byte 0.525 sat/B
Fee per weight unit 0.25 sat/WU
So it's even less than 1 sat/B ... all inputs are segwit. May have to wait a little longer than I expected. Hopefully 24 hours should be enough.
October 15, 2019, 04:05:37 AM
At the moment 10-12 Sat/Byte would be needed for a faster confirmation but it is getting back to lower fees slowly. 20 Sat/Byte was suggested just 30 minutes ago and the mempool is getting emptier since then.
October 14, 2019, 09:47:42 AM
I sent a 2 Sat per byte transaction a couple of days ago that seemed to confirm in the next block!
Fees are definitely very favourable atm... Don't miss your opportunity to consolidate.
Fees are definitely very favourable atm... Don't miss your opportunity to consolidate.
September 27, 2019, 05:33:23 PM
The weekends are a good time to get your transactions confirmed if you send them at a low fee (you're better off starting at a low fee and then bumping it up or cpfp if you're in a rush).
I noticed there's always a huge spike in transactions during daytime in the US too. Apparently this is due to BitMEX's "comically unoptimized" once-daily withdrawal system.
If you can wait until evening or overnight (US time) for confirmation, it's consistently cheaper. Getting 1 satoshi/byte transactions confirmed within a day has been consistently easy for the past couple months.
September 27, 2019, 12:47:25 PM
Can you get mempool estimates in core? Electrum let's you pick how far from the tip you want a transaction to be. If you need it confirmed quickly, it might be more helpful that cores default estimate which takes in the past couple of blocks over a few days.
The weekends are a good time to get your transactions confirmed if you send them at a low fee (you're better off starting at a low fee and then bumping it up or cpfp if you're in a rush). I think you pay less and get it confirmed faster that way (or you can send with a low fee to other places where they'll spend your coins with a high fee)...
The weekends are a good time to get your transactions confirmed if you send them at a low fee (you're better off starting at a low fee and then bumping it up or cpfp if you're in a rush). I think you pay less and get it confirmed faster that way (or you can send with a low fee to other places where they'll spend your coins with a high fee)...
September 27, 2019, 10:03:49 AM
I managed to use low fees too recently. If I'm not in a hurry and can wait 4 hours or more, I just set the fee lower. I look at the https://bitcoinfees.earn.com/ or other fee estimator websites and not rely on Core's estimate.
They also have an api if you don't want to look at all the graphs. https://bitcoinfees.earn.com/api/v1/fees/recommended
It's a little bit high at the moment with 1 hour fee = 20 sats, but during certain times (maybe evening in some countries or everyone is sleeping) the fees drop to 2 sats.
No matter what, this is still much faster than waiting for a check to clear, and if you're doing the consolidating you know there is no other attempt to double spend it.
They also have an api if you don't want to look at all the graphs. https://bitcoinfees.earn.com/api/v1/fees/recommended
It's a little bit high at the moment with 1 hour fee = 20 sats, but during certain times (maybe evening in some countries or everyone is sleeping) the fees drop to 2 sats.
No matter what, this is still much faster than waiting for a check to clear, and if you're doing the consolidating you know there is no other attempt to double spend it.
September 05, 2019, 07:08:48 AM
1 sat per byte is confirming really quickly this afternoon if you need to consolidate dust, now's your chance.
August 09, 2019, 09:50:09 AM
With 5000 sat fee, it took 211 minutes to confirm my transaction with 17 uncompressed legacy inputs. I signed the transactoin on an offline system (LIVE Linux DVD) with coinb.in.
Not bad for consolidating just over 3 kB of data
If fees ever reach their peak again, this same transaction would cost like $500.
Not bad for consolidating just over 3 kB of data
If fees ever reach their peak again, this same transaction would cost like $500.Yeah I have dropped to 3-5 sats.
It is all good.
August 09, 2019, 09:01:06 AM
With 5000 sat fee, it took 211 minutes to confirm my transaction with 17 uncompressed legacy inputs. I signed the transactoin on an offline system (LIVE Linux DVD) with coinb.in.
Not bad for consolidating just over 3 kB of data If fees ever reach their peak again, this same transaction would cost like $500.
Not bad for consolidating just over 3 kB of data
If fees ever reach their peak again, this same transaction would cost like $500. August 07, 2019, 09:11:16 AM
It is weird, I was trying to send a payment today and had the slider on 25 blocks and it predicted 1.1 sat per byte, within the next block it was hundredfold at about 100 sat per byte...
If you send a 1 sat per byte transaction now, it'll likely clear within six hours.
If you send a 1 sat per byte transaction now, it'll likely clear within six hours.
August 07, 2019, 03:22:41 AM
Today I was in a hurry, making a few payments for hosting. To prepare, I consolidated my 2 inputs into 1 at 1 sat/byte yesterday.
Even though coinb.in recommended 1 or 2 sat/byte, I went as high as 4 sat/byte. My transactions got confirmed in the next block.
Low fees can work! Meanwhile, Bitcoin Core and Mycelium recommended a 6 times higher fee.
I paid the first 2 services in 1 transaction. I could have saved more on fees if I would have sent all 3 outgoing payments at once, but the last one wasn't ready yet when I started.
Even though coinb.in recommended 1 or 2 sat/byte, I went as high as 4 sat/byte. My transactions got confirmed in the next block.
Low fees can work! Meanwhile, Bitcoin Core and Mycelium recommended a 6 times higher fee.
I paid the first 2 services in 1 transaction. I could have saved more on fees if I would have sent all 3 outgoing payments at once, but the last one wasn't ready yet when I started.
August 04, 2019, 11:49:43 PM
It depends on the wallet, if it keeps broadcasting (like Bitcoin Core does) it needs manual intervention if you want it to return to your wallet.
How about Electrum?as it was said, Electrum doesn't automatically broadcast transactions, user must do it.
as for transactions that drop out of memory pool, in older versions your wallet removed them from its database so it would have looked like as if the transaction never happened and you had to create it again from scratch.
ever since version 3.2.0 if a transaction is dropped from mempool or simply if the Electrum node you are connecting to doesn't have the transaction, your wallet won't remove it. instead it marks it as "local" so you still have access to it and can decide to remove it or rebroadcast the same thing again.
August 04, 2019, 02:34:27 PM
To sign an rbf transaction, you don't have to support it. You can merely flick a zero to a one and sign the new value (rbf is literally one byte if you check the bitcoin wiki spec). It makes more sense to sign it as an rbf if not just for debugging purposes.
August 04, 2019, 02:19:55 PM
They have stated "not yet supported" but I am not sure for how long that statement have been on their wiki page.
At least a year and a half judging by this Github issue.
What about Ledger or KeepKey?
KeepKey is far behind Trezor and Ledger, so you can guess what the answer is. It looks like Ledger does not support it either, but you can see such an option on one of the preview images. The only way is to pair all of these hardware wallets with Electrum. What a shame.
August 04, 2019, 02:02:06 PM
Unfortunately, they are not. I am sure that Trezor team is well aware of this since there is a wiki entry about it.
They have stated "not yet supported" but I am not sure for how long that statement have been on their wiki page.
Not sure if any other hardware wallet supports RBF in their native wallet without connecting to third party like Electrum.
What about Ledger or KeepKey?
August 04, 2019, 12:45:03 PM
Doesn't core automatically expire transactions after 7 days or sonething (or it used to)?
Bitcoin Core nodes used to drop transactions after 72 hours, but it has been extended to 2 weeks. Keep in mind that these are the default values and some nodes might keep transactions for a longer or shorter periods of time. -zapwallettxes parameter can be used to forget the unconfirmed transaction locally which allows you to create a new one. Technically, transactions never expire once you sign them. They become invalid once you spend previously signed inputs.
On online trezor are they marked rbf by default, if not we should suggest that?
Unfortunately, they are not. I am sure that Trezor team is well aware of this since there is a wiki entry about it.
August 04, 2019, 12:29:50 PM
How about Electrum?
Electrum does not rebroadcast transactions automatically. Nodes will keep the transaction for a couple of days and eventually drop it. All transactions are now marked as replacable by default if you use Electrum 3.1 or newer.
Doesn't core automatically expire transactions after 7 days or sonething (or it used to)?
On online trezor are they marked rbf by default, if not we should suggest that?
If so, it's really easy to connect hardware to mycelium as it scans all 3 derivation paths so you can use segwit and legacy...
August 04, 2019, 12:12:46 PM
How about Electrum?
Electrum does not rebroadcast transactions automatically. Nodes will keep the transaction for a couple of days and eventually drop it. All transactions are now marked as replacable by default if you use Electrum 3.1 or newer.
legendary
Activity: 2464
Merit: 3878
Hire Bitcointalk Camp. Manager @ r7promotions.com
August 04, 2019, 11:53:02 AM
It depends on the wallet, if it keeps broadcasting (like Bitcoin Core does) it needs manual intervention if you want it to return to your wallet.
How about Electrum? Jump to: