-
Notifications
You must be signed in to change notification settings - Fork 281
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.
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
feat(quorum): private transaction support #2293
feat(quorum): private transaction support #2293
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just write a detailed commit message for this and create follow-up issues to address the issue of privateUrl
being truely optional. Right now we are passing privateUrl in all the instances of QuorumConnector even though we don't need to do private transactions everywhere.
The follow up issue can also include 2 test cases, one showcasing private tx (the newly created file in this PR) and a seperate test file showing public tx (a similar file as packages/cactus-plugin-ledger-connector-quorum/src/test/typescript/integration/plugin-ledger-connector-quorum/deploy-contract/v2.3.0-deploy-contract-from-json-private.test.ts
, but just doing the public tx). Also that issue can include renaming of this privateUrl to something more specific, maybe a rpcApiHttpHost
and another field being privacyEnabled
set as true/false.
@petermetz are the expectations from the follow-up issues fine? (Or anything more required, given this PR being the current state of enabling private tx)
.../cactus-plugin-ledger-connector-quorum/src/main/typescript/plugin-ledger-connector-quorum.ts
Outdated
Show resolved
Hide resolved
eba671e
to
7fea3a0
Compare
...gin-ledger-connector-quorum/deploy-contract/v2.3.0-deploy-contract-from-json-private.test.ts
Outdated
Show resolved
Hide resolved
@jagpreetsinghsasan Sorry for the slow response! We do need a good test case verifying that the private transactions that the connector can now allegedly run actually are private (otherwise the implementation in the connector is broken). |
229711f
to
3ac6a46
Compare
@aldousalvarez I see some commits being pushed into the PR after the last review comment, if you think its ready, please |
@jagpreetsinghsasan I tried to update my branch with the latest commit at that time. my apologies I am still working on it as of now. Thank you |
3ac6a46
to
21bfd35
Compare
----------------------------------------- - Added v2.3.0-deploy-contract-from-json-private.test.ts that would support private transaction test for Quorum. - Added a QuorumPrivateTransactionConfig on openapi.json - Added Web3JsQuorum on plugin-ledger-connector-quorum and added a transact private method to be able to proceed with the private transaction. - Currently the privateUrl in the test is being truely optional and we need to address this in the future. - We are just passing privateUrl in all the instances even though we don't need to do private transactions everywhere. Fixes hyperledger-cacti#951 Co-authored-by: Travis Payne <travis.payne@accenture.com> Co-authored-by: johnhomantaring <john.h.o.mantaring@accenture.com> Co-authored-by: jagpreetsinghsasan <jagpreet.singh.sasan@accenture.com> Co-authored-by: aldousalvarez aldousss.alvarez@gmail.com Co-authored-by: Peter Somogyvari <peter.somogyvari@accenture.com> Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
21bfd35
to
00bbaa4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@aldousalvarez @jagpreetsinghsasan I pushed some minor changes to greatly reduce the diff and also did a rebase onto upstream/main. LGTM as-is now. Thank you all!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Fixes #951
Co-authored-by: Travis Payne travis.payne@accenture.com
Co-authored-by: johnhomantaring john.h.o.mantaring@accenture.com
Co-authored-by: jagpreetsinghsasan jagpreet.singh.sasan@accenture.com
Co-authored-by: aldousalvarez aldousss.alvarez@gmail.com