You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This PR is among the additional scope to be reviewed.
Reserve attempts to introduce a new functionality that allows governance to forcibly settle an auction, in the case of, say a censorship.
This imo has been sufficiently done.
After going through all 6 modified files we have a new supported method and the governance can achieve this by querying the newly implemented forceSettleTrade()
+ // === Governance ===+ /// Forcibly settle a trade, losing all value+ /// Should only be called in case of censorship+ /// @param trade The trade address itself+ /// @custom:governance+ function forceSettleTrade(ITrade trade) public virtual governance {+ // should not call any ERC20 functions, in case bricked++ IERC20Metadata sell = trade.sell();+ delete trades[sell];+ tradesOpen--;+ emit TradeSettled(trade, sell, trade.buy(), 0, 0);+ }
The text was updated successfully, but these errors were encountered:
Lines of code
Vulnerability details
See:
Pull Request
This PR is among the additional scope to be reviewed.
Reserve attempts to introduce a new functionality that allows governance to forcibly settle an auction, in the case of, say a censorship.
This imo has been sufficiently done.
After going through all 6 modified files we have a new supported method and the governance can achieve this by querying the newly implemented
forceSettleTrade()
The text was updated successfully, but these errors were encountered: