- From: Eduardo C. <e.chongkan@gmail.com>
- Date: Sat, 14 Mar 2026 01:50:28 -0600
- To: Christoph <christoph@christophdorn.com>
- Cc: "Michael Herman (Trusted Digital Web)" <mwherman@parallelspace.net>, W3C Credentials CG <public-credentials@w3.org>, Daniel Hardman <daniel.hardman@gmail.com>
- Message-ID: <CAANnk0JL99YeyOJqfnL_zWgKPbvHmKGFNMsryKdqah+F9vwn0g@mail.gmail.com>
Also guys, Wanted you to see a Visibility/Tracking issue for Cross-Chain Interoperability for name-based DIDs (SNS and ENS), but, beyond the traditional BC related DIDs, this particular approach aims to resolve the Privacy Issues that the BC public layer poses. I designed the DID:SNS spec with production grade, cross-border financial usage in mind, and the cross-chain interop extends that reach. https://github.com/w3c/did-extensions/issues/680 [image: image.png] -- Eduardo Chongkan On Fri, Mar 13, 2026 at 11:17 PM Eduardo C. <e.chongkan@gmail.com> 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 >> >> >>
Attachments
- image/png attachment: image.png
- image/png attachment: 02-image.png
- image/png attachment: 03-image.png
Received on Saturday, 14 March 2026 07:50:48 UTC