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.