• should maybe change password on key backup too

enables making next transfer before the first transfer is mined

Create a link or another button "ready" or "transfers" or "...."

User story

1. Merchant has a link like this on the web-page

euro2:?r=http://wallet.euro2.ee:8080/request/foobar123

2. Or merchant has encoded this same in the QR code
3. App opens up a confirmation page with the prefilled payment details
4. User presses confirm button
5. App navigates to "Transfers" page and shows pending (or alternatively to the callbank link in the pay request)

Things to build

• register URI scheme in cordova
• do the hack to failover to mobile web (or appstore) if app not installed http://stackoverflow.com/questions/38501604/how-to-create-a-deep-link-which-redirects-to-appstore
• confirmation page
• validation checks that it is a legit request
• response to merchant
• submission to transfer-info

http://id.euro2.ee:8080/v1//ldap/inactive should point to https://...

• generate the special key ( button on /keys ) and go through ID/Mobiil-ID verification.
• after successful verification indicate to account-identity that this address is special and send the public key

POST /v1/hdkey
{
  address: 0x32323cb232
  publicKey: 0x321553235
  batchSize: 20
  minBuffer:  5
}
returns:
{
  [
    {path: 2/1, address: 0x232},
    ...
    {path: 2/20, address: 0x232},
  ]
}

• mark this key as special in the app localStorage
• on the /keys page show the special keys with a different icon, when expanded then fetch non-0-balance paths from server and show on the expanded block
• when user refreshes balances, then pre-empt by loading non-zero balance sub-keys from account-identity and store these in localStorage

cordova.js is not present in the webbuild directory, but there seem to be references in the client.

When the app is opened then go through the array of password-encrypted private keys stored in localStorage.getItem("keys") and retrieve the identity for each verified key from account-identity in the form of:

{ idCode: "38008040123", idProvider: "EST-ID" }   
{ idCode: "123522", idProvider: "EST-BIZ" }   

See: cryptofiat/account-identity#21

Based on the responses construct profiles similar to the model

{ 
     identity: "38008040123",
     identifier: "Estonian-ID",
     commonName: "JUKU JUHALAINEN",
     name: { firstName: "Juku", lastName: "Juhalainen" }
     social: [ { schema: "twitter", URI: "@juhalainen" } , { schema: "facebook", URI: "jukujuh"}] ,
     avatar: "http://pic.twitter.com/nat.png",
     coverPhoto: "http://pic.twitter.com/blaah.png",
     keys: [ 
        { privateEncrypted: "0x1231", 
          public: "0x4323...",  
          hdKey: { type: hdKey, paths: [ "2/2322" , "2/3232" ] }, 
          addressCache: { timestamp: 1245342, balance: 32, approved: true, frozen: false } , 
          transferCache: { timestamp: "13456464", transfers: [ Transfer ] } 
        },
         ...
     ]
  }