End-to-End Smart Contract Audit
summary
Live audit uses Foundry and static analysis via Slither plus a darren report to scan a 387-line flash-loan codebase. The audit shows the core claim: a flash loan succeeds if ending balance >= starting balance, so an attacker can call deposit instead of repay and later withdraw funds — a direct flash loan deposit bypass that drains liquidity. Notes: tools catch ~20% of real-world bugs, manual logic review finds the rest; proof-of-concept tests are required.
AI-written summary · about
chapters (12)
- 0:00Smart contract audits intro
- 1:06Speaker intro and overview
- 3:54Smart contract audit types
- 6:41Protocol selection for live audit
- 10:56Initial review and scoping
- 17:35Recon and documentation review
- 27:28Vulnerability identification process
- 35:43Flash loan function deep dive
- 44:35Security findings write-up
- 51:01Live audit summary and lessons
- 53:32Further learning resources
- 53:54Q&A
related talks
15mWhy Smart Contract Audit is Not Enough
33mLive Coding Session
30mSmart-Contract Security 201: Auditing Lessons for Solana Founders
01h 00mWorkshop
10mHow to Understand a Smart Contract Hack
20mDiscussion - Security, Session 8
43mOutsmarting Smart Contracts
51mA Deal with the Devil: Breaking Smart Contracts