you read that comment, but you don't bother to note that at the top of your steemd profile info on the left hand side, it says this:
Voting Weight
28,325 SP
30,072 + 1,613 - 3,361 SP
Voting Power
83.92%@inertia
Bandwidth Remaining
99.99%
633mb of 633mb
I wonder what kind of mouse and keyboard you can push that much data onto the chain with. I'd like it cos typing is so damned slow.
Unless I did my math wrong, I would have to broadcast 146k every 20 seconds to the blockchain in order to use that much bandwidth. I don't think posts can be that big.
So if we assume maximum tx size is 2kb, the longest possible comment, then an accounnt c annot put more than 2.9mb per day on the chain. However, what other methods of flood protection does the system have? If every available RPC is used, and transactions are multiply broadcast across all available RPC's, and they all relay that into the gossip p2p between rpc, seed and witness nodes, what is going to stop the servers from being overwhelmed?
I think nothing. I think, if someone wants to take down this network, script kiddy level skills are all that's required. Besides that, once the nodes are being flooded, what other vulnerabilities are going to open?
The design assumes no adversaries at all. This seems like a pretty dumb assumption with all the astroturfing that goes on, and the trolling against anyone who raises a valid concern.
It appears to me you moved the goalpost.