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

[VC Issuance] Use persistent storage for VCs and Revocations #181

Merged
merged 4 commits into from
Feb 9, 2024
Merged

[VC Issuance] Use persistent storage for VCs and Revocations #181

merged 4 commits into from
Feb 9, 2024

Conversation

MarioRodriguezS
Copy link
Contributor

Description

Fixes #179

Type of change

  • New feature (non-breaking change which adds functionality)

Checklist

  • My code follows the style guidelines of this project
  • I have performed a self-review of my code
  • I have commented on my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my change

miguelnietoa
miguelnietoa requested changes Feb 9, 2024
View reviewed changes
Copy link
Member

@miguelnietoa miguelnietoa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@MarioRodriguezS comments added

vc_issuance_contract/README.md Show resolved Hide resolved
@MarioRodriguezS MarioRodriguezS force-pushed the change-persistence-in-vc-issuance-contract branch from 5039664 to 2c05c23 Compare February 9, 2024 21:22
@MarioRodriguezS MarioRodriguezS merged commit 31507bc into kommitters:v0.17 Feb 9, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@miguelnietoa miguelnietoa miguelnietoa approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@MarioRodriguezS @miguelnietoa