Samuel Smith

@daniel. I am not supporting did:key I would rather have a true ephemeral DID. @tplooker proposed did:key. But my comments are that this is similar to ephemeral DID and I...

@tplooker. Yes I share the same concern. I resist creating new classes of identifiers when I think that a DID will do. DIDs are sufficiently flexible that we should spend...

The URI speci proved to be a very resilient and long lived specification because it had a Goldilocks amount of flexibility. I would like DIDs to follow suite.

Fundamentally I am more in agreement with @dhh1128 than not. As long as the multicodec includes the crypto suite it is a self contained identifier than can be used in...

In general there are multiple use cases where we use crypto as part of a bootstrap of capability. A true Ly ephemeral DID would define a common syntax and semantics...

Attenuated Authorizations are a type of. Data not an identifier. They have an identifier but they are not the same as an identifier.

@CholoTook > Identities in DID are simply private keys Unless of course your DID supports key rotation so that the private keys may change which means that the identitiy is...

Not sure what you mean by suffix. After the did method there is the unique name string and then there may any number of colon separated strings. But forcing an...

@csuwildcat > "(I am honestly stunned to hear this was not plainly obvious to anyone who worked on decentralized identity)" I am likewise stunned whenever I see a proposal for...

@OR13 > AFAIK, Sidetree Create Payloads lead to self certifying identifiers... the payload data (which includes the authoritative keys) is hashed to produce the identifier, the inception event is witnessed...