Utilize LengthToFee feature #1353
Closed
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
notlesh
added
B7-runtimenoteworthy
notlesh
added
the
A3-inprogress
|
Superceded by #1496 |
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.
What does it do?
This updates Moonbeam runtimes to reflect paritytech/substrate#10785 (currently unmerged).
I'm not able to get this to compile locally (even with overrides in
.cargo/config.toml) so it's rather speculative so far.While the first commit (48a8ed3) provides a minimal no-op change to reflect the above-mentioned PR, the goal of this PR is to overhaul our length-based fees for non-Ethereum transactions. Based on my previous work, this probably means a fee on the order of
x^3(xbeing transaction length).That said, this PR will need to be reconciled with #1218.