# Emergency Mode

### Overview

> ***The Emergency Consensus System is a fault-tolerance mechanism designed for BSC-based blockchain networks that enables automatic failover from master validator nodes to mini-validator nodes during network disruptions. The system ensures continuous blockchain operation by dynamically reassigning validation responsibilities when primary infrastructure becomes unavailable.***

***

### System Architecture

#### Normal Operation Mode

**In standard operation, the network operates with a two-tier validation structure:**

**Master Nodes: Primary validators responsible for block validation and consensus mechanisms Mini-Validators: Secondary nodes that contribute transaction signing operations to the blockchain**

* **Master Nodes**: Primary validators responsible for block validation and consensus mechanisms
* **Mini-Validators**: Secondary nodes that contribute transaction signing operations to the blockchain

#### Emergency Operation Mode

When master nodes become unavailable, the system automatically transitions mini-validators into full validation roles, maintaining network consensus and block production capabilities.

### Core Components:

{% hint style="info" %}

#### Master Node Monitoring

Continuous health monitoring system that tracks master node availability and network participation. The monitoring mechanism detects when master nodes fail to participate in consensus rounds or become unresponsive.
{% endhint %}

{% hint style="info" %}

#### Automatic Role Transition

Smart contract-based role management system that handles the automatic promotion of mini-validators to full validator status during emergency conditions. The transition process includes validation authority transfer and consensus parameter adjustments.
{% endhint %}

{% hint style="info" %}

#### Consensus Continuity Engine

Maintains blockchain operation during the transition period by ensuring mini-validators can seamlessly assume validation responsibilities without network interruption or block production delays.
{% endhint %}

{% hint style="info" %}

#### Recovery Protocol

Automated detection and restoration mechanism that identifies when master nodes return online and orchestrates the transition back to normal operation mode, demoting mini-validators to their original signing roles.
{% endhint %}

### Operational States:

{% hint style="info" %}

#### Detection Phase

System continuously monitors master node status and network health metrics to identify potential emergency conditions requiring mode transition.
{% endhint %}

{% hint style="info" %}

#### Emergency Activation

Upon detecting master node unavailability, the system initiates emergency protocols, promoting mini-validators and adjusting network parameters for continued operation.
{% endhint %}

{% hint style="info" %}

#### Emergency Operation

Mini-validators assume full validation responsibilities, maintaining consensus mechanisms and block production while master nodes remain offline.
{% endhint %}

{% hint style="info" %}

#### Recovery Transition

When master nodes return online, the system validates their operational status and initiates controlled transition back to normal operation mode.
{% endhint %}

{% hint style="info" %}

#### Normal Restoration

Master nodes resume primary validation duties while mini-validators return to their original transaction signing functions.
{% endhint %}

***

#### Key Features:

* **Zero-downtime failover**: Seamless transition between operational modes without network interruption
* **Automatic detection**: No manual intervention required for mode transitions
* **Consensus preservation**: Maintains blockchain integrity throughout emergency operations
* **Dynamic role management**: Smart contract-controlled validator role assignments
* **Recovery automation**: Automatic restoration to normal operations when master nodes return


---

# 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://x1ecochain.gitbook.io/x1-ecochain-tech-whitepaper/consensus-and-validator-system/emergency-mode.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.