Re: New Work Item Proposal: Data Integrity BIP340 Cryptosuite

ne 10. 8. 2025 v 19:17 odesílatel Dr John O'Hare <w3c@xrsystems.uk> napsal:

> Really exciting to see. I'd kinda given up on DID / zk proofs etc; a
> couple of years ago to be honest, but this is hugely accessible to my vibe
> coding brain.
>

Cool, hope you find it useful!  Report back if you are able to make
anything, or want to propose a CG work item.  We would be happy to help :)


>
> On Sunday, 10 August 2025 at 17:59, Melvin Carvalho <
> melvincarvalho@gmail.com> wrote:
>
>
>
> ne 10. 8. 2025 v 18:15 odesílatel Dr John O'Hare <w3c@xrsystems.uk>
> napsal:
>
>> That's super useful thanks Melvin. I think I might try implementing this
>> into the back end of my knowledge system. How does the zero relay / point
>> to point system work? I think I've only ever used the relays.
>>
>
> It's a proposed spec right now, but I think it will be adopted by the CCG
>
> https://dcdpr.github.io/data-integrity-schnorr-secp256k1/
>
> Just run it through an LLM with questions, and then post back here if
> anything is unclear
>
>>
>> Is there code for protocol agnostic credentials around yet? ie, expanding
>> on your point about it being cross compatible?
>>
>
> That would be the verifiable credentials stack. It will be widely used, I
> think
>
> https://en.wikipedia.org/wiki/Verifiable_credentials
>
>>
>> On Saturday, 9 August 2025 at 21:58, Melvin Carvalho <
>> melvincarvalho@gmail.com> wrote:
>>
>> 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
>>>
>>
>>
>