DOS Attack caused by Data Overload

The Maid Managers problem should be answered by @dirvine.
But I’ll take a shot. Imagine 1 auditor who counts the individual storage portion of a group of 10 users. Easy, no problem. Now tell that 1 auditor to count the individual storage portion of a group of 10million users. That takes some time. Rather than counting the individual, the auditor just asks, how much total storage do we have? Okay everyone gets the average amount. If I butchered the explanation, I apologize.

The NSL solution “discourages” people from making more than one account. Here’s why… if people keep making multiple accounts, they will just end up reducing the NSL amount as well as burning more safecoins. This causes a diminishing return effect. So greedy people and bots end up paying more and gaining less each time they try to game the system. It is not a perfect solution, but it makes this kind of activity manageable.

The storage space allocated for the SAFE Network to sell is not affected. I haven’t worked out an exact formula yet, and should discuss this with the MaidSafe Team, if they decide to use this solution. Basically there will be 2 allocations: the NSL (Network Storage Limit) and the NR (Network Reserve).

One of the concerns from the Proof of Unique Human thread was compromised accounts. I don’t like the idea of locking people down. Everyone should have the ability to defend themselves, and that includes starting over with a new login account. So that option should always be open.

If we have a greedy community, the Network responds accordingly.
If we have a charitable community, the Network responds accordingly.

I’m a fan of voluntary human incentives.

1 Like