I'm out of sync with v0.10.10.1.

I'll revert the client tomorrow morning to check for the deposit. The Post Mortem is they're estimating a 2-3 week delay in Node Payments:

https://darkcointalk.org/threads/6-20-rc3-post-mortem.1463/

Evan also has programming reinforcements so that should help as well.

It's possible. However, this morning Evan was talking about possible forking issues hours several before the official fork time about 2 hours ago; A problem that may be related to having a mix of old/new software versions among nodes.

This. +1000

Thank you for offering your solution in a thread that's supposed to be about DRK and not a pissing match between coins. I'm having problems with finding good instructions on upgrading from RC2 to 3 and implementing cold wallet storage.

I also couldn't implement the final command to start payments from the local wallet with coins in the local cold wallet. On the other 3 nodes I was setting up last night, I kept getting a local qt console error that the masternodes variable needed to be set to 1 in the conf file...of which, it was set correctly in both conf files. Configs looked good and matched 100% on both ends.

I just paused my set up of community owned MasterNodes until the situation with RC3 sorts itself out.

Simcom: BTW, I def. saw some strong evidence of sideforking last night. My biz partner sent me 250DRK last night to top out our fifth community owned node and it just never arrived (he was using .9x I was using .10x). I'm assuming this transaction was orphaned since it never arrived (and I *think* it never left his wallet).

Strange. Nothing yet.

I would've thought that it would be fine to send DRK between the two client versions before the planned fork but it's possible that your transaction went out on some orphaned block in an unplanned side fork.

Oh, I may a solution for the RC2 to 3 upgrade to cold storage for our node #1: https://bitcointalk.org/index.php?topic=421615.msg7424706#msg7424706

I'll explore this tonight to see if its both applicable and possibly helpful. Turns out that occasionally there's good info in there amidst the trolling and mudslinging.

TBH: I don't know enough to have an informed opinion since I don't have time to be a testnet operator which would've likely informed me more. I don't know where and how the code is failing and that's out of my area of expertise.

This is more in the realm of program debugging with an assist from network admins/engineers involved behind the scenes.

Looks like we're seeing forking in the network and payments are still disabled:

https://bitcointalk.org/index.php?topic=421615.msg7421501#msg7421501

I thought the network wasn't behaving correctly due to behavior I was seeing and I was correct, unfortunately. I'm unsure it was related but I was literally 99.9% finished with our first 4 community nodes last night (entered the very last command) when the setup process completely stalled on this critical last step for nodes 2-4.

We're all in wait and see mode, at the moment. I did pre-fund 40 servers last night for a month in preparation of those that had 1-2 full nodes to set up.

Darnit. Just as I suspected there *is* network instability. You get a feel for it when you've been working with networks for so long (and other times it just slaps you in the face).

Evan confirms there's some forking issues: https://bitcointalk.org/index.php?topic=421615.msg7421501#msg7421501

Sigh. Sorry gents, I worked hard to get us ready for RC3 but we better wait for the situation to settle down before I start troubleshooting this again.

With network stability being low, Doesn't seem like much point of doing all this work just to possibly end up on the wrong fork and have to redo the config again. Looks like node payments are still disabled anyway until this is solved, so at least we're not losing out on rewards. I'll check the network status when I get home from work and continue troubleshooting that last step if the forking issues are solved by then.

Thanks Otoh. I'll shoot you a PM later. We"re not quite out of the woods yet: I keep running into this console error on my local wallet when I try to startup the MasterNode via cold storage & local wallet: says to set MasterNode=1 in conf file, and it *is* set in both conf files to 1.

I've gone thru the instructions & config with a fine toothed comb and the conf file settings match exactly on both ends. Worked till 1am on it. Slept a few hours and got back to it at 630: looked at config again. config was good but I keep getting the error without documentation around about what to do if you see this error.

I think I'm seeing weirdness from the Darkcoin network itself too. Otoh's deposit still hasn't shown up although its been a while and I upgraded qt last night to the latest ver. Hmm, we're up but we're literally at the final step of implementing node activation from cold wallet and stymied at that very last step! It's a bit frustrating to have had to troubleshoot this final step for hours without seeing anything wrong with the config.

I may have to just re-visit this when I get home this afternoon. I left a comment up explaining what I was seeing on the RC3 setup thread at Darkcoin Talk. There's steps you can do with troublesome nodes which involve moving funds around and regenerating keys but to do it properly I'll need more time and I want to see network stability. If there's forking problems we may have to wait for the network to settle down. Feeling a tad nervous moving several K of DRK around - even self-payments - if the network is acting funky.

