Removing the un-used and no longer needed key state escrow. #538
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…databases since key state notices are no longer top level KERI events and can not end up in escrow.
dhh1128
pushed a commit
to dhh1128/keripy
that referenced
this pull request
Jul 20, 2023
…databases since key state notices are no longer top level KERI events and can not end up in escrow. (WebOfTrust#538)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR removes the key state escrow logic and databases since key state notices are no longer top level KERI events and can not end up in escrow. The processing was actually disabled a while ago when KSNs were shifted to only being sent embedded in reply messages.