For retrievals don't round down payments to interval lower bound #549
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.
Will fix filecoin-project/lotus#6297 (when bubbled up to lotus)
When sending a payment voucher, we were rounding down the amount to the lower bound of the payment interval, so that payment would always proceed in exact intervals.
This PR changes the behaviour not to round down: the client will send a voucher that pays for all data that has been received (which may be more than the lower bound of the payment interval)