> For the complete documentation index, see [llms.txt](https://x1ecochain.gitbook.io/x1-ecochain-tech-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://x1ecochain.gitbook.io/x1-ecochain-tech-whitepaper/consensus-and-validator-system/finality-model.md).

# Finality Model

#### **Fast Finality Feature**

X1 EcoChain implements a dual-layer finality mechanism combining Economic Finality and Probabilistic Finality to ensure transaction security and network efficiency. Fast finality enables near-instantaneous transaction confirmation, significantly reducing the time required for transaction settlement compared to traditional blockchain networks. The Fast Finality feature, introduced through [BEP-126](https://github.com/bnb-chain/BEPs/blob/master/BEPs/BEP126.md), enables Economic Finality using a slashing mechanism similar to Casper FFG and Tendermint.

#### **Key Benefits:**

* **Rapid Confirmation:** Transactions achieve finality within seconds rather than minutes
* **Enhanced User Experience:** Reduced waiting times for transaction confirmations
* **Improved DApp Performance:** Applications can respond faster to user interactions
* **Lower Risk:** Reduced exposure to chain reorganizations and double-spending attacks

#### Technical Implementation:

The fast finality mechanism works by having validators reach consensus on block finality through **a Byzantine Fault Tolerant (BFT) process**. Once a supermajority of validators confirm a block, it becomes irreversible, providing immediate transaction finality.

This approach combines the speed and efficiency of **PoN consensus** with the security guarantees of fast finality, making it ideal for applications requiring quick settlement times and high throughput.

#### **Fallback Mechanism**

When **fast finality** is unavailable, BSC falls back to **probabilistic finality**. Security increases as more blocks are added – the deeper a block is buried, the lower the probability of reversal.

**Network Parameters:**

* **Turn Length:** 8 (consecutive blocks per validator)
* **ValidatorSize:** 3 (total active validators)
* **Block Time:** \~3 seconds

**Finality Requirements:**

* **Majority (>½) validator confirmations:** 16 blocks (2 × 8) ≈ 48 seconds
* **Supermajority (>⅔) validator confirmations:** 72 blocks (3 × 8) ≈ 216 seconds

This dual-layer approach ensures network security and finality guarantees even when Fast Finality encounters issues.


---

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

```
GET https://x1ecochain.gitbook.io/x1-ecochain-tech-whitepaper/consensus-and-validator-system/finality-model.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.