No need to be sorry. Congrats and thanks for letting me know.

Thank you for your patience.

Batch 1 is underway for full nodes but it is a large batch, so I still don't have an ETA.

Batch 1 for partial nodes (community owned) is complete but I have a bit more troubleshooting to do with partial node #1 which was unfortunately set up with the RC 2 hot wallet method, which is currently giving me issues.

The steps for handling multiple cold wallets on one PC are still being worked out, and it's more of a workaround then a proper solution. Here's a couple of threads discussing this.

http://www.reddit.com/r/DRKCoin/comments/294j3e/hi_how_can_i_have_multiple_wallets_for/

In preparation for full node owners, I expanded on this to discuss how someone with several nodes could provide me the info we need to get your full node started:

http://www.reddit.com/r/DRKCoin/comments/29ci8b/if_im_helping_someone_else_setup_a_masternode/

My method presumes that you'll save and backup a local configuration file first on your hard drive, and *then* on a USB drive so you're protected against one of the wallet.dat files going corrupt, and losing access to both your 1000DRK and your ability to generate DRK from that masternode.

Thank you, but all I did is what anyone with a conscience is supposed to do. In online sales and services, all you have is your reputation and track record, so I don't understand how some ASIC mfgs. bite the hand that feed them and expect to be in business for the long haul.

As for help, the community support has been great and exactly what was needed for me to get experience under my belt. One regret: In hindsight, if I knew that cold wallets were around the corner, I would've delayed launching node 1 with its RC2 hotwallet setup. Having gotten 3 RC3 nodes properly working, I feel much more confident with this RC3 coldwallet method which keeps Masternode deposits internal to your local wallet arnd doesn't send coins to some external address in mempool, that may or may not return your 1000DRK.

Good news / bad news:

Good news is the first "mined" deposits are in for Node #2!

Status: 590 confirmations
Date: 6/27/2014 07:30
Source: Generated
Credit: 1.00 DRK
Net amount: +1.00 DRK
Transaction ID: 044c57b57af453faa0b7901ec59a9becb85fef19880f11451f29d6cd6d11db65

Generated coins must mature 120 blocks before they can be spent. When you generated this block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, its state will change to "not accepted" and it won't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours.

==

Status: 374 confirmations
Date: 6/27/2014 16:57
Source: Generated
Credit: 0.50 DRK
Net amount: +0.50 DRK
Transaction ID: bcd8719a492aa6d70a8dfa1d4bada59e1be2528144687554de682a372c2b04b7

Generated coins must mature 120 blocks before they can be spent. When you generated this block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, its state will change to "not accepted" and it won't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours.

Bad news is that I screwed up and didn't update darkcoind correctly (wasn't in the ~/.darkcoin/ folder when I ran update) on Nodes #3 and 4.

Since that was entirely under my control and an oversight on my part due to fatigue (no excuse) for this one time and since it's my fault, I'll pay estimated payouts to Nodes #3 and 4 of 1.5 DRK for each node, which assumes that this is what you likely received if they had been running with the right version...no wonder they didn't show up in the masternode list correctly...sigh. That's about 2 months worth of mining from my 750TI, so I hope this is an acceptable compensation for Node owners. If something's my fault, I'll own it & do my best to not repeat it.

Spreadsheets going out tonight, I'm sure you want to help keep track of your own node. I have a day at the beach with the kids later this morning, but they'll def. be sent out tonight and I'm testing onionshare for the first time to share it.

I never saw this deposit. There's weirdness afoot with this beta network, for sure, with all the forking that's gone on and coins not making it but not being returned if they fail to be delivered. The only activity for that day shown in my wallet is a 0 dark self-payment from a RC3 wallet zero address. The day before was a 1 DRK tip I sent to a Darkcoin Talk member for info, and the day after is a 750DRK refund to ddink7.

I hope it's not showing as a minus deposit on your end as I never received this.  

Regarding Node 1: I put up a Darkcoin Talk thread where I was fishing for community answers and I PMed Evan 2 days ago but he still hasn't responded back to me about why the network daemon hasn't released back our coins from Node #1 from this transaction:

Status: 11879 confirmations
Date: 6/6/2014 18:08
To: Otoh/DZ MN XcFvsJ5JWnNNWaECCkUgLC5vBFJeXT3EDC
Debit: -1000.00 DRK
Net amount: -1000.00 DRK
Transaction ID: 0fb1c39fb2a49faed971eae5d743444649344b465c0fd8e421ce544189b65ac4

