Not sure, I guess you could keep adjusting the permitted maximum fee rate in the wallet to see how high you have to set it before it begins, but I assume this round will charge the same base fee as the last one which was 377 sat/vbyte
Читать полностью…zkSNACKs added additional adjustments to the Core estimator to keep it from overpaying (but not from underpaying)
Читать полностью…https://mempool.space/tx/fb2f8cd19de748a6d89346a873e21fadfd8eb037e63fa865abe48e735c39ec6b wtf 408 sat/vbyte?
Читать полностью…It was 36 block confirmation target before and I made it a little faster to 34 to see how much difference it makes.
Читать полностью…Last round as 33 sat/vbyte, so it's good again: https://mempool.space/tx/6e80141db08e1e21850740cd8212e12ea677032ecd94ea03b1f73e8c5977bde4
Читать полностью…Yes, Bitcoin Core node generates an estimate based on previous blocks that were confirmed. However, it doesn't look at the current pending mempool.
Читать полностью…It doesn't seem like any dev has picked that issue up yet, so I doubt it's fixed yet.
Читать полностью…