Quote from: MalReynolds on April 28, 2015, 03:41:30 PM

Quote from: Litoshi on April 28, 2015, 01:14:40 PM

An attacker would have to DDOS all 101 delegates at the same time to stop the network.

Unfortunately, I don't think this would be very hard. Assume a Villain knows the public IP addresses of all 101 Crypti Top Delegate nodes, knows the format of spoofed Crypti data packets (either Lite Wallet packets or 101Club forging packets) to send to these IP addresses, and has a single Vultr server to launch a DDoS attack. Vultr says their max data rate is 1 Gigabit per second (see https://discuss.vultr.com/discussion/210/connection-speed-in-vps/p1 ) . This means a single Villain with a single server can (theoretically / worst case) aim 10 Megabits per second at EACH Delegate SIMULTANEOUSLY. In a 10 second blocktime, EVERY node would have to process 100 million bits or 10 MBytes of fake Crypti DDoS packets. Are we scaled to handle such a load successfully? I bet the answer is no. This is not a rhetorical question, I would love to hear dev comments....

Currently the 101 Top Delegate servers are performing two functions simultaneously: (1) communicating with Crypti Lite wallets to accept details of ongoing Crypti transactions, and (2) communicating with other members of the 101 Top delegates to forge a blockchain. Function 1 REQUIRES a list of public IP address known to all (at least all Crypti Lite wallets) for the 101 Club servers. These public IP addresses are subject to a DDoS attack. Currently, such a DDoS attack would not only knock out Crypti Lite comms (Function 1), IT WOULD ALSO HALT THE FORGING OF THE CRYPTI BLOCKCHAIN (Function 2).

This is why I suggest that future versions of Crypti Delegate contain a darknet function, to maintain blockchain forging via a SECRET PRIVATE network of 101 IP addresses even if the PUBLIC network of 101 IP addresses are attacked. This would mean a new delegate would set up two sets of Crypti code on two separate servers - one block of code on one server with a public IP address to handle Crypti Lite comms, another block of code on another server to handle 101 club comms and blockchain forging. A DDoS attack would then halt Crypti Lite comms and stop incorporation of transactions for the duration of the attack...but the FORGING OF THE BLOCKCHAIN WOULD CONTINUE UNINTERRUPTED.

The very act of organizing the Crypti 101 Top Delegates to keep the blockchain forging on a darknet even when under a DDoS attack is a prime deterrent to a DDoS attack being started in the first place.

Something to think about.

Interesting Idea Mal. But i think that if we had hidden delegates to continue forging while under attack, we would not need 101...... we could run the bc with only one delegate forging, but better to have 6-10, same as number of required confirms for transactions.

Of course, this would only inflame starik69 that we have become CENTRALIZED!!