Author

Topic: How can I get a copy of blk0001 (Read 206 times)

staff
Activity: 3458
Merit: 6793
Just writing some code
May 05, 2018, 11:30:29 AM
#6
This is a quote from Matt. "This needs to go into 0.3.24, so that users who downgrade don't mess up their wallet by adding unencrypted keys to an encrypted wallet, making all versions unable to use the wallet." It is my understanding that when using Cwallet that Matt changed the private key around 0.3.2.1- 0.3.2.3 and it would crash the wallet in 0.3.2.4. it was part of garzik code for encrypted keys that Matt worked on
Email me if you know the format of encrypted keys.
No, you understand completely incorrectly.

As I said earlier, private key encryption was released in 0.4 and no earlier. Wallets prior to that were not encrypted. The problem here is that introducing encrypted keys changes the wallet format by adding things to the wallet that previous versions do not know. Thus the wallet will crash and become corrupted if you encrypted it with 0.4 and then downgraded to 0.3.x. The change for 0.3.24 was so that if someone downgraded from 0.4 to 0.3.24, the act of downgrading would not corrupt their wallet as it would with 0.3.23 and earlier. This has nothing to do with CWallet nor with 0.3.21-0.3.23. Encrypted private keys were not part of any 0.3.x version.
jr. member
Activity: 43
Merit: 1
May 05, 2018, 10:28:37 AM
#5
What are you really trying to do? Are you trying to upgrade an ancient Bitcoin installation to the current version and getting an error relating to blk0001.dat, or what?
Trying to figure out how to see orphans from 2010, also trying to figure out what format encrypted keys were before 0.3.2.4. I'm scanning old drives that I have.
jr. member
Activity: 43
Merit: 1
May 05, 2018, 10:00:24 AM
#4
This is a quote from Matt. "This needs to go into 0.3.24, so that users who downgrade don't mess up their wallet by adding unencrypted keys to an encrypted wallet, making all versions unable to use the wallet." It is my understanding that when using Cwallet that Matt changed the private key around 0.3.2.1- 0.3.2.3 and it would crash the wallet in 0.3.2.4. it was part of garzik code for encrypted keys that Matt worked on
Email me if you know the format of encrypted keys.
legendary
Activity: 4522
Merit: 3183
Vile Vixen and Miss Bitcointalk 2021-2023
April 29, 2018, 11:16:09 PM
#3
What are you really trying to do? Are you trying to upgrade an ancient Bitcoin installation to the current version and getting an error relating to blk0001.dat, or what?
staff
Activity: 3458
Merit: 6793
Just writing some code
April 29, 2018, 02:19:56 PM
#2
Like to get a copy of  blk0001 for 2009-2010.
It's the same as a modern blk0001.dat file. Those file formats have not changed.

And maybe you can tell me what format was the private key on a encrypted wallet was. Mid-2010 beta wallet before 3.2.4, before blue Matt changed the format on encrypted private keys.
Wallets were not encrypted prior to Bitcoin 0.4.0 when Matt introduced encrypted wallets. The format of wallets at that time for private keys is the same for unencrypted private keys today.
jr. member
Activity: 43
Merit: 1
April 29, 2018, 01:48:44 PM
#1
Like to get a copy of  blk0001 for 2009-2010. And maybe you can tell me what format was the private key on a encrypted wallet was. Mid-2010 beta wallet before 3.2.4, before blue Matt changed the format on encrypted private keys.
Jump to: