# Dual-Staking Logic

One of APChain’s core innovations is the introduction of the **Physical Proof-of-Stake (Physical PoS)** mechanism, which extends the traditional **Proof-of-Stake (PoS)** consensus model by deeply binding **on-chain security with real-world computing resources**.

This ensures that the blockchain not only maintains **high security**, but also provides **sustainable support for AI and high-performance computing tasks**.

### <mark style="color:orange;">Dual-Staking Logic</mark>

In APChain, nodes must meet **two staking requirements** to qualify as validators:

### <mark style="color:orange;">**Token Staking (APX)**</mark>

* Nodes must stake a certain amount of APX as their base collateral.
* Staked APX secures the network and protects against malicious behaviors (such as chain forks or double-spending attacks).

### <mark style="color:orange;">**Computing Power Staking (GPU/ASIC/Specialized Chips)**</mark>

* Nodes must connect hardware such as GPUs, ASICs, or NPUs and verify their computing capacity on-chain via the system’s benchmarking tools.
* Computing power metrics are included in the node scoring system and combined with APX stake weight to determine the final validator ranking.

***

This **dual-staking model** goes beyond traditional PoS systems that rely solely on token quantity, avoiding the **“capital dominance” problem** and tightly **linking real computing power with the on-chain economy**.


---

# 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/physical-pos-computing-mechanism/editor.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.