Bitcoin Forum
April 16, 2024, 11:54:26 AM *
News: Latest Bitcoin Core release: 26.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Surge in transactions + 1 MB blocks = what?  (Read 604 times)
Cubic Earth (OP)
Legendary
*
Offline Offline

Activity: 1176
Merit: 1018



View Profile
November 04, 2015, 12:11:58 AM
 #1

It's November, 2015.  Recent media attention and a rapid rise in the price of BTC are likely causes of the daily transaction count decisively moving above 150,000.  There looks to be a good chance of exceeding 200,000 daily transactions by the end of the month, if not sooner.

There will soon be more transactions submitted to the network than can be cleared by blocks.

It's clear that a transaction fee market for will develop, for better or worse.  But what about mempool growth?  And are there other backlog issues?  The stress tests came and went, but we might be entering a sustained period where transactional demand exceeds the networks capacity.  What will this look like with nodes and network we have today?
1713268466
Hero Member
*
Offline Offline

Posts: 1713268466

View Profile Personal Message (Offline)

Ignore
1713268466
Reply with quote  #2

1713268466
Report to moderator
If you want to be a moderator, report many posts with accuracy. You will be noticed.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
achow101
Moderator
Legendary
*
expert
Offline Offline

Activity: 3360
Merit: 6505


Just writing some code


View Profile WWW
November 04, 2015, 02:47:11 AM
 #2

It's clear that a transaction fee market for will develop, for better or worse.  But what about mempool growth?  And are there other backlog issues?  The stress tests came and went, but we might be entering a sustained period where transactional demand exceeds the networks capacity.  What will this look like with nodes and network we have today?
The Core Devs are working on a solution for the mempool issue (in fact it has already been merged to the master branch). This fix will officially be released in 0.12 sometime in early 2016 (feb I think). Basically the fix limits the mempool size and it will drop the transaction with the smallest fee in order to keep the mempool at a certain size which can be user defined.

Currently, the only fix is to change the minrelaytxfee which will prevent transactions under a certain fee and dust threshold from being accepted to the mempool and from being relayed by that node.

nicked
Full Member
***
Offline Offline

Activity: 175
Merit: 100


View Profile
November 04, 2015, 03:09:03 AM
 #3

Maybe they should just raise the blocksize limit.
Was
Member
**
Offline Offline

Activity: 75
Merit: 10

We are Satoshi.


View Profile
November 04, 2015, 03:36:53 AM
 #4

We knew this day would come. Round Two will be soon.... perhaps people will be more ambitious in implementing a solution this time around.

We Are Satoshi.
silverleafy
Sr. Member
****
Offline Offline

Activity: 538
Merit: 250


View Profile
November 04, 2015, 03:39:10 AM
 #5

They are having a Scaling Bitcoin conference in Hong Kong in December, but the likelihood of anything actually being done an consensus being reached is pretty low. I think part of the problems is that of the current proposals, only a few of them have actual implementations of what they are proposing.

Cubic Earth (OP)
Legendary
*
Offline Offline

Activity: 1176
Merit: 1018



View Profile
November 04, 2015, 04:35:17 AM
 #6

It's clear that a transaction fee market for will develop, for better or worse.  But what about mempool growth?  And are there other backlog issues?  The stress tests came and went, but we might be entering a sustained period where transactional demand exceeds the networks capacity.  What will this look like with nodes and network we have today?
The Core Devs are working on a solution for the mempool issue (in fact it has already been merged to the master branch). This fix will officially be released in 0.12 sometime in early 2016 (feb I think). Basically the fix limits the mempool size and it will drop the transaction with the smallest fee in order to keep the mempool at a certain size which can be user defined.

Currently, the only fix is to change the minrelaytxfee which will prevent transactions under a certain fee and dust threshold from being accepted to the mempool and from being relayed by that node.

Thanks for the synopsis.  The minrelaytxfee seems pretty straightforward to understand with respect to its effects on network.  If a tx does not meet the threshold, the tx will not propagate.  Is the behavior of the network if nodes have very different mempools well understood?
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!