• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

Memory pool...Dash

Currently There is no mempool in Dash, remember mempools are generated when there's so much traffic that not all transactions broadcasted in a certain period of time can be included in the current block, leaving them "on hold" waiting to be included in the next block.

Someone asked a similar question regarding "what if Dash was loaded with the same amount of tx in bitcoin right now? would it be congested?"

https://www.reddit.com/r/dashpay/comments/7mh203/if_dash_were_as_popular_as_bitcoin_would_it_be/

and the answer is no, Dash can currently support a lot more transactions than bitcoin currently HAS, meaning. even if every bitcoin transactions right now were to be done in the dash blockchain, it would still not generate a mempool.
 
Currently There is no mempool in Dash, remember mempools are generated when there's so much traffic that not all transactions broadcasted in a certain period of time can be included in the current block, leaving them "on hold" waiting to be included in the next block.

Someone asked a similar question regarding "what if Dash was loaded with the same amount of tx in bitcoin right now? would it be congested?"

https://www.reddit.com/r/dashpay/comments/7mh203/if_dash_were_as_popular_as_bitcoin_would_it_be/

and the answer is no, Dash can currently support a lot more transactions than bitcoin currently HAS, meaning. even if every bitcoin transactions right now were to be done in the dash blockchain, it would still not generate a mempool.
It's not quite accurate tbh. There is a mempool but there is no huge backlog because mempool is cleared at every block with no issues (all txes from mempool fit into the block).

You can use getmempoolinfo rpc to see current mempool stats e.g.

Code:
> dash-cli getmempoolinfo
{
  "size": 49,
  "bytes": 17089,
  "usage": 59936,
  "maxmempool": 300000000,
  "mempoolminfee": 0.00000000
}
 
It's not quite accurate tbh. There is a mempool but there is no huge backlog because mempool is cleared at every block with no issues (all txes from mempool fit into the block).

You can use getmempoolinfo rpc to see current mempool stats e.g.

Code:
> dash-cli getmempoolinfo
{
  "size": 49,
  "bytes": 17089,
  "usage": 59936,
  "maxmempool": 300000000,
  "mempoolminfee": 0.00000000
}

Yes I stand corrected, the mempool exists, what I meant to say is that there is no backlog because the mempool is cleared every block, just like you said !
 
Back
Top