You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This ticket is about to keep track of the discussions and implementation of a dynamic complexity mechanism for the proof of work implementation.
An idea could be to apply the following changes apply thresholds to implement a dynamic complexity of the proof of work for whistleblower sessions varying the complexity from level LOW to level HIGH based on a set of conditions:
Level should be set to HIGH if more than proof_of_work_reports_per_ip are detected over a certain proof_of_work_observation_period
Level should be set to HIGH if more than proof_of_work_reports_per_tenant are detected over a certain proof_of_work_observation_period
In recent times, given maybe the diffusion of the software and a growing interest on the technology we have observed multiple attempts of performing denial of services on setups run by the community.
The text was updated successfully, but these errors were encountered:
Proposal
This ticket is about to keep track of the discussions and implementation of a dynamic complexity mechanism for the proof of work implementation.
An idea could be to apply the following changes apply thresholds to implement a dynamic complexity of the proof of work for whistleblower sessions varying the complexity from level LOW to level HIGH based on a set of conditions:
An example of default configuration could be:
Motivation and context
In recent times, given maybe the diffusion of the software and a growing interest on the technology we have observed multiple attempts of performing denial of services on setups run by the community.
The text was updated successfully, but these errors were encountered: