feat: circuit breaker for deposit - #1142
Merged
Merged
Conversation
|
Crate versions that have been updated:
Runtime version has been increased. |
# Conflicts: # Cargo.lock # integration-tests/Cargo.toml # runtime/hydradx/src/weights/pallet_omnipool.rs
jak-pan
reviewed
Jul 25, 2025
jak-pan
reviewed
Jul 25, 2025
martinfridrich
approved these changes
Jul 26, 2025
|
Quick benchmark at commit dc8dbb1 has been executed successfully. |
mrq1911
approved these changes
Jul 29, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TODO:
wait for last rebench commit of ref machine
grab benchmarks from bench machine
remove amount from release
create issue for untrapping assets as in XcmEchangeAsset we trap instead or reserve tokens when depost limit exceeds
rebench exchange asset too - worst case is buy as we calculate amount in too
wait for rebech of two LM pallets then replace
add action to set xcm-rate-limits for famous, birdged, sharetokens, etc assets. Limit should be also calibrated based on bug bounty values, making it always more profitable for a hacker to report the issue than to exploit it. MAYBE IT IS BETTER TO DETERMINE the daily mint, and multiplying it. Do a histogram, but not only how much we mint and how much we burn, so net mint should be calculated. We query daily net mint, and pick end of the historgram, without outliers
we need bot for unlocking assets