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

XCM: Graceful Deletion of Overweight Messages #488

Open
Tracked by #925
gavofyork opened this issue Oct 7, 2022 · 0 comments
Open
Tracked by #925

XCM: Graceful Deletion of Overweight Messages #488

gavofyork opened this issue Oct 7, 2022 · 0 comments
Labels
I5-enhancement An additional feature request.

Comments

@gavofyork
Copy link
Member

At present overweight messages stick around in state until/unless they are executed. Instead, eventual unprivileged deletion of overweight messages should be allowed in certain circumstances:

  • Overweight messages are tagged with block number at which they arrived.
  • We also keep a count of the total number of overweight messages in storage message_count.
  • We have a min_duration (= 100) and threshold = 1,000,000.
  • Any messages older than min_duration + threshold / message_count can be deleted by anyone.
@gavofyork gavofyork mentioned this issue Oct 7, 2022
30 tasks
@juangirini juangirini transferred this issue from paritytech/polkadot Aug 24, 2023
@the-right-joyce the-right-joyce added I5-enhancement An additional feature request. and removed J0-enhancement labels Aug 25, 2023
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 8, 2024
* fixed block where proof is generated

* proof_is_generated_at_best_block_known_to_target_node
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 8, 2024
* fixed block where proof is generated

* proof_is_generated_at_best_block_known_to_target_node
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 8, 2024
* fixed block where proof is generated

* proof_is_generated_at_best_block_known_to_target_node
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 8, 2024
* fixed block where proof is generated

* proof_is_generated_at_best_block_known_to_target_node
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 9, 2024
* fixed block where proof is generated

* proof_is_generated_at_best_block_known_to_target_node
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 9, 2024
* fixed block where proof is generated

* proof_is_generated_at_best_block_known_to_target_node
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 9, 2024
* fixed block where proof is generated

* proof_is_generated_at_best_block_known_to_target_node
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 9, 2024
* fixed block where proof is generated

* proof_is_generated_at_best_block_known_to_target_node
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 9, 2024
* fixed block where proof is generated

* proof_is_generated_at_best_block_known_to_target_node
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 9, 2024
* fixed block where proof is generated

* proof_is_generated_at_best_block_known_to_target_node
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 10, 2024
* fixed block where proof is generated

* proof_is_generated_at_best_block_known_to_target_node
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 10, 2024
* fixed block where proof is generated

* proof_is_generated_at_best_block_known_to_target_node
bkchr pushed a commit that referenced this issue Apr 10, 2024
* fixed block where proof is generated

* proof_is_generated_at_best_block_known_to_target_node
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I5-enhancement An additional feature request.
Projects
Status: Backlog
Development

No branches or pull requests

2 participants