The claims collection of Dexie is suboptimal, it should be redefined. The proposed schema is:

db.version(1).stores({
...
    claims: '++_id, *subjects, *signers, type'
})

type is a string and can contain values 'claim', 'claim_request',
The claim itself is stored in a non indexed field jsonLd.

This should be done after we have transitioned to an SPV node.

Right now DID coupling among two devices is done exchanging two nonces. This can be simplified exchanging one verifiable claim containing the two DIDs that have to coupled.

Database schema

db.version(1).stores({
   ...
   didCoupling: '++_id, *subjects, nonce, type`
})

And a non-indexed field jsonLd.
type has values 'shown', 'acquired', 'verified', 'failed'

There is a problem with the spinner

Right now claims can be sent only to get them back signed. There should be an option to send a claim with all the signatures to any user in the DID contact list.

There are 2 transactions that define the initial DID, but right now we only check that the first one has been included in a block to confirm that the DID has been created. In cases where the second transactions was not mined this could lead to an invalid DID.

Using BCoin.js. This way we can remove the calls to blockexplorers to get balance, send raw transactions.

Eliminate a single point of failure using more than one blockchain service to convert tx references to tx ids and viceversa.

• https://testnet.blockexplorer.com/api-ref
• https://chain.so/api/v2
• https://api.blocktrail.com/v1/tBTC/

The client should be able to run on smartphones using cordova

Some bugs in your mnemonic input. Only first four letters is significant. Often on using iPhone the first letter is automatically capped or an extra space added at end — you should ignore those