-
Notifications
You must be signed in to change notification settings - Fork 708
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
Labels
I5-enhancement
An additional feature request.
Comments
12 tasks
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
This was referenced Jun 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
message_count
.min_duration
(= 100) andthreshold
= 1,000,000.min_duration + threshold / message_count
can be deleted by anyone.The text was updated successfully, but these errors were encountered: