SMART CONTRACT AUDIT: REQUEST FOR PROPOSAL

1. PROJECT OVERVIEW
Project name: [Name]
What it does (2–3 sentences, plain English): [e.g. "A fixed-rate lending
protocol. Users deposit collateral and borrow at a rate fixed at the time
of the loan."]
Chain(s) / network(s): [e.g. Base, Ethereum mainnet]
Stage: [Pre-launch / live with $X TVL / upgrade to a live protocol]
Website / docs: [Links]
Contact: [Name, role, Telegram or email]

2. CODE AND SCOPE
Repository: [Link. Private repos: access granted after NDA or on request]
Commit hash to audit: [Full hash. Code is frozen at this commit.]
Language and version: [e.g. Solidity 0.8.26, Foundry]
Total in-scope size: [X nSLOC]

In scope:
  [path/to/Contract1.sol]   [nSLOC]
  [path/to/Contract2.sol]   [nSLOC]
  [...]

Out of scope:
  [e.g. unmodified OpenZeppelin libraries, test files, deploy scripts,
  token contract audited by [Firm] in [Month Year]]

If this is a fork or an upgrade: [What the original is, exactly what changed,
link to the diff]

3. ARCHITECTURE AND TRUST ASSUMPTIONS
How the contracts fit together: [Short description or link to a diagram]
Privileged roles and what each can do: [e.g. Owner (3/5 multisig): set fees,
pause. Keeper bot: trigger liquidations.]
Upgradeability: [None / proxy pattern + who controls upgrades + timelock]
External dependencies: [Oracles, bridges, DEXs, other protocols, and what
happens if one misbehaves]
Tokens supported: [Any ERC-20? Allow-list? Fee-on-transfer or rebasing
tokens supported or not?]

4. WHAT MUST ALWAYS BE TRUE (INVARIANTS)
[e.g. "Total deposits always equal the sum of user balances."]
[e.g. "Only the timelock can change the interest-rate model."]
[e.g. "A healthy position can never be liquidated."]

5. KNOWN ISSUES AND PRIOR WORK
Previous audits: [Firm, date, scope, link to report, or "None"]
Known issues / accepted risks: [List them so firms don't report them again]
Areas we're most worried about: [e.g. liquidation edge cases, oracle
manipulation, rounding]

6. TESTING AND TOOLING
Test coverage: [e.g. 92% line coverage, Foundry]
Fuzz / invariant tests: [Yes/No, where]
Static analysis run: [e.g. Slither and Aderyn, findings addressed]
How to build and run tests: [Commands]

7. SERVICES REQUESTED
[ ] Manual security review
[ ] Fuzzing / invariant testing by the auditor
[ ] Formal verification of: [specific properties]
[ ] Economic / mechanism review
[ ] Fix review (please state how many rounds are included)
[ ] Other: [e.g. frontend or infrastructure penetration test]

8. TIMELINE
Proposal deadline: [Date. We recommend at least 5 days from sending]
Target audit start: [Date or window]
Target report date: [Date]
Planned launch: [Date, if any]
Fix window: [How long you'll need to fix findings before the fix review]

9. BUDGET (OPTIONAL)
[Range or ceiling, or "Open: quote on scope"]

10. CONFIDENTIALITY
NDA required before code access: [Yes/No. Attach NDA]
Can the final report be published? [Yes / No / after launch]

11. WHAT EVERY PROPOSAL MUST INCLUDE
Please answer every point, in this order:
  a. Fixed price (USD) and payment terms
  b. Reviewer-days (number of engineers × days)
  c. Named reviewers, their roles and relevant experience
  d. Relevant audits in the last 24 months (protocol type, language, links)
  e. Methodology: manual, tooling, fuzzing, formal methods
  f. Fix review: rounds included, and the cost of extra rounds
  g. Earliest start date and report delivery date
  h. Report format and severity classification used
  i. Anything you think is missing from this scope

12. HOW WE'LL CHOOSE
Proposals will be compared on:
  - Relevant experience with this type of protocol and language: [X]%
  - Review team (seniority, named, availability): [X]%
  - Review effort and methodology: [X]%
  - Fix review and post-audit support: [X]%
  - Price: [X]%
  - Timeline fit: [X]%
We aim to decide within [X] days of the proposal deadline.