Which was sent following RC2 instructions and the coins still haven't come back although I disabled the masternode and darkcoind was turned off. The address above was generated from a getaccountaddress 0 command and I copy/pasted the info into a notepad for future reference. I did the same for the privkey. I'm in the process of recreating Node 1 from scratch (nearly finished) and hoping that I can manually activate the wallet from the node or my local PC.

This guy claims he lost 1000DRK too, but for different reasons:

http://www.reddit.com/r/DRKCoin/comments/2955u5/tried_to_setup_masternode_and_lost_1000_drk_coins/

The thing is: you're supposed to regenerate an accountaddress0 and associated privkey if you're having problems getting payouts started. But what are you supposed to do if it hasn't released the coins back to you in the first place because it was set up during RC2 before the cold wallet storage method was made public?

node #4 is up! of course it wasn't easy and came with its own set of challenges/problems to overcome even though they're all based on the same base image.

22:20:13

masternode start somelongcomplexPW


22:20:13

successfully started masternode

==

fwiw, I haven't seen any payouts to nodes 2 or 3 yet but then again they're supposed to average about 1 DRK a day by some estimates, which would mean that a node was picked once a day with the current network. need to confirm that this node is on the official masternode list, but other than that, i'm done for the night.

plans for tomorrow afternoon/evening:

- make sure nodes still working as paying nodes and check if any payouts made
- attempt to relaunch RC2 node #1 with what I learned today...and I learned a lot in about 15 hours and troubleshot a few dozen things/obstacles. it was comparatively easy to launch a MN. Wasn't so easy to activate the cold wallet and node payouts.
- catch up on PMs and reservation updates for full nodes.
- work on spreadsheets and notify people as to which node they're in and the IP address of their node(s)

Thanks for being patient everyone! I'm sure that the wait hasn't been fun for you either but we appear to have three fully functional (hopefully) paying masternodes now and the original node which has been a different challenge since it was originally set up to be a hot wallet w/ RC2. This first wave of Community MNs is about 75% done.

BTW, full disclosure. Had to move 1000DRK x2 to other PCs I control, since there's no good directions about running multiple cold wallets from the same windows PC yet.

Status: 29 confirmations, broadcast through 8 nodes
Date: 6/26/2014 18:32
To: DZ DRK MN #3 New Wallet Stake Deposit XbpgwPKYSv1XL6je5HJRVJugWhpmvBdUB7
Debit: -1000.00 DRK
Net amount: -1000.00 DRK
Transaction ID: 71a2d77bc5d65ea12de746e0af507fa544a738a158a02a2d0cfc8641f51845e1

Node #3

==

Node #4

Status: 0/unconfirmed, broadcast through 7 nodes
Date: 6/26/2014 19:47
To: DZ DRK MN #4 XuExBLCw43yot5jw46BMEaEmPYv52BdsDt
Debit: -1000.00 DRK
Net amount: -1000.00 DRK
Transaction ID: 40e9d5181758ac473de6f31fb4b43a8b6083cd5a66b1ad2ca09a9dfe3d6bba93

Also: since ddink7 dropped out of Node #2, a 75% stake opened up so those in Nodes #3,4,5 will be moved up. Not sure how it all shakes out but I'm going to fit people's stakes like puzzle pieces.

Gotta eat dinner. Won't have time to do spreadsheets this evening as I put off work work to get this up. You should be able to guess from the previous public deposits which node you ended up in.  I've been at this about 12 hours with some breaks here & there.

No ETA. But it's the next one. Trust me: this isn't easy. Should be a bit quicker than #3 because most of the wait was waiting for my laptops to sync from 22 weeks back. Still several steps that need to be made to modify a node and workstation to operate as a node, and a workstation configured to operate that node via qt. I'm having to offer bounties just to try to get good info on how to scale this so that I can offer these services to you guys.

Node #3 is up:
19:33:15

masternode start PWofsomesort


19:33:16

successfully started masternode

==
Most of the delay in the next node coming up was the lack of information about having to deal with trying to run multiple cold wallets from one windows PC; a necessity if I'm going to scale this up to meet demand. It's a necessity also for my full node clients to understand so that if they have multiple nodes themselves, they'll know how to prep multiple cold wallet files without endangering their Darkcoin or screwing up the previous configuration.

Of course it wasn't going to be easy. The guides out there are meant for people setting up one node...not 5 or 30.

It's inelegant but I'm setting up the Darkcoin client and completely new wallet.dat files on a couple of laptops, in which I'll make sure to back up the wallet files on other media.

This will work for 2 more nodes, but it's really not going to work for when I have to set up 30 nodes or so. I have another 2 DRK bounty out there for those out there that can help me grok what flare and weirdgod meant by using a datadir trick to activate multiple nodes with cold storage from the same windows PC:

