Contract Security, Digital Identity, & Becoming a Blockchain Dev
summary
Q&A covers concrete advice: track exploits on the OpenZeppelin forum, always use the library keyword to avoid state-mixing when importing libs, treat oracles as a real engineering problem illustrated by the Chainlink oracle problem, expect DAOs and identity standards to remain unresolved for years, portable identity should allow multiple accounts but make exploitation costly, early mistakes include starting on Hyperledger Fabric instead of public chains, and the fastest learning comes from building real contracts.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:20How do you stay up to date on hacks
- 1:17What are the biggest challenges new smart contract developers should anticipate
- 2:00Should people be able to have multiple identities
- 4:45Who shouldnt get into blockchain
- 5:15How to figure out whats real
- 6:45State of DAOs
- 9:30Minimize Exploits
- 10:30Biggest Mistake
- 12:45Outro
related talks
20mLearning How to Build Secure Smart Contracts
12mSmart Contract Security
25mCommSec D2 - Smart Contract (In)Security
51mA Deal with the Devil: Breaking Smart Contracts
23mHow to overcome AI threat to user authenticity
01h 51mOnDaChain or OffDaChain? Design Considerations for User’s Data
52mThe Power Of DevSecOps In Web3 And Blockchain
49mHacked Blockchain Projects What we’ve learned