References — Web3 Security Mastery

Curated primary sources organized by topic. Prefer primary over secondary. [verify] marks items that may have changed since 2026-05. Date column = last verified or publication date. “Current” / “Historical” indicates whether the resource still reflects best practice.


How to use this list

  • Reading priority: items in bold are required for the topic; the rest are deep-dive.
  • Primary source = official spec, official docs, audit firm publication, or original post-mortem from the affected team.
  • Secondary source = community summary; use only when primary is unavailable.
  • Verify-at-study-time: tooling versions, EIP statuses, and L2 implementation details move fast. Always cross-check with the project’s GitHub main branch.

1. Official Documentation (always start here)

SourceURLStatusWhy credible
Ethereum.org Developer Docshttps://ethereum.org/en/developers/docs/CurrentOfficial Ethereum Foundation educational material
Solidity Documentationhttps://docs.soliditylang.org/CurrentOfficial language reference (check version selector for your target compiler)
Solidity Security Considerationshttps://docs.soliditylang.org/en/latest/security-considerations.htmlCurrentCompiler maintainers’ own list of foot-guns
Ethereum Yellow Paperhttps://ethereum.github.io/yellowpaper/paper.pdfCurrent (revised)Formal specification of EVM semantics; dense but authoritative
Ethereum Execution Specshttps://github.com/ethereum/execution-specsCurrentPython reference implementation of execution layer
EIPs Indexhttps://eips.ethereum.org/CurrentCanonical EIP registry; check status (Draft/Review/Final/Stagnant)
EVM Opcodes Referencehttps://www.evm.codes/CurrentInteractive opcode + gas reference; community-maintained but accurate
OpenZeppelin Contractshttps://docs.openzeppelin.com/contractsCurrentDe-facto secure-implementation library

2. Audit Firm Publications

Trail of Bits

ResourceURLNotes
Building Secure Contractshttps://github.com/crytic/building-secure-contractsSlither/Echidna-centric secure-dev guide; high-quality
Trail of Bits bloghttps://blog.trailofbits.com/Filter by tag/blockchain
Publications repohttps://github.com/trailofbits/publicationsPublic audit reports
Algo VM Security guidehttps://github.com/crytic/algo-vm-securityNon-EVM angle

ConsenSys Diligence

ResourceURLNotes
Smart Contract Best Practiceshttps://consensys.github.io/smart-contract-best-practices/Long-standing community resource
Diligence auditshttps://consensys.io/diligence/auditsPublic audit catalog
Diligence researchhttps://consensys.io/diligence/researchTooling and methodology posts

OpenZeppelin

ResourceURLNotes
OpenZeppelin blog (Security)https://blog.openzeppelin.com/security-auditsAudit summaries; deep technical write-ups
Ethernauthttps://ethernaut.openzeppelin.com/Browser-based Solidity wargame; required Week 5 lab

Spearbit / Cantina

ResourceURLNotes
Spearbit portfoliohttps://spearbit.com/portfolioPublic audit reports
Cantina platformhttps://cantina.xyz/Audit competitions + private audits

ChainSecurity / Sigma Prime / Halborn / Zellic / Macro / Asymmetric / Code4rena Zenith

Each maintains a public audit portfolio. Check their site directly; report quality varies, but their flagship engagements (e.g., ChainSecurity on Lido, Sigma Prime on Lighthouse) are gold standard.


3. Standards & EIPs (the ones auditors must know cold)

Core

EIPTitleNotes
EIP-20ERC-20 Token StandardOriginal; transfer return-value optional in some implementations — major footgun
EIP-721NFT StandardSafe-transfer callback hazard
EIP-1155Multi-Token StandardCallback hazard in batched transfers
EIP-4626Tokenized VaultInflation attack; share/asset rounding direction
EIP-777Token w/ Send-HooksReentrancy vector; mostly historical, but used in some legacy tokens
EIP-2612permit() for ERC-20Signature replay angle
Permit2Uniswap unified approvalNot an EIP but a deployed contract; widely integrated

Infrastructure

EIPTitleNotes
EIP-1559Fee marketBase fee + priority fee; affects MEV economics
EIP-4844Proto-Danksharding (blobs)L2 data-availability cost dropper
EIP-1967Proxy storage slotsCanonical slots for impl/admin/beacon
EIP-1822UUPS proxyUpgrade auth in impl; common audit subject
EIP-2535Diamond standardMulti-facet proxy; storage hazards
EIP-191Signed data standardPrefix to prevent transaction-collision
EIP-712Typed structured data signingReplay protection via domain separator
EIP-2930Access listsOptimization, mild audit relevance
EIP-3074 / EIP-7702EOA → smart-account migrationEIP-7702 in particular reshapes signing trust (post-Pectra) [verify status]
ERC-4337Account AbstractionUserOp pipeline; not a hard fork
EIP-6492Counterfactual signature verificationAA-friendly off-chain sig check

L2 / Rollup

EIP / SpecTitleNotes
OP Stack docshttps://docs.optimism.io/Optimistic rollup reference
Arbitrum Nitro docshttps://docs.arbitrum.io/Nitro architecture, fraud proofs
zkSync Era docshttps://docs.zksync.io/Native AA
Starknet docshttps://docs.starknet.io/Cairo VM
L2Beathttps://l2beat.com/Trust assumption tracking

4. Exploit Post-Mortems & Incident Aggregators

SourceURLNotes
Rekt Newshttps://rekt.news/Highest-quality narrative coverage of incidents; cite the protocol’s own post-mortem for technical details
Immunefi blog & writeupshttps://medium.com/immunefiBug-bounty disclosures, often with PoC
SlowMist Hacked DBhttps://hacked.slowmist.io/Incident database; cross-reference
DeFiLlama Hackshttps://defillama.com/hacksAggregated loss tracker; numbers are best-effort
PeckShield Twitter / bloghttps://x.com/peckshieldEarly on-chain incident detection
Solodithttps://solodit.cyfrin.io/Aggregated audit findings from competitive audits; searchable

Notable individual post-mortems (linked in case studies)

  • The DAO (2016): Phil Daian’s original analysis — https://hackingdistributed.com/2016/06/18/analysis-of-the-dao-exploit/
  • Parity multisig (2017): Parity post-mortem — https://www.parity.io/blog/security-alert-parity-wallet/ (historical)
  • bZx (2020): PeckShield analysis (Feb 2020)
  • Wormhole (2022): Wormhole official + Certus One write-up
  • Ronin (2022): Sky Mavis official statement (March 2022)
  • Nomad (2022): Nomad official + samczsun thread
  • Euler (2023): Euler Labs post-mortem + Omniscia/Sherlock follow-up audits
  • Curve Vyper (2023): Vyper team statement + Curve incident channel
  • Penpie (2024): Pendle/Penpie post-mortem

Verification rule: when citing a loss amount in an audit write-up, link to the protocol’s own statement or the block explorer transaction set, not aggregator estimates. Numbers from aggregators are approximations.


5. Competitive Audit Platforms (current state of practice)

PlatformURLFormatUse for
Code4renahttps://code4rena.com/Public competitiveReading judging decisions, finding write-ups
Sherlockhttps://www.sherlock.xyz/Hybrid competitive + lead auditorCoverage + judging policy clarity
Cantinahttps://cantina.xyz/Competitive + privateLarger competitions, top-of-leaderboard write-ups
Hats Financehttps://hats.finance/Bug bounty + auditActive bounties
Immunefihttps://immunefi.com/Bug bountyLargest bounty platform; severity rubric is industry reference

Reading judged findings on these platforms — especially the disagreements between auditors and judges — is one of the fastest ways to develop severity judgment.


6. Tooling Documentation

