Mircea Nistor

The problem was uport-mobile was using an old version of `ethr-did-resolver` that used a hardcoded RPC url. The url format was deprecated by infura and is now throwing an error....

> I can also look into the problem later this week as I also need to migrate from walleth/sha3 to komputing/KHash - just did not come around to it and...

@ligi yes. It is used by a JVM lib that passes tests and that lib is used in an android context which also passes tests. I had to exclude the...

@MariusBoepple I see the same thing in AndroidStudio but I am able to `CMD+click`(`CTRL+click`) on a call to `calculateSHA3()` in my code and see the implementation.

> but it seems jitpack only picks up the sha3 module: > > https://jitpack.io/com/github/komputing/KhasH/0.8/build.log I just assumed that was the only one available in 0.8. I didn't follow the history...

I also don't see a good reason to add `proof` section to the did doc. Perhaps I'm not grasping it completely but it seems to me that it serves only...

> @OR13 got it, ok. So that seems like a vote for option 2. I'm not reading it that way :) Also, I'm not putting any weight on either of...

> So, the reason I'm reading it as a vote for Option 2 is -- the question here is what's the data model of a did:web DID Doc _stored on...

It already supports path based routes, except that the base resolver is not up to spec with `verificationMethod`. It still expects a `publicKey` array, and throws an error if it...

the uport driver uses the implementation from [`web-did-resolver`](https://github.com/decentralized-identity/web-did-resolver) the `web-did-resolver` was not yet adapted to the latest did-core spec. I'm not aware of other implementations, but I guess it could...