Re: did:nostr v0.1.0 and BIP-340 Data Integrity

Hi Melvin,

Congratulations on the draft publication, and thanks for sharing it with
the CCG.

It's great to see the progress and the growing implementation ecosystem
around DID. I'd be happy to contribute in any way I can as the work moves
forward.

Best,
Amir Hameed Mir

On Wed, 1 Jul 2026 at 05:10, Melvin Carvalho <melvincarvalho@gmail.com>
wrote:

> Hi all,
>
> A brief heads-up that the W3C Nostr Community Group has published
> did:nostr v0.1.0 as a Community Group Draft Report:
>
> https://nostrcg.github.io/did-nostr/
>
> did:nostr defines a DID method for Nostr identities, based on secp256k1 /
> BIP-340. The method now has 30+ implementations, so this seemed worth
> surfacing here given the overlap with CCG work.
>
> A few items that may be of interest:
>
> 1. did:nostr is registered in the DID Method Registry.
>
> 2. It includes a conformance test-vector suite covering key
> transformation, parity decoding, error taxonomy, and document generation.
>
> 3. A DIF did-resolver driver is available, so it can be used through the
> Universal Resolver.
>
> 4. Verification methods use Multikey with secp256k1 keys, which connects
> directly with CCG work on Data Integrity and cryptosuites.
>
> If useful in making the case for that work, did:nostr provides a live DID
> method and implementation ecosystem that wants to issue and verify VCs with
> Nostr keys via Data Integrity.
>
> Status-wise, this is still an early Draft Report. The main open design
> item on the path to a Final Report is key rotation / deactivation. Review
> and critique are very welcome, especially around Multikey/parity handling,
> the resolution model, and how this should fit with CCG Data Integrity work.
>
> See also:
>
> https://did-nostr.com/
>
> Thanks,
> Melvin
>