Igrantio dcql credential sets

Skill L3-iGrant/skills/workflows/igrantio-dcql-credential-sets

DCQL pattern: credential_sets with alternatives - accept any one of several identity credentials (PID, Passport, or Photo ID, all dc+sd-jwt with cryptographic holder binding) in a single OpenID4VP verification on the iGrant.io Organisation Wallet Suite. Proof of identity for EUDI Wallet (EUDIW) relying parties under eIDAS 2.0 when multiple credential types are acceptable.From its SKILL.md

Install

npx -y skills add L3-iGrant/skills --skill igrantio-dcql-credential-sets

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.3 KB, 675 tokens by cl100k_base, as published. Nobody here has run it

DCQL: credential sets (identity alternatives)

Scenario

A verifier needs proof of identity and accepts any one of PID, Passport, or Photo ID. The wallet presents whichever the holder has; options are tried in order.

Before you build: run the integrator intake in igrantio-ows-overview - environment, API key, tenancy, backend host, webhooks, frontend - one question at a time, a recommended default with each.

The DCQL query

{
  "credentials": [
    {
      "format": "dc+sd-jwt",
      "id": "Passport",
      "meta": {
        "vct_values": [
          "Passport"
        ]
      },
      "require_cryptographic_holder_binding": true
    },
    {
      "format": "dc+sd-jwt",
      "id": "PID",
      "meta": {
        "vct_values": [
          "urn:eu.europa.ec.eudi:pid:1"
        ]
      },
      "require_cryptographic_holder_binding": true
    },
    {
      "format": "dc+sd-jwt",
      "id": "Photo ID",
      "meta": {
        "vct_values": [
          "eu.europa.ec.eudi.photoid.1"
        ]
      },
      "require_cryptographic_holder_binding": true
    }
  ],
  "credential_sets": [
    {
      "options": [
        [
          "PID"
        ],
        [
          "Passport"
        ],
        [
          "Photo ID"
        ]
      ],
      "required": true
    }
  ]
}

Run it on OWS

Store as a presentation definition; keep the presentationDefinitionId.
Send the verification request (v3); QR or DC API.
On presentation_acked + verified === true, inspect presentationSubmission to learn WHICH alternative was presented, then read its claims from presentation[0].

Adjust for your deployment

Order options by preference - wallets try them in order.
Set each vct_values to the VCTs your issuers actually use; add claims entries per credential if you need specific attributes disclosed.
Keep require_cryptographic_holder_binding: true unless you have a reason not to; it prevents replay of copied credentials.

Cross-references

igrantio-dcql-kyc - two required groups (identity + address) instead of one group of alternatives.
igrantio-dcql-trusted-authority - add issuer trust restrictions per credential.

Source of truth

This workflow mirrors https://docs.igrant.io/docs/dcql-2-4-3-credential-set-proof-of-identity-alternatives/ (query detailed in https://docs.igrant.io/concepts/eudi-wallet-dcql-openid4vp-business-wallet-payments/, §2.4.3). Before implementing, fetch the doc page; if it disagrees with this skill, the documentation wins - follow it and report the drift so the skill can be updated.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.