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

🐞 [Bug]: 3.2.2 No XCM delivery fees configured for sibling parachain messages #154

Closed
4 tasks done
KitHat opened this issue Apr 2, 2024 · 0 comments
Closed
4 tasks done
Assignees
Labels
bug Something isn't working

Comments

@KitHat
Copy link
Member

KitHat commented Apr 2, 2024

What happened?

To ensure fairness among users and prevent spamming of messages across chains, an adequate fee mechanism must be implemented for sending the XCM message.

Currently, there are no fees charged for delivering XCM messages across parachains. In the template runtime configuration, this is configured through PriceForSiblingDelivery by NoPriceForMessageDelivery.

Attackers may send spam messages across chains without paying a fee. Excessive messages could lead to XCM queue size exhaustion by excessive storage usage until messages are delivered. This could also lead to delays in message delivery for other users.

platform

  • linux
  • windows
  • macos

Expected behavior

Charge adequate message delivery fees in the runtime configuration template. To prevent excessive delivery times and storage exhaustion, an exponential fee mechanism should be used as configured in Kusama

Contribution Guidelines

  • I agree to follow this project's Contribution Guidelines
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Archived in project
Development

No branches or pull requests

1 participant