TLDR
- Quorum Freeze lets Stellar validators freeze risky accounts without stopping the chain or shipping code.
- CAP-77 records freeze actions onchain, so observers can review affected accounts and timing clearly later.
- Validators must reach quorum consensus before any CAP-77 freeze can take effect across Stellar network.
- Authorized recovery transactions can move returned funds while a freeze stays active on attacker accounts.
- Institutions may see CAP-77 as a clearer emergency process for tokenized value on Stellar network rails.
Stellar’s CAP-77 proposal introduces Quorum Freeze, an onchain incident response tool for the Stellar network. It allows validators to freeze accounts, contract data, or asset balances through consensus.
The proposal presents a governed method for emergencies, rather than relying on rushed off-chain action. It also keeps freeze records in the ledger, so observers can review the process.
CAP-77 Creates an Onchain Freeze Process
CAP-77 gives Stellar validators a way to quarantine selected accounts or balances during network incidents. The process does not require a chain halt or emergency software release.
The freeze command would move through Stellar’s standard validator consensus process. A quorum of validators must agree before any action takes effect.
The mechanism is also reversible, according to the proposal. That means validators can later remove a freeze through the same governed process.
CAP-77 also supports authorized recovery transactions under limited conditions. For example, a negotiated fund return could occur while the freeze remains active.
Recent Exploits Add Context for the Proposal
The CAP-77 discussion points to recent crypto attacks as context for the proposal. It cites the Balancer V2 exploit on November 3, 2025.
That incident reportedly moved more than $120 million across nine blockchain networks. Responses differed by chain, and many actions happened outside protocol rules.
The proposal also refers to a reported $280 million-plus Drift Protocol exploit on Solana. It says the response relied on off-chain coordination and improvised steps.
These cases raise questions around “how fast networks can respond” and “who can authorize emergency action.” CAP-77 seeks to answer those questions inside Stellar’s governance process.
Stellar Validators Would Govern the Response
Stellar uses the Stellar Consensus Protocol, also known as SCP. The model relies on federated trust and public validator relationships.
Under CAP-77, validators would use that structure to approve a freeze. The proposal says the same process governs protocol changes and network settings.
This design makes the action visible in ledger state. Any observer could check what was frozen, when it happened, and how it changed later.
Supporters describe the tool as “Quorum Freeze” because a validator quorum must approve it. The name refers to the process, not a single actor.
Institutions Get a Clearer Emergency Framework
Banks, custodians, payment firms, and funds often need defined control processes. They also need records that support audits and compliance reviews.
CAP-77 aims to give those users a clearer path during major incidents. It offers a formal method for freezes, reversals, and controlled recovery actions.
The proposal does not remove the need for careful governance. Validators would still need shared rules for when a freeze is justified.
That question remains central to future use of Quorum Freeze. The framework depends on transparent standards, validator agreement, and public ledger records.
CAP-77 adds Quorum Freeze to Stellar L1 giving validators an onchain method to freeze accounts, data, and balances through consensus voting.





