Loading video player...
Welcome to Module 3 of the ETH-Crash-Course! This is the class where blockchain theory finally turns into actual execution. Today, we dive deep into Solidity, the dominant programming language for writing smart contracts on Ethereum. In this lesson, we shift away from abstract architecture and start looking directly at code. We will build a complete mental model of a Solidity file's anatomy—from license tags and compiler pragmas to state variables, visibility modifiers, and core structures like mappings, structs, events, and code modifiers. By the end of this video, you will understand how to write and read a fully functional smart contract! 🔗 Essential Links: Sign up for Live Classes: https://luma.com/9hyzpvth Main Course Repo: https://github.com/SM-Web-Systems/eth-crash-course Module 3 Detailed Notes: https://github.com/SM-Web-Systems/eth-crash-course/blob/main/Modules/Module3.md Presentation Slides: https://www.slideshare.net/slideshow/eth-crash-course-ethereum-from-zero-to-smart-contracts-module-3-solidity/287332015 🧠 Key Concepts Covered: The "Write-Compile-Deploy" Pipeline: How your .sol text file turns into execution instructions for the EVM. Storage vs. Memory in Action: Why state variable writes (SSTORE) dominate 99% of your function's gas costs. The Principle of Least Privilege: Designing tight visibility constraints (private/internal) to dramatically slash your contract's security attack surface. Why Events Matter: Recognizing that smart contracts can't natively send API webhooks, making on-chain logs the crucial link for Web2 frontends. 🧪 Mini-Challenge for the Comments: Look closely at the SimpleBank architecture introduced near the end of the video. 👉 Why is it critical to update a user's balance in storage before triggering an external transfer of Ether? Drop your answer in the comments below! (Hint: Think back to the security warnings about watching out for reentrancy!) Don't forget to Like, Subscribe, and Star the GitHub repository! Next up in Module 4, we will break open the smart contract lifecycle completely—exploring compiling, local deployment, and testing infrastructure using Foundry.