Re: Call for Co-Editors: Post-Quantum Migration Pattern for Verifiable Credentials (Ed25519 + ML-DSA Dual-Signature Model)

Hi Brigitte,

Thanks for volunteering and for sharing the Jiaozi experience. I’d be very
happy to have you involved in the contributor/co-editor pool.

For now, could you please add a short expression of interest directly to
the proposal issue here:

https://github.com/w3c-ccg/community/issues/260

Once the work item kicks off, we can start working together on the
crypto-agility patterns and implementation guidance.

Looking forward to having you involved.


Best,
Amir


On Tue, 11 Aug 2026 at 11:34 PM, Brigitte Qirong LI <hello@jiaozi.io> wrote:

> Hi Amir, all,
>
> I'd like to volunteer for the co-editor / contributor pool for this work
> item (and the broader "Cryptographic Continuity and Post-Quantum Transition
> Patterns" proposal).
>
> We operate Jiaozi Protocol, an identity and attestation layer for AI
> agents (introduced on this list last week in the transparency-log design
> review thread). Two things we can bring that may be useful:
>
>    1.
>
>    A live case study in multi-suite coexistence. For regulatory reasons
>    our production issuing service already runs two cryptographic regimes side
>    by side today: Ed25519 + SHA-256 for international verifiers, and the
>    Chinese national suite (SM2 signatures + SM3 digests) as co-signatures on
>    the same status credentials for domestic verifiers — dual digests, dual
>    proofs on identical canonical bytes (JCS), and verifiers that must decide
>    what to do when they only understand one of the two suites. This is
>    structurally the same problem as the Ed25519 + ML-DSA transition, except we
>    hit the verifier-behavior, key-distribution and canonical-byte-stability
>    questions in production every day. Happy to write these operational lessons
>    into the migration-pattern and verifier-behavior sections.
>    2.
>
>    Test vectors and implementation reports. Our specs ship with
>    conformance vectors and a runner (status credential suite is public in our
>    repo), and we plan to adopt the dual-proof Ed25519 + ML-DSA profile in our
>    own stack — so the document's guidance would get a production
>    implementation report, not just review comments.
>
> Time commitment: a few hours weekly for editing and calls is fine.
>
> Thanks,
>
> Brigitte Qirong LI
>
> Jiaozi Protocol (https://www.jiaozi.io)
>
>
>