I am using Web3 to send a transaction to a smart contract address. The public transactions are working OK. However, when I use the PrivateFor parameter in the web3 call, the transaction is still sent to the nodes but not working correctly.

Is this a configuration issue or web3 does not support for PrivateFor transaction as yet?

Thank you.

  • Can you provide more details about the "not working correctly" part? Is there an error message? Aug 9 '18 at 8:06

The question is not explaining all the details.

**Suggestion: **

  • Make sure you are using web3-quorum package from below link:

quorum-web3 npm package

  • I was using the latest web3 beta. quorum-web3 is abit behind. I have a huge smart contract that I am unable to deploy to the blockchain. Other than changing the maxCodeSize, and recompiling the code, do you know how to work around that?
    – Nathan Aw
    Aug 9 '18 at 11:39
  • Web3 beta and web3-quorum serves different purpose, you can't just use web3 beta for quorum development, you have to use the web3-quorum for that. web3 beta is for ethereum, it doesn't include all the functionality of web3-quorum.
    – geekybot
    Aug 22 '18 at 10:43

You can try using quorum.js which is the official release of web3.js for quorum. You can read it here: https://github.com/jpmorganchase/quorum/issues/604

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.