Bitcoin Forum
January 20, 2017, 04:13:32 AM *
News: Latest stable version of Bitcoin Core: 0.13.2  [Torrent]. (New!)
 
   Home   Help Search Donate Login Register  
Pages: « 1 [2]  All
  Print  
Author Topic: IMPORTANT: April 1 deadline for BIP16 support  (Read 3550 times)
Gavin Andresen
Legendary
*
Offline Offline

Activity: 1652


Chief Scientist


View Profile WWW
April 19, 2012, 06:36:55 PM
 #21

I have a question
Why we have "block/transaction versions" if we don't use it? There was a good moment to increment version number and later use it in such way: if Miner gets a "strange" block with increased version number -- it is a signal for him to check for new soft. We could have avoided many of lost orphaned blocks
We should have, but "we" didn't think of that in time.

I've been working on a "how to do it better next time" document:
  https://gist.github.com/2355445


How often do you get the chance to work on a potentially world-changing project?
There are several different types of Bitcoin clients. The most secure are full nodes like Bitcoin-Qt, but full nodes are more resource-heavy, and they must do a lengthy initial syncing process. As a result, lightweight clients with somewhat less security are commonly used.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1484885612
Hero Member
*
Offline Offline

Posts: 1484885612

View Profile Personal Message (Offline)

Ignore
1484885612
Reply with quote  #2

1484885612
Report to moderator
1484885612
Hero Member
*
Offline Offline

Posts: 1484885612

View Profile Personal Message (Offline)

Ignore
1484885612
Reply with quote  #2

1484885612
Report to moderator
1484885612
Hero Member
*
Offline Offline

Posts: 1484885612

View Profile Personal Message (Offline)

Ignore
1484885612
Reply with quote  #2

1484885612
Report to moderator
DeathAndTaxes
Donator
Legendary
*
Offline Offline

Activity: 1218


Gerald Davis


View Profile
April 19, 2012, 06:40:49 PM
 #22

I've been working on a "how to do it better next time" document:
  https://gist.github.com/2355445

Nice read.  Lots of good ideas/concepts.
deepceleron
Legendary
*
Offline Offline

Activity: 1470



View Profile WWW
May 06, 2012, 07:56:58 AM
 #23

I have a question
Why we have "block/transaction versions" if we don't use it? There was a good moment to increment version number and later use it in such way: if Miner gets a "strange" block with increased version number -- it is a signal for him to check for new soft. We could have avoided many of lost orphaned blocks
We should have, but "we" didn't think of that in time.

I've been working on a "how to do it better next time" document:
  https://gist.github.com/2355445

...so this doesn't happen: http://blockchain.info/tx-index/3618498/4005d6bea3a93fb72f006d23e2685b85069d270cb57d15f0c057ef2d5e3f78d2

Pages: « 1 [2]  All
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!