Samuel Smith
Samuel Smith
DID resolution should be a lightweight indirection to some DID service endpoints where all the work is performed. As opposed to a heavy weight one stop shop.
Adding the auth block to a DID URL vis query parameters allows for ephemeral DIDs to avoid resolution entirely. Which is even more lightweight.
One weakness of the existing internet is DNS resolution. It’s slow buggy and insecure. We don’t want IMHO to repeat those mistakes.
Given multicodec provides the crypto suite than the query string is not needed. But being a did still allows some degree of future proofing. I guess my inclination is to...
It’s a philosophical orientation.
But it may be that I am way off base here if its legacy standards we are trying to support.
The way to get both speed and future proofing is to use caching. This can be done with identity based crypto by making identifier itself be the catche and then...
A ordered dict (key: value pairs, or an ordered tuple of pairs, or a URL with query are all functionally equivalent representations and can be used interchangeable as identifiers for...
Ordering makes the dict and tuple consistently6 hashable so they can be identifiers in their own right not merely encodable as a URL.
The semantics of control embedded in a ‘DID is the essential feature of self-certifiability so having only one semantic for self-certifiability makes composing more complex behaviors decomposable to fewer primitives....