Let's hope this fork goes smoother than last time.

Node #4 wallet transaction to cold storage:

Status: 0/unconfirmed
Date: 6/20/2014 00:09
Debit: -1000.00 DRK
Credit: 1000.00 DRK
Net amount: 0.00 DRK
Transaction ID: 30762d9e5644cb8f486a7e27c4db4cc7f07ae64e0ad8cfc00b01d800f17bcaeb

sumofallpears@xxx-xx-xx-19:~$ darkcoind getinfo
{
    "version" : 100811,
    "protocolversion" : 70015,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 86402,
    "timeoffset" : 0,
    "connections" : 2,
    "proxy" : "",
    "difficulty" : 3198.16472526,
    "testnet" : false,
    "keypoololdest" : 1402136780,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00001000,
    "errors" : "Hard Fork Alert: Masternode Payments begin on Friday, June 20th. Please update! http://goo.gl/ucp4m7"

Whew! Ok that does it. I have a little more to do to finish up but that's it for the night.
Otoh if you can send 250 DRK for the last node, we'd have a complete 5th node I can launch pretty quickly.

Node #3 Cold storage transaction and current status:

Status: 6 confirmations, broadcast through 11 nodes
Date: 6/19/2014 23:53
Debit: -1000.00 DRK
Credit: 1000.00 DRK
Net amount: 0.00 DRK
Transaction ID: 26e347b1f6119915e59b561d5145a03ad65f31e55528a72ea0fd46305af47b14

unkofester@ip-xxx-xx-xx-22:~$ darkcoind getinfo
{
    "version" : 100811,
    "protocolversion" : 70015,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 87547,
    "timeoffset" : 0,
    "connections" : 2,
    "proxy" : "",
    "difficulty" : 3270.72867714,
    "testnet" : false,
    "keypoololdest" : 1402136780,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00001000,
    "errors" : "Hard Fork Alert: Masternode Payments begin on Friday, June 20th. Please update! http://goo.gl/ucp4m7"

Node #2 is now up utilizing cold storage and RC3. It's all ready for tomorrow.

sumguy@XX-XX-XX-21:~/.darkcoin$ ./darkcoind getinfo
{
    "version" : 100811,
    "protocolversion" : 70015,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 86914,
    "timeoffset" : 0,
    "connections" : 1,
    "proxy" : "",
    "difficulty" : 3601.02705821,
    "testnet" : false,
    "keypoololdest" : 1402136780,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00001000,
    "errors" : "Hard Fork Alert: Masternode Payments begin on Friday, June 20th. Please update! http://goo.gl/ucp4m7"

This was the movement of funds into cold storage for Node #2:
Status: 64 confirmations
Date: 6/19/2014 21:18
Debit: -1000.00 DRK
Credit: 1000.00 DRK
Net amount: 0.00 DRK
Transaction ID: 12cb0d02f4f3aee8ca1b55f1ce7883e32d20822ff322c9a73eee85337b4f1994

==

Node #1 is also running but with the orig. hot wallet at the moment:

SumbunnythatIusedtoknow@xx-xx-xx-147:~$ darkcoind getinfo
{
    "version" : 100811,
    "protocolversion" : 70015,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 88632,
    "timeoffset" : 0,
    "connections" : 1,
    "proxy" : "",
    "difficulty" : 3117.28726659,
    "testnet" : false,
    "keypoololdest" : 1402136780,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00001000,
    "errors" : "Hard Fork Alert: Masternode Payments begin on Friday, June 20th. Please update! http://goo.gl/ucp4m7"


Still trying to figure out how to send the coins back from Node #1 to the orig. wallet so I can put stake funds from #1 into cold storage. Interestingly, when you implement this it tells you you're paying a payment to yourself and your balance stays the same.

If all goes well, they'll go live sometime tonight after I harden the 2nd template (turns out there's two at the moment based on two different Linux OS systems ). First template's almost finished and I'm working on node prep/hardening this evening without too much distraction (family's at the movies).

I plan on heading to work a little later tomorrow morning but I leave before payments go live at I believe 11am my time. Cross your fingers for us that there's no major stumbling blocks that keeps us from being live with at least 4 community nodes by tomorrow morning.

==

Last update of the night: Template #1 survived a pretty intensive scan of...well, everything, audit and check of logs. I don't want to say it's bulletproof because we all know how that goes but this system as is, would be near DoD CAT I STIG standards if submitted for Accreditation; I deviate because I disagree with certain vendor choices.

Node #1 is good to go except I need to take it down to implement cold storage for RC3 for even better security, and it will be the first to be up with cold storage.

BTW, we ended up at 4.75 Nodes filled.

Ok, back to work.

I saw your email but I didn't see a quantity for the number of nodes. Please feel free to send me a PM with the number of nodes you were interested in if you were interested in more than one.

Roger that. Thank you and Welcome Aboard!

You're the first person on the Batch 2 Waiting List. 

Yes, you are.

You're in Batch 1 but Batch 1 is large. If you can prep your wallet file as per the instructions that'll help when I get to your place in the Q.

Thanks for the info and good night!

Will do DRKsi, thanks for the heads up.

Getting contacted over multiple channels but this the primary sub forum to centralize discussion about full and partial MNs I've been contacted to set up for others.

New batch Three Reservations are Closed. Only those that contacted me offsite for the first time yesterday will get a 24 hour extension to 9PM HST tonight.

After that: partial node set ups will be completely closed until the backlog of first Batch of Full Nodes clears from the daughter thread for Full nodes that this thread spawned.

Sorry, just had my nose to the grindstone on 2 jobs. I missed the quantity and will check later this evening.

No worries though, thanks to Reddit you are the 2nd one in the Batch 1 Full Node Q behind Otoh's 2nd node (he's going to fully own the 2nd one). If you're ordering 3 or more nodes, you'll need to make some arrangement with a Cloud Provider such as Amazon, OVH, Dreamhost, & Digital Ocean, for example, and you'll need to allow me co-access to the account for admin and setup purposes.

Need to head to work work now. BBL 

Q: What are the benefits of owning a MasterNode?
A: If you're unfamiliar with them, one awesome difference is the Proof of Stake algorithms being implemented in the coin's ecosystem. If you think about it: as long as ownership/management is kosher (or you're doing it yourself), partial and full node ownerships are great places to store DRK in cold storage you weren't going to spend anyway and then you get to earn interest on them. You can also remove the coins whenever you want so this 1000DRK is not a "sunk cost."

At this point the two main competing minting/reward systems for cryptocoins are PoW and PoS. Darkcoin essentially combines the best of both worlds and becomes both a Proof of Work and a Proof of Stake coin tomorrow: Work is represented by mining, like in the BTC realm. Earnings from Proof of Stake are offered via Masternodes, like forging in the NXT realm. Masternode owners receive 20%

Q: How does a Darkcoin Masternode compare to a Bitcoin or Scrypt miner?
A: Mining rigs have a short half life compared to other electronics. They consistently lose double digit percentages every month in both earning power and resale value. MasterNodes on the other hand, tend to rise in value and requires no exotic ASICs which will be obsolete in 6 months. They only require real or virtual servers, power, network connectivity, administration and security.

Also your stake can be removed at any time, and your access to your 1000DRK restored at any time, at loss of future node rewards. To earn coins in Darkcoin's ecosystem as a node owner, compared to a mining rig you don't have to permanently sink a large sum of money on a rapidly depreciating asset with depreciating earning power as time goes on, as we see with Bitcoin or Scrypt miners.

Q: How is setup handled/funded?
A: If you're only going to own one or two nodes I'll front the setup costs for you, like I'm doing for the Community Nodes in the related thread. If you're looking at setting up 3 or more nodes, please contact me to arrange this as we will need you to setup an account at a cloud provider AND authorize me to have access to this account for setup/administration purposes.

Q: How do I know what kind of server(s) to reserve if I'm doing 3 or more nodes?
A: Please contact me with your requirements to help you best decide. If you're running multiple nodes, you're obviously going to need a beefier server or even multiple servers. I will give you some options for you to decide about how to proceed.

Q: If I'm talking to a server provider about specs what should I tell them?
A: Just make sure to tell them that you need to have at least one CPU core or one vCPU per node you would like to have run. You'll also require at least 700MB of RAM per instance and one static IP per node. You can give them my email address to contact me to start the co-authorization process at: surfskatekauai@gmail.com

If you have a question not covered here or in the Partial Node thread please send me a PM or pose your question below if it's non-sensitive. If you have new information for the community about the implementation of cold storage, please leave that below too. Mahalo!

Thanks bregge. Noted, Mahalo and Welcome Aboard! We should be fine, as there's a few more that might straggle in (late PMs on other sites) and Otoh has offered to fill up any partial nodes left hanging.

Also: I posted the FULL NODE thread but there's not much info yet because we know little at this point: https://bitcointalk.org/index.php?topic=658285.0

As you hear about the cold storage setup for full nodes, please feel free to share anything new you learn with the rest of us.