The max-writes and write-freq parameters for signers of StackerDB are currently set to their default values, with write-freq always set to 0 and max-writes set to a very high value. Have these settings been reviewed to ensure they are resilient against potential DDoS attacks? Is it more optimal to be set to other values?
This test is more general for participants in the StackerDb.
This test could be useful as it uses max-writes.
What's expected from bad actor:
send a lot of packages (instead of 1 because has custom node)
signers/nodes see that as bad behavior and stop communicating with that
The
max-writesandwrite-freqparameters for signers of StackerDB are currently set to their default values, withwrite-freqalways set to 0 andmax-writesset to a very high value. Have these settings been reviewed to ensure they are resilient against potential DDoS attacks? Is it more optimal to be set to other values?This test is more general for participants in the StackerDb. This test could be useful as it uses
max-writes.What's expected from bad actor:
Involve test peer to maybe try to test this.