Since blockchain.info finally acknowledges that their iOs app was the cause for me losing my private key. I too would like my funds back.
So you were able to contact someone at blockchain.info and they told you that the comment escaping issue is what caused your problem?
If a comment escaping issue caused the problem, you just go into the wallet file and escape the comment properly, and your private key should be recognized properly.
When you say you "searched everywhere through your backup" what does that mean? Was the backup something taken after generating the new address on your phone?
When you generated the address, did you tap "Enter" at all? (ie, did you add a line break in your label?)
That one guy got his funds restored because they were never gone. The app just couldn't read the private key because the comment the user put in was in effect "hiding" the rest of the wallet file from the app.
If you open the wallet file, you should see something like:
{
"version" : "2.0",
"pbkdf2_iterations" : 10000,
"payload" : "<gibberish>"
}The <gibberish> is your encrypted wallet. Decrypt those contents using:
The exact AES specifications are n rounds of PBKDF2, Block Mode CBC ISO10126 padding.
PBKDF2 would be 10000 rounds in the example given above.
Crypto.AES.decrypt(enc_json, password)
Then you should get something like this:
{
"guid" : "abf66471-fe0a-6820-8877-55d7e8c1f6b2",
"sharedKey" : "5ad12271-57d5-6ad8-79ce-49785a99f539",
wallet_options :
{
pbkdf2_iterations : 10, //Number of pbkdf2 iterations to default to for second password and dpasswordhash
fee_policy : 0, //Default Fee policy (-1 Tight, 0 Normal, 1 High)
html5_notifications : false, //HTML 5 Desktop notifications
logout_time : 600000, //Default 10 minutes
tx_display : 0, //Compact or detailed transactions
always_keep_local_backup : false //Whether to always keep a backup in localStorage regardless of two factor authentication
},
"keys" : [
{
"addr" : "1Fqdu8waAy53dFKqjBgRgbciLjHQyDrdyY",
"priv" : "HtacbtAnGRxvecHkjf3Jia5r8TZRpnwZek1aU7CApYDi",
"tag" : 2,
"label" : "Savings"
}
{
"addr" : "1Fqdu8waAy53dFKqjBgRgbciLjHQyDrdyY",
"priv" : "HtacbtAnGRxvecHkjf3Jia5r8TZRpnwZek1aU7CApYDi",
"tag" : 2,
"label" : "Savings"
}
{
"addr" : "1Fqdu8waAy53dFKqjBgRgbciLjHQyDrdyY",
"priv" : "HtacbtAnGRxvecHkjf3Jia5r8TZRpnwZek1aU7CApYDi",
"tag" : 2,
"label" : "Savings"
}
}The problem would occur that the user you mentioned added a line break in the label / comment...
This is how it SHOULD look
This is the bug.
Because they forgot to add the slash in, the computer thinks that the json ends mid-string, This causes an error, and the object which it is contained: ie,
{
"addr" : "1Fqdu8waAy53dFKqjBgRgbciLjHQyDrdyY",
"priv" : "HtacbtAnGRxvecHkjf3Jia5r8TZRpnwZek1aU7CApYDi",
"tag" : 2,
"label" : "Savings\n"
}The computer would read this, hit the "\n" and throw an error on the \ part and the entire object (from addr all the way down) would not be read properly.
IF this was your problem (I have no idea) You just need to add an extra \ in there (or delete the line break... I mean seriously... who needs a line break in their label?) and your funds would be fine.
However, I don't know if this is your problem, as I have not seen your wallet file.
