Quote from: roede94105 on June 29, 2014, 11:40:07 AM

Quote from: chaeplin on June 29, 2014, 11:30:42 AM

Quote from: dewdeded on June 29, 2014, 11:12:08 AM

I scanned the whole MasterNode list 3 times yesterday.
Only 200 till 220 MasterNodes are actually working. (Depending on day time.)

Are the offline/inactive 50% turned off as backup ressource or disguise (and get randomly turned on?)? Or are they misconfigured or is the list wrong?

Why did you do that ??

We have wonderful tool for that.

https://elbzo.net/masternodes.html
Darkcoin MasterNodes Monitoring (last refresh 2014-06-29 11:28:06 / refresh every 1min)

I have port check: closed, is that a problem? everything else is green except darkcoin.io: unlisted

If port is closed somehow, nothing happens if the NM is not selected for DarkSend master.
If the NM is selected, DarkSend client tries to connect the NM.
If DarkSend client can't connect the NM, Masternode re-election msg is broadcasted.

I don't know yet, whether port problem will affect score of top 10 masternodes

https://www.darkcointalk.org/threads/rc4-development-and-path-going-forward.1604/

Quote

New enforcement strategy

Over the last few days weve been looking at a few different options to enforce Masternode payments in RC4. Weve settled on a brand new implementation that is much more simple, yet robust enough to protect the network.

Each round, a winning Masternode is chosen to carry out Darksend transactions. This process is carried out by the individual nodes across the network independently using the masternode election algorithm. This algorithm chooses a winning node for Darksend, but there is also a runner up, third, forth, fifth place, etc.

Utilizing this code, we can make a deterministic list of the top 10 masternodes with the winning scores. These will be the same nodes accross the network and they will vote on who they believe should get paid for that round. The winning Masternode will be the one with the most votes (up to 10 votes) and the network will reject blocks not containing that payment entry.

Other functionality

RC4 will also still include improvements to the anonymity of Darksend. After the implementation phase is complete we will begin by testing the non-enforcement / enforcement switch and the new anonymity layer on testnet.

+ edit

Quote from: eduffield on April 28, 2014, 12:56:11 PM

Quote from: AlexGR on April 28, 2014, 10:01:26 AM

I think it was mentioned, in the discussion between evan/anonymint that by darksending it multiple times through a number of nodes it reduces the bad-actor probabilities to a statistically safe degree to solve the issue that the darksend node knows who sends what.

I think I have a better solution than that, I want to turn the masternodes into I2P relays for darkcoin. So your client will pick one when you start, then relay any messages through that one. It encrypts all of the traffic, removes the connection between IP and address and it the blockchain is still a complete fog. Plus it'll be a private I2P, so it'll be super fast. Masternodes are going to be awesome Grin