Bitcoin Forum
May 27, 2024, 12:59:49 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: What's new in version 2 of Block header message ?  (Read 1262 times)
Yves Cuicui (OP)
Newbie
*
Offline Offline

Activity: 18
Merit: 0



View Profile
August 30, 2013, 05:46:09 PM
 #1

The version field in block header message is now '2'.
Does someone know what is the difference compared to version 1?
Thanks
Peter Todd
Legendary
*
expert
Offline Offline

Activity: 1120
Merit: 1150


View Profile
August 30, 2013, 05:57:49 PM
 #2

Read this: https://en.bitcoin.it/wiki/BIP_0034

Yves Cuicui (OP)
Newbie
*
Offline Offline

Activity: 18
Merit: 0



View Profile
August 30, 2013, 06:48:16 PM
 #3

Many thanks
fpgaminer
Hero Member
*****
Offline Offline

Activity: 560
Merit: 517



View Profile WWW
August 31, 2013, 03:16:00 AM
 #4

Quote
95% rule ("Point of no return"): If 950 of the last 1,000 blocks are version 2 or greater, reject all version 1 blocks. (testnet3: 75 of last 100)
Are we here yet on mainnet?

joshlang
Newbie
*
Offline Offline

Activity: 26
Merit: 0


View Profile
August 31, 2013, 03:49:39 AM
 #5

Yeah - At block 227930, the previous 1000 contained the supermajority of 950.
fpgaminer
Hero Member
*****
Offline Offline

Activity: 560
Merit: 517



View Profile WWW
August 31, 2013, 07:53:35 AM
 #6

Quote
Yeah - At block 227930, the previous 1000 contained the supermajority of 950.
Very cool  Cool  Thank you for taking the time to look that up.

Yves Cuicui (OP)
Newbie
*
Offline Offline

Activity: 18
Merit: 0



View Profile
September 05, 2013, 01:34:46 PM
 #7

Anyway, this is not an information we can rely on.

I notice many blocks pretending to be version 2 but showing bad height encode values

See
http://blockexplorer.com/block/00000000000005d024e86337ca13439b7f3dbd5e1a005b1dbe510150d45b6e98 is block 200433 and pretends to be 436591499
http://blockexplorer.com/block/00000000000003c6947e260dc80d6ab426771a7ba9d8d5fb58ff66a0db26c361 is block 199914and pretends to be 436591499

May be such blocks must not be accepted by the network as the BIP34 is now enforced?
kjj
Legendary
*
Offline Offline

Activity: 1302
Merit: 1025



View Profile
September 05, 2013, 02:23:33 PM
 #8

Anyway, this is not an information we can rely on.

I notice many blocks pretending to be version 2 but showing bad height encode values

See
http://blockexplorer.com/block/00000000000005d024e86337ca13439b7f3dbd5e1a005b1dbe510150d45b6e98 is block 200433 and pretends to be 436591499
http://blockexplorer.com/block/00000000000003c6947e260dc80d6ab426771a7ba9d8d5fb58ff66a0db26c361 is block 199914and pretends to be 436591499

May be such blocks must not be accepted by the network as the BIP34 is now enforced?

Early on, there was some debate about the proper encoding.  See this discussion for information on why the bogus encodings were allowed (specifically a post from gmaxwell on July 2nd).

17Np17BSrpnHCZ2pgtiMNnhjnsWJ2TMqq8
I routinely ignore posters with paid advertising in their sigs.  You should too.
Yves Cuicui (OP)
Newbie
*
Offline Offline

Activity: 18
Merit: 0



View Profile
September 05, 2013, 02:35:44 PM
 #9

Do you mean that some miners start building v2 blocks on main network while the debate was not closed?
kjj
Legendary
*
Offline Offline

Activity: 1302
Merit: 1025



View Profile
September 05, 2013, 03:00:31 PM
 #10

For something like this, a supermajority of miners have to move in lockstep, or there is risk of forking.

17Np17BSrpnHCZ2pgtiMNnhjnsWJ2TMqq8
I routinely ignore posters with paid advertising in their sigs.  You should too.
joshlang
Newbie
*
Offline Offline

Activity: 26
Merit: 0


View Profile
September 05, 2013, 06:13:07 PM
 #11

Anyway, this is not an information we can rely on.

I notice many blocks pretending to be version 2 but showing bad height encode values

See
http://blockexplorer.com/block/00000000000005d024e86337ca13439b7f3dbd5e1a005b1dbe510150d45b6e98 is block 200433 and pretends to be 436591499
http://blockexplorer.com/block/00000000000003c6947e260dc80d6ab426771a7ba9d8d5fb58ff66a0db26c361 is block 199914and pretends to be 436591499

May be such blocks must not be accepted by the network as the BIP34 is now enforced?

After block 227930, it's information you can rely on.
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!