Samuel Smith

Another way to think of this is that a single persistent identifier with its KEL provides a root-of-trust for an ecosystem of ephemeral or effectively ephemeral identifiers that all share...

@pfeairheller > wouldn't it be desirable to allow an event to commit to new configuration information without requiring everyone using this identifier as a witness to rotate to a new...

To summarize again. The policy is that Backers can only endorse something previously committed to via a seal in the KEL for which the backer is a backer. This brings...

Yes I just had to reason through all the options to get clarity in my own mind. We don't need an explicitly identified default TEL with unique message types for...

It is true that the delegator may not be changed. So having the `di` in the rotation event may be redundant. My biggest concern is that one of the not...

But having complex hetero attachments is allowing a rethinking of the existing key events. So worthwhile suggestion.

I couldn't find a reason to keep the `di` field in the `drt` event. Every time I tried to come up with an exploit the prior digest field commitment chain...

Here is a suggestion for how we can be more precise in our terminology: I used this terminology for the RAET protocol which is much more complex than what we...

Delegation is cooperative. This enables enhanced security because the delegator and delegate may cooperate to recover compromised keys of the delegate. An attacker would have to exploit both the delegate...

# Design Proposal Preliminary design approach suggestions for query message is to start with Restful API parameters and then back out from the Restful API a compatible query message format....