Earlier quoted context omitted.
Maybe I'm missing something, but doesn't this mean the work has to be done by the client AND the server every time a challenge is issued? I think ideally you'd want work that was easy for the server and difficult for the server . And what is to stop being DDoS'd by clients that are challenged but neglect to perform the challenge? Regardless, I think something like this is the way forward if one doesn't want to throw…
The magic of proof of work is that it's something that's really hard to do but easy to validate. Anubis' proof of work works like this: A sha256 hash is a bunch of bytes like this: 394d1cc82924c2368d4e34fa450c6b30d5d02f8ae4bb6310e2296593008ff89f We usually write it out in hex form, but that's literally what the bytes in ram look like. In a proof of work validation system, you take some base value (the "challenge") an…
I imagine it costs more resource to access the protected website but would this stop the bots? Wouldn't they be able to pass the challenge and scrap the data after? Or normal scrapbots usually timeout after a small amount of time/ resources is used?