Bitcoin Forum
May 11, 2024, 02:40:36 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Question about 'Height' certainty  (Read 715 times)
RangerK (OP)
Member
**
Offline Offline

Activity: 93
Merit: 10



View Profile WWW
March 27, 2014, 11:08:35 AM
 #1

I assume that faking the blockchain 'height' is not a serious threat to the bitcoin protocol.  It isn't on the list of vulnerabilities: https://en.bitcoin.it/wiki/Common_Vulnerabilities_and_Exposures

I'm trying to better understand the process by which it is prevented.  Any references are appreciated.  Thanks!

edit:  I think what I may be asking for is the background workings of the API call 'getblockcount' -- https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_calls_list

Cool ---> Who will mine the next 777 Block??? Place your bets at block777.com!!!
1715395236
Hero Member
*
Offline Offline

Posts: 1715395236

View Profile Personal Message (Offline)

Ignore
1715395236
Reply with quote  #2

1715395236
Report to moderator
Even in the event that an attacker gains more than 50% of the network's computational power, only transactions sent by the attacker could be reversed or double-spent. The network would not be destroyed.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715395236
Hero Member
*
Offline Offline

Posts: 1715395236

View Profile Personal Message (Offline)

Ignore
1715395236
Reply with quote  #2

1715395236
Report to moderator
1715395236
Hero Member
*
Offline Offline

Posts: 1715395236

View Profile Personal Message (Offline)

Ignore
1715395236
Reply with quote  #2

1715395236
Report to moderator
kjj
Legendary
*
Offline Offline

Activity: 1302
Merit: 1025



View Profile
March 27, 2014, 11:32:52 AM
 #2

Blocks come in discrete lumps.  You always know how many of them you have.

17Np17BSrpnHCZ2pgtiMNnhjnsWJ2TMqq8
I routinely ignore posters with paid advertising in their sigs.  You should too.
smolen
Hero Member
*****
Offline Offline

Activity: 524
Merit: 500


View Profile
March 31, 2014, 03:13:03 AM
 #3

I assume that faking the blockchain 'height' is not a serious threat to the bitcoin protocol.  It isn't on the list of vulnerabilities: https://en.bitcoin.it/wiki/Common_Vulnerabilities_and_Exposures

I'm trying to better understand the process by which it is prevented.  Any references are appreciated.  Thanks!

edit:  I think what I may be asking for is the background workings of the API call 'getblockcount' -- https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_calls_list
Hashing process could be optimized by mining for blocks with only one constant coinbase transaction - so no other transactions will fit in the block. BIP 0034 prevents it.

Of course I gave you bad advice. Good one is way out of your price range.
kjj
Legendary
*
Offline Offline

Activity: 1302
Merit: 1025



View Profile
March 31, 2014, 11:47:32 AM
 #4

Hashing process could be optimized by mining for blocks with only one constant coinbase transaction - so no other transactions will fit in the block. BIP 0034 prevents it.

No, BIP 34 prevents duplicate transactions because they were an ugly corner case.

It was heavily discussed, so searching these forums for it will provide enlightenment on the matter.  The short version is that allowing duplicate generate transactions was surprising, but realizing that they could be spent and then mined again was even more surprising.  In theory, whole strings of transactions with identical IDs could be made that way.

17Np17BSrpnHCZ2pgtiMNnhjnsWJ2TMqq8
I routinely ignore posters with paid advertising in their sigs.  You should too.
smolen
Hero Member
*****
Offline Offline

Activity: 524
Merit: 500


View Profile
April 03, 2014, 02:24:30 AM
 #5

Hashing process could be optimized by mining for blocks with only one constant coinbase transaction - so no other transactions will fit in the block. BIP 0034 prevents it.

No, BIP 34 prevents duplicate transactions because they were an ugly corner case.

It was heavily discussed, so searching these forums for it will provide enlightenment on the matter.  The short version is that allowing duplicate generate transactions was surprising, but realizing that they could be spent and then mined again was even more surprising.  In theory, whole strings of transactions with identical IDs could be made that way.

That's a part of Bitcoin history I've missed Smiley Looks like easier mining of empty blocks with duplicate coinbase transactions was not considered as a possible attack, but developers sticked to their clever hack of using transaction hash as an key. Anyway, the mining advantage would be small, something like 2% and this vulnerability was fixed without being discovered Smiley

Of course I gave you bad advice. Good one is way out of your price range.
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!