Re: Experimental did:cel Witness Service (open-source)

I like the idea of a gh action to get started.

Regarding the shared link: reading the specification led me to believe that
logs must be stored as a compressed gzip archive
<https://w3c-ccg.github.io/did-cel-spec/#compression>. Is this not the case?

On Tue, Mar 10, 2026 at 5:30 PM Manu Sporny <msporny@digitalbazaar.com>
wrote:

> On Mon, Mar 9, 2026 at 3:59 PM Filip Kolarik <filip26@gmail.com> wrote:
> > did:cel:zW1aUdGpZoVs789MPqMuHhgnpyk7yzrfMUs3p7VGk7vqTmi?storage=
> https://storage.googleapis.com/did-cel-log/
> >
> > This resolves [3] to the live event log here:
> https://storage.googleapis.com/did-cel-log/zW1aUdGpZoVs789MPqMuHhgnpyk7yzrfMUs3p7VGk7vqTmi
>
> Filip, I think you have the great honor of the first production
> did:cel identifier and log. :)
>
> > Beyond that, I'm also exploring which existing infrastructure could be
> utilized as DID ecosystem services. For example, GitHub as a
> CelStorageService [2] is affordable and easily accessible to anyone, and it
> can also serve as a mirror.
>
> Yes, that's excellent! I wonder if you can just run a Github Action to
> do the witnessing? If you publish that Action, then you enable anyone
> w/ a Github account to create a did:cel and then port away from Github
> at a future date.
>
> You could also simulate a forking attack by literally forking the
> Github repo. :)
>
> Awesome work, Filip -- really excited by your progress!
>
> -- manu
>
> --
> Manu Sporny - https://www.linkedin.com/in/manusporny/
> Founder/CEO - Digital Bazaar, Inc.
> https://www.digitalbazaar.com/
>
>