Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Divide ref time XCM fees by four #2929

Merged
merged 6 commits into from
Sep 4, 2024
Merged

Conversation

librelois
Copy link
Collaborator

@librelois librelois commented Sep 3, 2024

What does it do?

Since we have 4 times more cpu time per block, we need to divide as well the xcm fees constant that account for cpu time

What important points reviewers should know?

Is there something left for follow-up PRs?

What alternative implementations were considered?

Are there relevant PRs or issues in other repositories (Substrate, Polkadot, Frontier, Cumulus)?

What value does it bring to the blockchain users?

@librelois librelois added B7-runtimenoteworthy Changes should be noted in any runtime-upgrade release notes D3-trivial PR contains trivial changes in a runtime directory that do not require an audit breaking Needs to be mentioned in breaking changes labels Sep 3, 2024
@librelois librelois changed the title Divide by 2 XCM fees Divide ref time XCM fees by two Sep 3, 2024
@librelois librelois changed the title Divide ref time XCM fees by two Divide ref time XCM fees by four Sep 3, 2024
Copy link
Contributor

github-actions bot commented Sep 3, 2024

WASM runtime size check:

Compared to target branch

Moonbase runtime: 2180 KB (no changes) ✅

Moonbeam runtime: 2120 KB (no changes) ✅

Moonriver runtime: 2116 KB (no changes) ✅

Compared to latest release (runtime-3101)

Moonbase runtime: 2180 KB (+2180 KB compared to latest release) ⚠️

Moonbeam runtime: 2120 KB (+144 KB compared to latest release) ⚠️

Moonriver runtime: 2116 KB (+2116 KB compared to latest release) ⚠️

Copy link
Contributor

github-actions bot commented Sep 3, 2024

Coverage Report

@@                      Coverage Diff                      @@
##           master   elois-divide-xcm-cost-by-2     +/-   ##
=============================================================
  Coverage   80.92%                       80.92%   0.00%     
  Files         286                          286             
+ Lines       81804                        81813      +9     
=============================================================
+ Hits        66196                        66205      +9     
  Misses      15608                        15608             
Files Changed Coverage

Coverage generated Tue Sep 3 20:35:22 UTC 2024

@pLabarta
Copy link
Contributor

pLabarta commented Sep 3, 2024

Changes to test/suites/dev/moonbase/test-fees/test-fee-multiplier-max.ts do not exactly match a /4 change in the constant but it may involve other fees. Seems an expected change to me, but needs review.

Copy link
Collaborator Author

@librelois librelois left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tests changes LGTM

@noandrea noandrea merged commit c6a71e5 into master Sep 4, 2024
35 of 38 checks passed
@noandrea noandrea deleted the elois-divide-xcm-cost-by-2 branch September 4, 2024 13:47
noandrea pushed a commit that referenced this pull request Sep 5, 2024
* divide by 2 xcm fees

* divide by 4 xcm fees

* try to fix rust tests

* fix dev tests including the hardcoded constant

* fix remaining constant in xcm dev test

* update expected values to ~/4 the previous ones

---------

Co-authored-by: Pablo Labarta <[email protected]>
@noandrea noandrea mentioned this pull request Sep 5, 2024
18 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
B7-runtimenoteworthy Changes should be noted in any runtime-upgrade release notes breaking Needs to be mentioned in breaking changes D3-trivial PR contains trivial changes in a runtime directory that do not require an audit
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants