Re: Announcement: Cryptographic Event Logs specification

On Thu, Dec 19, 2024 at 4:17 AM Kalin NICOLOV <kalin.nicolov@gmail.com> wrote:
> This is awesome news, Manu, thank you for sharing it!

Glad to hear it's being received well. :)

> I imagine this is building further on did:tdw

Yes, the CEL spec is an attempt to generalize some of the work that's
gone into did:tdw, blockchain-based DID Methods, ActivityPub, and
Bluesky. There's 30+ years of history here -- cryptographic event logs
(and timestamping services) have existed for a while. That discussion
is being tracked here:

https://github.com/digitalbazaar/cel-spec/issues/1

> KERI KEL and TELs

There are some conceptual similarities with things like version,
previous hash, SAIDs, and backers, but not to the degree to which KERI
defines the state machine, encoding, and other aspects. You will find
some of those same features are common among the other work listed as
prior art.

> I am curious if this is the case, or if there are important distinctions and lines the teams are trying to draw?

One of the goals for the CEL spec is to create a base data structure
that multiple communities can build on top of with a particular focus
on the DID Methods community and the Social Web community (including
ActivityPub and BlueSky). We are trying to not be opinionated about
serializations (JSON vs. CBOR), canonicalization (none, JCS, dCBOR),
and signing (DI vs. CWT). Some might say that's a mistake, others
might say extensibility is good.

As with all specs, this is an attempt to create a tool that is broadly
useful to multiple communities while not making the thing have so many
options that it leads to many non-interoperable implementations. The
people and communities that provide input are the ones that are most
likely to shape what the specification becomes. :)

-- manu

-- 
Manu Sporny - https://www.linkedin.com/in/manusporny/
Founder/CEO - Digital Bazaar, Inc.
https://www.digitalbazaar.com/

Received on Thursday, 19 December 2024 15:54:11 UTC