# Node Network

APChain’s security and performance come from its **large-scale decentralized validator network**:

* Launches with **>1,000 validator nodes** at mainnet start and plans to expand to **50,000+ nodes globally within 3 years**, achieving cross-region fault tolerance and low latency.

### <mark style="color:orange;">**Key Features**</mark>

* **Dual staking:** Each validator must stake APX and submit real computing power (GPU/ASIC), forming a dual security model of “capital + computing power.”
* **Node ranking:** Based on combined staking + computing power scores, rewarding nodes with real contributions to network performance.
* **Global distribution:** Nodes spread across North America, Europe, and Asia for cross-timezone synchronization and rapid recovery.
* **High performance targets:**
  * TPS ≥ 10,000
  * Block time: 2s
  * Finality: 6–12s
  * Node sync latency < 1s
* **Monitoring and governance:** Nodes must periodically upload computing power proofs, which are verified by AI Oracles to prevent falsified computing claims.

This architecture ensures APChain stays **openly decentralized while offering strong computing power and high availability** for AI + Web3 applications. As the network grows, APChain will evolve into a **globally distributed supercomputing network** and become the **standard for future AI-native blockchains.**


---

# 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://apchain.gitbook.io/apchain-docs/technical-architecture/node-network.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.