Developer Tech News #5From the left: Piotr Janiuk, Golem’s CTO & Co-Founder and Aleksandra Skrzypczak, our Lead Software Engineer & Co-Founder giving their speech at “Golem and Friends” meetup in Berlin on Thursday.
There was a lot of traveling for Golem around Europe last week and we will describe that in the further part of this post but it didn’t discourage us from the most important task at hand — technical development.
Securing against DoS attacks
When Golem was still in its Proof-of-Concept phase, protecting the network against DoS attacks was of secondary importance. Now, as we approach a mainnet launch, security issues have become paramount. While there’s no complete solution to all possible hypothetical security issues, as of this week we have certainly made significant progress.
An example of a basic attack on the Golem network would be to flood the network with numerous computation requests. This would deprive the rest of the network of computational power and crowd out other user requests. The change that is just about to land will combat just such a hypothetical attack.
When any requestor wants a task to be calculated, he or she broadcasts a task request to the network. The easiest countermeasure we can employ here is just to limit the number of tasks from the same requestor which are stored by a single node. This should limit the number of requests that can be propagated into the network by a single requestor.
This solution could still be circumvented if a malign user employed something more sophisticated like a Sybil attack. In this example a malign user could spawn numerous, malicious nodes with the aim of outnumbering the non-malign ones. Figuring how to disable this next level of attack is part of Golem’s ongoing research and development. Except to hear more in the coming months.
Task protocol on devp2p
As you might know from our previous updates, we’re in the process of ...