As of July 1st 2023 the EU DCC project has been handed over to the WHO. The project has therefore been frozen. This repository will be placed into archival mode and will remain available for the foreseeable future, however it will no longer be actively maintained.
Welcome to the official home of the EU DCC (Digital Covid Certificate) on Github. Here you will find the specifications of the DCC system - HCERT, Schema, Value sets, and Business Rules.
In addition, we gratefully host example implementations of various components of the DCC. We aim to provide examples in a broad range of languages and platforms and welcome any contributions. Do you have something that you would like to contribute? Then read contributing.md and get started today.
If you just want to see how the entire system in action on your own computer: check out this repository.
eHN defines, specifies, manages and provides sample implementations of the HCERT (the specification) and DCC (the EU implementation). Member States (from the European Economic Area, which encompasses more countries than the EU Member States) implement the specifications. TSi provide open source reference implementations of the DCC. In addition, they operate the EU trust Gateway (DGCG) including onboarding services.
The sister organization EU Digital Green Certificates - managed by TSi - is the home of the official reference implementations of the DCC gateway, Holder and Verifier apps and associated tooling.
A number of Member States have open sourced their implementations, including their signing services, Holder apps and Verifier apps. You can find an overview of them here.
The DCC specifications have been split into four repositiros:
- eu-dcc-schema specifies the DCC schema (the specification of the data stored within the DCC).
- eu-dcc-valuesets provides the valueset datastructures and a snapshot of the valuesets (the current versions are published on the DCCG Gateway.
- eu-dcc-business-rules specifies the Business Rules framework.
- eu-dcc-hcert-spec specifies the container and encoding formats used by the DCC.
You can find these repositories pinned on our github homepage.
We have a team of maintainers who monitor the above mentioned pinned repositories. If you have questions or suggestions please feel free to open an issue on the respective repository.
The core repositories are maintained a small group of people attached to EU Member States or the European Commission.
| Repository | Teams |
|---|---|
| eu-dcc-overview | eu-dcc-overview-editors |
| eu-dcc-schema | eu-dcc-schema-editors |
| eu-dcc-valuesets | eu-dcc-valueset-editors |
| eu-dcc-business-rules | eu-dcc-business-rules-editors |
| eu-dcc-hcert-spec | eu-dcc-hcert-spec-editors |
The remaining repositories have been donated by parties and are maintained by them. Feel free to raise issues on them, if you feel that they need the attention of the core team (for example you have found a bug) then you may also raise an issue on this repository (the overview).
- DCC Issuer website created by the Austrian team which let you generate a DCC using an example signing key (or you can provide your own).
- DCC Verifier website created by a member of our team where you can scan a DCC, verify it and view the contents. Verification supports both Production and Acceptance environments.
- DCC Validation website created by a member of our team where you can view all of the QA DCC and are supported in a validation process.
There is a large amount of documentation and knowledge of the DCC but it can be hard to find. We maintain an overview of important documentation here to help with this.
If you have questions or find something hard to understand please feel make an issue on this repository and we'll see if we can improve the documentation to help.
| Document | Description |
|---|---|
| EC eHealth and COVID-19 | Homepage of EU-DCC at the EC, here you'll find all of the officially published technical documentation as well as the various forms and procedures required for onboaring of non-EU countries (referred to as "Third Countries" in EC parlance) |
| Implementing decisions | Implementing decisions between the EU and Third Countries are published here. |
| Key documents | Key legal documents, ammendments etc |
| Revocation B2B | Documentation of the revocation B2B API from the gateway |
In the FAQ folder you can find answers to a number of common questions as well as a selection of detailed guides and "how tos" written and maintained by the core team.
| Link | Description |
|---|---|
| Convert public/private keypair to x509 chain | Technical guide to converting a public/private keypair into a full x509 certificate chain. Useful if you have existing infrastructure which you wish to issue DCCs from your existing DIVOC or SHC system. |
| Create a valid DCC payload | Guide to issuing a valid DCC, this covers a lot of edge cases such as how to correctly encode boosters and vaccination DCC based on combinations of recovery/vaccination. |
In this repository we host a number of implementations of the DCC and forks of a several implementations which are used in production DCC deployments by various Member States.
If you're getting started or just want to under how the DCC fits together then check out the fully worked example of the full stack here. It's written in simple Python and is easy to understand even for those with little Python experience.
Here's an overview of most of the repositories under the organisation. Please refer to the repositories themselves for information on licenses, contribution policies etc.
| Repository | Description |
|---|---|
| base45-ansi-c | base45 encoder/decoder in C |
| base45-cs | base45 encoder/decoder in C# |
| base45-java | base45 encoder/decoder in Java |
| base45-js | base45 encoder/decoder in Javascript |
| base45-php | base45 encoder/decoder in PHP |
| base45-swift | base45 encoder/decoder in Swift |
| DccCachingService | Caches trustlist, business rules, valuesets on the device built in Swift (iOS) |
| DGCValidator | Cross-platform verifier app build in Xamarin |
| hcert-app-swift | HCERT validation app in Swift (iOS) |
| hcert-app-kotlin | HCERT validation app in Kotlin (Android) |
| hcert-dotnet | HCERT validation and creation in C# (Xamarin/server) |
| hcert-java | HCERT validation and creation in Java (Android/server) |
| hcert-kotlin | HCERT validation and creation in Kotlin (Android) |
| hcert-service-kotlin | HCERT creation service (server) , deployed here |
| icao-ml-Tools | Scripts to download, parse and cross-reference public ICAO master lists |
| python-hcert | HCERT validation and creation in Python (server) |
| ValidationCore | Validation libraries for both iOS and Android |
| x509-resign | Tool to resign x509 cert |
| ehn-dcc-vsu | Prototype client-server to demonstrate how clients can update to the latest Digital COVID Certificate (DCC) value sets |
| ehn-ecdsa-verify-mbed | Simple MBED-TLS code for verifying an ECDSA signature as used in DCCs |
CBOR Object Signing and Encryption (COSE) is used data format for the DCC payload and signature.
Various implementors make use of the Javascript implementation erdtman/cose-js (forked here) and the Java implementation cose-wg/COSE-JAVA (forked here)
Keys from acceptance can be used to verify the example QR codes in the Quality Assurance repository.
| Country | URL |
|---|---|
| NL | https://webtooling.rdobeheer.nl/unpacker/?shit=https://verifier-api.acc.coronacheck.nl/v9/verifier/public_keys |