Overview
The Security Council is a multisig composed of multiple independent parties across different timezones. It serves as the protocol’s emergency response and governance mechanism, with the authority to suspend approved withdrawers, manage roles, and replace the Allocator.Tiered Thresholds
The Security Council uses tiered thresholds to balance rapid response with governance safety:
The low suspend threshold (1-of-N) ensures rapid response to emergencies, while the high thresholds for structural changes prevent unilateral action. Restoring a suspended withdrawer is done through a role grant by the Allocator owner; any stricter threshold is an operational governance choice rather than a rule enforced by the contract itself.
Suspend Mechanism
In the current production deployment, withdrawal proof generation flows through theRelayAllocatorSpender contract, which holds APPROVED_WITHDRAWER_ROLE on the Allocator. Any single Security Council member can call suspend(address) on the Allocator to revoke this role from a specific withdrawer, including RelayAllocatorSpender.
If RelayAllocatorSpender is the only approved withdrawer, then suspending this single address is effectively a global halt for new withdrawal proofs. That is a deployment property, not an invariant enforced by the Allocator contract itself.
Scope
The Security Council cannot:- Modify the Hub ledger or create balances
- Withdraw user funds from the Depository
- Alter Oracle attestations
- Access funds held in any contract