Orie Steele

Please link to the code, provide more details so someone can help.

downgrading to 2.3.2 resolved this issue for me as well.

@peacekeeper better to just answer on the did core issue: https://github.com/w3c/did-core/issues/417 I think this will help clarify a lot.

Can you be more specific? This repo contains docker examples, are you looking for a node-js sdk for the universal resolver http interface?

@peacekeeper I'd be happy to provide a js sdk for the public http interface if that would help resolve this issue, its something I would find very useful generally.

I will open a PR, it might be rough, but it will work in both the browser and nodejs... it will be based on: https://github.com/transmute-industries/PROPOSAL-OpenPgpSignature2019/blob/master/src/universalResolver.js

I think this would be helpful, particularly to help test resolution and dereferencing. We would need code that maps a `DID_URL` and `RESOLUTION_OPTIONS` to an http request... We've avoided this...

@BernhardFuchs thanks for reporting this, the endpoint referenced is no longer maintained due to sidetree version changes, I will have some folks on our end update the endpoint. The readme...

@csuwildcat you can probably nearly copy paste from this file: https://github.com/transmute-industries/sidetree.js/tree/main/packages/did-method-element#element-did-method-specification

@gjgd ^ not sure if this is up to date, but it you have a spare cycle to review, would welcome one.