What an audit actually examines, how to read a report, and why a clean audit is not a security guarantee.
A bug report in Web3 is a structured submission that describes a discovered vulnerability, logic flaw, or defect in a smart contract or protocol. Unlike traditional software bug reports that track feature requests and minor issues, Web3 bug reports often describe conditions that could lead to fund losses — and are typically submitted through formal bug bounty programs or responsible disclosure channels.
Anatomy of a Web3 Bug Report
Essential Components
- Severity level: Critical, high, medium, low, or informational
- Vulnerability type: Reentrancy, oracle manipulation, access control, etc.
- Description: Clear explanation of the issue and what goes wrong
- Proof of Concept (PoC): Code or transaction demonstrating the exploit
- Impact: What an attacker could achieve (funds at risk, protocol damage)
- Mitigation: Suggested fix or workaround
Severity Classification
| Severity | Impact | Example | Typical Bounty |
|---|
| Critical | Funds can be stolen | Reentrancy in withdrawal | $50K–$1M+ |
| High | Protocol manipulation | Oracle price manipulation | $10K–$100K |
| Medium | Limited fund risk | Griefing attack, DoS | $2K–$25K |
| Low | Minor issues | Gas optimization, edge case | $500–$5K |
|
Where to Submit Bug Reports
- Immunefi: The largest Web3 bug bounty platform, covers major protocols
- Sherlock: Audit contests and ongoing bounties for DeFi protocols
- Code4rena: Competitive audit contests with prize pools
- Hats Finance: Decentralized bug bounty protocol
- Direct disclosure: Many protocols have security@ email or dedicated channels
Responsible Disclosure Process
- Report privately through the protocol's designated channel
- Do not exploit the vulnerability or disclose it publicly
- Allow the team reasonable time to fix the issue
- Coordinate public disclosure after the fix is deployed
- Receive bounty payment after verification
Writing an Effective Bug Report
Do
- Include a minimal, reproducible PoC — the easier to reproduce, the faster the triage
- State the exact contracts and functions affected
- Quantify the impact: how much value is at risk
- Suggest a specific code fix when possible
- Test your PoC on a forked mainnet before submitting
Don't
- Submit theoretical issues without proof of exploitability
- Publicly disclose before the team has fixed the vulnerability
- Demand immediate payment before the team has verified the finding
- Submit duplicates — check existing reports first
- Exaggerate severity — honest assessment builds reputation
Bug Report vs. Audit Finding
| Aspect | Bug Report | Audit Finding |
|---|
| Discovery context | Independent researcher | Hired auditing firm |
| Timing | Any time, often post-launch | Pre-launch, scheduled |
| Compensation | Bounty (variable) | Fixed fee (already paid) |
| Relationship | Arms-length | Contracted, collaborative |
| Scope | Anything the researcher finds | Defined scope in engagement |
Why It Matters
Bug reports are the backbone of Web3's distributed security model. Unlike traditional software where a security team handles everything, Web3 relies on a global network of independent researchers to find and report vulnerabilities before malicious actors exploit them. For security researchers, writing clear, impactful bug reports is a career — top hunters earn millions annually. For protocols, a healthy bug report pipeline is cheaper and more effective than any single audit. For the ecosystem, responsible disclosure through bug reports prevents exploits that would damage trust in the entire space.