I graduated with a degree in Computer Science, but I’ve been limited by not owning a personal laptop. For the next 20 days, I’m building publicly. I’ll be breaking down Web3 security, scam prevention, and Base ecosystem safety in simple terms. My goal: raise $300 to get a working laptop and start building full-time. I’ll document: • Every post • Every contribution • The final purchase • My 30-day build challenge after If you believe in investing in future builders, feel free to support. Day 1/20 🚀 ADD: 0x05b0EB3576CA4692FD899AF1869F72Aa91C63C40
- 0 replies
- 0 recasts
- 0 reactions
Day 4 Today I learned how reentrancy attacks work. A contract sends funds before updating its internal balance. An attacker can repeatedly call the withdraw function before the balance updates. Small logic mistake. Massive exploit potential. This is why order of operations in smart contracts matters. A quest came to my head while learning about reentrance today, if a contract updates balance first, but still makes an external call later, can reentrancy still happen somewhere else in the contract and yeah I found out that yes reentrancy can still happen if: 1. There are other vulnerable functions e.g cashbacks etc 2. There are multiple balances 3. There are shared state variables 4. There are cross-function dependencies.
- 0 replies
- 0 recasts
- 0 reactions
Day 3/20 If I’m verifying a token on Base before buying, I check 5 things: 1. Contract address from official source 2. Liquidity lock 3. Holder distribution 4. Ownership status 5. Recent large transactions Most people skip at least 3 of these. I’m documenting Web3 security daily while raising $300 for a laptop to build full-time. Day 3/20.
- 0 replies
- 0 recasts
- 0 reactions