Mempool if full, but what does that actually mean? - page 2.

NeuroticFish

legendary

Activity: 3668

Merit: 6382

Looking for campaign manager? Contact icopress!

Quote from: T0asti on November 15, 2022, 07:27:18 PM

It explains how we got there, but doesn't elaborate on what that means for Bitcoin.

I think that a better term would be "congested".
What it means for bitcoin, nothing.
What it means for miners, a bit more income.
What it means for bitcoiners, a bit higher transaction fees if they're in a hurry. If nothing special happens, all this will be gone in less than 5 days.

o_e_l_e_o

legendary

Activity: 2268

Merit: 18711

Quote from: hosseinimr93 on November 15, 2022, 07:46:02 PM

I wonder where you got the 354 MB from. That's wrong.
Currently, there are around 150 MB of transactions waiting for confirmation in the mempool and even a transaction paying only 1 sat/vbyte should be able to enter the mempool of any node.

Quote from: Charles-Tim on November 15, 2022, 07:56:41 PM

I checked https://mempool.observer and I saw 10294 unconfirmed transactions (138.35 MB) which should be correct.

Quote from: tranthidung on November 15, 2022, 08:39:54 PM

Double check, it is a little bit less than 135 vMb in mempool according to Johoe's site

You are all mixing up your numbers here.

The 300MB limit is the RAM usage of the deserialized data for all the transactions in the mempool. This is not the same as the space that these transaction will take up in a block (either in terms of virtual bytes or raw bytes). Of course every node has its own mempool, but even identical mempools would result in different RAM usage between nodes due to different hardware, node software, OS, and so on.

Although we currently have around 120 vMB of unconfirmed transactions in the mempool, when deserialized these transactions are using around 300 MB of memory.

Here is a good site to visualize this: https://statoshi.info/d/000000020/memory-pool?orgId=1&from=now-2d&to=now
The green line in the top graph shows the total transaction size, while the white line in the middle graph shows the memory usage of those transactions.

jackg

copper member

Activity: 2856

Merit: 3071

https://bit.ly/387FXHi lightning theory

Also, it sounds like it's being used because it's the size you want to make for the best discoverability by the network for a transaction to not be forgotten by most nodes that use default values (which might make it less likely to confirm).

A lot of transactions fall out of the mempool after 2 weeks too but this might mean a transaction at 280mb could have a chance to confirm at a point in the week when there are fewer transactions (such as the weekend).

tranthidung

legendary

Activity: 2310

Merit: 4085

Farewell o_e_l_e_o

Double check, it is a little bit less than 135 vMb in mempool according to Johoe's site

It will take a lot of time for miners to congest all these waiting transactions and additional ones in future. It will force others have to join the fee race if they can not wait.

Important to use Replace-by-Fee if you don't want to join the fee race at the moment but still want to have an option to bump fee for your transaction later and get a higher priority to be confirmed by miners.

Child-Pay-For-Parents is more complicated than Replace-by-Fee so I strongly recommend to use opt-in RBF at start.

Charles-Tim

legendary

Activity: 1512

Merit: 4795

Leading Crypto Sports Betting & Casino Platform

Quote from: hosseinimr93 on November 15, 2022, 07:46:02 PM

Quote from: T0asti on November 15, 2022, 07:27:18 PM

Right now we are at 354 MB / 300 MB,

I wonder where you got the 354 MB from. That's wrong.
Currently, there are around 150 MB of transactions waiting for confirmation in the mempool and even a transaction paying only 1 sat/vbyte should be able to enter the mempool of any node.

I guess he got it from https://mempool.space

I checked https://mempool.observer and I saw 10294 unconfirmed transactions (138.35 MB) which should be correct.

hosseinimr93

legendary

Activity: 2380

Merit: 5213

Quote from: T0asti on November 15, 2022, 07:27:18 PM

Right now we are at 354 MB / 300 MB,

I wonder where you got the 354 MB from. That's wrong.
Currently, there are around 150 MB of transactions waiting for confirmation in the mempool and even a transaction paying only 1 sat/vbyte should be able to enter the mempool of any node.

bitmover

legendary

Activity: 2352

Merit: 6089

bitcoindata.science

Quote from: T0asti on November 15, 2022, 07:27:18 PM

It explains how we got there, but doesn't elaborate on what that means for Bitcoin.

Right now we are at 354 MB / 300 MB, but if that doesn't have any effect why are we even talking about a limit in the first place?

Mempool size is a node configuration. Some nodes may set higher limit.
The main reason to have a mempool size limit is to protect the network against a denial of service attack.

It doesn't mean much for bitcoin when it is full. You might need to rebroadcast your transaction if it is out of the 300mb mempool, but not necessarily.

If you are making a new transaction now and mempool is full, just send a higher fee and you will get ahead other transactions.

T0asti

newbie

Activity: 7

Merit: 12

According to https://mempool.space/docs/faq:

What does it mean for the mempool to be "full"?
When a Bitcoin transaction is made, it is stored in a Bitcoin node's mempool before it is confirmed into a block. When the rate of incoming transactions exceeds the rate transactions are confirmed, the mempool grows in size.
The default maximum size of a Bitcoin node's mempool is 300MB, so when there are 300MB of transactions in the mempool, we say it's "full".

It explains how we got there, but doesn't elaborate on what that means for Bitcoin.

Right now we are at 354 MB / 300 MB, but if that doesn't have any effect why are we even talking about a limit in the first place?

Topic: Mempool if full, but what does that actually mean? - page 2. (Read 457 times)