Another masternode... another first payment. :-)

In case you are curious, the first payment came after 46 hours.

Thanks,with the exception of those 2 weeks in August and my first masternode,  I haven't had a problem until now.
(
I'm using the CLI only...have thought about using the GUI wallet but I prefer to keep things lightweight. Coin control could be handy. I haven't felt a need for it yet.

I found the coins, with the help of listunspent and grep... and the blockexplorer. The unspent 9959.9something instead of unspent 10000 put me on the right track.

Perhaps you could clear up one thing about (remote) masternodes and controller wallets. I have had mixed luck with being able to restart a masternode without having to start it from the controller wallet.

When the the controller has not been restarted since the last time I have reactivated the masternode. The state changes as follows ( output from darknet-cli masternode status)

- error: {"code":-28,"message":"Loading block index..."}
- "status" : "Node just started, not yet activated"
- "status" : "Masternode successfully started"

When the controller has been restarted, at that masternode has not been activated. So, miss some mn payments and need to restart.

- error: {"code":-28,"message":"Loading block index..."}
- "status" : "Node just started, not yet activated"
- "status" : "Not capable masternode: Hot node, waiting for remote activation."

I guess there is some information in the controller about the masternode that is not stored persistently or does the controller need to sync with the network?  I have normally kept the controller running... and sometimes held off upgrading the controller in order to keeps the masternodes up.

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.

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.

- Participation in a testnet
   - running a peer or masternode
   - testing functionality of a testnet
   - Identifying  / Fixing problems in the testnet

I took a look at Bittrex's Twitter feed  and saw no text and no images about delisting Shift or any other coins...
I looked as far back as July.

https://twitter.com/BittrexExchange

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?

Nice to see more markets! Also DNET-DOGE, DNET-DOT, DNET-FTC and DNET-UNO.

Currently, only some very optimistic orders  DNET_BTC but it will change.

It's hard to say for sure. SSD can fail too, just in different ways. I haven't seen a failed SSD yet though.

I did find a simple command line test for Windows using WMIC.

from the command prompt, run
"wmic"
and then
"diskdrive get status"

I noticed that  https://www.smartmontools.org/ is available for windows too.

If you decide to start any of the SMART tests, I'd suggest backing up important stuff before. I did have a hard disk that failed during an "extended test". I have seen enough disks fail and don't trust storing anything important on just 1 disk.

For fun, I started up uther and tried to add the 4 peers mentioned in the OP.

https://bitcointalk.org/index.php?topic=1407495.msg14276861#msg14276861

Nobody home... or perhaps some other nodes running with a clock that is badly out of sync.

Sending Uther to c-cex won't be so easy.

Not sure about how to do this with Windows... but it is worth using a tool to check the S.M.A.R.T. data for your hard disk.

A few years ago, a family member had a Windows Vista laptop that was really slow... It was nice that Vista had some kind of tool to resize disk partitions so I could install Linux. Windows didn't indicate any problem... but running dmesg under Linux showed something was up, looking at the S.M.A.R.T. data  with smartctl showed that there were lots of seek errors.

Not sure if windows is any better now about telling the user their disk is dangerously close to being useless. Maybe someone else can recommend a good windows utility to check this?

Good to have backups!
 

A quick look a google this... https://github.com/bitcoin/bitcoin/issues/5668

A long read but my guess would be that block file is corrupted.

Reload the blockchain from scratch... or copy it from a wallet or node that doesn't have this problem.
(keep/backup your wallet and configuration).
If you copy the blockchain from another node, make sure it is stopped when you make the copy.

Not sure, I don't think there has been a pool.

If there are still peers, I suppose you can test solo mining.

Note that this is on more than one market on c-cex.

Though I doubt there are any more possibilities for arbitrage.

I restarted my wallet/controller with the new version first. Maybe 30 minutes later, restarted the some masternodes with the new version.

The stayed in the same state. (Not capable masternode: Hot node, waiting for remote activation.) for about an hour so I ran start-alias ... from the controller and then the state changed.

Information from the wallet/controller is based on information is has last received from the masternode... and I think that after it doesn't hear from the masternode after a certain amount of time, then the masternode changes to the Missing state.

Maybe a bit more explanation if non-default setting are needed and if restarting is needed.

I would like to... I guess it is not so simple....

Looking at the help in the cli...

darknet-cli help obfuscation
obfuscation <darknetaddress> <amount>
darknetaddress, reset, or auto (AutoDenominate)<amount> is a real and will be rounded to the next 0.1

The help for darknetd says talks about "automated obfuscation",

 -enableobfuscation=<n>          Enable use of automated obfuscation for funds stored in this wallet (0-1, default: 0)

So I would guess that one could manually enable obfuscate some  coins from the CLI without any change or restart... but no...

$ darknet-cli obfuscation Dabc123abc123abc123zzzzzzzzzz 500
error: {"code":-1,"message":"value is type str, expected real"}


Am I doing something wrong?

Ok, if LSK wasn't in the to 20 market cap... I would have just  moved on to something else.

For me, the block explorter hire is stlill out of date. https://login.lisk.io/

I have tried Google chrome on 2 machines, and Firefox on one. None have an up to date
blockchain in the wallet.

Yes,
846403   2222990152730148636   17027481066703298407L   2016/09/06 20:33:30

While https://explorer.lisk.io/ shows

14152265585912817024
862174
2016/09/08 18:53:00
0   7052850813925530894L   

Thought I'd like to see what I could do with my Lisk outside the Exchange.

Deploying a lisk node seems like it is not something an average user would need to know about...

I tried out the webwallet at the login cluster,  https://login.lisk.io/   

Login works, but the block explorer on the login server is stuck at the following block.

Height 846399
Block id 13208488579176059510
2016/09/06 20:32:50

Anyone else see the same problem or did I just manage to get a bade cluster node?

Nice update, this has the kind of information I like to see.

Building now.. testing soon...

As in the past, I'm sure the team will see that relevant balances large and small are preserved in the fork. Pissing off those who support the coin by mining or by market speculation is not a sustainable was to run things.

Coins that have a had a rollback or fork can preserve market value even with a couple weeks of being disabled/in maintenance on an exchange while issues are being dealt with. A good recent example would be Darknet (DNET).