Bitcoin Forum
August 21, 2018, 12:08:35 AM *
News: Latest stable version of Bitcoin Core: 0.16.2  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Can we validate all the blocks created till date with the first Satoshi client?  (Read 1036 times)
100bitcoin
Sr. Member
****
Offline Offline

Activity: 384
Merit: 250


View Profile
June 02, 2017, 07:53:32 PM
 #1

Can confirmed transactions spent from or received at multi-sig addresses be validated by first Satoshi client, i.e. bitcoin-0.1.0?

If not, then should we consider that all changes made to bitcoin so far are not backward compatible in nature?
1534810115
Hero Member
*
Offline Offline

Posts: 1534810115

View Profile Personal Message (Offline)

Ignore
1534810115
Reply with quote  #2

1534810115
Report to moderator
1534810115
Hero Member
*
Offline Offline

Posts: 1534810115

View Profile Personal Message (Offline)

Ignore
1534810115
Reply with quote  #2

1534810115
Report to moderator
BOUNTY PORTALS
BLOG
WHERE BOUNTY MANAGEMENT
MEETS AUTOMATION
SIGNATURE CAMPAIGNS
TWITTER
FACEBOOK
MEDIA CAMPAIGNS
AND MORE!
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
DannyHamilton
Legendary
*
Offline Offline

Activity: 2198
Merit: 1371



View Profile
June 02, 2017, 11:57:13 PM
 #2

The original client had some bugs in it that were fixed later (some of them fixed by Satoshi himself), so I wouldn't want to use it to send transactions or build blocks.

That being said, I'm not certain.  I *think* it *might* be able to validate all blocks and transactions, but I wouldn't bet any money on that.  I look forward to seeing if anyone with more knowledge than me responds.  It'd be great to see what GMaxwell has to say about it.

achow101
Moderator
Legendary
*
expert
Offline Offline

Activity: 1498
Merit: 1530


3F1Y9yquzvY6RWvKbw2n2zeo9V5mvBhADU


View Profile WWW
June 03, 2017, 04:50:31 AM
 #3

You can't. I know for certain that all versions of Bitcoin/Bitcoin-qt 0.7.2 and earlier will not be able to sync with the network due to an insufficient number of Berkeley DB locks which then essentially imposed a block size limit at around 500kB. This issue is what caused the March 2013 fork. Because of this, all versions of Bitcoin/bitcoin-qt 0.7.2 and earlier will be unable to fully sync the blockchain.

2112
Legendary
*
Offline Offline

Activity: 2114
Merit: 1027



View Profile
June 03, 2017, 05:48:36 PM
 #4

You can't. I know for certain that all versions of Bitcoin/Bitcoin-qt 0.7.2 and earlier will not be able to sync with the network due to an insufficient number of Berkeley DB locks which then essentially imposed a block size limit at around 500kB. This issue is what caused the March 2013 fork. Because of this, all versions of Bitcoin/bitcoin-qt 0.7.2 and earlier will be unable to fully sync the blockchain.
This is bullshit. Not just garden-variety bullshit, but military-grade weaponized bullshit.

This is exactly what happens when people willfully don't read documentation as a matter of development policy.

It is exactly like the proverbial "giving people just enough rope to hang themselves".

I posted about this on the same night it happened because I was driving long distance and couldn't really stop for a full post earlier.

https://bitcointalk.org/index.php?topic=152208.0
https://bitcointalk.org/index.php?topic=152030.msg1616542#msg1616542
The "manual tweak" is exactly two lines. Anyone can apply it, because the recompilation is not necessary. All it takes is to create a short text file and restart the bitcoin client.

Those threads are interesting read for anyone wondering how Bitcoin ended up with a fragmented development community that we have now. You'll understand how the division lines were drawn and what methods of disinformation were applied. I certainly was enlightened on that very afternoon-evening-night about what was really going on amongst the leading developers and pool operators.

