# Trust Assumptions 信任假设

完整版本见仓库内：

[`docs/audit/trust-assumptions-2026-05-07.md`](https://github.com/leeleeEcho/babyDriver_Layer2/blob/main/docs/audit/trust-assumptions-2026-05-07.md)

## 5 大类信任假设速览

### 1. 链级

* Ethereum L1 共识不发生 51%
* L2 sequencer 不审查 / 不 withhold batch (PoC 单点 anvil-zksync, 主网需多节点)
* ZK Prover 服务可用 (PoC 不存在, 主网必备)

### 2. 角色 / 权限

* DEFAULT\_ADMIN\_ROLE 为项目方 multisig (PoC 单 key, 主网 4/7 hardware wallet + 24h Timelock)
* GUARDIAN\_ROLE 为独立安全响应小组 (PoC 无, 主网 2/3 multisig + emergencyWithdraw 硬编码 receiver)
* Aggregator 已抵押 ≥ MIN\_STAKE
* Challenger bond + 7 天 window 经济抑制 spam
* Inference Attestor 私钥入 HSM (PoC 裸放, 主网 KMS / TEE)
* TEE Attestor: Intel/AMD root key 不泄漏 (PoC mock DCAP, 主网真 verifier)
* ZkmlCircuitPublisher 注册 verifier 合约 (PoC permissionless, 主网建议 governance)
* Oracle Operator multi-source 推送 (PoC single source, 主网 ≥ 3 source)
* Treasury 是简单 receiver 不会 reentrancy (CEI 已修)
* Spec / Policy Publisher (Permissionless register, consumer 自己选 trusted)

### 3. 链下基础设施

* RPC (Alchemy / Infura) 不审查
* IPFS / Arweave content 可达
* GitHub repo 公开可验

### 4. 密码学

* keccak256 抗碰撞
* ECDSA secp256k1 私钥保密
* Groth16 trusted setup ceremony 无人作弊
* BN254 \~110-bit security (主网评估 BLS12-381 swap)
* Halo2 KZG SRS 来自可信源
* ECDSA EIP-191 chain ID 绑定防 cross-chain replay

### 5. 业务流程

* Aggregator → Agent: 链上不验证 agent 真实性 (高保证用 zkML / TEE)
* PolicyRegistry → 法律: 链上不验证法律有效性 (链下背书)
* Explanation → SLM: 链上不验证 SLM 推理 (链下用 D2 TEE)

## 主网前必须新增的 7 项

按 [Trust Assumptions §7](https://github.com/leeleeEcho/babyDriver_Layer2/blob/main/docs/audit/trust-assumptions-2026-05-07.md#7-主网前必须新增的-trust-缓解):

1. T-3mo: Gnosis Safe 4/7 hardware wallets + Timelock 24h
2. T-3mo: Guardian 多签 + emergencyWithdraw 硬编码 receiver
3. T-2mo: Oracle ≥ 3-source aggregation + circuit breaker
4. T-2mo: 真 DCAP verifier swap (替换 MockDcapVerifier)
5. T-2mo: 真 EZKL Halo2 verifier swap (替换 MockHalo2Verifier)
6. T-1mo: 完整 incident response runbook + on-call
7. T-1mo: Bug bounty live (Immunefi)


---

# 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/security/trust-assumptions.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.