Smart Contract Security Research: A Curated Resource List
Smart contract security is a demanding field. You need to understand Solidity, the EVM, DeFi protocols, cryptographic primitives, and how attackers think โ all at once.
This post collects the resources worth your time. Each section covers a distinct area of knowledge. Work through them in order if you are starting out, or jump to the section you need.
Solidity and the EVM
Before auditing contracts, you need to read and write Solidity well. These resources cover the language and the execution environment beneath it.
Official documentation
- Solidity Docs โ the authoritative reference for the language
- Solidity by Example โ short, focused examples of common patterns
EVM internals
- Ethereum Virtual Machine by Zaryab โ a readable series on how the EVM actually executes code
Secureum series
The Secureum substack is one of the most concentrated sources of Ethereum and Solidity knowledge available. Read these in order:
Quick reference
Foundry
Foundry is the standard toolkit for writing tests, running forks, and building proof-of-concept exploits in Solidity. If you are not using it already, start now.
- Foundry Book โ complete documentation for the toolchain
Token Standards and EIPs
Auditors spend a lot of time reviewing token contracts. Knowing the standards and their edge cases is not optional.
- Token Standards: ERC-20, 721, 777, 1155, 4626
- ERC-2981: NFT Royalty Standard
- Weird ERC-721 Tokens โ a collection of non-standard ERC-721 implementations that break naive assumptions
- Important EIPs for Auditors
Proxy Patterns and Upgradeable Contracts
Proxy contracts are a common source of vulnerabilities. The different patterns each carry different risks.
- Proxy Patterns Overview: EIPs 897, 1822, 1967, 1538, 2535
- Solidity Proxy Playground โ both vulnerable and fixed implementations to study side by side
Security Best Practices and Checklists
These resources cover what to look for during a review and how to structure your thinking.
- Security Pitfalls and Best Practices 101
- Security Pitfalls and Best Practices 201
- Solidity Security Considerations โ official guidance from the Solidity team
- Smart Contract Security Verification Standard (SCSVS) โ a structured checklist for audits
- Useful Solidity Patterns โ patterns that help avoid common mistakes
- The Solcurity Standard โ a practical security checklist from the community
- Semgrep Rules for Smart Contracts โ static analysis rules you can run on codebases
- Smart Contract Auditing Heuristics
DeFi Knowledge
Most audit targets are DeFi protocols. Understanding how they work โ AMMs, lending markets, derivatives, vaults โ is a prerequisite for finding meaningful bugs.
Finance foundations
- Khan Academy: Derivatives and Other Securities โ start here if you are not familiar with how financial instruments work
DeFi overviews
- DeFi Developer Roadmap
- Teach Yourself Crypto: DeFi Module
- Finematics DeFi Playlist โ visual explainers for major DeFi protocols
- Smart Contract Programmer DeFi Playlist
- RazzorSec DeFi Deep Dive
Vulnerabilities and Attack Vectors
This is the core of security research. Study these to understand what attackers exploit and how.
Secureum
Vulnerability databases and lists
- Solidity Security Blog by sigp
- Smart Contract Vulnerabilities
- Smart Contract Weakness Classification (SWC Registry) โ structured classification of known weaknesses
- Smart Contract Attack Vectors
- DeFiVulnLabs by SunWeb3Sec โ live, runnable PoC exploits for known vulnerabilities
- Immunefi Vulnerability Library
QuillHash collections
Additional references
Audit Reports
Reading past audit reports is one of the most effective ways to develop an eye for bugs. You see how real auditors reason, what they flag, and how they write findings.
Contest platforms
- Code4rena Reports
- Sherlock Reports
- The Auditor Book โ aggregated Sherlock and Code4rena findings
- Audit Hero โ search Code4rena and Sherlock findings together
- Solodit by Cyfrin โ filtered view of high and medium findings across contests
Bug bounty writeups
Security firms
- Consensys Diligence
- Trail of Bits (Ethereum/EVM)
- OpenZeppelin Security Audits
- Spearbit Portfolio
- QuillHash Audit Reports
Solo auditor portfolios
These are worth reading to see how individual auditors present their work:
Lists and directories
- Blockchain Security Audit List โ firms and solo auditors
- Bridge Hack List
Secureum SAFU Series
A focused set of posts analyzing the security of specific DeFi protocols:
- Eth2 Security Overview
- Smart Contract Security Resources
- Making DeFi SAFU
- Making Hermez SAFU
- Making Cover SAFU
- Making Opyn SAFU
- Smart Contract Security 101
- Making Primitive SAFU
- Making Alpha SAFU
CTFs and Hands-On Practice
Reading about vulnerabilities is not enough. You need to exploit them yourself. These CTFs give you practice in a structured environment.
- Ethernaut โ the classic starting point for smart contract security challenges
- Capture the Ether
- Damn Vulnerable DeFi โ DeFi-specific challenges, progressively harder
- Paradigm CTF
After completing a challenge, read other players' writeups. The same vulnerability can often be exploited in multiple ways, and seeing different approaches sharpens your thinking.
Contest Practice
Once you have finished the CTFs, first-flight contests are a low-stakes way to practice writing findings on real (if simpler) codebases.
Writing Proof of Concept Exploits
A finding without a working PoC is weak. These resources cover how to build them properly.
Postmortems and Bug Fix Analysis
Studying how protocols responded to real exploits teaches you what auditors missed and why. This is underrated as a learning method.
Where to Start
If you are new to smart contract security, a reasonable progression is:
- Learn Solidity basics using Solidity by Example and the Secureum 101 posts
- Understand the EVM at a basic level before going deeper
- Work through Ethernaut, then Damn Vulnerable DeFi
- Read 10 to 20 high-severity findings on Solodit and understand each one
- Participate in a CodeHawks First Flight contest
- Expand your DeFi knowledge in parallel with your security knowledge
The two skills reinforce each other. The better you understand how a protocol is supposed to work, the easier it is to see where it breaks.