Re: did:cel - a cryptographic event log-based DID Method

Hi Manu,

Thanks for the quick and insightful feedback!

To clarify: GLR is NOT static per domain. It is a global mathematical
constant: SHA-256("").

Anyone can derive it independently: GLR =
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855

It acts as the "Genesis of Geneses". Regarding the "big log file" vs
"blockchain" dilemma:

No Central Log: In Glogos, there is no single "big file" to download.
Instead, the DAG itself is the log. When a zone creates an attestation, it
references (refs) previous IDs. This builds a Causal History that is
globally traversable.
Addressing Forking/Heartbeat: Because every attestation traces back to GLR,
any attempt to "fork" a DID history becomes globally visible. The DAG
provides implicit witnessing: if I reference your attestation, I am
effectively "timestamping" your past with my present.
Infrastructure-free: Unlike a blockchain, Glogos doesn't need miners or
consensus. It only needs the mathematical invariant that "B cannot exist
before A if B references A".
I’d love to show you how a CEL entry can be wrapped in a Glogos attestation
to inherit this "Universal Root" without adding any blockchain weight.

Best regards, Thanh

On Sun, Jan 4, 2026 at 1:53 AM Manu Sporny <msporny@digitalbazaar.com>
wrote:

> On Sat, Jan 3, 2026 at 1:25 PM Manh Thanh Le <vnlemanhthanh@gmail.com>
> wrote:
> > Following Markus's question about alignment between verifiable history
> formats (webvh, webs/KERI, CEL) - I'd like to suggest that Glogos might
> serve as a complementary substrate layer for did:cel, rather than another
> competing format.
>
> Interesting... I took a quick look and see many similarities (which is
> a good thing). One thing in particular jumped out at me:
>
> > 3. Universal Root: GLR provides a mathematical root that all CELs could
> trace to, addressing the "where does the chain start?" problem.
>
> A modification of this feature could also address the forking issue
> that the heartbeat feature is designed to prevent, where the
> "heartbeat" is effectively kept in once place and addresses all DIDs
> via a Merkle tree of some kind... though, that would require
> additional infrastructure that did:cel is attempting to get rid of. I
> am also, almost certainly misunderstanding how the GLR is managed,
> updated, and is worked into the local log... it seems like a static
> value per domain right now?
>
> What I'm hoping for is some sort of "big timestamp log file" that
> everyone downloads/mirrors, and then you have the CEL anchor to that
> "central" file... though, at that point we're effectively back to a
> blockchain and we haven't reduced the size of the log files by much
> (because you still need a reference to the GLR "chain"). :)
>
> -- manu
>
> --
> Manu Sporny - https://www.linkedin.com/in/manusporny/
> Founder/CEO - Digital Bazaar, Inc.
> https://www.digitalbazaar.com/
>