http://www.reddit.com/r/DRKCoin/comments/297ga6/another_2_drk_bounty_whats_the_datadir_trick_to/

I think he means deleting/moving the wallet.dat on the local PC and putting it in a subdirectory that gets called in DOS when you start the Darkcoin Client but details were sketchy. No fancy illustrated instruction manuals here at this stage of the software's development.   

Anyway, gonna be awhile to sync they were 22 weeks behind when I walked away.

Holy cow. You won't believe how simple the problem was.  

Good thing I was going to manually move my darkcoin.conf file over to another folder in DOS or I wouldn't have noticed that the FULL name of my local darkcoin.conf file was darkcoin.conf.txt. Hours of work to be tripped up by one little detail that's a function of a windows text editor. Sheesh. Forgot that notepad appends that on if you're not paying attention. Sorry, bounty's closed.

Node #2 is running! On local console:


14:22:50 masternode start LongPW


14:22:50 successfully started masternode


The following cmd. ran from the node confirms that Node #2 is part of the darkcoin masternode list:

unkofester@ip-x-x-x-147:~/.darkcoin$ darkcoind masternode list | grep y.y.y.236
    "y.y.y.236:9999" : 1

Quick break & now the next challenge of setting up multiple nodes from the same wallet. If all goes well, replication should be easy.

Early afternoon update:

- Been troubleshooting since this morning. The errors I was seeing that I hoped would go away with software updates are still there: still stuck on that last step. The nodes are operating as part of the network, it's just that the payout activation command (the very last step) fails when applied either locally or on the remote server.
- Still no closer to getting a solution to why node #1 funds not released back even w/ new software and turning off masternode. Contacted Evan. I know he's busy but hoping for some response eventually.
- Went to node #2 since #1 is stalled. Here's a running log of the problems I was seeing with this error with a 2 DRK bounty for troubleshooting this error:

http://www.reddit.com/r/DRKCoin/comments/296jlx/2_drk_bounty_you_must_set_masternode1_in_the/

- Did 2 updates on both ends as mentioned and waiting for yet another self-payment for cold wallet storage with yet another generated privkey to confirm to test latest fix attempt.
- Also reached out to certain node operator vets and also taking applications for vetted co-administrators:

http://www.reddit.com/r/DRKCoin/comments/297092/taking_applications_for_coadministrators_of/

Please remember: this is still very much beta software and sometimes problems crop up.

Sorry not yet. My priority was figuring why the hell the daemon still hasn't released our 1000DRK from RC2 Node 1 and then getting the other 3 nodes fully running and payments started before I worked on less pressing matters like spreadsheets. I thought I had a bit more time to figure out this problem as the orig. estimate was a 2-3 week delay.

As you can imagine: there's a bit of angst and concern about this 1000DRK since that was set up with the old hot wallet method and I sent that payment with an older v.09 client. I had enough concern that I just messaged Evan on the DRK forum about the problems I was seeing and how community responses I was receiving weren't helpful. (BTW, these problems are *just* with RC2 Node 1 set up with the old wallet client; the other community nodes were set up with the RC3 cold wallet method and the deposit to the associated getaddress 0 happily shows up as a self-payment of 0). It was suggested that the node could be on the wrong blockchain with RC2 software which could account for the problem I saw; that it could be because Node 1 was running RC2 and I didn't update it to RC3 when they halted the June 20 launch.

Hoping the software updates I apply tomorrow will sort all this out so I can start chipping away at the backlog.

Sorry, these should be updated tomorrow morning. Evan didn't give us much of a heads up this time. The cold wallets for Nodes 2-4 were prepped from the last false start. They're up with the old software but I'm not synced yet with the latest updates.

Got caught off guard by the insta start & I was still working out weirdness with RC2 Node 1 as I couldn't seem to remove coins from the hot wallet to prep Node 1 for cold wallet storage and was still troubleshooting this issue on Darkcoin Talk. As of now, I still haven't gotten good instructions on releasing back our 1000DRK from mempool in Node 1 and may have to contact Evan and team.

I'm off tomorrow so I'll be working on nodes most of the day. Tomorrow: I'm *not* going to be answering PMs on any forum (except for Evan if he gets back to me) as I'm going to be knee deep in CLI land trying to get our node payments started.

Stake sent as requested.

Status: 19 confirmations, broadcast through 7 nodes
Date: 6/23/2014 20:23
To: Refund to ddink7 XnYYYYYYYYYYYYYYYYYYYYYYY7
Debit: -750.01 DRK
Net amount: -750.01 DRK
Transaction ID: 3c59fae22ff93595be4cbba7de6361ed1ae6d366f1ae62636b1407169d4cee9a

