I’ve run into an issue with Quorum, where do I get support?
The Quorum Slack channels are the best place to query the community and get immediate help.
How does Quorum achieve Transaction Privacy?
Quorum achieves Transaction Privacy by:
- Enabling transaction Senders to create a private transaction by marking who is privy to that transaction via the
- Replacing the payload of a private transaction with a hash of the encrypted payload, such that the original payload is not visible to participants who are not privy to the transaction
- Storing encrypted private data off-chain in a separate component called the Transaction Manager (provided by Constellation or Tessera). The Transaction Manager distributes the encrypted data to other parties that are privy to the transaction and returns the decrypted payload to those parties
Please see the Transaction Processing page for more info.
How does Quorum achieve consensus on Private Transactions?
In standard Ethereum, all nodes process all transactions and so each node has the same state root. In Quorum, nodes process all ‘public’ transactions (which might include reference data or market data contracts for example) but only process the private transactions that they are party to.
Quorum nodes maintain two Patricia Merkle Tries: one for private state and one for public state. As a result, block validation includes a state check on the new-to-Quorum
public state root. Block validation also includes a check of the
global Transaction hash, which is a hash of all Transactions in a block - private and public. This means that each node is able to validate that it has the same set of Transactions as other nodes. Since the EVM is provably deterministic through the synchronized public state root, and that the Private Transaction inputs are known to be in sync across nodes (global Transaction Hash), private state synchronization across nodes can be implied. In addition, Quorum provides an API call,
eth_storageRoot, that returns the private state hash for a given transaction at a given block height, that can optionally be called at the application layer to specifically perform an off-chain state validation with a counterparty.
Are there any restrictions on the transaction size for private transactions (since they are encrypted)?
The only restriction is the gas limit on the transaction. Constellation/Tessera does not have a size limit (although maybe it should be possible to set one). If anything, performing large transactions as private transactions will improve performance because most of the network only sees hash digests. In terms of performance of transferring large data blobs between geographically distributed nodes, it would be equivalent performance to PGP encrypting the file and transferring it over http/https..so very fast. If you are doing sequential transactions then of course you will have to wait for those transfers, but there is no special overhead by the payload being large if you are doing separate/concurrent transactions, subject to network bandwidth limits. Constellation/Tessera does everything in parallel.
Should I include originating node in private transaction?
No, you should not. In Quorum, including originating node’s
privateFor will result in an error. If you would like to create a private contract that is visible to the originating node only please use this format:
privateFor:  per https://github.com/jpmorganchase/quorum/pull/165
Is it possible to run a Quorum node without a Transaction Manager?
Starting a Quorum node with
PRIVATE_CONFIG=ignore (instead of
PRIVATE_CONFIG=path/to/tm.ipc) will start the node without a Transaction Manager. The node will not broadcast matching private keys (please ensure that there is no transaction manager running for it) and will be unable to participate in any private transactions.
Is there an official docker image for Quorum/Constellation/Tessera?
Yes! The official docker containers:
Can I create a network of Quorum nodes using different consensus mechanisms?
Unfortunately, that is not possible. Quorum nodes configured with raft will only be able to work correctly with other nodes running raft consensus. This applies to all other supported consensus algorithms.
Known Raft consensus node misconfiguration
Quorum version compatibility table
|Adding new node v2.0.x||Adding new node v2.1.x||Adding new node v2.2.x|
|Existing chain consisting of v2.0.x||block sync
|block sync||block sync|
|Existing chain consisting of v2.1.x||block sync||block sync
|Existing chain consisting of v2.2.x||block sync||block sync
Note: While every Quorum v2 client will be able to connect to any other v2 client, the usefullness will be severely degraded. Red color signifies that while connectivity is possible, red colored versions will be unable to send public or private txns to the rest of the net due to the EIP155 changes in the signer implemented in newer versions.