> For the complete documentation index, see [llms.txt](https://kerneldao.gitbook.io/kernel/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kerneldao.gitbook.io/kernel/getting-started/kelp/security/emergency-monitoring.md).
# Emergency Monitoring
Kelp runs automated monitoring across bridge liveness on active chains, large rsETH bridge-transfers, L2 rate/price, and supply/checkpoint jobs
#### Emergency Response Playbook
In case of an incident, this is how we respond:
1. Declare the incident in the war-room and assemble responders (24/7).
2. Pause Ethereum mainnet — Pauser Safe → LRTConfig.pauseAll().
3. Pause affected L2s — Pauser Safe → pause() on each active chain.
4. If Bridge is impacted — Manager Safe → RSETH.blockUserTransfers() on the LayerZero/CCIP lockboxes and any attacker address.
5. Inform the community — suspicious txs, affected asset, what is paused, what is at risk.
6. Scenario response — asset depeg / token-control exploit / oracle-rate-bridge fault / ecosystem contagion (e.g. major DeFi protocol is compromised and we need to help stop further damage), each with a defined playbook.
7. Controlled unpause (resume) only on sign-off from the incident and security leads.
\
We are reachable 24/7 for our users and partner protocols via the official Telegram group.
---
# 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://kerneldao.gitbook.io/kernel/getting-started/kelp/security/emergency-monitoring.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.