Who feels like us? 💜
It took a coal mine accident in China, which caused a blackout, drop in hash rate and very high fees. Eventually this lead to a lower difficulty while miners were back online.TL;DR: enjoy it while it lasts!
Topic: [Aug 2022] Mempool empty! Use this opportunity to Consolidate your small inputs! - page 33. (Read 83494 times)
May 07, 2021, 05:42:03 AM
TL;DR: enjoy it while it lasts!
May 07, 2021, 05:37:29 AM
@PocketBitcoin
Mempool soon to clear 1 sats/vbyte transactions which hasn't happened since early January 🔥🥰
Who feels like us? 💜
https://twitter.com/pocketbitcoin/status/1390595067547721728?s=21
Mempool soon to clear 1 sats/vbyte transactions which hasn't happened since early January 🔥🥰
Who feels like us? 💜
https://twitter.com/pocketbitcoin/status/1390595067547721728?s=21
May 07, 2021, 03:48:15 AM
Update: In the past hours, transactions with 2.2 sat/byte have been confirmed.
My Bitcoin Core shows 168 MB waiting in mempool, Johoe's site shows 79 MB. I don't know what causes the difference.
It looks like the coming weekend is going to be a great chance to consolidate small inputs, 2 sat/byte or less might just get through. Fees haven't been this low in 4 months.
My Bitcoin Core shows 168 MB waiting in mempool, Johoe's site shows 79 MB. I don't know what causes the difference.
It looks like the coming weekend is going to be a great chance to consolidate small inputs, 2 sat/byte or less might just get through. Fees haven't been this low in 4 months.
May 05, 2021, 05:06:05 AM
Fees are still very low, which is quite rare for a Wednesday. Consolidate small inputs while it lasts!
Update: 4 sat/byte is currently enough for a fast confirmation!
Update: 4 sat/byte is currently enough for a fast confirmation!
May 02, 2021, 04:53:27 AM
And the week-end is far from over 
Miners are chewing their way through mempool:
(Screenshot taken from jochen-hoenicke.de)
May 02, 2021, 04:42:55 AM
At the moment, 8 sat/byte is enough for a fast confirmation.
In case it helps anyone, I've sent a tx today at 7.7 sat/vByte and it's already confirmed. And the week-end is far from over
April 11, 2021, 09:12:20 AM
It's Sunday and the mempool looks good just like last week at this time. I am sure that many of the transactions in the 5-7 sat/vByte range will be confirmed today. Right now, 7-8 sat/vByte is probably enough for a next block confirmation. Keep your eyes on the mempool and consolidate your inputs while the fees are down.
A couple of hours ago I got confirmed a transaction of 5 sat-vByte, the one I sent three weeks ago:
... I've just tried now 5 sat/vb with the address I had with the lowest amount, like 5/6$, I think this thread is going to be useful for me.
April 11, 2021, 05:12:30 AM
It's Sunday and the mempool looks good just like last week at this time. I am sure that many of the transactions in the 5-7 sat/vByte range will be confirmed today. Right now, 7-8 sat/vByte is probably enough for a next block confirmation. Keep your eyes on the mempool and consolidate your inputs while the fees are down.
April 05, 2021, 11:13:54 AM
Right now, you need 70-80 sats to get in the next 3-5 blocks the way it stands now.
There was no block found in the last 55 minutes, hence I expect that there could be soon another opportunity to send transactions at under 10 sat/vByte.
I got one confirmed yesterday at 10 sats per byte (very fast conf). It has 120 conformations now so only took 4 hours at most to confirm.
April 04, 2021, 02:43:11 PM
Right now, you need 70-80 sats to get in the next 3-5 blocks the way it stands now.
There was no block found in the last 55 minutes, hence I expect that there could be soon another opportunity to send transactions at under 10 sat/vByte.
April 04, 2021, 02:20:13 PM
Today really was a good day for those who were waiting for good opportunities to consolidate their inputs. I had a next block confirmation using a transaction fee of 6 sat/vByte. I made another consolidation at a little above 5 sats which got confirmed in an hour. I was planning to send some other less important transactions but the window has passed. Right now, you need 70-80 sats to get in the next 3-5 blocks the way it stands now.
April 04, 2021, 05:38:38 AM
In the past weeks, I've seen fees rise a lot. At the moment, 7 sat/byte is enough for a fast confirmation. If you're not in a hurry, you can go lower: I've just had a 5 sat/byte transaction that confirmed today (after several days). In this transaction I double spent a transaction from February, which didn't confirm with 2 sat/byte.
I had a transaction not confirmed since February 11 2021 which is over a month ago, luckily confirmed in two hours ago, the transaction is 5 sat/vbyte. 3a7101abfeba0b5ea31777f97b8c27a0705e197e087aa2ba676cebf8816bf88b
March 26, 2021, 08:09:14 AM
edit: assuming this is the 1Merit address this may actually be a bug in electrum with uncompressed public keys.
That makes sense, will you report the bug?unfortunately my hard disk blew up a while ago and i lost some of my login passwords including the one to my github account. it would be quicker for someone with access to report it than me creating a new account for this.
Noted: boating accident. lost all bitcoins too.
March 25, 2021, 04:28:01 PM
Today, someone added about 35 MB transactions with 6 sat/byte fee to mempool.
That's about 2 Bitcoin in fees for what looks like consolidating about a quarter million inputs.
Anyone who's hoping to get his 5 sat/byte transaction confirmed any time soon: good luck!
That's about 2 Bitcoin in fees for what looks like consolidating about a quarter million inputs.
Anyone who's hoping to get his 5 sat/byte transaction confirmed any time soon: good luck!
March 24, 2021, 06:31:38 AM
my fee turned out to be only 6.2 sat/byte.
This transaction was confirmed last night. Fees have been slowly dropping for 4.5 days now:
Don't underestimate the current mempool size though: there's 13 vMB to clear before confirming transactions under 6 sat/byte, and 61 vMB for transactions under 4 sat/byte.
March 23, 2021, 12:35:22 PM
edit: assuming this is the 1Merit address this may actually be a bug in electrum with uncompressed public keys.
That makes sense, will you report the bug?unfortunately my hard disk blew up a while ago and i lost some of my login passwords including the one to my github account. it would be quicker for someone with access to report it than me creating a new account for this.
March 23, 2021, 11:28:25 AM
If you can live with a slightly restricted character set, you can make native segwit (bc1qxxxx) vanity addresses... even legacy compatible segwit (3xxxx) vanity addresses.
Like bc1qfeedch80zxged6apxyknugt67e47nsw00tpguu for example. Feed Ch-ildren? heh... used to be 1food.
Like bc1qfeedch80zxged6apxyknugt67e47nsw00tpguu for example. Feed Ch-ildren? heh... used to be 1food.
March 22, 2021, 05:51:39 PM
edit: assuming this is the 1Merit address this may actually be a bug in electrum with uncompressed public keys.
That makes sense, will you report the bug? March 22, 2021, 01:44:58 PM
Isn't it just because the signature part makes the transaction larger?
it does but the estimator on your online wallet should take that into consideration when showing the fee/byte values. that extra zero byte doesn't happen that often and the signers nowadays usually choose another nonce to get a lower r to avoid that extra byte.
edit: assuming this is the 1Merit address this may actually be a bug in electrum with uncompressed public keys.
if we remove the 15 extra bytes of uncompressed pubkeys (15*32=480 byte) from the size the fee turns into 7.5 sat/byte. that means the estimator messed up here not knowing the pubkey takes 65 byte not 33.
March 22, 2021, 01:27:16 PM
You will really need to be patient, legacy address will make the transaction longer to be confirmed
That's not true when using the same number of sats/(v)byte.are you using the new versions of electrum or the old ones?
I used Electrum 4.0.9.Quote
if you shared the transaction (or maybe another one on testnet that looks like it if privacy is a concern) it could be analyzed better.
The address is publicly known already.Quote
the only time the size is changed is when the signatures you produce end up needing an additional 00 at the beginning of their r value when they are encoded. depending on number of signatures this could increase but i don't think enough to decrease the fee by 1 sat/byte.
Isn't it just because the signature part makes the transaction larger? Jump to: