Bitcoin Forum

Bitcoin => Mining => Topic started by: ThePok on November 19, 2013, 12:31:18 AM



Title: Pools please rais blocksize limit!
Post by: ThePok on November 19, 2013, 12:31:18 AM
Pools please rais blocksize limit!

Most Blocks are actuly full!

Btc Guild at least makes 500kb Blocks, others should do so too :)


Title: Re: Pools please rais blocksize limit!
Post by: wizkid057 on November 19, 2013, 03:33:22 AM
Eligius (http://eligius.st/) makes 1MB blocks.  No reason not to.


Title: Re: Pools please rais blocksize limit!
Post by: dexX7 on November 19, 2013, 05:10:12 AM
Push. This needs attention!


Title: Re: Pools please rais blocksize limit!
Post by: solex on November 20, 2013, 05:18:29 AM
Push. This needs attention!

Reminds me of this situation:

https://bitcointalk.org/index.php?topic=149668.0


Title: Re: Pools please rais blocksize limit!
Post by: os2sam on November 20, 2013, 01:46:27 PM
Pools please rais blocksize limit!

Most Blocks are actuly full!

Btc Guild at least makes 500kb Blocks, others should do so too :)

Bull Butter!

The last 7 had ONLY ONE block larger than the 250K default!

Please, if you think this really needs to be done, use your gift of logic and human reason to put forth an intelligent argument for it!

It does nobody any good to stir up fear, or any other emotion, to cloud sound judgement.

The last time people went willy nilly about this subject it created a hard fork in the block chain and many people lost SERIOUS revenue over it.


Title: Re: Pools please rais blocksize limit!
Post by: stompix on November 20, 2013, 04:27:02 PM
Pools please rais blocksize limit!

Most Blocks are actuly full!

Btc Guild at least makes 500kb Blocks, others should do so too :)

Every block in the blockchain is full, can't push anything else in it.
Also , currently there are lots of blocks <250 , i don;t see any reason to panic , YET.


Title: Re: Pools please rais blocksize limit!
Post by: os2sam on November 20, 2013, 06:07:31 PM
Every block in the blockchain is full, can't push anything else in it.
Also , currently there are lots of blocks <250

Uh, which one is it?  Can it really be both?


Title: Re: Pools please rais blocksize limit!
Post by: stompix on November 20, 2013, 06:12:38 PM
Every block in the blockchain is full, can't push anything else in it.
Also , currently there are lots of blocks <250

Uh, which one is it?  Can it really be both?

Well , isn't every mined block full? you can't add anything to it even if it's 10kb.


Secondary , I haven't seen too many 1MB blocks lately.
Also, OP can u please show examples of those "Most Blocks are actuly full" ?

Height   Age   Transactions   Total Sent   Relayed By   Size (kB)
270648   21 minutes   223   3,539.36 BTC   BTC Guild   146.45
270647   22 minutes   1231   9,328.25 BTC   P2Pool   515.11
270646   24 minutes   1177   23,505.30 BTC   Eligius   589.85
270645   47 minutes   682   24,925.84 BTC   GHash.IO   243.29
270644   1 hour 21 minutes   598   15,655.15 BTC   BTC Guild   332.65
270643   1 hour 27 minutes   342   9,175.72 BTC   Eligius   213.97
270642   1 hour 36 minutes   679   18,706.02 BTC   GHash.IO   243.28


Title: Re: Pools please rais blocksize limit!
Post by: DeathAndTaxes on November 20, 2013, 06:14:14 PM
Well , isn't every mined block full?

No.  Full would be every block is exactly 1MB or at the time each block is created it is less than 1MB but there are none (as in zero) tx waiting confirmation.

It would be like asking is a gallon container with only 1/10th of a gallon in it full, no it is 10% full.


Title: Re: Pools please rais blocksize limit!
Post by: Gavin Andresen on November 22, 2013, 12:57:52 AM
It looks like maybe some pools have reacted; the average block size is going up:
  http://www.quandl.com/BCHAIN-Blockchain/AVBLS-Bitcoin-Average-Block-Size

