Experiment with did:webvh using an Oblivious Witnessing service such as one available for did:cel

The following (below) was posted on the CCG mailing list -- [link to original message](https://lists.w3.org/Archives/Public/public-credentials/2026Feb/0332.html). This issue is to consider if such an Oblivious Witnessing service can be used for did:webvh witnesses. Given the v1.0 did:webvh spec, it would not be compliant as the service does not verify the did:webvh log before generating a proof. However, as discussed at recent meetings and in emails about did:cel/did:webvh comparisons, perhaps what is the v1.0 spec goes too far into governance that is best left to the ecosystems using did:webvh. No doubt we'll continue to discuss this over the next few meetings, as we start to prepare the next version of the spec. As part of that efforts, let's look at this service, and see if it can be used effectively with did:webvh.

FYI @filip26 -- thanks!

Here is the message, including within that, the repo of the code that can run an Oblivious Witness Service.

> Hi,
>
> I’m excited to share an experimental witness service I’ve been working on. It’s a lightweight, open-source implementation that runs as a Google Cloud Function using KMS with HSM-backed EC keys, and can be adapted to almost any infrastructure with minimal effort.
>
> The service achieves O(1) proof generation by using pre-generated templates for ecdsa/eddsa-rdfc/jcs VC DI proofs. Because the model is fully known, there’s no runtime canonicalization or JSON-LD/RDFC/JCS processing required; making the service fast, simple (<1000 lines), and cost-effective.
>
> While designed for did:cel, the service can also be used to witness arbitrary events, providing a lightweight, verifiable, and high-performance proof layer for other decentralized or event-driven applications.
>
> I would greatly value your feedback! Please feel free to fork the repository, raise issues ...
>
> https://github.com/filip26/iron-did-cel-witness
>
> Looking forward to hearing your thoughts!