Quote from: MalReynolds on May 14, 2015, 01:40:32 PM

Quote from: starik69 on May 14, 2015, 11:39:38 AM

Quote from: GreXX on May 14, 2015, 05:04:37 AM

Starik, if someone were to run a full node on windows and try to become a delegate, it would be pointless. As soon as they became a delegate and were active and started missing blocks, they would just get voted out.

If this is true and the network became only 101 delegates then this is very bad because it could be stopped by simple ddos attack. Cry

A few points.

First, stasDelegates 1,2,4,5,6 and 8 are below 25% uptime and still dropping. They've obviously been offline for some time now and still haven't been voted down. We've got six new standby delegates (cryptiNeo,starick69, btc, Intrinsic1, Intrinsic2 and China) waiting to get votes and replace them.

Second, I totally agree about the vulnerability of Crypti in its current form to DDoS attacks. As I have discussed before, one solution is to split Top Delegate communications with Lite clients and their communications with each other onto separate IP addresses. Top Delegates should have their own darknet where only they know the IP addresses being used for communications to new forge new blocks.

Mal,

In the past hour I brought this up to the group, and updated our internal list for voting/upvoting the foundation delegates.

One reason that the Stas delegates show low uptime is that the uptime is figured from the first block that the delegate forged. In the case of stas, that is around 110,000. we are now in 270,000 range. Stas was offline for a few days due to a billing problem with Vultr. Since he missed forging some 50,000 blocks, he dropped to about 14%. It takes about 100,000 blocks for him to advance 15%. He is forging around 100% now.

This is t change in version 021. The uptime will be figured with the last X blocks. Value of X is undecided, and depends on testing results.