> For the complete documentation index, see [llms.txt](https://docs.zama.org/protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zama.org/protocol/protocol-apps/governance/pausing.md).

# Pausing

Circuit breakers are deployed on all chains involved with the Zama protocol. Any operator can trigger any of these on their own to pause parts of the protocol, but a governance vote is needed to unpause again.

## Contract information

| Resource           | Link                                                                                                                                            |
| ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| Deployed addresses | [Addresses directory](/protocol/protocol-apps/addresses.md)                                                                                     |
| Source code        | [PauserSetWrapper.sol](https://github.com/zama-ai/fhevm/blob/main/protocol-contracts/contracts/pauserSetWrapper/contracts/PauserSetWrapper.sol) |

## Structure

```mermaid
flowchart
    subgraph Ethereum
        Protocol-DAO
        PauserSet-Host
        ACL-Host
        PauserSet-Wrapper
        ZAMA-ERC20
    end

    subgraph Gateway
        Gateway-Multisig
        PauserSet-Gateway
        GatewayConfig
    end

    Protocol-DAO -- owner (via ACL contract) --> PauserSet-Host
    Pauser-1..n -. member .-> PauserSet-Host

    PauserSet-Host -. defines pausers .-> ACL-Host
    PauserSet-Host -. defines pausers .-> PauserSet-Wrapper
    PauserSet-Wrapper -- pauser role --> ZAMA-ERC20

    Gateway-Multisig -- owner (via GatewayConfig contract) --> PauserSet-Gateway
    Pauser-1..n -. member .-> PauserSet-Gateway
    PauserSet-Gateway -. defines pausers .-> GatewayConfig
```

## Wallets

Each operator has their own wallet that can be used to trigger the circuit breakers. This address presents a trade-off between being readily available, for instance to anyone who’s on-call, while also being able to potentially cause significant damage if misused.

Operators are free to choose their implementation, but we suggest to use a hot wallet kept as a secret in their deployment system.

## Targets

The following components can be paused.

| Component   | Functionality                             |
| ----------- | ----------------------------------------- |
| $ZAMA token | Minting can be paused                     |
| Ethereum    | ACL updates can be paused                 |
| Gateway     | Decryption requests can be paused         |
| Gateway     | Input verification requests can be paused |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zama.org/protocol/protocol-apps/governance/pausing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.