Book Image

Solidity Programming Essentials - Second Edition

By : Ritesh Modi
Book Image

Solidity Programming Essentials - Second Edition

By: Ritesh Modi

Overview of this book

Solidity is a high-level language for writing smart contracts, and the syntax has large similarities with JavaScript, thereby making it easier for developers to learn, design, compile, and deploy smart contracts on large blockchain ecosystems including Ethereum and Polygon among others. This book guides you in understanding Solidity programming from scratch. The book starts with step-by-step instructions for the installation of multiple tools and private blockchain, along with foundational concepts such as variables, data types, and programming constructs. You’ll then explore contracts based on an object-oriented paradigm, including the usage of constructors, interfaces, libraries, and abstract contracts. The following chapters help you get to grips with testing and debugging smart contracts. As you advance, you’ll learn about advanced concepts like assembly programming, advanced interfaces, usage of recovery, and error handling using try-catch blocks. You’ll also explore multiple design patterns for smart contracts alongside developing secure smart contracts, as well as gain a solid understanding of writing upgradable smart concepts and data modeling. Finally, you’ll discover how to create your own ERC20 and NFT tokens from scratch. By the end of this book, you will be able to write, deploy, and test smart contracts in Ethereum.
Table of Contents (21 chapters)
1
Part 1: The Fundamentals of Solidity and Ethereum
7
Part 2: Writing Robust Smart Contracts
13
Part 3: Advanced Smart Contracts

The Hacker contract

A hacker writes a simple and small smart contract that interacts with the EtherPot contract by becoming one of its users. The Hacker contract consists of similar functions to those available in the EtherPot contract, and it mimics an externally owned account – that is, it can send Ethers, withdraw them, and check the account balance. Additionally, it also has a special receive() payable function. This is a special function because it cannot be called on demand. It is executed automatically whenever the contract receives Ether. To receive Ether, it should be tagged as payable:

    contract Hacker {
        address payable etherpot;
  
        constructor(address payable _etherpot) payable {
            etherpot = _etherpot;
        }
 
  ...