Support mandatory recipients #1243
Merged
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
…eject if PTM does not support correct version
chris-j-h
approved these changes
Aug 25, 2021
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.
The change is to allow users to add a
mandatoryForparameter when sending a transaction to Quorum. This feature is useful for use cases where there are requirements for regulatory/observing entities that will have access to the full state of a contract.Changes
MandatoryRecipients(2). Transactions sent with this enhanced privacy mode will inherit the validations ofPartyProtectionbut notStateValidation. It allows state divergence.mandatoryFor : []- which are private TM public keys - otherwise it will be rejectedmandatoryForwill need to be included in theprivateForotherwise transaction will be rejected./sendand/sendsignedtxrequests to private TM will include mandatory recipients datamandatoryFormembers will also be checked against the contracts that the transaction impact. This is achieved by evm simulation that returns a list of ACOTHs and validations performed in Tessera