Topic: DyslexicZombei's Darkcoin Community MasterNode Svcs: CLOSED. Nodes 2 4 5 Refunds - page 5. (Read 27909 times)

I don't know, I've had 3 nodes up for just over 3 weeks now with zero problems or downtime with any of them (local separated wallet.dat(s) launched with win-qt and remote Ubuntu VMs). Now payments over the last couple days are a totally different issue.  

DZ, I am so happy that you are here. Actually I am very proud for you and for our community, at the same time that I am so ashamed and sorry for my recent lack of trust of you.

Communication can be (and is) very crucial to a community. Please receive my recent criticism with this in mind, understand that it is meant to be constructive criticism, and that I am here at your disposal, and at the disposal of this community and of the Darkcoin community as a whole, to help in whatever I can be useful.

As wisely said before, let's take these last incidents as a wake up call for us all, as a community (including here the Darkcoin Community) to make our best for the improvement of your service, that IS very important to Darkcoin development as a whole.

I wish you (and, of course, all of us) all the success. I already know that you are doing your best, and once more I put myself available for anything needed.

Thank you DZ, thank you all.

Hello DZ
I'm trying to figure out what is your problem on node 3 as I have a myself some nodes running.
What I can't understand is why you do not reset the whole setup (sending all the funds to a new wallet, regenerating the masternode privkey and reassociating the MN with the cold wallet)

My current setup: all my cold wallets are copied three times in different location on a linux vm - I just need to copy the darkcoin.conf files and wallet.dat corresponding to the node I need to activate into the .darkcoin folder each time. I don't use the qt wallet, and I generated the wallet files using the open sourced darkcoind compiled by myself. I would never use MS Windows to manage my wallets, but that is my personal opinion.
All wallet.dat files have been encrypted using OpenSSL and sent by emails from the vm to 2 inbox.
The vm itself has been fully copied on my ZFS RAIDZ-3 NAS, with monthly backups.

The MN instances are hosted by a reputable third party company remotely .

I can't understand why you struggle so much to have the service up and running, honestly.

 this is your address???

The coins are always on wallet. They are not used for coin mixing or anything. You can simply copy the wallet.dat to another machine and transfer out. You can do this even on a functioning hot wallet to transfer mined coins out. Hope that helps.

Glad that you're back, Ewan has been and is also on a well deserved holidays/break, actually on your islands atm, hopefully to return well rested and restored, there are good things for DRK going on behind the scenes, for me it's a long term play, I've sold none of my main initial stake and don't intend to anytime soon:

http://bitinfocharts.com/darkcoin/address/XosXcEm3Y6Mv6tmBKd1rUWhqB9Pf1hABj7

Do you mind me to rise this issue on main thread?

Or even better to PM ghost and cheaplin?

Thanks. I actually reached out to one of the guide creators to be a co-admin but this person went on vacation, then I went on vacation. I have been too busy after getting back from this short vacation to follow up with this individual. This person is interested so perhaps reinforcements and improvements in code could convince me to continue this service which I think has a lot of potential (if the dang bugs and masternode disconnects could be stomped out).

Yeah, regarding that one. Node 1 re-build attempt was attempted a final time when I wasn't trying to rebuild Node 3's local wallet association. I moved away 1K from this Node 1/2 wallet (that originally had at least 2k) and restarted the node using a different PC. Therefore, the local wallet was now only associated with just one node instead of using a Cold Wallet and a Hot Wallet with different launch conf files to try to connect to 2 nodes.

So, the local wallet was the orig. wallet associated with the Hot Wallet payment. Problem was even with a fresh darkcoin client install and restoring the orig. wallet file, the hot wallet stake payment still looks to go to some accountaddress0 representing a privkey that never released the coins back when I took the RC2 Hot Wallet node down.

I can't regenerate another privkey because we never got our DRK back (45% which was mine) after the hot wallet payment was sent to whereever it is that hot wallet payments hold these funds to register as a masternode.

Glad to hear that you are fine, I was worried that something happen to you.
Problems with MNs will be solved dont worry, it just takes time, lets all try to be constructive here and try helping DZ at least to pull pressure off him as much as we can!

DZ I dont know if you have contact with chaeplin or GhostPlayer, they seems to be very handful in masternodes issues on main thread, maybe they can help since devs are too busy with RC4.

We all have to realize that this project is still in development and problems will be rising in the future as well, before we are in production 100%.

Stay well,
and if you find anything further we as your clients could help you, feel free to ask, at least you can count on me for any assistance!

I do. Only Node 1 was set up via the hot wallet method.

I'd say including copies of wallet.dat: make copies of your database and blockchain in your user's AppData folder (if using Windows) while things are working well and hope that the copy you made isn't corrupt if you need to use it.

Rebuild *appears* to be going well so far: was showing about 3.5 DRK previous to this evening's latest rebuild attempt (of many). Still syncing but finally seeing 1000DRK as the balance at the moment! Crossing fingers, toes, etc.

