Using Fault Injection to Assess Blockchain Systems in Presence of Faulty Smart Contracts

TL;DR

This paper uses fault injection to evaluate how blockchain systems with smart contracts respond to software faults, highlighting the importance of formal verification and runtime protections for system dependability.

Contribution

It introduces a fault injection approach to assess blockchain dependability and compares the effectiveness of verification and runtime protections in fault detection.

Findings

Formal verification and runtime protections improve fault detection.

Faults in smart contracts can compromise system dependability.

Complementing platform checks with additional protections is necessary.

Abstract

Blockchain has become particularly popular due to its promise to support business-critical services in very different domains (e.g., retail, supply chains, healthcare). Blockchain systems rely on complex middleware, like Ethereum or Hyperledger Fabric, that allow running smart contracts, which specify business logic in cooperative applications. The presence of software defects or faults in these contracts has notably been the cause of failures, including severe security problems. In this paper, we use a software implemented fault injection (SWIFI) technique to assess the behavior of permissioned blockchain systems in the presence of faulty smart contracts. We emulate the occurrence of general software faults (e.g., missing variable initialization) and also blockchain-specific software faults (e.g., missing require statement on transaction sender) in smart contracts code to observe the impact on the overall system dependability (i.e., reliability and integrity). We also study the effectiveness of formal verification (i.e., done by solc-verify) and runtime protections (e.g., using the assert statement) mechanisms in detection of injected faults. Results indicate that formal verification as well as additional runtime protections have to complement built-in platform checks to guarantee the proper dependability of blockchain systems and applications. The work presented in this paper allows smart contract developers to become aware of possible faults in smart contracts and to understand the impact of their presence. It also provides valuable information for middleware developers to improve the behavior (e.g., overall fault tolerance) of their systems.