-snip-
6. Look back at the Network tab in your Developer Tools. You should see a list of network requests. Find the one named `wallet` (or something very similar). Click on it.
7. A new pane will appear. Look for a tab within this pane labeled "Response" or "Preview".
Firstly, THANK YOU for posting this detailed guide.
Now I am stuck where I have quoted you.
I don't know how you managed to get to that point without any issue with obtaining the payload since the instructions isn't specific on the "
wallet" part.
Specifically, in step 6, it should be named as your actual wallet_id instead of "
wallet".
For clarification and for you to double-check, you should see
"payload": appended to the actual payload.
And take note that the given instructions will only download the same wallet file that you've been using in their client, containing the same keys.
It's mostly used for obtaining the wallet.aes.json file of a wallet with forgotten password for bruteforce purposes.
It's apparent in step5 where it said that "
it will likely fail" since it expected the user to put a random wrong password.
Anyways, it could be a solution if the issue is only in their client's synchronization or inability to manage its old keys.