From 17e890fffc8af3a04f80634f601ae1b84754840a Mon Sep 17 00:00:00 2001 From: kulayddon Date: Fri, 25 Sep 2026 12:07:03 +0100 Subject: [PATCH] Update ISSUES_723_897_IMPLEMENTATION.md Closes #1184 Closes #1183 Closes #1179 Closes #1180 --- ISSUES_723_897_IMPLEMENTATION.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ISSUES_723_897_IMPLEMENTATION.md b/ISSUES_723_897_IMPLEMENTATION.md index 85a1a149..2eb8bce4 100644 --- a/ISSUES_723_897_IMPLEMENTATION.md +++ b/ISSUES_723_897_IMPLEMENTATION.md @@ -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.