- fastestFee: 3 sat/vB
- halfHourFee: 3 sat/vB
- hourFee: 3 sat/vB
- economyFee: 3 sat/vB
- minimumFee: 3 sat/vB
Topic: Mempool Observer Topic - page 23. (Read 21649 times)
- fastestFee: 4 sat/vB
- halfHourFee: 4 sat/vB
- hourFee: 4 sat/vB
- economyFee: 4 sat/vB
- minimumFee: 2 sat/vB
- fastestFee: 3 sat/vB
- halfHourFee: 3 sat/vB
- hourFee: 3 sat/vB
- economyFee: 3 sat/vB
- minimumFee: 3 sat/vB
- fastestFee: 4 sat/vB
- halfHourFee: 4 sat/vB
- hourFee: 4 sat/vB
- economyFee: 4 sat/vB
- minimumFee: 3 sat/vB
- fastestFee: 3 sat/vB
- halfHourFee: 3 sat/vB
- hourFee: 3 sat/vB
- economyFee: 3 sat/vB
- minimumFee: 2 sat/vB
Fees are really getting lower.
2 sat v/B got confirmation in many blocks recently according to mempool.space and feebuddy (same data lol)
I don`t see 1 sat v/B yet, but certainly this is an opportunity for consolidations.
2 sat v/B got confirmation in many blocks recently according to mempool.space and feebuddy (same data lol)
I don`t see 1 sat v/B yet, but certainly this is an opportunity for consolidations.
- fastestFee: 5 sat/vB
- halfHourFee: 4 sat/vB
- hourFee: 4 sat/vB
- economyFee: 4 sat/vB
- minimumFee: 3 sat/vB
- fastestFee: 3 sat/vB
- halfHourFee: 3 sat/vB
- hourFee: 3 sat/vB
- economyFee: 3 sat/vB
- minimumFee: 3 sat/vB
- fastestFee: 3 sat/vB
- halfHourFee: 3 sat/vB
- hourFee: 3 sat/vB
- economyFee: 3 sat/vB
- minimumFee: 2 sat/vB
- fastestFee: 4 sat/vB
- halfHourFee: 4 sat/vB
- hourFee: 4 sat/vB
- economyFee: 4 sat/vB
- minimumFee: 2 sat/vB
- fastestFee: 3 sat/vB
- halfHourFee: 3 sat/vB
- hourFee: 3 sat/vB
- economyFee: 3 sat/vB
- minimumFee: 3 sat/vB
- fastestFee: 4 sat/vB
- halfHourFee: 4 sat/vB
- hourFee: 4 sat/vB
- economyFee: 4 sat/vB
- minimumFee: 2 sat/vB
I didn't say it's an error. I said it's rejected by default, but it is valid (if included in a block). Try broadcasting a transaction that pays 0 sat/vb and see what I mean.
(also, there is a consensus default settings not to broadcast transactions below 1 sats/vbyte.
Anything between 0 and 1 sat/vb is by default rejected, but it is valid (can be included in a block). If you saw a negative fee rate, then that must have been an error by FeeBuddy, as that would create coins out of thin air. (Which is obviously invalid.)This is not an error.
Coinbase transactions are 0 satvB, and there are some empty blocks.
You can check here
https://mempool.space/tx/4c37b9a033422575f4d34638d16aff3831751d1a56f39d5f09d37a5d1140767d?mode=details
This is last block coinbase, 0 satvb fee rate.
Negative is wrong, probably it is some error in the scale? I will try to check
(also, there is a consensus default settings not to broadcast transactions below 1 sats/vbyte.
Anything between 0 and 1 sat/vb is by default rejected, but it is valid (can be included in a block). If you saw a negative fee rate, then that must have been an error by FeeBuddy, as that would create coins out of thin air. (Which is obviously invalid.) 
Speaking about graphs, I notice a negative value at around 8 August at midnight on the feebuddy charts.
How is it even possible to have a negative value in a graph tracking non negative values (also, there is a consensus default settings not to broadcast transactions below 1 sats/vbyte.
How is it even possible to have a negative value in a graph tracking non negative values (also, there is a consensus default settings not to broadcast transactions below 1 sats/vbyte.
- fastestFee: 3 sat/vB
- halfHourFee: 3 sat/vB
- hourFee: 3 sat/vB
- economyFee: 3 sat/vB
- minimumFee: 2 sat/vB
- fastestFee: 3 sat/vB
- halfHourFee: 3 sat/vB
- hourFee: 3 sat/vB
- economyFee: 3 sat/vB
- minimumFee: 3 sat/vB
- fastestFee: 4 sat/vB
- halfHourFee: 4 sat/vB
- hourFee: 4 sat/vB
- economyFee: 4 sat/vB
- minimumFee: 2 sat/vB
- fastestFee: 6 sat/vB
- halfHourFee: 5 sat/vB
- hourFee: 4 sat/vB
- economyFee: 4 sat/vB
- minimumFee: 3 sat/vB
Jump to: