Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test - Config Stacker DB Signer #5122

Open
ASuciuX opened this issue Aug 29, 2024 · 0 comments
Open

Test - Config Stacker DB Signer #5122

ASuciuX opened this issue Aug 29, 2024 · 0 comments

Comments

@ASuciuX
Copy link
Contributor

ASuciuX commented Aug 29, 2024

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:

  1. send a lot of packages (instead of 1 because has custom node)
  2. signers/nodes see that as bad behavior and stop communicating with that

Involve test peer to maybe try to test this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Status: 🆕 New
Development

No branches or pull requests

2 participants