Starting..., | Bitcointalksearch.org

Kaonashi1993

jr. member

Activity: 97

Merit: 3

Quote

I'm a bit confused by your explanation. Undecided

So to clarify, you are saying that if you use the coworkers wallet.dat as the ONLY wallet.dat it works OK? But if you try and use multiwallet functionality then Bitcoin Core crashes? Huh

Or are you saying that it starts ok with "default_wallet" and "co-worker wallet.dat" files in the data directory, but when you try to switch it crashes? Huh

Yes HCP sorry to leave you hanging but my time was limited some of us are, Thanks locking now

Kaonashi1993

jr. member

Activity: 97

Merit: 3

i'll try my best thanks for the help I'll be locking the thread now as is I do get all the information I needed really thanks you achow

Quote from: achow101 on March 30, 2020, 11:22:13 AM

Quote from: Kaonashi1993 on March 30, 2020, 01:24:38 AM

I'm using latest bitcoincore release thus,, upon my investigation inside the wallet.dat file I can find a ckeyA which corresponds to the passcode been used to lock this wallet 'cause on my new default_wallet I cannot see any ckeyA that corresponds to my passcode which was 0919 but on the other hand of wallet.dat file I see ckeyA but after that a gibberish presentation I'f I could only knew what Berkeley using to hash this encrypted password I could perhaps somehow decrypt it using reverse engineering,

ckey is not the hashed password nor is it the password encrypted. A ckey record is followed by the public key, which is then followed by the encrypted private key. You are looking at the completely wrong place. The A is because the pubkey is prepended by its length which is 0x41 which happens to be the ascii A.

If you want to "reverse engineer" your passphrase, then use https://github.com/gurnec/btcrecover to do it for you. You aren't going to learn it yourself by inspecting the wallet.dat file, it's not in there in plaintext. And you clearly don't understand the wallet format because you are chasing the completely wrong thing. This tool has already been written to do all that for you.

HCP

legendary

Activity: 2086

Merit: 4363

Quote from: Kaonashi1993 on March 29, 2020, 06:08:04 PM

It could be not corrupt wallet as I said the core start up fine on my co worker's wallet but upon exchanging from my default_wallet (the core give) to the wallet.dat of my co-worker the core quit on it's own no whatsoever reasoning why the core did it there's a function to the bitcoincore network where you can switch upon many wallets but you need to rename every wallet to not overwrite the first one (what the core give)

I'm a bit confused by your explanation. Undecided

So to clarify, you are saying that if you use the coworkers wallet.dat as the ONLY wallet.dat it works OK? But if you try and use multiwallet functionality then Bitcoin Core crashes? Huh

Or are you saying that it starts ok with "default_wallet" and "co-worker wallet.dat" files in the data directory, but when you try to switch it crashes? Huh

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

Quote from: Kaonashi1993 on March 30, 2020, 01:24:38 AM

I'm using latest bitcoincore release thus,, upon my investigation inside the wallet.dat file I can find a ckeyA which corresponds to the passcode been used to lock this wallet 'cause on my new default_wallet I cannot see any ckeyA that corresponds to my passcode which was 0919 but on the other hand of wallet.dat file I see ckeyA but after that a gibberish presentation I'f I could only knew what Berkeley using to hash this encrypted password I could perhaps somehow decrypt it using reverse engineering,

ckey is not the hashed password nor is it the password encrypted. A ckey record is followed by the public key, which is then followed by the encrypted private key. You are looking at the completely wrong place. The A is because the pubkey is prepended by its length which is 0x41 which happens to be the ascii A.

If you want to "reverse engineer" your passphrase, then use https://github.com/gurnec/btcrecover to do it for you. You aren't going to learn it yourself by inspecting the wallet.dat file, it's not in there in plaintext. And you clearly don't understand the wallet format because you are chasing the completely wrong thing. This tool has already been written to do all that for you.

Kaonashi1993

jr. member

Activity: 97

Merit: 3

I'm using latest bitcoincore release thus,, upon my investigation inside the wallet.dat file I can find a ckeyA which corresponds to the passcode been used to lock this wallet 'cause on my new default_wallet I cannot see any ckeyA that corresponds to my passcode which was 0919 but on the other hand of wallet.dat file I see ckeyA but after that a gibberish presentation I'f I could only knew what Berkeley using to hash this encrypted password I could perhaps somehow decrypt it using reverse engineering,

Quote from: achow101 on March 30, 2020, 12:37:04 AM

Quote from: Kaonashi1993 on March 29, 2020, 06:08:04 PM

It could be not corrupt wallet as I said the core start up fine on my co worker's wallet but upon exchanging from my default_wallet (the core give) to the wallet.dat of my co-worker the core quit on it's own no whatsoever reasoning why the core did it

What version are you trying to use? If you are still trying to use 0.3.24, of course it won't work. It's too old and doesn't support encryption. Bitcoin Core has specific compatibility breaking things that disallow wallet downgrades. A wallet that supports encryption is inherently unopenable on older software.

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

Quote from: Kaonashi1993 on March 29, 2020, 06:08:04 PM

It could be not corrupt wallet as I said the core start up fine on my co worker's wallet but upon exchanging from my default_wallet (the core give) to the wallet.dat of my co-worker the core quit on it's own no whatsoever reasoning why the core did it

What version are you trying to use? If you are still trying to use 0.3.24, of course it won't work. It's too old and doesn't support encryption. Bitcoin Core has specific compatibility breaking things that disallow wallet downgrades. A wallet that supports encryption is inherently unopenable on older software.

Kaonashi1993

jr. member

Activity: 97

Merit: 3

It could be not corrupt wallet as I said the core start up fine on my co worker's wallet but upon exchanging from my default_wallet (the core give) to the wallet.dat of my co-worker the core quit on it's own no whatsoever reasoning why the core did it there's a function to the bitcoincore network where you can switch upon many wallets but you need to rename every wallet to not overwrite the first one (what the core give)

Quote from: HCP on March 29, 2020, 05:51:04 PM

How exactly are you attempting to "switch" wallets? Huh

The easiest method is to shut down Bitcoin Core. Once it is completely closed, then copy/move the current wallet.dat from the Bitcoin data directory. Then copy your "co-workers wallet.dat" into the Bitcoin Core data directory and overwrite the existing wallet.dat or, if necessary, rename it to wallet.dat.

Then restart Bitcoin Core. If it starts up it'll probably want to rescan to get the wallet up to date with current blocks etc. At the end of that process you will have a better idea if the wallet contains anything.

If it doesn't start up, either report what the error message shown is, or you can check the debug.log file for the errors... although chances are if it doesn't start up with the "co-workers wallet.dat" it is most likely not a Bitcoin Core wallet.dat or it is corrupted.

HCP

legendary

Activity: 2086

Merit: 4363

How exactly are you attempting to "switch" wallets? Huh

The easiest method is to shut down Bitcoin Core. Once it is completely closed, then copy/move the current wallet.dat from the Bitcoin data directory. Then copy your "co-workers wallet.dat" into the Bitcoin Core data directory and overwrite the existing wallet.dat or, if necessary, rename it to wallet.dat.

Then restart Bitcoin Core. If it starts up it'll probably want to rescan to get the wallet up to date with current blocks etc. At the end of that process you will have a better idea if the wallet contains anything.

If it doesn't start up, either report what the error message shown is, or you can check the debug.log file for the errors... although chances are if it doesn't start up with the "co-workers wallet.dat" it is most likely not a Bitcoin Core wallet.dat or it is corrupted.

Kaonashi1993

jr. member

Activity: 97

Merit: 3

What happen was when I load the wallet.dat my co worker had the core star-up fine and upon some experimentation I could not swith from this wallet.dat file using the default_wallet the core given to me just force_quit no message or whatsoever,

Quote from: achow101 on March 28, 2020, 01:00:09 PM

Quote from: Kaonashi1993 on March 28, 2020, 01:10:41 AM

what next should I do opening it up using Bitcoin version 0.3.24 released

Open it using a modern version of Bitcoin Core that has the check. Don't use old software. It won't help you either way.

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

Quote from: Kaonashi1993 on March 28, 2020, 01:10:41 AM

what next should I do opening it up using Bitcoin version 0.3.24 released

Open it using a modern version of Bitcoin Core that has the check. Don't use old software. It won't help you either way.

Kaonashi1993

jr. member

Activity: 97

Merit: 3

what next should I do opening it up using Bitcoin version 0.3.24 released

Quote from: achow101 on March 28, 2020, 12:31:12 AM

Quote

Wallet needed to be rewritten: restart Bitcoin Core to complete

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

Besides the fact that what you are asking is extremely fishy and sounds possibly illegal, it is highly unlikely that your coworker's wallet.dat file still has the unencrypted private keys in the slack space of the wallet.dat file. When the bug was fixed, new clients would also fix wallet.dat files to no longer have the unencrypted keys still in them. So unless your coworker was still using 0.4.0 and never upgraded (even though this was a big bug with lots of noise around it), then there won't be unencrypted keys in the wallet file. If you think there might be, just try to open it up in Bitcoin Core (any version since the fix). If the wallet might have the unencrypted keys, then the wallet file will fail to load and Bitcoin Core will give a message that says

Quote

Wallet needed to be rewritten: restart Bitcoin Core to complete

Even though this bug is almost 10 years old, every version of Bitcoin Core since has had this check and will force those wallets to purge the unencrypted keys.

So that's how you can tell if abusing that bug might even be possible.

Otherwise there's nothing you can do.

Kaonashi1993

jr. member

Activity: 97

Merit: 3

I'm quite don't know if it is particular to this board as I'd like to ask any one who's far smarter to me regarding to this core

I'd found on some articles that the bitcoin-qt 0.4.0 have a bug where upon upgrading wallet.dat from unencrypted to encrypted parts of unencrypted not necessarily overwritten leaving some private key accessible for a while thus the 0.4.1 0.5.0 making this bug fix

if it is true how could I possibly know where my wallet been encrypted to unencrypted and what version do I did this as I'm telling this' cause way back before I'd found a wallet to one of my co-workers pc 2008 to 2009 I guess this happen 2019 Dec, I just scramble his file and happen to get this is it possible that he mined during our time that's is why he is not here anymore and leaving me with some coins behind if so thanks for that but the file is encrypted and I don't quite guess the passcode to this wallet.dat

any help'

Topic: Starting..., (Read 337 times)