mining-requires-peers set to "true" in a network, but it´s not working

+1 vote
We see that the nodes can get disconnected, but they continue mining on itself.

We ccreated the chain with the following steps :

1 - Dowloaded

2 - Changed mining-requires-peers to "true"

3 - Changed ports

4 - Changed Network name to myNet

5 - Launch : multichaind myNet -daemon

6 - Sent resulting params.dat to peer node

7 - Run multichaind myNet -daemon on peer node

The issue was before bullet 6, when the first node started, it commenced to mine right away.
asked Aug 7, 2017 by germat
We made a lot of changes to how mining-requires-peers is applied to support the multichain protocol and permissioned networks. So it's possible we made an inappropriate change to its behavior for regular bitcoin-style networks, which MultiChain is rarely used for. I'll ask the team about this and revert.
Thanks. Do you have an estimation on when it will be reverted?
There are other issues we are finding during the test, we wanted to start changing a few parameters at a time starting from a bitcoin-like chain as the page suggests. Do you still recommend this approach?
Please see the other answer.

3 Answers

+1 vote
answered Aug 7, 2017 by MaSsv
Thanks for your answer, but it seems that the issue is present in release 1 , as per the MultiChain comment in the post above. Regards
0 votes
So mining-requires-peers is not applied if there are less than two permissioned miners, and obviously this is inappropriate for a bitcoin-style blockchain where all mining is open. We'll fix this in the 1.0.1 release, which should come out around the end of this month.
answered Aug 8, 2017 by MultiChain
0 votes
This should be fixed in MultiChain 1.0.1 released today.
answered Sep 13, 2017 by MultiChain