Awesome Web3 Security - Project Overview
Purpose
This is a curated collection of Web3 security materials and resources for pentesters, auditors, and bug hunters. The goal is to keep the list high-signal, well-categorized, and non-duplicated.
Project Structure
awesome-web3-security/
├── README.md # Main resource list (curated)
├── LICENSE # License
├── .claude/
│ └── skills/ # Claude skills (this directory)
└── ref/ # Optional reference notes (not curated)
├── notes/ # Personal notes, drafts, checklists
└── Crypto-resources/ # Reference lists (used for gap checks)
README.md Format Convention
Heading Structure
- Top-level categories use
##.
- Subcategories use
### (e.g., inside Development).
- Starter Pack uses bold bullets for sub-sections (e.g.,
- **Bug Bounties**).
Link Format
- Use full URLs, one per bullet line.
- Add a short description in square brackets:
- https://... [Short description]
- Keep descriptions English and concise.
- Do not add the same URL in multiple places.
Example Entry
### Decompilers
- https://example.com/tool [EVM decompiler]
Categorization Rules (How to Place a New Link)
- Security Starter Pack: learning, CTFs, audits/bounties, newsletters, beginner tools.
- Blockchain Guide: ecosystem overviews, protocol primers, learning roadmaps (broad).
- Development: frameworks, SDKs, tools, compilers, decompilers, test suites, contract source code.
- Security: security references, standards, vulnerability catalogs, analyzers, audit methodology.
- DeFi Topics: Stablecoin/MEV and other DeFi-focused topics.
Duplicate Policy
No duplicate URLs in README.md. If a link fits multiple categories, pick the primary one.
Contribution Checklist
- Check for duplicates in
README.md before adding.
- Verify the link points to the canonical source (avoid low-value forks).
- Keep the description English and useful.
- Put it into the most appropriate category.
- Prefer minimal changes over reformatting large sections.
Data Source
For detailed and up-to-date resources, fetch the full list from:
https://raw.githubusercontent.com/gmh5225/awesome-web3-security/refs/heads/main/README.md
1---2name: awesome-web3-security-overview3description: Guide for understanding and contributing to the awesome-web3-security curated resource list. Use this skill when adding resources, organizing categories, or maintaining README.md consistency (no duplicates).4---56# Awesome Web3 Security - Project Overview78## Purpose910This is a curated collection of Web3 security materials and resources for pentesters, auditors, and bug hunters. The goal is to keep the list **high-signal**, **well-categorized**, and **non-duplicated**.1112## Project Structure1314```15awesome-web3-security/16├── README.md # Main resource list (curated)17├── LICENSE # License18├── .claude/19│ └── skills/ # Claude skills (this directory)20└── ref/ # Optional reference notes (not curated)21 ├── notes/ # Personal notes, drafts, checklists22 └── Crypto-resources/ # Reference lists (used for gap checks)23```2425## README.md Format Convention2627### Heading Structure2829- Top-level categories use `##`.30- Subcategories use `###` (e.g., inside `Development`).31- Starter Pack uses bold bullets for sub-sections (e.g., `- **Bug Bounties**`).3233### Link Format3435- Use full URLs, one per bullet line.36- Add a short description in square brackets: `- https://... [Short description]`37- Keep descriptions **English** and concise.38- Do not add the same URL in multiple places.3940### Example Entry4142```markdown43### Decompilers44- https://example.com/tool [EVM decompiler]45```4647## Categorization Rules (How to Place a New Link)4849- **Security Starter Pack**: learning, CTFs, audits/bounties, newsletters, beginner tools.50- **Blockchain Guide**: ecosystem overviews, protocol primers, learning roadmaps (broad).51- **Development**: frameworks, SDKs, tools, compilers, decompilers, test suites, contract source code.52- **Security**: security references, standards, vulnerability catalogs, analyzers, audit methodology.53- **DeFi Topics**: Stablecoin/MEV and other DeFi-focused topics.5455## Duplicate Policy5657**No duplicate URLs in README.md.** If a link fits multiple categories, pick the primary one.5859## Contribution Checklist60611. Check for duplicates in `README.md` before adding.622. Verify the link points to the canonical source (avoid low-value forks).633. Keep the description English and useful.644. Put it into the most appropriate category.655. Prefer minimal changes over reformatting large sections.6667## Data Source6869For detailed and up-to-date resources, fetch the full list from:70```71https://raw.githubusercontent.com/gmh5225/awesome-web3-security/refs/heads/main/README.md72```73
gmh5225