Need of Web 3.0 Security
summary
Claims that “code is money” and smart contracts are immutable, cites about $2 billion lost in 2022 and single incidents like $600 million hacks to justify audits. Recommends concrete steps: 95%+ unit test coverage, use OpenZeppelin libraries, static analysis, line‑by‑line manual review, dual third‑party audits, post‑deployment monitoring and bug bounties on platforms like Code4rena and Immunefi. Describes products that run these processes: quill play (generate contracts), quill relay (pre‑audit checks) and quill monitor (transaction alerts).
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:49Web 3.0 security importance
- 3:18Billions lost to hacks
- 4:22Web 2 hackers in Web 3.0
- 6:13Rug pulls in DeFi
- 8:23Biggest blockchain incidents
- 9:29Smart contract auditing critical
- 11:56Blockchain adoption vs scams
- 12:59Fifty-one percent attacks
- 13:42Smart contract auditing process
- 16:54Securing Web 3.0 projects
- 19:42Bug bounties and monitoring
- 21:06Blockchain developer guidelines
- 23:36Solidity DeFi NFT DAO security
- 24:38Quill Audits tools
- 26:44Web3 Suggest platform
- 28:28Q&A
related talks
36mDeciphering Web3 Security: Implications and Innovations
15mWhy Smart Contract Audit is Not Enough
21mPractical Security Measures for Web3 Founders
30mSmart-Contract Security 201: Auditing Lessons for Solana Founders
14mWeb3 Security: The Epic Battle Against Evil
20mLearning How to Build Secure Smart Contracts
12mSmart Contract Security
04mWhat Should the Scope of the Web3 Audit Look Like?