Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • I fail to see, how "proof of work" can prevent from DOS attacks? The client could ignore the challenge and keep sending requests up to the fail. Is there a 3rd process handling the challenge? Commented Dec 24, 2018 at 19:07
  • 6
    @Laiv POW can be reliably issued and checked distributed without connecting to a central database, which is where most other rate limiting schemes fail. It increases the cost of an attack for an attacker, as scaling out your defence and increasing load factor is cheaper for you and legitimate users than scaling out the attack for the attacker. It creates an economic disincentive to attack the system, as it also effectively excludes low powered devices (e.g. compromised printers, IOT, routers) from being used as an effective attack platform. Commented Dec 25, 2018 at 0:29