Skip to main content

Credential Type Registry

The SIROS Foundation maintains a public registry for publishing credential type metadata at registry.siros.org.

Purpose​

The registry provides a publication platform for organizations to share their credential type metadata files (including VCTM). It serves as:

  • A storage backend for credential type metadata organized by organization
  • A publication point where credential type metadata can be discovered
  • An aggregation service that collects metadata from multiple sources
Important Distinction

The registry is a publication mechanism, not a resolution service. Credential type resolution (looking up metadata by VCT identifier or mdoc doctype) is done by the consumers: the VC platform (common.credential_registry, see Resolving Credential Types from a Registry) and go-wallet-backend can both use registry.siros.org as a backend.

Don't confuse the "registries"

The SIROS ecosystem has four components that use the word "registry" — they serve different purposes:

ComponentRoleDescription
registry-cliPublisherCLI tool that builds the credential type catalogue (the static site at registry.siros.org). This is the publishing side.
registry.siros.orgCatalogueThe public static site produced by registry-cli.
VC registry (vc/registry)Token Status ListsA completely separate service in the VC suite that manages credential revocation via Token Status Lists. It has nothing to do with credential type metadata.
go-wallet-backend registry (the registry role of the go-wallet-backend binary, image go-wallet-registry)Consumer/cacheA service in go-wallet-backend that fetches and caches credential type metadata from registry.siros.org (or any compatible source). This is the consuming side.

In short: registry-cli publishes credential type metadata, go-wallet-backend's registry (and the VC platform) consume it, and VC's registry manages revocation — an entirely unrelated concern.

What is VCTM?​

Verifiable Credential Type Metadata (VCTM) files define how credentials should be displayed and what claims they contain. They follow the IETF SD-JWT VC specification.

Visit registry.siros.org for details on available credential types and how to publish your own.