marigold-dev/deku

Spam Protection

Opened this issue · 0 comments

We need to implement some kind of spam protection to make attacks more expensive:

Ideas off the top of my head:

  • we're PoA, so we can blacklist validators who spam us effectively, since < 1/3rd of the validators are bad.
  • We can use PoW before we accept blocks from a validator. Maybe same thing for clients submitting transactions?