feat: contract specified encryption/decryption keys (stage 1 contract bounds)#1358
Merged
Conversation
…nto feat/contractBoundsV2
Member
Author
|
Merging as all tests are passing |
6 tasks
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Issue being fixed or feature implemented
This feature is for contract bounds, contract bounds allow for the ability to say that a contract has specific encryption or decryption keys associated to it, or to a document type.
What was done?
How Has This Been Tested?
Added multiple tests, however this has not been tested with actual state transitions.
Breaking Changes
Checklist:
For repository code-owners and collaborators only