Orie Steele

@mirceanis yes, we have a similar issue we are tracking in our implementation.

ION remains one of the DID Methods that was added to https://w3c.github.io/did-spec-registries/ before we had a more rigorous registration process. If it were attempted today, it would be rejected, because...

this issue could be closed by adding the required sections to the readme.

See this older closed issue: https://github.com/decentralized-identity/did-jwt-vc/issues/54

Specifically the documentation should address this section of the W3C TR. https://www.w3.org/TR/vc-data-model/#proofs-signatures > This specification identifies two classes of proof mechanisms: external proofs and embedded proofs. An external proof is...

Can't be trusted... anyone can write dids of type "make you waste time"....there is no write side protection in sidetree. You can build an index based on your own surveillance...

categories of "type" are metadata... "we kill people based on metadata." - Michael Hayden we won't be able to scrub timing information from sidetree ever... thats metadata as well... If...

@kdenhartog @troyronda add your comments to this ticket.

@csuwildcat to add language to the spec about "implementers may add other properties that mutate what the didUniqueSuffix will be".

Since create payloads are not signed, can't this tagging system be used to label all DIDs being created by a certain vendor? Isn't that the exact use case for this?...