Yeah, the network is constantly forking. Reminds me of litedoge, which had the same issue when it reached the stage of smoothly, slowly decreasing block rewards. It's broken code that originated in spreadcoin I believe.
I'm not a competent coder by any means, but I'd take a look at litedoge if I were the NTRN devs. I'd bet whatever fix they implemented would be the solution here.
I'm not a competent coder by any means, but I'd take a look at litedoge if I were the NTRN devs. I'd bet whatever fix they implemented would be the solution here.
OK, so after many resyncs the problem I found is the nodes. Don't add them into the config. That list of nodes to use is causing a problem. Rather remove the config and let the wallet find it's own nodes and update.
My wallet has been online for 2 hours without a hassle and settles on 4 active connections. So lets try this list:
1. Lock the wallet
2. Delete all except wallet.dat - Make sure that is the only file in the folder. NO CONFIGS
3. Open QT and let the blockchain sync completely
4. Unlock wallet after 15 mins - check it is matching the block explorer during this time.
Edit:
At present I am trying a config with the following to see if it helps.
rpcuser=username
rpcpassword=passowrd
rpcallowip=127.0.0.1
listen=1
server=1
daemon=1
I cannot say yet if it will make a difference as I have not staked a block since I have done this.
After deletning the old blockchain from the data directory and removing "addnodes" from the "conf"-file the staking have worked flawlessly for over seven hours.
It seems you should not have nodes from the first page of this thread in the "conf"-file.
It screwed up for me as well. 7 Hours is almost bang on the money. Get a few stake blocks perfectly then it screws out. It was the best make shift I could offer. I will keep on this route so I can stake at least otherwise it's pointless having the wallet online. My view is it's due to other people still holding onto the nodes with the config. The moment the route is clear it might help.
Till then...
