# Challenge Approval

The final steps of the Challenge Process focus on **consensus** among **Validating Nodes (VNs)** to determine whether the challenge is valid and should move further. The image bellow illustrates the decision point where 5 VNs must agree to raise the same challenge for it to proceed. 

<figure><img src="https://651401021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FY2TowO8fF4a1GlgpRfIZ%2Fuploads%2FOegatKuq8twdcWJgJpYZ%2Fimage.png?alt=media&#x26;token=2eed7d3f-d336-4b48-a8c7-87736a2fd5e0" alt=""><figcaption><p>Challenge Approval</p></figcaption></figure>

## **5 VN Consensus**

Once a VN raises a challenge, the system requires at least **5 VNs** to raise the **same challenge** for it to proceed further. This rule ensures that challenges are not raised based on the opinion of a single VN, but rather based on **collective agreement** from multiple independent validators.

**If fewer than 5 VNs** raise the same challenge:

* The challenge remains **pending**. This means the process pauses, waiting for additional VNs to support the challenge. If the required 5 VNs do not raise the same challenge, it does not proceed further.

**If 5 or more VNs** raise the same challenge:

* The challenge **moves forward**. The process continues into the next phase, where the challenge is reviewed in-depth by all other VNs.

The requirement for **at least 5 VNs** to raise the same challenge is designed to **avoid congestion** and prevent **single points of failure** in the system. If a single VN or a small group could initiate challenges on their own, it could lead to an overload of unnecessary challenges, congesting the system and slowing down the validation process.