Quote from: mikegi on September 19, 2016, 11:45:26 AM

Quote from: mikegi on September 19, 2016, 07:13:30 AM

Quote from: mikegi on September 19, 2016, 05:32:07 AM

Went through the same procedure as setting up my other masternodes.

Using the latest version...
   "version" : 2010203,
   "protocolversion" : 70701,
   "walletversion" : 61000,

Sent 10000 to the address, made the private key... updated masternode.conf, restarted wallet.

The transaction does show up in this list "darknet-cli listlockunspent"

But is not in in the list "darknet-cli masternode outputs"

Unsurprisingly, trying to start the masternode shows...

"errorMessage" : "Could not allocate vin ...... for masternode ........onion:51472"

Any ideas what went wrong here?

I'm going to try a fresh install and regenerate my wallet from a dump.

Any ideas about how to disable staking? This is a feature request.

I wouldn't want the wallet to stake transactions from my running masternode before I can lock the transactions

EDIT: From the logs, it looks like the TXs from masternode.conf are parsed

Some ideas.
- start with "maxconnections=0"

EDIT: this does not disable p2p connections

I guess "darknet-cli setstakesplitthreshold" would not be useful.

EDIT: Well at least the wallet conflicts are fixed.

Turns out that the 10000 DNET was used to pay a 40 DNET fee in the same block.... perhaps to do with having obfuscation enabled.

So what have I learned...

Transactions shown by "darknet-cli listlockunspent" might already be spent or might not even exist
(Try putting a fictional txid into masternode.conf )

Transactions listed in masternode.conf will be locked when starting the node.

"darknet-cli masternode list-conf" does exactly what it says... Print's the contents of masternode.com at the time dartknetd was rund in JSON format as well as printing the status of the node.

Glad to see that you found the issue. Yeah, the 40 DNET is the collateral fee for obfuscation. It is actually still in your wallet, and can be found with coin control. My guess is that when you created the 10K transaction you spent the collateral, and it was created again. In the future use coin control when creating your masternode vins to avoid similar issues.

Also, there are 2 ways to stop staking, You can enter "reservebalance true 9999999" in the console to temporarily disable it while setting up a new masternode then enter "reservebalance false" when you are finished. A more permanent solution is to add "staking=0" to your darknet.conf, although there is not much point in using that method, we had to add that for bittrex, when you have more than 9999999 coins the reserve balance command is useless.

On a side note, I haven't had any issues with my masternodes, and would be interested in some debug.logs the next time anyone has issues like the past several posts have mentioned.