From b1be1fe14ab254115f0ad2c1aee83a1d323af2e6 Mon Sep 17 00:00:00 2001
From: Paul Latzelsperger <43503240+paullatzelsperger@users.noreply.github.com>
Date: Wed, 14 Jun 2023 16:08:08 +0200
Subject: [PATCH] docs: add decision record about the use of
 iron-verifiable-credentials (#472)

---
 .../2023-06-13_use_of_iron_library/README.md  | 22 +++++++++++++++++++
 1 file changed, 22 insertions(+)
 create mode 100644 docs/development/decision-records/2023-06-13_use_of_iron_library/README.md

diff --git a/docs/development/decision-records/2023-06-13_use_of_iron_library/README.md b/docs/development/decision-records/2023-06-13_use_of_iron_library/README.md
new file mode 100644
index 000000000..1a51f0c18
--- /dev/null
+++ b/docs/development/decision-records/2023-06-13_use_of_iron_library/README.md
@@ -0,0 +1,22 @@
+# Usage of `iron-verifiable-credentials`
+
+## Decision
+
+Tractus-X EDC will use the [iron-verifiable-credentials](https://github.com/filip26/iron-verifiable-credentials) library
+for all processing of VerifiableCredentials and VerifiablePresentations.
+
+## Rationale
+
+The Eclipse Dataspaces Components project uses iron's sister
+library, [titanium-json-ld](https://github.com/filip26/titanium-json-ld/) for processing JSON-LD, which achieves close
+to 100% of conformance with the JSON-LD specification.
+
+It thus stands to reason that we use `iron-verifiable-credentials`, because it supports issuing/verifying VCs/VPs, has
+support for JSON-LD (internally it also uses `titanium-json-ld`) and otherwise has a very light dependency footprint.
+which means high runtime type compatibility can be expected and minimal mapping/compatibility layers are needed. Crypto
+suites are pluggable, so in addition to `iron-ed25519-cryptosuite-2020`, which is also provided, we will implement
+support for `JsonWebKey2020` which was mandated by the Catena-X consortium.
+
+## Approach
+
+- add support for `JsonWebKey2020` to Tractus-X EDC using `iron-verifiable-credentials`.