You're reading from Blockchain with Hyperledger Fabric Build decentralized applications using Hyperledger Fabric 2

Product type Paperback

Published in Nov 2020

Publisher Packt

ISBN-13 9781839218750

Length 756 pages

Edition 2nd Edition

Languages

Java

Tools

Blockchain

Concepts

Blockchain

Authors (7):

Salman A. Baset

Venkatraman Ramakrishna

Salman Baset

Anthony O'Dowd

Petr Novotny

Nitin Gaur

Luc Desrosiers

+3 more

View More author details

Table of Contents (18) Chapters

Preface

1. Blockchain – An Enterprise and Industry Perspective

2. Exploring Hyperledger Fabric FREE CHAPTER

3. Business Networks

4. Setting the Stage with a Business Scenario

5. Designing Smart Contract Transactions and Ledger Data Structures

6. Developing Smart Contracts

7. Developing Applications

8. Advanced Topics for Developing Smart Contracts and Applications

9. Network Operation and Distributed Application Building

10. Enterprise Design Patterns and Considerations

11. Agility in a Blockchain Network

12. Governance – A Necessary Evil of Regulated Industries

13. Life in a Blockchain Network

14. Hyperledger Fabric Security

15. Blockchain's Future, Protocol Commercialization, and Challenges Ahead

16. Another Book You May Enjoy

17. Index

Smart contract security

In Hyperledger Fabric, as indicated previously, smart contracts (chaincodes) can be written in Go, Java, or JavaScript. The smart contract must be installed on a peer and then explicitly instantiated.

When instantiated using the docker builder command, each smart contract is built and then launched in its own Docker container. Starting with version 2.0, external builders can be utilized to build and run smart contracts without requiring a Docker daemon.

When running the smart contract inside a Docker container, it is important to understand what access this container may have to the network. If care is not taken in carefully reviewing the smart contract before it gets installed on the peer, and in isolating the network access for that smart contract, it could result in a malicious or misconfigured node probing or attacking the peer attached to the same virtual network.