Search results

Okay, sorry guys. I will stop complaining. It is not about money hunger. I just consider this is an essential part of darkcoin and many make/made/will make their investment decision on this. Let's hope the enforcement will really fulfill its promise.

I'm behind the philosophy and that's why I'm still waiting. I just wonder how you guys are getting your MN payments right now. That's all. Not that I think you should tell me. But, I do believe that something is missing in my setup to make it work after the updates.

One can practically host it only if it works and can receive payments without hacking the code like a developer. Right now, I can run the software but I cannot get payments for days. I know you guys (i.e. developers) put a lot of efforts on this. So, I guess I don't have any rights to say...

Where can I find It is a very nice service at a very reasonable fee. However, isn't the idea of distributing masternodes all over the internet one of the goals of having many running their own masternodes? People were even saying not to host masternodes on cloud servers because you don't want...

What do you mean by taking care of your MN's? Does it mean he is hosting your MN's and takes care of everything?

I wonder what tungfa did to get the payments rolling again.

I still have no payment since the updates. :sad:

Or, the attacker has figured out how to do this in a stealth manner so that we don't see it at all. After all, this is darkcoin so attack should go dark as well. :sad: BTW, the patch that prevents the node from reporting dying is increasing some time window. As someone who is not familiar with...

Versions after 0.10.15.13 at the moment all have the same PROTOCOL_VERSION.

I have scripts on my masternode to check its status every 3 minutes. After the 0.10.15.16 patch, it is still on the MN list. However, I have another script checking poolhash every 3 minutes. It was disconnected by one node after 8 hours, by all other nodes after 2 additional hours. One scenario...

I think this only tells you that your node sees itself as masternode. Some reported earlier that he did not see his other nodes on different machine. And, the inactivity shown in drk.mn or poolhash is about how many nodes see your node as a masternode. Right?

How can we find out our masternode status on the network besides the drk.mn and drk.poolhash.org websites? Even if the MN payment system is not enforced, we should get a fair share from pool operators who are not blocking the payments. There is another thread "Darkcoin is more centralized than...

And, his son can play some drug dealer if he can get out of the prison.

Does Jackie Chan accept DRK?

Haven't got any MN payments yet after the recent updates. How long will this situation continue?

% darkcoind masternode list | sort | uniq -c | grep -v '^[^"]*1' 2 "37.46.114.158:9999" : 1, Only two MN's with a duplicated IP address now. They are: "37.46.114.158:9999" : "XwY1a8oh7Pbt6ApcyTXbezrBGaphF39CyY", "37.46.114.158:9999" : "XvH3qoo6F8c9yLCunVaAFt1rY7xj8ngXji", The...

flare, thanks for the explanation. It is good to know. I did not know the "vin" option after "masternode list". Where can a newbie like me find all the documentation if there is any?

Yes, my list matches your list. The duplicated MN's are disappearing. Great! But, according to my understanding, it is not a permanent fix. Evan is working on a more proper solution in the future.

When a masternode is unique, shouldn't it have a single external IP address? I could imagine something like running the same daemon thrice with some intelligent firewall tagging and forwarding may let some run three darkcoind on the same host. Or, I'm completely off here. Please enlighten me in...

% darkcoind masternode list | sort | uniq -c | grep -v '^[^"]*1' 3 "37.46.114.158:9999" : 1, 2 "37.46.114.244:9999" : 1, 2 "37.46.114.245:9999" : 1, 2 "37.46.114.58:9999" : 1, 2 "37.46.114.66:9999" : 1, 2 "37.46.114.76:9999" : 1, 2...