Feat/dispute freeze effect - #656
Merged
thlpkee20-wq merged 13 commits intoJul 29, 2026
Merged
Conversation
Contributor
Author
|
Done, Close: #656 |
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
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.
Close: #595
Here's a summary of what we accomplished:
Feature: Dispute freeze effect — halts claims for an offering while a critical dispute is open.
Pre-existing corruption fixes (merge artifacts):
8 edge case tests added to src/test_dispute.rs covering: multiple simultaneous critical disputes, freeze on/off events, rejected resolutions still clearing freeze, freeze isolation across offerings, and standard disputes not emitting freeze events.
Known blocker (pre-existing): #[contracterror] LengthExceedsMax — 63 RevoraError variants exceed Soroban SDK v21's ~32-variant limit. Affects both master and our branch — not caused by our changes.