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

On Thu, Mar 5, 2026 at 4:37 PM Christoph <christoph@christophdorn.com>
wrote:

>
> I love your simple building block implementation approach. This is exactly
> what we need. A bunch of small and simple libraries that operate on what I
> call cryptographic spaces. The tools sit at the boundary where data crosses.
>
> I believe the last hurdle to overcome for the technologies discussed on
> this list is general adoption. That requires interoperable building blocks
> around a coherent model.
>

Thanks, that's the goal: to identify the minimal services and agents acting
on behalf of a user and orchestrating those services. I've made further
progress, please check the updated README. [1]

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.

...
> My plan is to port your libraries to javascript and begin building what I
> call the "Sovereign Substrate". The idea is that it is a data space that
> the user controls and it starts locally in a single process and distributes
> to the web with adapters everywhere.
>

That would be great! I'm really looking forward to interop.

Also, here is probably the first worldwide publicly available did:cel
identifier, HSM-protected and auto-generated. Please note that it has
multiple CelStorageService endpoints: GCS and GitHub.

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

Feedback is very welcome!

Best regards,
Filip
https://www.linkedin.com/in/filipkolarik/

[1] https://github.com/filip26/iron-did-cel
[2] https://github.com/apicatalog/did-cel-log
[3] https://github.com/filip26/iron-did-cel/blob/main/resolver/README.md