Bitcoin Forum
May 24, 2024, 03:43:27 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 [2]  All
  Print  
Author Topic: ELI5 for BIP100?  (Read 1344 times)
achow101
Staff
Legendary
*
Offline Offline

Activity: 3402
Merit: 6648


Just writing some code


View Profile WWW
August 27, 2015, 08:02:51 PM
 #21

There is a historical limit of 32 Mb on Bitcoin message sizes, thus also limiting blocks since blocks are passed in the block p2p message.

Miners vote for block sizes within the range of half of the current to double the current block size (e.g if the block size is 1 mb, then miners can vote to change the block size to somewhere between 0.5 mb and 2 mb. They cannot go below 0 or greater than 32 mb whatsoever. The hard fork is scheduled to occur after 90% of the last 12000 blocks support BIP 100 and the date is past Jan 11 2016. Presumably (the bip is unclear on when the votes are counted) the block size limit is also changed every 12000 blocks. Miners vote by encoding ‘BV’+BlockSizeRequestValue into the coinbase script to vote for their block size limit. The final size is determined by dropping the highest 20% and lowest 20% votes and then choosing the minimum (the bip is not very clear on what is actually chosen).
If he said that, he is really bad at math. Wink
If you drop the lowest 20% and take the minimum, it doesn't matter if you also drop the highest 20%, since the minimum stays the same
That is what I understood from the pdf, but I could be wrong. Someone on the mailing list did ask him for clarification on this but he did not respond yet.

CryptoEdge
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
August 27, 2015, 08:49:43 PM
 #22

i guess you are right, it cant pass 32 MB.

Not only that. It gives all voting right to pool operators. End users have no right to exercise. Size of mempool needs to be considered. My vote goes for this proposal.

Dynamic Blocksize makes alot of sense. It should be made to scale dynamically as adoption and growth scale organically.
achow101
Staff
Legendary
*
Offline Offline

Activity: 3402
Merit: 6648


Just writing some code


View Profile WWW
August 28, 2015, 01:43:42 AM
 #23

There was a reply by Garzik to the question about how the votes are counted. The block size chosen is the 20th percentile block, meaning that the supposed 21% attack cannot work. This means that it will choose the block size which is greater than 20% of the all of the other votes. Even if a miner had 21% of the mining power, they cannot change or force a minimum since all of their blocks would not be in the 20th percentile, they would probably be in the 1st or 2nd percentile.

Finksy
Legendary
*
Offline Offline

Activity: 1022
Merit: 1003



View Profile
August 28, 2015, 02:16:20 AM
 #24

Anyone else notice the size of the last block?

974.74 kb  & 2,320 transactions.

https://blockchain.info/block/00000000000000000971eaf8d7ad55052ae8a109f2e723a77dec911c0cadb850


IBM 2880W PSU Packages: https://bitcointalk.org/index.php?topic=966135 IBM 4K PSU Breakout Boards & Packages: https://bitcointalk.org/index.php?topic=1308296 
Server PSU-powered GPU rig solutions! https://bitcointalk.org/index.php?topic=1864539  Wallet address: 1GWQYCv22cAikgTgT1zFuAmsJ9fFqq9TXf 
HostFat
Staff
Legendary
*
Offline Offline

Activity: 4242
Merit: 1203


I support freedom of choice


View Profile WWW
August 28, 2015, 02:41:59 AM
 #25

With BIP100 it is possible to arrive to 32 MB in 12 months Grin

NON DO ASSISTENZA PRIVATA - http://hostfatmind.com
meono
Full Member
***
Offline Offline

Activity: 196
Merit: 100


View Profile
August 28, 2015, 03:24:32 AM
 #26

i guess you are right, it cant pass 32 MB.

Not only that. It gives all voting right to pool operators. End users have no right to exercise. Size of mempool needs to be considered. My vote goes for this proposal.

Dynamic Blocksize makes alot of sense. It should be made to scale dynamically as adoption and growth scale organically.

I disagree the dynamic blocksize limit does not make any sense whatsoever. Remember we're talking about limit not the blocksize.

If we have parameters that determizr the blocksize limit then we should not have limit at all. We're governing the wrong target.
Pages: « 1 [2]  All
  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!