# Symbiosis Relayers Network: Emergencies

## MPC Group Inefficiency

<table><thead><tr><th width="230">Q</th><th>A</th></tr></thead><tbody><tr><td>What does it look like?</td><td>The relayers network stops to proceed oracle requests for all blockchains.</td></tr><tr><td>How do we notice it?</td><td>Alerts</td></tr><tr><td>What may be a cause?</td><td><ul><li>There are not enough relayers to compose TSS signatures.</li><li>The leader of the MPC group is offline.</li></ul></td></tr><tr><td>How do we solve this?</td><td><ol><li>Ban offline relayers in the Staking contract,</li><li>Initiate epoch change.</li></ol></td></tr></tbody></table>

## Epoch Change Failure

Once epoch change is triggered, the following stages should be completed:

1. Epoch change preparation. This stage includes:
   1. Formation of a new MPC group,
   2. Generation of a new MPC key,
   3. Approval of the epoch change by holders of 2/3 of the total stake.
2. Epoch change in the Staking contract.
3. Epoch change in BridgeV2 contracts.

On each stage an emergency can happen.

### **New MPC group formation failure**

<table><thead><tr><th width="253">Q</th><th>A</th></tr></thead><tbody><tr><td>What does it look like?</td><td>Relayers cannot generate a new MPC key.</td></tr><tr><td>What may be a cause?</td><td><ul><li>Many relayers are offline, and the rest are not enough to form a new MPC group.</li><li>The leader of the MPC group is offline.</li></ul></td></tr><tr><td>How do we solve this?</td><td><ol><li>Ban offline relayers in the Staking contract,</li><li>Set the MPC group size to a smaller value,</li><li>Initiate epoch change one more time.</li></ol></td></tr></tbody></table>

### **Epoch change failure in the Staking contract**

<table><thead><tr><th width="254">Q</th><th>A</th></tr></thead><tbody><tr><td>What does it look like?</td><td>Relayers cannot save a new MPC address in the Staking contract.</td></tr><tr><td>What may be a cause?</td><td>Many relayers are offline, and the rest cannot provide enough signatures for epoch change.</td></tr><tr><td>How do we solve this?</td><td>Save the new MPC address manually.</td></tr><tr><td></td><td></td></tr></tbody></table>

### **MPC address change failure in the BridgeV2 contract(s)**

| Q                       | A                                                                                          |
| ----------------------- | ------------------------------------------------------------------------------------------ |
| What does it look like? | The relayers network does not proceed oracle requests for a particular blockchain.         |
| How do we notice it?    | Alerts                                                                                     |
| What may be a cause?    | There are not enough relayers to compose a proper TSS signature to change the MPC address. |
| How do we solve this?   | Replace the MPC address with a new one manually.                                           |


---

# Agent Instructions: 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:

```
GET https://docs.symbiosis.finance/relayers-network/symbiosis-relayers-network-emergencies.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.