Mining halted permanently

+1 vote

I'm running a single node Blockchain with the following parameters. For the past few days the mining got halted and no transactions are being confirmed. Only 119 blocks have been mined so far. Couldn't figure out the root cause. Please help me solve this.

{
    "chain-is-testnet":false,
    "target-block-time":15,
    "maximum-block-size":8388608,
    "default-network-port":50001,
    "default-rpc-port":50000,
    "support-miner-precheck":true,
    "allow-arbitrary-outputs":false,
    "allow-p2sh-outputs":true,
    "allow-multisig-outputs":true,
    "setup-first-blocks":60,
    "mining-diversity":0.3,
    "admin-consensus-upgrade":0.5,
    "admin-consensus-admin":0.5,
    "admin-consensus-activate":0.5,
    "admin-consensus-mine":0.5,
    "admin-consensus-create":0,
    "admin-consensus-issue":0,
    "lock-admin-mine-rounds":10,
    "mining-requires-peers":true,
    "mine-empty-rounds":10,
    "mining-turnover":0.5,
    "first-block-reward":-1,
    "initial-block-reward":0,
    "reward-halving-interval":52560000,
    "reward-spendable-delay":1,
    "minimum-per-output":0,
    "maximum-per-output":100000000000000,
    "minimum-relay-fee":0,
    "native-currency-multiple":100000000,
    "skip-pow-check":false,
    "pow-minimum-bits":8,
    "target-adjust-freq":172800,
    "allow-min-difficulty-blocks":false,
    "only-accept-std-txs":true,
    "max-std-tx-size":100000000,
    "max-std-op-returns-count":1024,
    "max-std-op-return-size":8388608,
    "max-std-op-drops-count":100,
    "max-std-element-size":32768,
    "chain-name":"testchain",
    "protocol-version":10009,
    "network-message-start":"f4fbe8ef",
    "address-pubkeyhash-version":"00c93ea5",
    "address-scripthash-version":"0577ad23",
    "private-key-version":"805ae676",
    "address-checksum-value":"ef8f9da0",
    "chain-params-hash":"a8d4669e85fe7cb75d7866db0fb2286b7a6fb16b791c0c2f376acc0ccc81d275"
}

asked Oct 9, 2017 by Cypher

1 Answer

+1 vote
 
Best answer

Assuming you are using permissioned mining, but didn't grant mining permission to other (non-active) addresses, the problem is probably target-adjust-freq, which allows the difficulty of mining to increase. Unless you're using an open blockchain with proof-of-work mining, there's no reason to change target-adjust-freq from its default value of -1. Please see the production recommendations at the bottom of this page: https://www.multichain.com/developers/blockchain-parameters/

answered Oct 9, 2017 by MultiChain
selected May 29, 2019 by Cypher
...