we have change to version MC 1.0.5, still the chain stops on it own

+2 votes
Hi we have moved to older stable

1\) still as we crunch a file of 1.5 mb it stops the chain, we have to restart the chain again.

we have changed the params setting for 6 MB file.

2) Blocks are stuck at 133 blocks since the first breakdown, after restarting the chain the block count is not increasing.

"version" : "1.0.5",
    "nodeversion" : 10005901,
    "protocolversion" : 10011,
    "chainname" : "dibs",
    "description" : "MultiChain dibs",
    "protocol" : "multichain",
    "port" : 6733,
    "setupblocks" : 60,
    "nodeaddress" : "dibs@172.31.25.41:6733",
    "burnaddress" : "1XXXXXXWvXXXXXXX9vXXXXXXTrXXXXXXakkvdH",
    "incomingpaused" : false,
    "miningpaused" : false,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "walletdbversion" : 2,
    "reindex" : false,
    "blocks" : 133,
    "timeoffset" : 0,
    "connections" : 0,
    "proxy" : "",
    "difficulty" : 0.00000006,
    "testnet" : false,
    "keypoololdest" : 1531915340,
    "keypoolsize" : 2,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00000000,
    "errors" : ""
asked Jul 18, 2018 by brijesh

1 Answer

0 votes

The three most common reasons for mining stopping are:

  1. No new transactions and the mine-empty-blocks setting is being applied.
  2. There is only one mining node attached and mining-requires-peers is being applied.
  3. Multiple addresses have mine permissions but not enough of them are active to satisfy the mining-diversity criterion.
answered Jul 19, 2018 by MultiChain
...