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

[slema002]

 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)

[Anonymous-User-d9f1b]

``

[Ronlabrie7470]

 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)

[Anonymous-User-d9f1b]

Un'unica app per tutte le esigenze di Word, Excel, PowerPoint e PDF. Scarica l'app Microsoft 365: https://aka.ms/GetM365 Inviato da Outlook per Android<https://aka.ms/AAb9ysg>

[Kya123iu]

 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)

22486031349709