Stephen Curran

Closing. Decision was made to not reference the HA DIDs with DNS spec. That spec can be used with did:webvh in the "same as all DID methods other than did:web"...

@PatStLouis @dbluhm — can either of you help here?

Thanks for the questions and notes. Responses: It is required by the specification that the DID Controller publish the witness proofs in the `did-witness.json` file beside the DID Log (`did.json`)....

I don’t think is quite right `SCID does not protect the verifier beyond the first entry in the log.`. The SCID within the DID allows verification of the first entry....

Re: Verifier protection Assuming a separation between the DID Controller and the Web Server, the Dishonest Web Server can at most suppress the publication of the most recent update(s) to...

Thanks. The majority of the proposals fall into the DID Controller / Witness handling/governance, which we've noted in the specification is being out of scope. I do see two (and...

Per the February 27, 2025 meeting ([agenda](https://hackmd.io/k4cIK9vQSlaeg2pdHE51IQ)), we've decided to add Watchers to the specification. In simple terms, the DID Controller can add a list of URLs to the DID...

Regards the expanded information to return. Based on the DID Core spec, there really is only three values to return — success, fail/invalid, and not found — and that is...

Just reading this last note — not the whole stream. Indicio has implemented [SocketDock](https://github.com/Indicio-tech/aries-socketdock) that I think addresses the questions raised here. Perhaps it can help. Quick overview — SocketDock...

In the AnonCreds spec, there are 8 “restrictions” that are supported, all of which are optional. The details of each are described in the spec [here — restrictions](https://hyperledger.github.io/anoncreds-spec/#restrictions). So yes,...