Mass Account Attack and Sleeper Cell Attack prevention algorithm.
This is a continuation of
Priority by Threat -- Designing a block with security features - Nano Forum
The post will discuss how a mass account attack or a sleeper cell attack could be prevented.
Needless to say what the mass attack is:
If the network can update 39 (a level created at 10% of total raw)
level_tps [ ], and if a block is created with
level_tps and threat as threat x
level_tps[level], we should be able to single out a mass account attack or a sleeper cell attack.
level_tps: Number of transactions per second received from a level in an epoch X.)
Also, to prevent low raw attacks, we can introduce another variable
Q and set
level_tps [level< P] = level_tps[level] * Q, effectively putting spammers at the bottom of the queue. Considering the growth in adoption, we can we can further apply some method to decrease the
value of 'Q' as time goes by.