DCC Issuer Coordinator
github.com
Spec sheet
- Purpose
- The app issues signed Verifiable Credentials and allows them to be revoked.Read 11 Oct 2026 · github.com
- Intended users
- The README describes using the issuer within a larger system, such as a school's credential issuance flow, with an API client sending credential data to be signed.Read 4 Oct 2026 · github.com
- Audience
- The README presents the issuer for organizations such as schools that integrate credential issuance into their own systems and student portals.Read 11 Oct 2026 · github.com
- Deployment
- The quick start runs prebuilt Docker Hub images through Docker Compose and the README says setup takes less than five minutes.Read 11 Oct 2026 · github.com
- API
- The service implements VC-API endpoints for issuing credentials and updating credential status, plus an endpoint for returning a status list.Read 4 Oct 2026 · github.com
- Integrations
- The README describes using the issuer from a larger system that prepares a credential and posts it to the issuer, and mentions importing credentials into the Learner Credential Wallet.Read 11 Oct 2026 · github.com
- License
- The repository identifies its license as MIT License, copyright 2023 Digital Credentials Consortium.Read 11 Oct 2026 · github.com
- Headquarters
- United StatesRead 28 Sep 2026 · github.com
- Founded
- 2018Read 28 Sep 2026 · github.com
- Architecture
- It is an Express app that coordinates calls to separate signing and status services running together in Docker Compose.Read 11 Oct 2026 · github.com
- Credential signing
- The README says the issuer supports the did:key and did:web DID formats for signing keys.Read 4 Oct 2026 · github.com
- Credential status
- Its optional revocation and suspension mechanism implements Bitstring Status List and stores status lists through database or Git services.Read 11 Oct 2026 · github.com
- Endpoint security
- Tenant endpoints can require a Bearer token, and the README suggests IP filtering; setting a tenant token to UNPROTECTED leaves its endpoint unprotected.Read 11 Oct 2026 · github.com
- Issuing API
- It implements the VC-API POST endpoints /credentials/issue and /credentials/status.Read 11 Oct 2026 · github.com
- Key support
- The issuer supports did:key and did:web key formats, and the README recommends did:web for many production deployments because keys can be rotated without updating credentials signed with old keys.Read 11 Oct 2026 · github.com
- Multiple issuers
- Tenants allow different signing keys and DIDs to be used for different credentialing purposes.Read 11 Oct 2026 · github.com
- Production guidance
- The README warns that the shared default signing key is only for testing and evaluation, and says issuers must generate and keep their own signing key private for real credentials.Read 11 Oct 2026 · github.com
- Revocation and suspension
- Optional status management implements Bitstring Status List and can store status lists using database or Git services.Read 4 Oct 2026 · github.com
- Security guidance
- The README warns that the shared test signing key is unsafe for real credentials and recommends configuring a private key and suggests IP filtering for issuer endpoints.Read 4 Oct 2026 · github.com
- Setup time
- The project says its four-step quick start should take less than five minutes.Read 4 Oct 2026 · github.com
- Status storage limit
- The README recommends database-backed status storage for production and testing, and Git-backed storage only for light testing or experiments.Read 11 Oct 2026 · github.com
- Support and contribution
- The README says pull requests are accepted.Read 11 Oct 2026 · github.com
- Tenants
- Multiple signing authorities can be configured as tenants, each with its own key and optional bearer-token protection.Read 4 Oct 2026 · github.com
- Wallet integration
- The README describes importing issued credentials into the Learner Credential Wallet and points to a separate exchange-coordinator for direct wallet exchange.Read 4 Oct 2026 · github.com
Where Specifiction places it
- Credentialing Software#23 of 317.5