feat: Deliver initial spent HTTPS outcalls cycles#10727
Draft
eichhorl wants to merge 5 commits into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
For pay-as-you-go pricing of HTTPS outcalls, shares gossiped by subnet peers contain the amount of cycles spent out of the per-replica allowance.
During block payload building, multiple such shares are combined into a full response object, containing responses and signature of multiple nodes on the subnet.
In addition to the response, this PR aggregates the cycles spent by all contributing peers, plus the "consensus cost" required to include the response in a block. This results in the "initial cost" of the HTTP outcall.
The initial cost is delivered to execution. There, it is used to calculate the "initial refund" that is credited back to the canister.
In the future, also asynchronous spending reports (leading to asynchronous refunds) will be delivered. These are shares that are received later, and did not contribute to the response delivered to the canister.