For those that haven't, the relevant bitcoind command-line arguments are:

Code:
 -blockminsize=<n>      Set minimum block size in bytes (default: 0)
 -blockmaxsize=<n>     Set maximum block size in bytes (default: 250000)
 -blockprioritysize=<n> Set maximum size of high-priority/low-fee transactions in bytes (default: 27000)
 -mintxfee=<m.n>        Minimum  fee-per-kilobyte to qualify as fee-paying (default: 0.0001)

Adding:
Code:
blockmaxsize=500000
blockprioritysize=45000
... to your bitcoin.conf and re-starting bitcoind (or running with the command-line arguments) will really help with the transaction crunch.

I'm still hard at work (nearly done!) on making the reference implementation much smarter about transaction fees, but until wallet software gets smarter about fees we need to rely on big pools doing the right thing so Bitcoin users don't get frustrated by long transaction confirmation times.


Title: Re: Pools please rais blocksize limit!
Post by: solex on November 22, 2013, 01:29:00 AM
Great work! Looking forward to the tx fee improvements.


Title: Re: Pools please rais blocksize limit!
Post by: oakpacific on November 22, 2013, 01:48:25 AM
Can the pools adopt a stepwise approach to the problem? I.e., increase the blocksize by 5-10k a time, shouldn't have a noticeable influence on the propagation time, then wait to increase further only until other pools also catch up.


Title: Re: Pools please rais blocksize limit!
Post by: eleuthria on November 22, 2013, 02:18:17 AM
BTC Guild has been using a max size of 500KB and min size of 150KB for months (the only gap being when we had the 0.8 hardfork event and had to wait a few months to give everybody time to upgrade before allowing another potential hardfork block due to the bug in 0.7 and earlier versions).

Orphans are a concern for all pools, but my experience has shown that these sizes did not materially affect orphan rates, and actually reduced stale shares for users.  The minimum size helped our nodes clear out the memory pool faster, which is the biggest slowdown when a new block is found and bitcoind recalculates the priority of everything in the memory pool to build it's new blocks.


Title: Re: Pools please rais blocksize limit!
Post by: DeathAndTaxes on November 22, 2013, 02:33:28 AM
BTC Guild has been using a max size of 500KB and min size of 150KB for months (the only gap being when we had the 0.8 hardfork event and had to wait a few months to give everybody time to upgrade before allowing another potential hardfork block due to the bug in 0.7 and earlier versions).

Orphans are a concern for all pools, but my experience has shown that these sizes did not materially affect orphan rates, and actually reduced stale shares for users.  The minimum size helped our nodes clear out the memory pool faster, which is the biggest slowdown when a new block is found and bitcoind recalculates the priority of everything in the memory pool to build it's new blocks.

Great.  Thanks for the quote.  I am going to try and see if we can get similar info from other pools.  If we know what pools are doing then users and merchants can make more intelligent decisions.

Also 150KB for free txs per block?  Awesome that is pretty generous.

Looking through the memory pool a significant portion of the "really delayed" (>1 hour) paying transactions are ones that have unconfirmed inputs.  "child pays parent" patch can't come soon enough.


Title: Re: Pools please rais blocksize limit!
Post by: Trongersoll on November 22, 2013, 10:19:55 PM
So, am i reading this right? the OP is offering to reimburse the pools for orphanned blocks that may be the result of increasing the size of the blocks? And, they have some way to speed up the creation of new wallets?


Title: Re: Pools please rais blocksize limit!
Post by: eleuthria on November 23, 2013, 02:43:14 AM
Also 150KB for free txs per block?  Awesome that is pretty generous.

It's not 150KB free (that's blockprioritysize, not minblocksize).  The space set aside for freebies/low-fee is 27KB.  If it doesn't have 150KB of transactions, it will include extra freebies to fill up the space.