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.