# 审计师上手

## 30 秒概览

* **27 合约 in scope** (audit RFP §3)
* **905 forge tests, 75.75% branch coverage**
* **0 round prior audit** (this is the first)
* **预算 envelope: $80-100K** (单家)
* **推荐周期: 4-6 周 audit + 30-90 天 fix**

## 9 文档送审包

[审计送审包总览](/consolidated-resources/audit-prep-package.md)

直接 clone repo 看：

```bash
git clone https://github.com/leeleeEcho/babyDriver_Layer2.git --depth 1
cd babyDriver_Layer2/docs/audit
ls
```

## 推荐 audit 工时分配

按 STRIDE × 子系统分析（[Threat Model §9](/security/threat-model-stride.md)）:

| 子系统                     | 推荐工时         |
| ----------------------- | ------------ |
| PoB / Stake / Challenge | 60-80h       |
| PoD / 3 Verifier        | 50-70h       |
| L2 Policy               | 20-30h       |
| CSDRT / DID             | 40-60h       |
| Oracle / Bridge         | 80-120h      |
| Cross-system            | 30-40h       |
| **总计**                  | **280-400h** |

## 已修 / 已知 finding

* **HIGH**: ChallengeManager.resolveExpired CEI (commit `7a1c8b5`)
* 7 immutable state vars (commit `70fcce0`)
* 11 dependency CVE (commit `f57c7da`)
* 18 branch arm uncovered (详见 [coverage gap](https://github.com/leeleeEcho/babyDriver_Layer2/blob/main/docs/audit/coverage-gap-analysis-2026-05-07.md))
* \~30 false-positive 已注解（pre-audit-self-review）

## 联系

* 详见 [audit outreach email template](https://github.com/leeleeEcho/babyDriver_Layer2/blob/main/docs/guides/audit-outreach-email-template-2026-04-30.md)
* Repo: github.com/leeleeEcho/babyDriver\_Layer2
* 基线 commit: `7c438db`


---

# 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/getting-started/for-auditors.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.