ToolTypeDocsNotes
Foundry (forge/cast/anvil/chisel)Dev + test frameworkhttps://book.getfoundry.sh/Industry default. Mainnet fork + cheatcodes + invariant fuzzing built-in
HardhatDev frameworkhttps://hardhat.org/docsOlder but still used; TypeScript scripts ecosystem
SlitherStatic analyzerhttps://github.com/crytic/slitherRun first on every codebase. Detector list at docs/detectors/
EchidnaProperty-based fuzzerhttps://github.com/crytic/echidnaStateful Haskell-based fuzzer
MedusaProperty-based fuzzerhttps://github.com/crytic/medusaGo-based, parallel fuzzing, geth-fork
MythrilSymbolic executorhttps://github.com/Consensys/mythrilOlder; useful for specific patterns
ManticoreSymbolic executorhttps://github.com/trailofbits/manticore[verify maintenance status] — primarily research / archival
Certora ProverFormal verificationhttps://www.certora.com/CVL spec language; commercial but free tier exists
HalmosSymbolic-test runnerhttps://github.com/a16z/halmosFoundry-compatible, BMC-style; lightweight formal
TenderlyTx simulator + monitoringhttps://tenderly.co/Best transaction debugger
Etherscan / block explorersTx + contract explorerhttps://etherscan.io/Verified-source browsing, decoded calls
Phalcon / BlocksecTx tracerhttps://app.blocksec.com/explorer/txExcellent for tracing exploit transactions
4byte directorySelector lookuphttps://www.4byte.directory/Function selectors → signatures
FortaReal-time monitorhttps://forta.org/Detection bots for incidents
DethCrypto contract indexContract indexhttps://github.com/dethcrypto/ethereum-typesType-safe interaction

Non-EVM tooling


7. Research Papers & Books

Books

TitleAuthorNotes
Mastering EthereumAndreas M. Antonopoulos & Gavin WoodFoundational. Free online: https://github.com/ethereumbook/ethereumbook
Programming BitcoinJimmy SongCrypto/curve math foundations
Real-World CryptographyDavid WongMost accessible serious-crypto book
Bitcoin: A Peer-to-Peer Electronic Cash SystemSatoshi NakamotoThe 9-page paper that started it; read at least once

Papers (selected)

PaperWhy it matters
Flash Boys 2.0 (Daian et al., 2019)https://arxiv.org/abs/1904.05234Foundational MEV paper
SoK: Decentralized Finance (DeFi) (Werner et al., 2021) — https://arxiv.org/abs/2101.08778DeFi taxonomy reference
Quantifying Blockchain Extractable Value (Qin, Zhou, Gervais, 2021)MEV quantification
An Empirical Study of Smart Contract Vulnerabilities — various authorsEmpirical bug-class distribution
A Survey of Smart Contract Formal Specification and Verification — Tolmach et al.Formal methods landscape

8. Continuing-Education Feeds

SourceURLCadence
Paradigm researchhttps://www.paradigm.xyz/writingIrregular; high-signal
a16z crypto researchhttps://a16zcrypto.com/research/Irregular
Flashbots researchhttps://writings.flashbots.net/MEV / PBS
Vitalik’s bloghttps://vitalik.eth.limo/Roadmap thinking
Samczsunhttps://samczsun.com/Exploit threads; required reading
Trust Security bloghttps://trust-security.xyz/blogAudit-firm-style explainers
Privacy & Scaling Explorations (PSE)https://pse.dev/ZK applied research

9. Communities

PlaceWhat
r/ethdevDiscussion; mixed quality
Ethereum Magicians (https://ethereum-magicians.org/)EIP discussion at proposal stage
Ethereum Research forum (https://ethresear.ch/)Protocol research
Code4rena DiscordCompetitive audit community
Secureum bootcamp materialsFree curriculum on smart contract security

10. Quality / Currency Tagging Convention

When this course cites a source, the convention is:

(Author/Org, YYYY-MM, [Current|Partial|Historical])
  • Current: matches present best practice; safe to apply.
  • Partial: still useful but some recommendations outdated; flag the parts that are.
  • Historical: was best practice at time of writing; do not apply without verification.

Examples in lesson notes:

  • “OpenZeppelin AccessControl docs (OZ, 2025, Current)”
  • “SWC Registry (SmartContractSecurity, 2020, Partial — many SWC entries are still valid but the project is not actively updated; cross-check with current detector docs)”
  • “ConsenSys SCBP (ConsenSys, 2021, Partial — reentrancy / external call sections current; randomness section outdated, use VRF guidance instead)”

Last updated: 2026-05-16 See also: MOC-Web3-Security-Mastery · Roadmap