Shunkichi Sato

I'd suggest: - Shuffle on the nth view change, where n % 3 == 0 - Shift by `f`, otherwise The idea is to maximize the difference of the set...

According to [the code](https://github.com/hyperledger/iroha/blob/33ab59a1c6c3f4e85a842df3fbbdfbdcfe38fdf6/cli/src/main.rs#L37), the path to the `config.json` seems to be wrong. One solution will be to overwrite the path with `IROHA2_CONFIG_PATH` environment variable

Let me know the image IDs (preferably the original git commits) of the failing and succeeding containers @BAStos525

Have you checked that the remote instance and your local machine have the same hashes of `hyperledger/iroha2:dev` ? BTW this can be a issue specific to the current `iroha2:dev` image,...

If the necessity for `config.json` is the case with the latest image after the fix, we have to reopen #1990

Ok, then we can proceed to the question of what is remote-specific. The error seems to be the same as when `config.json` is absent

[This](https://github.com/hyperledger/iroha/blob/iroha2-dev/cli/README.md#configuration-file) worked to me under absence of `config.json` @BAStos525 > 

Interestingly, the genesis and other peers are failing with different errors. Since this is a consistency problem between the internal repository and the external (e.g. the compose file), could you...

Yes, you can take the latter way to configure, as long as `config.json` is actually accessible. The possibility is that the path is correct while the permission is wrong >...

I think it is proper as the [default permission](https://github.com/hyperledger/iroha/blob/9c5c53153f7b3b5bf183229deec00845570f8b03/permissions_validators/src/public_blockchain/mod.rs#L68) that only the registerer can mint. Minting will be a very privileged instruction, just like that only the central banks or...