Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

12 WORD SEED PHRASE NOT ACCEPTED ON BLOCKCHAIN.COM WALLET ALTHOUGH ITS CORRECT #6266

Open
slema002 opened this issue Jan 31, 2024 · 3 comments

Comments

@slema002
Copy link

slema002 commented Jan 31, 2024

 Hi Folks, for those following or who find this in the future, I got a copy of the wallet file from DanielsBerlin.

Basically for those who are technically inclined, the issue is that that wallet file is that it was a V3 wallet, structured just like any V2+ wallet. (PBKDF2, 5000 iterations, etc...)

The issue comes in that for some reason, the files encrypted with the second password weren't using the "modern" encryption for the second password hashing. (Which includes information about the the pbkdf2 iterations, etc, within the body of the JSON that is decrypted with the main password) What makes this extra strange is that all of this information is actually in the decrypted JSON, but doesn't reflect the parameters used to encrypt the data which is protected by the second password. (In the sample wallet provided, the password was only hashed with 10 SHA256 iterations, just like in a V0 wallet)

Anyways BTCRecover has been updated so as to automatically handle this so as to correctly find the password as well as decrypt/dump the wallet and private keys.

Originally posted by @3rdIteration in #3095 (comment)

blockchain
blockchain create new wallet

@slema002 slema002 changed the title 12 WORD SEED PHRASE NOT ACCEPTED ALTHOUGH ITS CORRECT 12 WORD SEED PHRASE NOT ACCEPTED ON BLOCKCHAIN.COM WALLET ALTHOUGH ITS CORRECT Jan 31, 2024
@Anonymous-User-d9f1b
Copy link

``

@Ronlabrie7470
Copy link

 Hi Folks, for those following or who find this in the future, I got a copy of the wallet file from DanielsBerlin.

Basically for those who are technically inclined, the issue is that that wallet file is that it was a V3 wallet, structured just like any V2+ wallet. (PBKDF2, 5000 iterations, etc...)

The issue comes in that for some reason, the files encrypted with the second password weren't using the "modern" encryption for the second password hashing. (Which includes information about the the pbkdf2 iterations, etc, within the body of the JSON that is decrypted with the main password) What makes this extra strange is that all of this information is actually in the decrypted JSON, but doesn't reflect the parameters used to encrypt the data which is protected by the second password. (In the sample wallet provided, the password was only hashed with 10 SHA256 iterations, just like in a V0 wallet)

Anyways BTCRecover has been updated so as to automatically handle this so as to correctly find the password as well as decrypt/dump the wallet and private keys.

Originally posted by @3rdIteration in #3095 (comment)

blockchain
blockchain create new wallet

@Anonymous-User-d9f1b
Copy link

Anonymous-User-d9f1b commented Aug 23, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants
@slema002 @Anonymous-User-d9f1b @Ronlabrie7470 and others