From b1d5ee66cd0d598f7f7a70391d1181a43d89d3c0 Mon Sep 17 00:00:00 2001
From: Patrick Amrein <47777208+ubamrein@users.noreply.github.com>
Date: Wed, 9 Jun 2021 13:12:52 +0200
Subject: [PATCH] Update README.md

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 9236334..cc82c0a 100644
--- a/README.md
+++ b/README.md
@@ -2,4 +2,4 @@
 
 This repo contains code to study CWTs. We use `serde_cbor` for deserializing and follow the [CWT](https://tools.ietf.org/html/rfc8392#page-5) specification.
 
-We check our implementation with the samples from the RFC and also parse the example data found [here](https://github.com/eu-digital-green-certificates/dgc-testdata). Sadly, currently the CWT on the `dgc-testdata` `README` uses a SHA1 algorithm, which we won't support and should not be supported according to the (Digital Green Certificates outline)[https://ec.europa.eu/health/sites/health/files/ehealth/docs/digital-green-certificates_v1_en.pdf] c.f. Section 3.3.2.
\ No newline at end of file
+We use this implementation for an online hcert viewer and signature verifier for debugging purposes. Further, we use this to generate custom weird and broken hcerts to verify that decoding issues are caught.