Skip to content

Update ISSUES_723_897_IMPLEMENTATION.md #1383

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.

Sign up for GitHub

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

Merged
joelpeace48-cell merged 1 commit into from
Sep 25, 2026
Merged

Update ISSUES_723_897_IMPLEMENTATION.md #1383

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion ISSUES_723_897_IMPLEMENTATION.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ This document summarizes the changes introduced to implement per-account and glo
- **Implementation**: We added a tracking mechanism `AccountRedeemVolume(Address, WindowId)` to store the total amount redeemed by each user in a given time window.
- **Verification**: The `redeem` function now checks this volume against `PER_ACCOUNT_REDEEM_CAP`. If exceeded, it reverts with `Error::PerAccountCapExceeded`.

## 2. Global Circuit Breaker (#723)
## 2. Global Circuit Breaker (#723).
- **Implementation**: We track aggregate system-wide redemptions using `GlobalRedeemVolume(WindowId)`.
- **Verification**: If a transaction pushes the global volume over `GLOBAL_REDEEM_CAP`, the contract emits a `CircuitBreakerTripped` event, sets the contract state `redeem_paused` to true, and reverts with `Error::GlobalCapExceeded`.
- **Resolution**: Only an admin can invoke `unpause_redeem` to resume operations after an investigation.
Expand Down
Loading