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
{{ message }}
This repository was archived by the owner on Aug 2, 2021. It is now read-only.
Issue #1440 is about implementing thresholds into accounting.
This issue is about making these thresholds parametrizable, so that it is possible to provide different values to the code, allowing for experimentation with different thresholds.
Questions to be answered (may need coordination/sync with research track):
What happens if nodes have different thresholds in production?
Is it ok for nodes to have their own thresholds?
Should this parametrization only be allowed for testing?
Should there be some kind of protocol to set these thresholds network-wide?
This issue is about allowing experimentation; thus the questions above are meant to obtain clarity, but do not need to find implementation as part of this issue.
The most obvious solution for parametrization is to provide values via command line parameter. Other options may be proposed as part of this issue.
Issue #1440 is about implementing thresholds into accounting.
This issue is about making these thresholds parametrizable, so that it is possible to provide different values to the code, allowing for experimentation with different thresholds.
Questions to be answered (may need coordination/sync with research track):
This issue is about allowing experimentation; thus the questions above are meant to obtain clarity, but do not need to find implementation as part of this issue.
The most obvious solution for parametrization is to provide values via command line parameter. Other options may be proposed as part of this issue.