Of course, I did not send you my synchronized wallet, but does the fact that the 1gdc address in this synchronized wallet has a compressed key make it a real wallet this time?
As for the question mark in your head?
I did not tell anyone that I gave permission by saying "let's set the password"
I think being informed about a password that has already been created will better summarize my situation.
I would be grateful if my friends who are really interested in solutions rather than questions on this issue would take our time. I am not trying to destroy a state or gain someone's fortune.
More than just a translation, it's as if we're starting to need more and more people who solve problems rather than create them, that's for sure.
All kinds of technique? Does that include tool specialized to brute-force Bitcoin wallet (such as btcrecover)?
I get a warning that there is a problem with AES and mkey structure.
We don't know what exactly you did. But do you know that Bitcoin Core wallet use AES-256-CBC?
If someone actually hacked your computer, stole your wallet.dat file and sell it on internet, i think you have far more serious problem. That means it's likely they also steal your other personal data and access to online accounts.
John says this about my hash;
Loaded 1 password hash (Bitcoin, Bitcoin Core [SHA512 AES 128/128 SSE4.1 2x])