- From: Melvin Carvalho <melvincarvalho@gmail.com>
- Date: Sat, 9 Aug 2025 22:58:17 +0200
- To: public-nostr@w3.org
- Message-ID: <CAKaEYhKJmPKWdyhAD1QH=1ntbjif4qFczyxJfWHitVwU-ZFskw@mail.gmail.com>
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: https://github.com/w3c-ccg/community/issues/254#issuecomment-3172061021 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! ne 3. 8. 2025 v 19:10 odesílatel Melvin Carvalho <melvincarvalho@gmail.com> napsal: > FYI > > ---------- Forwarded message --------- > Od: Will Abramson <wip.abramson@gmail.com> > Date: čt 31. 7. 2025 v 18:13 > Subject: New Work Item Proposal: Data Integrity BIP340 Cryptosuite > To: Credentials Community Group <public-credentials@w3.org> > > > Hello CCG community, > > Digital Contract Design in collaboration with Legendary Requirements and > Danube Tech are proposing a new CCG Work Item for adoption: > https://dcdpr.github.io/data-integrity-schnorr-secp256k1/ > > See the proposal issue here: > https://github.com/w3c-ccg/community/issues/254 > > We feel this is important as there are currently no up to date Data > Integrity cryptosuites available for the secp256k1 curve, which has wide > adoption throughout multiple blockchain ecosystems. > > Thanks, > All the best, > Will Abramson >
Received on Saturday, 9 August 2025 20:58:33 UTC