Hope to see you again soon!

==

Otoh's deposit(s) never arrived but we're still currently at 4 complete Community Nodes with room for 1 more partial node as others have offered to fill your spot(s). I'm currently on wallet v0.10.10.2 FWIW.

I confirmed that the nodes were all working well this evening (sans that whole payout and cold storage thing we're promised in RC3) and did normal updates to our community node servers.

6/29 update: 250 DRK from Otoh found. Was sent to Batch 1 address, which wasn't being checked as B2/3 addresses were funding Nodes 2-4. Whew!

Congrats nexus.

Appears to be well built from the exterior at least. You planning to do any internal shots?

Sorry, Phil.

I was so depressed to see this whole model collapse thanks to delay after delay and lies to all of us miners. The trolling made me sick to my stomach to even think of stopping by and the last straw was PG dragging my kid into our pissing match about nada since he never even bought from us. I'm at peace though with the fact that a grown man that would do such a thing and stalk another grown man must have some diagnosed or undiagnosed mental issues.

As for having to deal with the fallout of the delays and flat out lies to us involved with the reassurances coming out of HashFast and Bitmine. I really hate to be in the middle and I still get asked for refunds even though I haven't controlled R17 refunds (or most Round refunds) for a while, in our division of labor, and checks/balances.

Anyway, I'm out of BTC mining entirely. Only mining x11 w/ one GPU and Scrypt with a couple Blizzards.

Trying to be positive after taking some time to recharge...still excited about Bitcoin and the crypto economy in general...not so stoked about how centralized and greedy its become. Cex.io takes 44% annual fees and somehow it's the dominant pool? Wow. I don't get it, sorry.

Sure, why not. Like I said: "Nothing happened."

I'll send it tonight sometime after dinner. I need to track down your orig. deposit and finally update my wallet client to .2. This work project was a zombei that kept coming back to life and I just couldn't get a headshot nor a break. Can you believe that a Certification (on a dang standalone PC no less) on a server can fail simply because the two giant AV companies have awful Linux AV programs with not enough tech support? It's not like I was using a Linux version that was brand new nor out of support. Both vendors are trying to force the user or admin to install 32 bit AV suites on a 64 bit system and the fit can be awkward or sometimes impossible, at times. Sigh. Sorry for venting but our current security guidelines often put those in R&D between a rock and a hard place as they simply try to do their job.

Anyway, feel free to remind me which one(s) were yours, as I don't have my notes in front of me at the moment.

==

Oh, BTW, as of yesterday Evan *thinks* it'll be ready in "a few days" in the last update if you decide to change your mind:

https://darkcointalk.org/threads/rc3-relaunch-strategy-and-testing.1482/

I had a bit of an emergency at work that required me to work a 3rd weekend in a row (although I took off Saturday). Looks like I'm finally past this work project that caused me to work so much OT this month.

Tonight is my first night to re-dig into troubleshooting and to catch up on PMs. Since we weren't live anyway, and this big project had been troublesome (mostly because I was limited to 2 vendors for security), I had to pause troubleshooting the final step. All I can say is the two "biggest" names in AV - which are required for DoD ops even on a standalone computer (!) - have awful AV suites IMHO. Told one of the two Tier 3 engineers I'm dealing with: "It shouldn't require 10 days and 4 engineers to install a (standalone) AV program."

Forgot about my buddy's wedding today. One of those years long common law marriages finally turning into the real thing. Some women have more patience than others.  

Taking a break for the rest of the day. Haven't forgotten about those that contacted me privately. My day job doesn't usually fill up my weekends. I know people have PMed me but with this project consuming the days off I did have, today was essentially my first day off this month and I needed the downtime and extra sleep. I'll be back to pick up on PM discussions either this evening or tomorrow morning if the reception...runs late.    

I haven't confirmed Otoh's transaction yet but I'll just confirm here Otoh's second claim of a community node: this one being 25% in Node 5.

That means Node #5 is complete and we successfully raised 5000 DRK on these first batches of community nodes! Nice job everyone! We've proven there's demand for this type of service and that significant amounts of funds can be raised thru a trusted community operator.

I'll be bringing up Node 5 either when I get thru the bug/issue I was seeing on the final command or if the upcoming RC3.1 (?) fixes the issue I was seeing.

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.

Taking a break this evening as our date for node payments has been pushed back. I'll catch up on PMs tomorrow if you sent me a PM. Thanks.