> For the complete documentation index, see [llms.txt](https://etherfi.gitbook.io/etherfi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://etherfi.gitbook.io/etherfi/security/security-and-risks/active-defense.md). # Active Defense [ether.fi](http://ether.fi) does not rely on people watching dashboards to keep the protocol safe. The built-in controls are paired with continuous, automated monitoring and response from Hypernative, an independent security firm, so protective action can happen the moment something looks wrong rather than after a person notices. ### Always-on monitoring and automated response [Hypernative](https://www.hypernative.io/) monitors ether.fi's core contracts and bridge routes around the clock. When it detects an abnormal pattern, for example an unexpected mint or release on a bridge or an unusually large outflow, it can automatically trigger an on-chain pause. This response is set up in advance across weETH's bridge routes and core contracts, so it does not wait for a team member to be awake and at a keyboard. ### How pausing works Pausing is controlled by a dedicated role. That role is connected to the automated triggers above, and is also available to the team for manual use. A pause can fire on its own the moment a threat is detected, and the team can also pause directly. The existence of a pause role is not the same as relying on a person to push the button. ### Abnormal redemptions Outflows and redemptions are watched continuously. A sudden, abnormal spike in outflows is one of the patterns that can trigger an automatic pause, which slows activity down while the team reviews what is happening. ### Bridge limits Every route that moves weETH between chains has an automated cap on how much can move within a set time window. These limits are enforced on-chain and take effect without any human action. --- # 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://etherfi.gitbook.io/etherfi/security/security-and-risks/active-defense.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.