[BUG] Iroha doesn't panic and shut down if the key pairs for IROHA_GENESIS_ACCOUNT
are completely different for each peer.
#3195
Labels
Bug
Something isn't working
Dev defect
The defect was found at the development stage. Did not have an impact on users.
iroha2-dev
The re-implementation of a BFT hyperledger in RUST
QA-confirmed
This bug is reproduced and needs a fix
OS and Environment
MacOS, Docker Hub
GIT commit hash
44ec1a1
Minimum working example / Steps to reproduce
IROHA_GENESIS_ACCOUNT
key pairs for each peerdocker-compose.yml
Actual result
Error and continue working.
Expected result
Panic and shut down
Who can help to reproduce?
@astrokov7
Notes
If your original leader gives you the incorrect genesis, you can't continue. The network needs to restart with a different topology. If you're bootstrapping it's a different situation, though.
The text was updated successfully, but these errors were encountered: