Re: New Work Item Proposal: Data Integrity BIP340 Cryptosuite

Been chatting to the CCG group about did:nostr and verifiable credentials,
and it looks like did:nostr should be compatible with VCs, now.

While still a work in progress, here is the outline of what a nostr VC
could look like, for example (according to GPT), a drivers license for a
nostr user.

Some have expressed interest in implementing VCs, so this should be a step
towards that

{
  "@context": [
    "https://www.w3.org/ns/credentials/v2",
    {
      "dl": "https://example.org/driver-license#"
    },
    "https://w3id.org/security/multikey/v1"
  ],

  "id": "urn:uuid:51fa0f0d-8b63-4ad7-9f85-424af6e99830",
  "type": ["VerifiableCredential", "DriverLicenseCredential"],

  /* —— canonical Nostr issuer ———————————————— */
  "issuer":
"did:nostr:124c0fa99407182ece5a24fad9b7f6674902fc422843d3128d38a0afbee0fdd2",

  "issuanceDate": "2025-08-04T12:00:00Z",
  "expirationDate": "2029-05-01T00:00:00Z",

  "credentialSubject": {
    "id":
"did:nostr:abcdefabcdefabcdefabcdefabcdefabcdefabcdefabcdefabcdefabcdef",
    "dl:licenseNumber": "CA-DL-1234567",
    "dl:issuedIn": "CA",
    "dl:name": "Alice Example",
    "dl:birthDate": "1990-07-12"
  },

  /* —— BIP-340 proof in the new cryptosuite —————— */
  "proof": {
    "type": "DataIntegrityProof",
    "cryptosuite": "bip340-jcs-2025",
    "created": "2025-08-04T12:00:05Z",
    "verificationMethod":

"did:nostr:124c0fa99407182ece5a24fad9b7f6674902fc422843d3128d38a0afbee0fdd2#key-1",
    "proofPurpose": "assertionMethod",

    /* 64-byte BIP-340 signature — dummy value here */
    "proofValue":

"z3RfvM6kXG2qRhC9qgy1H6kUuS8U7U9H3RJSbVbHqPCA9kqTge9hKKxi2iXn8MDF9UxZ2KwgS2x9aFTyE3u1L6EG"
  }
}

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
>