You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Branch, Commit Hash or Release: ee498061b5a74bf1f3290139a53840345fa038cb
Expected behaviour
We are using IBFT consensus over Quorum v.2.0.1 and Constellation 0.3.1.
We don't want our validator nodes to start constellation and PRIVATE_CONFIG isn't defined because we want them to be specialized in running the consensus algorithm.
When a regular node starts a private transaction the validator node must mine the block.
Actual behaviour
When a regular node starts a private transaction, the validator node raises a runtime error and terminates.
Steps to reproduce the behaviour
Don't start constellation with Geth in one node and send a private transaction.
Right, this is not a consensus issue. Quorum expects to have a Constellation node configured if it sees private transactions because it needs to check with that Constellation node to ensure it's not a recipient. This is mostly to avoid a scenario where somebody forgets to set PRIVATE_CONFIG , but it doesn't have to be that way.
@marcossanlab What if we added PRIVATE_CONFIG=ignore or similar to indicate that you explicitly want to ignore private transactions?
patrickmn
changed the title
IBFT - Panic if validator don't configure constellation
Panic if a node without PRIVATE_CONFIG set sees a private transaction
Feb 28, 2018
System information
Geth version:
1.7.2-stable
OS & Version: Linux
Branch, Commit Hash or Release:
ee498061b5a74bf1f3290139a53840345fa038cb
Expected behaviour
We are using IBFT consensus over Quorum v.2.0.1 and Constellation 0.3.1.
We don't want our validator nodes to start constellation and
PRIVATE_CONFIG
isn't defined because we want them to be specialized in running the consensus algorithm.When a regular node starts a private transaction the validator node must mine the block.
Actual behaviour
When a regular node starts a private transaction, the validator node raises a runtime error and terminates.
Steps to reproduce the behaviour
Don't start constellation with Geth in one node and send a private transaction.
Backtrace
Solution proposed
We make a fork of quorum repository and change core/state_transition.go verifying if private.P is nil.
The text was updated successfully, but these errors were encountered: