Quote from: BitcoinOtter on March 24, 2024, 06:08:39 PM

I wasn't able to use the extract script, but using the dev tools I was able to extract two payloads that look like

Code:

{"pbkdf2_iterations":5000,"version":3,"payload":"jshhfjsagfhsjdgfasukdfgsuafgudfgsauyfguhfusag"}

I didn't expected that to work, really.
It's good to know that the "URL trick" to get the wallet.aes.json's contents still works in old wallets with associated email.
Usually, it'll request for email authorization but wont show the payload even after refresh.

Quote from: BitcoinOtter on March 24, 2024, 06:08:39 PM

Edit: I also noticed this message from Blockchain. Now that I've extracted my file, would I be impacted by this with BTCRecover?

Quote

"Important Note Some older blockchain.com wallets (2014-2015 era at least, perhaps more) have a bug where some private keys were incorrectly encoded and saved to the wallet file... (Basically if the hex encoded private key included any leading zeroes, these were left off, leading to private keys that are less than 32 bytes... The current blockchain.com simply rejects these as invalid and assumes an incorrect password...) The symptoms of this are that your wallet may have correctly worked until about 2015/2016"

Since you're suing BTCRecover where there are separate decryption scheme for old and new wallets,
it may still work in your old wallet because the buggy code might still be applied there.
Link: github.com/3rdIteration/btcrecover/blob/master/btcrecover/btcrpass.py#L2027-L2036