With node 1, physically copy wallet.dat to a local comp. Then send exactly 1000 darks to a fresh wallet from the copied wallet.

DZ suggest you just run MN with wallet.dat. If it's good enough for Satoshi, it's good enough for me.

Currently working on node 3 at the moment and that's priority 1. It's showing possible progress (finally) but I hope to be able to regain association with the Node 3 stake. Yes, the node 3 stake has been disassociated with the local wallet, but this latest rebuild appears to be working so far...but I can't guarantee jack with with beta software and a coin creator/programmer that wouldn't even look into our RC2 Node 1 wallet problem.

I've been one of Darkcoin's biggest and most public cheerleaders but I am re-thinking this whole community and even multiple full node service: I had original wallet files and even a copy of the blockchain and database for Node 3 from prior to the disassociation. Didn't seem to make a difference whether I was using an old copy (which appears to be a copy of a corrupt file) of the database/blockchain or the latest copy of the these two sets of files.

There's funding for half of node 5, with an offer to fill the rest from a community member & I would be turning down *several hundred* node reservations but I can't, at the moment in good faith, recommend a multiple node setup for anyone unless they use separate PCs or virtual machines where they make several offline copies of the wallet file *&* database/blockchain. I can't recommend that anyone set up a cold wallet without realizing that they're depending on zeroes and ones and the perfect harmony of beta software, and that even with backup wallet files and backup databases/blockchain, the cold wallet may *still* be at risk, as I unfortunately found out.

I may end up just finishing out the month and refunding everyone without penalties based on how this latest rebuild attempt goes for Node 3. It's been a bit disheartening to see the nodes just fall offline like that and one node (Node 2) which is actually the best earning node is requiring its 3rd setup/restart in 2 weeks. Every node has required a restart and reactivation at least once in the last two weeks; at this point these nodes can't be set and forgotten about for weeks or months.

I'm working on the spreadsheets and the payments will go out tomorrow morning, including Node 3, whatever it's showing. For Node 3, I said I wasn't going to guarantee payouts when nodes were down/problematic but I will send the mining output of 2 Zeusminer Blizzards and my 750TI from the 2nd to the 15th as a partial compensation. I have no idea what they've earned but whatever they've earned I'll convert to DRK and split that among Node 3 owners along with the last Node 3 payments withheld while I tried to reassociate the local wallet with the cold wallet deposit (yes, as awful and scary as that sounds).

TL;DR: Node 3 owners will see two sets of payouts tomorrow. Node 2 and 4 will see payouts from July 1-15.

I was supposed to send the Node 3 payouts from late June but I wasn't touching anything related to the balance of Node 3 and its local wallet until I was convinced there was no hope in regaining association with the cold wallet stake payment for Node 3.

Guys, I'm here. I absolutely can't run off with peoples funds as I'd lose my job/clearance and many forum members including Otoh know my real ID and have my real contact info. I did have to take time off for a family reunion as mentioned and didn't have access to my usual IT gadgets. Was my first real break in 2 years. My wife said I was getting way too snappy with everything going on and I left off with several hundred reservations for full nodes that I completely stopped because of Node 3 problems.

The sum of it is Node 3 is offline and showing problems, Node 2 needs to be brought back up again and showed modest returns, and Node 4 is up but has had crappy mining returns.

When I did have time to break away from family I was working on problems with Node 3 or bringing Nodes back up that didn't go offline as remote servers but became disconnected as Master Nodes. Node 3 has been driving me nuts and after problems with our Hot Wallet in Node 1, where I was completely ignored by Evan regarding problems I was seeing as a Beta tester for his network with Node 1's hot wallet, I don't feel that I'll get any help/support with this one either. The best way to describe the problem is in picture form:

http://i286.photobucket.com/albums/ll87/SurfSkateKauai/Corruptedblockdatabase.png

=66771012&filters[recent]=1&sort=1&o=2]http://s286.photobucket.com/user/SurfSkateKauai/media/coldwalletdisappears.png.html?filters[user]=66771012&filters[recent]=1&sort=1&o=2

http://i286.photobucket.com/albums/ll87/SurfSkateKauai/ReceivingAddressesonDZNode3.png

Well, DZ has been online today. At least we can assume that he is well.

Still only 6:57 PM, here - HST.

But reading other posts of payouts received by others, earlier.

Come on DZ,  we don't want to go down this path.

The payout date has passed, even though promised by DZ that they would be on schedule this time around. Disappointed.

Thank you so much Otoh, for your post. I am really glad to see things getting cleared after all.

Also, 2dogs, thank you for your post. If the community works on a solution for a contingency plan, I want to collaborate as best as I can.

Cheers

Indeed. This shows that communication is king. This piece of information can explain many things that before were open to interpretation.

A contingency plan IS indeed necessary. For example: having a someone else responsible, trustworth to DZ and to the group, for unexpected situations is very important.

The idea with this service is great. I have always believed in it. And it is from difficult moments like these that it gets improved.

I'm happy for you all.