Search results

Stopping and restarting darkcoind sorted things out for me. I was stuck on 1 in the list. Make sure you're fully synced too.

Back up running 10.16.6 with some new details: IP: 176.126.247.190 Addr: XiSYDTd4pKThFDRBVdbC96VUC29XPWLWQJ The 18.55386816 earnings so far this month will be added to whatever else is earned and paid out as usual on the 19th/20th. :smile: edit: updated about 5 times today, now on v16.10...

1st of my MNs updated to 16.6, looking fine, appeared in MN list immediately both local and remote, not a CPU/RAM hog. :smile:

https://bitcointalk.org/index.php?topic=421615.msg9542571#msg9542571 Fix is up if you want to compile it yourself, I imagine binaries will be along presently.

Doing a bit of maintenance and reorganisation, don't panic!

4 MNs got terminatificated by my UK VPS provider overnight, the AWS one wasn't quite dead, but zombified with CPU overload... Hope Evan got a good night's sleep, and eats hearty for breakfast when he gets up, and tonight will hopefully not be dining in /dev/null. :grin:

That's been underway for years...

No, you should only have to do that once initially when there's a protocol version bump. Your MN AI should take care of itself otherwise.

ssh to your MN and run 'crontab -e' If you get asked, select your text editor of choice, then add '@reboot /home/user/.darkcoin/darkcoind' to the end of the textfile that pops up. (Modify line to suit username and daemon location.) Should restart darkcoind in the event of a brownout. You can...

Minor update, v44 separates out the update and fresh install functions for easier debugging, and has some slightly improved exception handling. Tested working multiple times today both updating and doing a clean install. (Install still needs you to run masternode genkey and stick that and your...

Hope so, thought I was getting even dafter... :eek:

16.3 seemed to grind to a halt after first 1000DRK got DS's 1 round, 16.4 still sitting there not doing much. Log shows a lot of this: 2014-11-13 18:44:08 vout - CTxOut(nValue=1.00000001, scriptPubKey=OP_DUP OP_HASH160 e357600fcdbe) 2014-11-13 18:44:08 vout - CTxOut(nValue=10.00000001...

Updated, is this right, MN list seems to have blossomed somewhat... { "version" : 101604, "protocolversion" : 70045, "walletversion" : 60001, "balance" : 1000.00000000, "darksend_balance" : 0.00000000, "blocks" : 63320, "timeoffset" : 0, "connections" : 10, "proxy" : ""...

Still getting some console spam: dsa -- last dsq too recent, must wait. 176.126.245.22:19999

Just waiting for 15 confirmations. Liking the newfangled base 2 denoms. edit: root@testnet:~/.darkcoin# ./darkcoind masternode start successfully started masternode root@testnet:~/.darkcoin# ./darkcoind masternode list { "158.58.250.202:19999" : 1, "188.226.225.170:19999" : 1...

Ugh, the cheapo VPS I was using cooked itself overnight running a main net and test net MN... I will rent another just for test net.

I don't think that can possibly be right. I think Evan said that a client would use a different MN each time. Client A uses MN 345, Client A wont use it again but Client B can still use MN 345...

I fired up v16 with whatever wallet version was lying around from last time and my log shows this: 2014-11-12 23:01:54 Submiting Darksend for 1000.000000 DRK 2014-11-12 23:01:54 DoAutomaticDenominating -- Found unconfirmed denominated outputs, will wait till they confirm to continue. But...

Awesome, I think this will also help greatly with adoption and PR. :smile: Will fire up a testnet MN - need to test SMUT 1-click MN install ;) - and a mining rig in an hour or so.

No. :tongue: