Mircea Nistor

The broken URL that was causing the issue has been temporarily reinstated. A more permanent solution involves configuring the resolver used during verification. The mobile app has also been patched...

we have a similar problem in `did:ethr` where the solution is to embed the network name or chainID in the id: `did:ethr:rinkeby:0xblabla` or `did:ethr:0x4:0xblabla` It is not a perfect solution...

Not sure what you are referring to. Can you point to the "login example" flow and how is it different?

This is the right channel, thank you for reporting this. You are right, that fix has not been deployed, so if you are using that feature it makes sense to...

That depends on the changes. The old contracts are still there, and are immutable, so existing resolver implementations will continue to work. Ideally, the upgrade would act as a proxy...

yes, please go ahead with PRs. We can discuss individual changes there.

You can fork this repository and push to your fork. Then you can make the PR from the forked repository to the main repository.

This issue and other requests made me realize that this contract's immutability is becoming an issue, so I started a governance topic for did:ethr on our discord: https://discord.gg/MTeTAwSYe7

The rawTx is already signed. The corresponding private key does not exist, or rather it's impossible to find. The next step is to send the raw transaction to your local...

I guess so, as it seems your local network requires it. After you do that and you rebuild the deployment transaction, the sender address will change.