Good news! After a helpful discussion with the W3C Credentials Community Group, we’ve aligned on a verification method that works cleanly with did:nostr and the Verifiable Credentials stack:

w3c-ccg/community#254 (comment)

I’ve already patched the did:nostr draft to reflect this.

What this unlocks

1. Production-ready reference implementations

2. Compatibility with the wider W3C Credentials ecosystem

3. A straightforward path to issuing industry-standard credentials (badges, awards, driver’s licences, etc.) over Nostr

4. The ability to sign and exchange JSON payloads between Nostr services (relays optional)

It’s a nice step up in standards alignment and Nostr functionality.

Many thanks to everyone who weighed in, feedback very welcome!

Reply to this note

Please Login to reply.

Discussion

Number 4 sounds high-key relevant.

If my erection lasts longer than 4 hours, your lawyers will be hearing from my doctor.

Super! I have been following on the mailing list. Glad to see you leading this!

I just hope this isn't a precursor to Nostr eventuating into a mismanaged W3C standard. Would rather NOT have ActivityPub 2: Electric Boogaloo.

I'm not sure I'm a fan of using hex pubkeys instead of encoded "npub" pubkeys as user IDs.

The reason is that the DID contains "nostr:" and "nostr:npub…" is a valid Nostr URI.

Wouldn't it be neat if the DID URI were "did:[valid Nostr URI]"?

Greetings! I'm guiding 10 people on how to invest in stocks, turning an investment of $160 into $6,200 in just 2 hours. If you’re curious, feel free to DM me with 'want to know how'. Don’t let this opportunity slip away; message me for more info!

TEXT SMS: +1 (703) 879-8125

WhatsApp: +1 (873) 300-3966

Check the WhatsApp link below 👇👇👇👇

https://wa.me/message/M2YPIT5J6LL3A1

Awesome to see that you've continued to chip away here nostr:nprofile1qqsdulkdrc5hdf4dktl6taxmsxnasykghdnf32sqmnc7w6km2hhav3gpzpmhxue69uhkummnw3ezumt0d5hs7a7gha . Great stuff