Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use custom KMS store implementation instead of Aries storage provider #119

Open
DRK3 opened this issue Aug 22, 2022 · 0 comments
Open

Use custom KMS store implementation instead of Aries storage provider #119

DRK3 opened this issue Aug 22, 2022 · 0 comments

Comments

@DRK3
Copy link
Collaborator

DRK3 commented Aug 22, 2022

With this change in Aries, a consumer of the Aries KMS interface can now inject in their own storage without being limited by the overall Aries storage interface defined in the spi module. For now, I'm using a wrapper as a bridge solution (the kms.NewAriesProviderWrapper call) to allow the KMS project to continue functioning, but in order to reap the benefits of this new storage design we should create our own implementation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
No open projects
TrustBloc Wallet/VCS
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
1 participant
@DRK3