> For the complete documentation index, see [llms.txt](https://balancer.gitbook.io/balancer-v2/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://balancer.gitbook.io/balancer-v2/security/emergency-pause.md). # Emergency Pause The Balancer V2 Vault and WeightedPool contracts have an emergency pause mechanism which can be activated within the first three months of mainnet operation. After three months, the mechanism cannot be activated by anyone, including the Balancer Governance Multisig and Balancer Labs. After three months, Balancer V2 becomes unstoppable. The emergency pause is only meant to be activated in the event of a serious vulnerability being discovered which puts user funds at risk. During the pause, all trading is halted and liquidity can no longer be *added* to the Vault, but **liquidity can always be removed by users**, even while the protocol is paused. Pausing does not grant anyone, including the Balancer Governance Multisig or Balancer Labs, direct access to user funds. It simply creates a safe environment in which funds can be withdrawn and any potential attack on the protocol can be mitigated. By default, at deployment time, the Balancer Governance Multisig was the only entity with the authority to activate the emergency pause. But in the week immediately following the initial deployment, [Balancer governors voted to also grant this same authority to an EOA (Externally Owned Address) controlled by Balancer Labs.](https://vote.balancer.fi/#/proposal/Qma3oK8Ltq6YqLvh4xBc359LvYpkQ3b6kxhTCVMnDkHb1M) There is some concern that the Multisig may not be able to coordinate quickly enough during an emergency situation, so this EOA address is controlled by a handful of stakeholders at Balancer Labs and Balancer Maxis across different time zones to ensure quick response time to potential emergencies. Again, to be clear, this address has no control over user funds and can only pause the system to protect funds from being drained (and only within the first three months). {% hint style="info" %} The emergency pause period ended on July 18, 2021. The Vault and WeightedPools are now immutable. {% endhint %} While the Balancer V2 Vault and WeightedPool can not be paused anymore, new deployments of the Vault for other networks and pools deployed from new factories can be subject to emergency pause. After the following [proposal](https://vote.balancer.fi/#/proposal/0x63fab7ab9ef5b9579dabb82058b8ea309e39c766d435438b55fff8db7c1f69fd), the [Emergency subDAO ](/balancer-v2/ecosystem/governance/emergency-subdao.md)has been granted the role to operate the emergency pause. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://balancer.gitbook.io/balancer-v2/security/emergency-pause.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.