Skip to main content

Interoperability Tests: the WE BUILD and NXD Trust Lists in the iGrant.io Organisation Wallet Suite

Specifications:

In short​

  • We added every list of the WE BUILD List of Trusted Lists (12 lists) and every list of the NXD Trust List as trust anchors in the iGrant.io Organisation Wallet Suite, on the demo server, on 18 November 2026.
  • All 12 WE BUILD lists load: each one is current, its signature verifies with the signer certificate that the List of Trusted Lists gives, and all 137 entries can be used by the checks.
  • Six of the eight NXD lists load in XML, with verified signatures. The other two, the lists of registration certificate providers and of registrars and registers, are empty today.
  • The JSON form of the NXD lists loads, but its signature does not verify. Use the XML form.

How we test​

For each list, we:

  1. Add it as a trust anchor, with the kind and the Used As role of the list, and with its list signer certificate.
    • For a WE BUILD list, the certificate comes from the pointer to the list in the WE BUILD List of Trusted Lists (https://webuild-consortium.github.io/wp4-trust-group/list_of_trusted_lists.xml).
    • For an NXD list, it is the NXD Foundation certificate that signs all NXD lists.
  2. Read the state of the list, whether its signature verified, and its entries, as the Trust Anchors page and the Trust Sources API show them.

A list that cannot be read, or whose signature does not verify with the given certificate, is refused when it is added (trust_source.list_not_usable). See Manage Trust Anchors.

The WE BUILD List of Trusted Lists​

The WE BUILD WP4 trust group publishes a List of Trusted Lists (TS 119 612) that points to the test lists of the pilot's trust registries: IDunion, Credimi and the NXD Foundation.

ListKindUsed AsStateSignatureServicesEntries
IDunion PID ProvidersETSI LOTEPID providerCurrentVerified1313
IDunion Wallet ProvidersETSI LOTEWallet providerCurrentVerified2525
IDunion PuB-EAA ProvidersETSI LOTEPuB-EAA providerCurrentVerified1515
IDunion QEAA ProvidersETSI TLQEAA providerCurrentVerified1212
IDunion SCA Attestation IssuersETSI TLEAA providerCurrentVerified88
IDunion WRPAC ProvidersETSI LOTEAccess certificate providerCurrentVerified1111
IDunion WRPRC ProvidersETSI LOTERegistration certificate providerCurrentVerified33
IDunion Registrars and RegistersETSI LOTEAny role except Status issuer: the list names no role, and no check needs this list (see finding 2)CurrentVerified88
Credimi QEAA ProvidersETSI TLQEAA providerCurrentVerified11
Credimi EAA ProvidersETSI TLEAA providerCurrentVerified11
NXD QEAA ProvidersETSI TLQEAA providerCurrentVerified22
NXD EAA ProvidersETSI TLEAA providerCurrentVerified3438

Services and entries. A service with more than one certificate gives more than one entry. For example, the 34 services of the NXD EAA list give 38 entries.

The NXD Trust List​

ListKindUsed AsResultServicesEntries
NXD-TL-WalletProviders.xmlETSI LOTEWallet providerCurrent, signature verified56
NXD-TL-PID.xmlETSI LOTEPID providerCurrent, signature verified1117
NXD-TL-PubEAA.xmlETSI LOTEPuB-EAA providerCurrent, signature verified66
NXD-TL-QEAA.xmlETSI TLQEAA providerCurrent, signature verified22
NXD-TL-EAA.xmlETSI TLEAA providerCurrent, signature verified3438
NXD-TL-WRPAC.xmlETSI LOTEAccess certificate providerCurrent, signature verified5761
NXD-TL-WRPRC.xmlETSI LOTERegistration certificate providerRefused: the list has no entries0
NXD-TL-Registrars.xmlETSI LOTENo roleNot added: a trust anchor needs a role, and the list has no entries0

Findings​

1. An empty list cannot be added. A list with no entries is refused with trust_source.list_not_usable ("the list has no entries"), even when its signature is valid. So you cannot add the NXD lists of registration certificate providers or of registrars and registers yet. Add them once they have entries.

2. There is no role for registrars and registers. A trust anchor needs one Used As role, and no role fits a list of registrars and registers (TS 119 602 Annex I).

3. The NXD JSON lists: entries yes, signature no.

  • The Organisation Wallet Suite reads the JSON form of an NXD list, for example nxd-pid-providers-lote.json, with the same 11 services as the XML form.
  • With the NXD signer certificate, it refuses the list: "the list signature does not verify with the signer certificates".
  • The NXD JSON list has its signature in a signature member, over a form of the document that the wallet does not make again, so the signature does not verify.

Until this is aligned, add the XML form of each NXD list.

4. Other statuses. The Credimi EAA list gives its entry the status recognisedatnationallevel of ETSI TS 119 612, which the checks accept.

5. An expired certificate in a list. One entry of the NXD WRPAC list has a certificate that has expired. The list stays usable; a check that meets that entry gives not_trusted with the reason certificate_not_valid.

6. The legacy NXD lists. The NXD legacy lists (NXD-TL.xml, EWC-TL.xml) are not in the WE BUILD List of Trusted Lists. Two points about them:

  • Their status URIs are not the registered ETSI URIs: they use https and end in a slash.
  • A lookup match in them returns an empty prohibitedCredentials.

Use the per-role lists.

Add these lists yourself​

  • For the NXD Trust List, use the table in Manage Trust Anchors. It gives the kind and the Used As role of each list.
  • For a WE BUILD list:
    1. Take its URL and its signer certificate from the WE BUILD List of Trusted Lists.
    2. Add it with the kind and role of the table above. A list of registrars and registers has no role yet. Give it a name of your own: the IDunion lists all end in tl.xml.
    3. Add each trust anchor to the accepted lists of the checks that should use it.