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

Introduction to ZeppelinOS

ZeppelinOS is a development platform used to develop, deploy, and manage upgradable contracts. The platform uses the Truffle framework, which is built especially for managing upgradable contracts.

As we discussed earlier, there is no native way to write an upgradable contract on the Ethereum blockchain, hence developers are left with some patterns with which they can make contracts upgradable. One such design pattern is the proxy design pattern, in which a contract behaves like a proxy to forward function calls to the target contracts. The administrator of the proxy contract can change the target contract; however, one limitation of the proxy design pattern is that the contract API cannot be changed. The function API that was being supported by the proxy contract is only able to forward the call to the target contract because, once it has been deployed...