# PoC 状态声明

## 真 vs mock vs 占位 全清单

### 真实有效（chain 391 LIVE 可独立验证）

* **PoB 行为记录**：33 合约真部署，905 forge tests 全过
* **Fraud-proof e2e**：真 slash 0.5 ETH，commit `023f7aa`
* **L2 OPA SDK e2e**：3 case 全绿
* **Challenger Rust daemon**：chain 391 真链 soak 0 false-positive
* **G3 稳定性 30-min soak**：100% uptime, p50=749ms
* **Cross-language byte-pin**：12 个 keccak literal 强制对齐
* **EcdsaInferenceVerifier**：真 OpenZeppelin ECDSA 验签
* **Groth16PoBVerifier**：真 snarkjs 生成
* **OracleHub**：system contract slot 真注入

### Mock — 必须在主网前 swap

| 组件                         | mock 行为                      | swap 计划               |
| -------------------------- | ---------------------------- | --------------------- |
| **MockHalo2Verifier**      | 接受任何 zkML proof              | EZKL roadmap 6 周      |
| **MockDcapVerifier**       | 接受任何 TEE quote               | DCAP 真 verifier 3-4 周 |
| **baby-explanation crate** | deterministic stub explainer | 真 SLM 微调 4-8 周        |

### 占位 — 还没设计

* **Token economics**：无设计
* **法律实体**：无注册
* **Bug bounty**：无 program
* **多节点 sequencer**：单 anvil-zksync
* **真 ZK Rollup prover**：G1-blocked

详见 [非主网就绪](/legal-and-disclaimers/not-mainnet-ready.md)。

## 不要做的事

* 把 chain 391 当真实生产环境使用
* 用 PoC anvil rich 账户私钥到任何主网
* 把"链上 EU AI Act hash"等同于"法律 sign-off"
* 假设 mock verifier 会拒绝伪造证明（mock 全是 permissive）

## 可以做的事

* 学术 / 论文引用 PoC 完整度
* 黑客松 / hackathon demo
* Audit firm pitch（proof-of-work）
* Investor pitch（seed → A round）
* Partner technical preview


---

# 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://yellowpaper.axblade.io/about-axblade/poc-status-disclaimer.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.