Timeline for Seeking KDF parameters for Bitpie/imToken 2023 private backup file in {"data":...} JSON format
Current License: CC BY-SA 4.0
Post Revisions
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 16, 2025 at 18:32 | comment | added | Maarten Bodewes♦ | Obviously the encoded string doesn't contain those parameters but I don't see any hint of structure in the binary data after base 64 decoding either. So this seems to be binary format probably with a salt in there somewhere. Problem is: both the salt and the ciphertext look consist of random bytes. | |
| Oct 15, 2025 at 16:24 | comment | added | MingYang | Thank you very much for your critical insight. The file I have is strictly in this format: {"data":"[VERY LONG BASE64 STRING]"} It contains NO other fields like "crypto", "kdf", or "kdfparams". Does this confirm that this is a private, non-standard Bitpie/imToken format? If so, are there any known resources or GitHub repositories that contain the fixed Scrypt parameters (N, r, p) used by this specific wallet in June 2023? | |
| Oct 15, 2025 at 8:22 | comment | added | Maarten Bodewes♦ | Can't you find an older version that does support it and configure it that way? I don't see anything that looks like a delimiter or iteration count in the binary data, so this means we would have to find the protocol description or even read the source code - if available. | |
| S Oct 15, 2025 at 6:53 | history | suggested | Rohit Gupta | CC BY-SA 4.0 |
Removed unnecessary quotes and added formatting
|
| Oct 15, 2025 at 4:58 | review | Suggested edits | |||
| S Oct 15, 2025 at 6:53 | |||||
| S Oct 15, 2025 at 0:14 | review | First questions | |||
| Oct 15, 2025 at 4:58 | |||||
| S Oct 15, 2025 at 0:14 | history | asked | MingYang | CC BY-SA 4.0 |