Book Image

Mastering Blockchain Programming with Solidity

By : Jitendra Chittoda
Book Image

Mastering Blockchain Programming with Solidity

By: Jitendra Chittoda

Overview of this book

Solidity is among the most popular and contract-oriented programming languages used for writing decentralized applications (DApps) on Ethereum blockchain. If you’re looking to perfect your skills in writing professional-grade smart contracts using Solidity, this book can help. You will get started with a detailed introduction to blockchain, smart contracts, and Ethereum, while also gaining useful insights into the Solidity programming language. A dedicated section will then take you through the different Ethereum Request for Comments (ERC) standards, including ERC-20, ERC-223, and ERC-721, and demonstrate how you can choose among these standards while writing smart contracts. As you approach later chapters, you will cover the different smart contracts available for use in libraries such as OpenZeppelin. You’ll also learn to use different open source tools to test, review and improve the quality of your code and make it production-ready. Toward the end of this book, you’ll get to grips with techniques such as adding security to smart contracts, and gain insights into various security considerations. By the end of this book, you will have the skills you need to write secure, production-ready smart contracts in Solidity from scratch for decentralized applications on Ethereum blockchain.
Table of Contents (21 chapters)
Free Chapter
1
Section 1: Getting Started with Blockchain, Ethereum, and Solidity
5
Section 2: Deep Dive into Development Tools
9
Section 3: Mastering ERC Standards and Libraries
16
Section 4: Design Patterns and Best Practices

Chapter 9

  1. It is bad practice to copy and paste the OpenZeppelin library code and use it in your project. You must install the OpenZeppelin npm package in your project. You can stick to using a specific version of the library files in your project. 
  2. You should not make any modifications in the OpenZeppelin library files present in the node_modules folder. These library files are thoroughly tested, and so if you need a modified version of the files, copy it from the library and maintain your version separately in your project.
  3. Sometimes, there are requirements for which you do not need some of the functions of the OpenZeppelin library files. In such cases, you can override specific functions in your implementation to always revert a transaction. This is the best way to handle and remove these functions from the library contract files.
  4. You can use the mathematical...