Really unusual situation right now: the minrelayfeen of most mempools is very close to a typical next block transaction fee, due to a huge amount of txs at the same fee.

#m=image%2Fjpeg&dim=1080x1799&blurhash=%5DE7ws%40bAe*oGjZ-tj.s%2Bavt8RqW%3As%3BWUjZNDXBW%3FWGR%25RdkGR%3DR%3ANHNUj%7Bb1WGR*JVoNs%2CjcfhXRsSs%3Aawog-sfNW9oJWB&x=73772ab1298546496d9fbfbbbfc18861e2dfa46ea7044897a9bb79820f5de0eb

#m=image%2Fjpeg&dim=1079x1613&blurhash=%5EUFrkED%2B4%3DNHIWt6.YVyM%2CWEV%7Bocmlf%2Bb%5DbabuaeMWoto%40k9ouai1Kw_%24ioKxFWV%2BGS%23S%24bIX8n%25Ixj%3Ds%2BoJoIa%239%7EocxCoJsma%23Z%24bbkVj%5BkCjZ&x=fea78ab36f50590de36555928832704fb79859c70f7d7629500e9b2ae5cd600d

Reply to this note

Please Login to reply.

Discussion

High tide

Could it be that the screenshot it is taken as soon as the new block start to being mined? fee should raise up as mutch as block is near to get mined

Do you think the behavior of mempool.space's mempool is aligned with the programmed incentives of the bitcoin network, or is it still evolving as new participants learn?

But "empty" is something else

#m=image%2Fjpeg&dim=913x1920&blurhash=%5BKO%7ChM%3Fa%25K%253%7EpjdIUoMMv9ZjKNE01tL%3FHbH00t7RkoM_0RUIoae00t7t3j%5D%25NW%2Csqa%234mWCRkfh&x=ff342454701578b817f35dae65b6ddea7c60b45a762155522c6e24ec8b13a6b4

We had fun encountering this particular fee environment scenario in Core Lightning for the first time. The minimum acceptable feerate could end up the same as the proposed feerate (typically they are relatively far apart.) Then if one node increased by a single sat it would disable the channel and force a disconnect due to feerate disagreement. We now ensure a minimum offset (by the feerate proposer) to account for the next_block_feerate == min_relay_feerate situation.

Why would that surprise you? isn't that expected? can you elaborate more.