Unclear trust anchors in the deployed registries

In the registry API it is only possible to validate a trust anchor if you already have a certificate of that trust anchor. Currently, the v1 and development versions have different trust anchors configured, since LetsEncrypt's ISRG Root X1 is accepted in development but not in v1.

It would be very helpfull to actually being able to browse the trust anchors to make sure participants can find the right anchor to use for their requests. Either via the API, or somewhere in documentation around the registries.

The used example:

POST https://registry.lab.gaia-x.eu/v1/api/trustAnchor/chain/file

{
  "uri": "https://wallet-gx.alpha.scsn.dataspac.es/keys/key-gx2"
}

Returns:

{
  "message": "Unable to validate certificate chain",
  "error": "Certificate Root not found in trusted anchors",
  "statusCode": 409
}

And for development:

POST https://registry.lab.gaia-x.eu/development/api/trustAnchor/chain/file

{
  "uri": "https://wallet-gx.alpha.scsn.dataspac.es/keys/key-gx2"
}

Returns:

{
  "result": true
}

Added complexity is that the development version of the compliance service is, I assume, connected to registry v1, which makes debugging even more difficult.