Feature/add privacy marker transactions #58
Merged
Conversation
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
2 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.
Add support for Privacy Marker Transactions (released in go-quorum v21.7.1).
Note that this PR builds on top of PrivacyEnhancements PR (in the expectation that older PR would be merged to master prior to this one).
These changes mirror the changes made to web3js-quorum in PR#24 and PR#25.
New API methods:
Transaction receipt modification:
Modified Transaction Receipt to include extra field:
Retrieve contract address from private receipt:
If contract is deployed using
ClientTransactionManagerand the transaction is a Privacy Marker, then the receipt for the inner private transaction is retrieved to obtain the contract address for participants.