feat(protocol): improve precision for slot-availability multipliers #13108
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Assuming the first slot's baseFee is
bMin
, the last slot's baseFee isbMax
, the ration ofbMin/bMax
is the slot availability multiplier. Usually we want to set this multiplier to a certain value, for example, 20, then we calculate the internal parameterslotSmoothingFactor
reversely to ensurebMin/bMax == 20
.Before this PR, the actual
bMin/bMax
value is way off 20 because the number of slots are not a large value. We need to make sureslotSmoothingFactor
has higher precision, that's why we multiply 1000 in the calculate of fees so we can giveslotSmoothingFactor
a bigger value -- if it's supposed to have a value of 12.1234, now it will have a value of 12123 instead of 12.