One possible attack against the Holo hosting network that I keep thinking about could be called a “Flood and Corrupt” attack.
In this scenario a large organization, such as Google or Amazon, would spin up a vast number of nodes and connect them to the Holo network, accumulating a large portion of the overall data stored through Holo.
Then they’d shut down all their nodes simultaneously. If their portion of data was large enough they might be able to break the resilience of some data-points, thus corrupting the integrity of the DHT. While this attack would probably be unlawful, it would nevertheless severely harm the reputation of Holochain.
Also, large corporations can probably run huge numbers of nodes way more efficiently than my little HoloPort at home, drastically undercutting the hosting price I am able to afford. So they could starve small hosts until they dominate the network.
An obvious solution:
Allow hApp providers to limit the number of nodes per real person, when setting the hosting requirements for their hApp. So they would:
- Only allow hosts who have verified their personhood via KYC
- Limit the number of nodes per person
In doing so they woul guarantee that their hApp data is stored on a large variety of devices and cannot easily be centralized under the control of a nefarious large entity. In the case of a Flood and Corrupt attack on the Holo network, their hApp’s data wouldn’t be affected too much.
What I like about this approach is that it would not impose any restrictions on hosting. It would simply allow hApp providers to do so themselves.
Not only would this feature increase security, it would also ensure the spirit of Holochain is being maintained…