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

Remove refund instructions #429

Merged
merged 2 commits into from
Sep 19, 2023
Merged

Remove refund instructions #429

merged 2 commits into from
Sep 19, 2023

Conversation

imstar15
Copy link
Member

@imstar15 imstar15 commented Sep 18, 2023

The reason of these removal is that each XCM instruction costs 1M weight, so removing the last two for refunding actually will cost users less than having a refund process.

Besides, Rocstar doesn’t allow high XCM weight per block, so reducing weight of each XCM messages will help our messages get unblocked.

Copy link
Member

@v9n v9n left a comment

Choose a reason for hiding this comment

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

code looks good but i didn't quite get the reason we have to do this. could you help explain ? thanks

Copy link
Member

@chrisli30 chrisli30 left a comment

Choose a reason for hiding this comment

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

Yeah @imstar15 please explain the PR when you submit it ...

@v9n, the reason of these removal is that each XCM instruction costs 1M weight, so removing the last two for refunding actually will cost users less than having a refund process.

Besides, Rocstar doesn’t allow high XCM weight per block, so reducing weight of each XCM messages will help our messages get unblocked.

@imstar15 imstar15 merged commit cf4a6ea into master Sep 19, 2023
3 checks passed
@imstar15 imstar15 deleted the remove-refund-instructions branch September 19, 2023 06:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants