Replies: 1 comment
-
That is true, the coupling is too tight. The current implementation of didcomm will be replaced with didcomm v2 which has other crypto requirements and will likely require some breaking changes in the KMS layer. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
DIDComm plugin implementation is tightly coupled with Private/Public Key and depending on KMC to sign/encrypt the data.
So is there is any plan to make it less coupled because on our project we are planning to use HSM instead of normal DB?
Beta Was this translation helpful? Give feedback.
All reactions