Search results

It might be superior or not. I bet for the latter. Because I already start having my doubts when I see a whitepaper released on mega, an abstract written in CAPS Lock, the whole text edited in microsoft word and there are no references in the whitepaper either. And the screencast video just...

Well lets see how rc4 changes the behaviour. I think so too, that there must be at least one hidden factor i.e. my longest running masternode http://drk.poolhash.org/masternode.html?srch&nmstr=Xb6PwPmyuhr53qDUEKhq4jNxqRNmswnRmy has had only 3 payments in 12 days (0.25drk/day) and none of my...

Awesome, I will point my miner to testnet if the time is ready and if it makes sense. Is there anything an outsider can do to help?

Do you mean wetsuit like in diving equipment? If so it might be of interest for a friend of mine. So put it on the website :-)

Its just a shot in the dark, but what happens if you have a screen session ( preferebly http://wiki.ubuntuusers.de/byobu ) open and just close the terminal window. Then everything should continue to run in the context of screen.

To understand that fully: This happens if your local time has an offset too big from the right time?

The silence makes me kind of nervous too, but I am convinced its more like christmas and my birthday at the same day whereas its not evident what day it will actually be.

I guess he has tried restoring it. The point that deletion and corruption of just small files can mean losses of thousands and even millions of dollars is something I really dislike about the digital currencies. It not like with a real wallet or gold.

Nice :-) Then thanks for your condolences. I have started a little bruteforce attack myself. Lets see what happens. Maybe one day one day one darkcoin is worth a zillion dollars than I can buy a quantum computer, crack the wallet and end all third world problems in one strike...

Thanks for the links. I just have a very slow Winows machine whereas brute forcing is that much of a choice. And bruteforcing in the cloud is something I can't afford since the amount of possible typos is in the quadrillions I guess...

Hi, I think I just did the second most stupid thing besides deleting a wallet: I just moved 1000DRK into a wallet which was already encrypted. I have created it last week in preparation of the setup of some masternodes and guess what: I am not able to unlock anymore. I have no idea what I had in...

I really hope the syncing issues are over after this release. I just spend several hours debugging because locally everything synced fine, but on my hetzner server nothing happened at all. The only solution I found was syncing on my local machine and deploying the peers.dat to the server...

Damn, but still I haven't written my puppet script for nothing. I don't need that many changes to modify it to listen to several ip addresse instead of ports.

I know I can bind to different ports. The whole point is to run more than run one masternode per server.

Damn it :-) It haven't had any luck with ipv6 and haven't really tried. I was thinking the port mapping should be perfectly fine. Can anyone help me direct to the piece of code where this is triggered? Or is it in the closed Source part?

With two users, two daemons listening to different ports it seems to work. They are synced fine. Have a look at the deployment script: https://bitbucket.org/cwinkelmann/darkcoin_provisioning/commits/fa87f23fba4a1c7025eadd71ff635f58bebc6555

I will test that today when i am not "supposed to work" anymore and I have big hopes for a setup where I have just X configs for X daemons and X ports and a single user and a single ipv4 address would enough to make it work. because that would be even easier than ipv6 subnets or X separate ip...

Hi, my root server arrived and I am doing my first tests with it and I am playing around with the port=XXX Parameter in the darkcoin.conf. Using IPv6 would be a bit overdone if it would be possible to run several darkcoin daemons simply listening on multiple ports. Would that make problems with...

I had the same problem once when I started bitcoind without a darkcoin.conf and then without adding rpcpassword=CqbmPwd49ArBeqT1x9VnJUT4dfsJ6B3pPPu8AbbaSvoo rpcallowip=127.0.0.1 I started the daemon again which resulted in the exact same message. I think it can happen too if you don't have the...

I know this problem too. It really depends on the Firewall/Router you are behind. I tried running several clients in many places. Sometimes it works sometime it does not. But you are right, that issue should be addressed. It think the easiest would be to provide a zip/tar.gz which holds...