Bitcoin Forum
May 24, 2024, 01:46:43 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Why blocks txn_count is always zero in response to getheaders  (Read 627 times)
Sergio_Demian_Lerner (OP)
Hero Member
*****
expert
Offline Offline

Activity: 554
Merit: 632


View Profile WWW
February 19, 2013, 03:25:42 AM
 #1

The wiki https://en.bitcoin.it/wiki/Protocol_specification#Block_Headers says that in response to getheaders, nodes send block headers with the field  txn_count set to zero. The code seems to agree.

Wouldn't be a lot more helpful if the returned headers contained the correct txn_count field so receivers could validate the block PoW before requesting the full block?

Thanks, Sergio.
gmaxwell
Moderator
Legendary
*
expert
Offline Offline

Activity: 4186
Merit: 8424



View Profile WWW
February 19, 2013, 03:50:21 AM
 #2

Wouldn't be a lot more helpful if the returned headers contained the correct txn_count field so receivers could validate the block PoW before requesting the full block?
This doesn't have anything to do with the POW.
Sergio_Demian_Lerner (OP)
Hero Member
*****
expert
Offline Offline

Activity: 554
Merit: 632


View Profile WWW
February 19, 2013, 04:29:24 AM
 #3

Ohh I see, txn_count is not included in the PoW hash computation...
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!