1

On Quorum_Node1 I am sending a transaction with privateFor: parameter as follows: 

eth.sendTransaction({from: eth.accounts[0], to: "0xca84356...9a3d0ccf92b8e", 
data: web3.toHex('sample message for node 2'),privateFor:
['QfeDAys9MPDs2XHExtc84jKGHxZg/aj52DTh0vtA3Xc=']})

Where QfeDAys9MPDs2XHExtc84jKGHxZg/aj52DTh0vtA3Xc= is a public key of Transaction Manager on Quorum Node2

When I try to get the transaction data on Quorum Node2 via: 

eth.getTransaction("0x26a550c39b816...97c6f6eb35c3953e53b7")

I am getting an encrypted payload. Ideally, I should receive hex representation of the data sent in the original transaction.

Is this possible in Quorum or it works just with contracts?

Improve this question
1
  • 1
    Quorum uses the regular eth transaction to send an encrypted payload hash (you found it) and an additional P2P layer (Constellation or Tessera) to send encrypted transactions.
    – Rob Hitchens
    Feb 19, 2019 at 15:13

1 Answer 1

Reset to default
2

so as pointed out in comments, when you read the transaction on any node, you receive the encrypted hash of the transaction and not the actual payload. To access the payload, you would run this api on node 2.

Improve this answer

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.