Daniel Buchner

@henkbirkholz mind telling me how one would both allow for multiple types of decentralized systems to underpin DID Methods, while also normative defining a singular resolution process that operates exactly...

Two points: 1. Any standard for truly decentralized identifier methods should allow for different types of implementations based on different substrates, which necessitates differences in resolution steps. This is not...

The reason the browser vendors brushed off the spec during and after has nothing to do with the various Game of Nerds episodic plots highlighted above, it's simply because the...

I think these are great questions, most of which are rooted in the inherent limitations/issues with using an ephemeral trusted-node floodsub system for reliable, secure decentralized identifiers and PKI lineage....

> DID history does not have any private keys in it. I wasn't suggesting that, I was saying that if any past private key is leaked, even many rotations/years later,...

Adding a pointer to my response here for any observer who may view the thread: https://github.com/TBD54566975/did-nostr/issues/2#issuecomment-1446101709

Third option sounds best, with a pref for cache slots given to the DIDs that have the highest frecency of hits.

The pattern we are thinking is that users add `IdentityHub` type descriptors to their DID Doc that specify a Host DID as the `serviceEndpoint` value, which, when resolved, leads to...

@peacekeeper yeah, good point, there is a double resolution from user DID to Hub DID and its related http (and possibly non-http) endpoints. Not sure how I forgot that 🤦‍♂️...

@TomCJones please note we have one of the co-author's of the TLS spec working in this group, who has already commented on this thread. Also realize DIDs provide a new...