Re: Web 7.0 DID OS

Christoph,

Thanks a lot for the feedback!

"It is evidence for what I am saying: There is a path to presenting DID
tech in a way to catalyze the ecosystem for general adoption."

In the Spec of the did:sns, you could find more info on how the tech can be
used functionally to resolve a real life problem

- did:sns spec ( Executive Summary )
https://github.com/Attestto-com/did-sns-spec/blob/main/did-sns/executive-summary.md
- Full Spec: https://spec.attestto.com/did-sns
- And here is how everything fits together: Cross-Chain and Web2 inter-Ops.
https://github.com/w3c/did-extensions/issues/680

Kind Regards,

--
Eduardo Chongkan



On Sat, Mar 14, 2026 at 9:03 AM Christoph <christoph@christophdorn.com>
wrote:

> Hi Eduardo!
>
> This is exactly consistent with the kind of ecosystem tooling I am
> envisioning.
>
> Your initiative and ability to produce this quickly is a perfect example
> of the new paradigm we now live in.
>
> It is evidence for what I am saying: There is a path to presenting DID
> tech in a way to catalyze the ecosystem for general adoption.
>
> You were able to put this together quickly because you understand the
> ecosystem more than me.
>
> What is it that is enabling this tool to function?
>
> 1) Specs in repos with metadata
> 2) A model of what should be (how everything fits together towards
> practical use-cases)
> 3) Functional processing logic that transforms source of truth code/data
> to other representations
>
> Both are deliverables that can be achieved with focus and some discipline.
>
> Visibility creates alignment.
>
> I encourage someone else to provide the next prototype for a tool that
> will help onboard people to the DID ecosystem.
>
> In reviewing the tool I find that I now want a higher level overview that
> introduces me to what a DID method is and where it fits in to arm me with
> more information about how to evaluate the DID methods presented in the
> tool.
>
> Christoph
>
>
>
> On Sat, Mar 14, 2026, at 12:17 AM, Eduardo C. wrote:
>
> Christoph,
>
> I think I share your same point of view:
>
> "One challenge I face when looking into the DID approach is that I need to
> consult many documents and projects to understand where everything fits in.
> When wanting to contribute to the ecosystem, one is faced with a steep
> learning curve and then a lack of community around building solutions with
> DID tech.
>
> I have always seen the DID/VC standards as patterns with many
> implementations. This is great but where can I learn about all the VC/DID
> patterns and see which are supported to what extent by which implementation?
>
> Furthermore, how do I use the patterns to solve my actual problems I face
> when building full-stack SASS and other systems?"
>
> just last night I made a PR and included some tooling and files to help
> reduce friction in that.
>
> [image: image.png]
> [image: image.png]
>
> There are more screenshots here;
> https://github.com/w3c/did-extensions/pull/677,
>
> You can check the tool here:
> https://chongkan.github.io/did-extensions/explorer.html, it was fed form
> the repo as it was, and the idea is that all new methods, use the new json
> so that tool can stay up to date and run during CI -- ( if it gets approved
> )
>
> Regards,
>
> --
> Eduardo Chongkan
>
>
> On Fri, Mar 13, 2026 at 1:48 PM Christoph <christoph@christophdorn.com>
> wrote:
>
>
>
> Hi Michael,
>
> I watched your presentation.
>
> I like what kinds of problems you think about and that you are trying to
> propose a solution that achieves an end result by using and extending
> existing specifications.
>
> I see you are working towards a complete stack and there are still some
> hurdles to overcome.
> When I compare your effort to what others are doing I see a wide variety
> of application of the DID standards.
>
> I like the concept of a Library Operating System with host adapters. I
> believe this is a natural architecture for where we are going with the web.
>
> My interest is in figuring out how we can make progress towards an
> architecture such as you are describing.
> What is the commonality between how progress is achieved towards your
> architecture as well as those others are working on?
>
> One challenge I face when looking into the DID approach is that I need to
> consult many documents and projects to understand where everything fits in.
> When wanting to contribute to the ecosystem, one is faced with a steep
> learning curve and then a lack of community around building solutions with
> DID tech.
>
> I have always seen the DID/VC standards as patterns with many
> implementations. This is great but where can I learn about all the VC/DID
> patterns and see which are supported to what extent by which implementation?
>
> Furthermore, how do I use the patterns to solve my actual problems I face
> when building full-stack SASS and other systems?
>
> I am working towards practical solutions in the short-term. You are
> working towards an ideal solution in the long-term.
>
> What are the things we are missing around the VC/DID ecosystem that is
> slowing our progress towards realizing what we envision? I bet many others
> are in the same boat.
>
> I do not subscribe to the notion of "lack of interest".
>
> What if the onus is on us to make what we envision and build more
> consumable in a significant way to others?
> What if there is actually a way to do this and all we have to do is pursue
> it?
> I have no concrete answers but I believe there is a path open to be
> discovered with further discourse.
>
> Christoph
>
>
>
> On Thu, Mar 12, 2026, at 12:18 AM, Michael Herman (Trusted Digital Web)
> wrote:
>
> Here's a comprehensive Web 7.0 update that I presented to the DIDComm WG
> earlier this week (starts 4 minutes into):
>
> https://us02web.zoom.us/rec/play/uCkJ9lauFX8XBfoUSf4-ck4q51E7gXG3M6HmWDbabuEHWuDcgEGgR83aQ01WwgjzDpsVnhtkJXkNyVdz.CFR9MZV7vCxX8h61
>
> It is of interest to anyone working in field of large scale Decentralized
> Systems Architecture (DSA).
>
> Michael Herman
> Chief Digital Architect
> Web 7.0 Foundation
>
>
>
>