Enable gas-budget-based congestion control with overage & absolute cap #20072
+28
−10
Conversation
This file contains 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
- Changes congestion control mode to use gas budget with cap. - Sets a separate (lower) limit for randomness-using tx. - Allows up to one tx per-commit per-object to exceed the budget, with accumulated debt tracking. - Adds absolute capped cost at a multiple of per-commit budget.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Skipped Deployments
|
aschran
force-pushed
the
aschran/cc-accum-enable
branch
from
f6af357
to
2c06703
Compare
aschran
force-pushed
the
aschran/cc-accum-enable
branch
from
2c06703
to
7190f70
Compare
mystenmark
approved these changes
Oct 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Test plan
Unit tests & simtests in PRs adding these
ProtocolConfigparameters.Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.