Please comment, critique, criticize or ridicule BIP 2112: https://bitcointalk.org/index.php?topic=54382.0
Long-term mining prognosis: https://bitcointalk.org/index.php?topic=91101.0
100bitcoin
Sr. Member
****
Offline Offline

Activity: 384
Merit: 250


View Profile
June 03, 2017, 06:03:13 PM
 #5

You can't. I know for certain that all versions of Bitcoin/Bitcoin-qt 0.7.2 and earlier will not be able to sync with the network due to an insufficient number of Berkeley DB locks which then essentially imposed a block size limit at around 500kB. This issue is what caused the March 2013 fork. Because of this, all versions of Bitcoin/bitcoin-qt 0.7.2 and earlier will be unable to fully sync the blockchain.

Was multi-sig implemented after Bitcoin/Bitcoin-qt 0.7.2? If yes, can confirmed transactions spent from or received at multi-sig addresses be validated by Bitcoin/Bitcoin-qt 0.7.2?
achow101
Moderator
Legendary
*
expert
Offline Offline

Activity: 1498
Merit: 1530


3F1Y9yquzvY6RWvKbw2n2zeo9V5mvBhADU


View Profile WWW
June 03, 2017, 08:52:30 PM
 #6

Was multi-sig implemented after Bitcoin/Bitcoin-qt 0.7.2? If yes, can confirmed transactions spent from or received at multi-sig addresses be validated by Bitcoin/Bitcoin-qt 0.7.2?
P2SH (commonly known as multisig) was implemented in 2012, before 0.7.2. P2SH transactions can be validated by earlier versions.

100bitcoin
Sr. Member
****
Offline Offline

Activity: 384
Merit: 250


View Profile
June 04, 2017, 03:17:08 PM
 #7

Was multi-sig implemented after Bitcoin/Bitcoin-qt 0.7.2? If yes, can confirmed transactions spent from or received at multi-sig addresses be validated by Bitcoin/Bitcoin-qt 0.7.2?
P2SH (commonly known as multisig) was implemented in 2012, before 0.7.2. P2SH transactions can be validated by earlier versions.
Do u mean blocks having P2SH transactions can be validated by first Satoshi client, i.e. bitcoin-0.1.0?
achow101
Moderator
Legendary
*
expert
Offline Offline

Activity: 1498
Merit: 1530


3F1Y9yquzvY6RWvKbw2n2zeo9V5mvBhADU


View Profile WWW
June 04, 2017, 03:48:11 PM
 #8

Do u mean blocks having P2SH transactions can be validated by first Satoshi client, i.e. bitcoin-0.1.0?
P2SH was a soft fork so older versions which technically do not support it can still partially validate those transactions and blocks. However, in order to fully verify P2SH transactions, you would need to have bitcoin 0.5.4+

100bitcoin
Sr. Member
****
Offline Offline

Activity: 384
Merit: 250


View Profile
June 04, 2017, 04:00:53 PM
 #9

Do u mean blocks having P2SH transactions can be validated by first Satoshi client, i.e. bitcoin-0.1.0?
P2SH was a soft fork so older versions which technically do not support it can still partially validate those transactions and blocks. However, in order to fully verify P2SH transactions, you would need to have bitcoin 0.5.4+
That means, in short, all bitcoin client releases were not backward compatible in nature. Does not it lead to the fact that Bitcoin has hard forked before?
achow101
Moderator
Legendary
*
expert
Offline Offline

Activity: 1498
Merit: 1530


3F1Y9yquzvY6RWvKbw2n2zeo9V5mvBhADU


View Profile WWW
June 04, 2017, 04:56:36 PM
 #10

That means, in short, all bitcoin client releases were not backward compatible in nature. Does not it lead to the fact that Bitcoin has hard forked before?
No, Bitcoin has not hard forked before, and all releases are actually backwards compatible since all protocol changes have been soft forks. As 2112 said earlier, you can actually get past the BDB lock issue with some special configuration. So in theory, you could sync a 0.1.0 client fully up to date with some special configuration.

Pages: [1]
  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!