A smart contract audit is a comprehensive security review of a blockchain protocol's smart contract code conducted by specialised security researchers to identify vulnerabilities, logic errors, and potential exploits before the code is deployed to mainnet and handles real user funds. Audits have become a fundamental expectation for any serious DeFi protocol.
WHAT AN AUDIT COVERS
Line-by-line code review: Auditors manually read every line of smart contract code, building a mental model of how contracts interact.
Common vulnerability classes checked: Reentrancy attacks (like the DAO hack). Integer overflow/underflow. Access control flaws (missing onlyOwner checks). Oracle manipulation vulnerabilities. Flash loan attack vectors. Incorrect event emission. Front-running vulnerabilities.
Business logic errors: Even technically correct code can be economically exploitable, as auditors test economic attack vectors and game-theoretic exploits.
Automated scanning: Tools like Slither, MythX, and Echidna run automated vulnerability detection in parallel with manual review.
LEADING AUDIT FIRMST
rail of Bits: New York, US-focused. Among the most rigorous. Audited Ethereum core infrastructure.
OpenZeppelin: Developer of widely-used security libraries. High-profile DeFi audits.
Consensys Diligence: Ethereum-focused.
CertiK: High volume, transparent public reports. Some criticism of the thoroughness vs speed trade-off.
Quantstamp: Early DeFi auditor. Large portfolio.
Halborn: Specialises in blockchain-specific vulnerabilities.
AUDIT LIMITATIONS — CRITICAL UNDERSTANDING
Audits are not guarantees: Many audited protocols have been exploited. An audit is a point-in-time review; new code added after the audit may be unreviewed.
Auditors are human: Complex economic attack vectors, novel composability exploits, and subtle logic errors can be missed.
Post-audit changes: Protocols sometimes deploy slightly modified code after auditing.
Time and cost: A thorough audit costs $50,000-$500,000+ and takes weeks, creating pressure to cut corners.
VERIFYING AUDIT LEGITIMACY
Find the audit report linked directly from the protocol's official docs or GitHub. Read the report, check that findings were addressed, not just acknowledged. Cross-reference the audit firm's website to confirm the audit is listed there. Recent audits by multiple firms provide more confidence than a single old audit.