A scalable blockchain framework for secure transactions in IoT

Sujit Biswas, Kashif Sharif*, Fan Li, Boubakr Nour, Yu Wang

*Corresponding author for this work

Research output: Contribution to journalArticlepeer-review

208 Citations (Scopus)

Abstract

Internet of Things (IoT) and blockchain (BC) technologies have been dominating their respective research domains for some time. IoT offers automation at the finest level in different fields, while BC provides secure transaction processing for asset exchanges. The capability of IoT devices to generate transactions prompts their integration with BC as the next logical step. The biggest challenges in this integration are the scalability of ledger and rate of transaction execution in BC. On one hand, due to their large numbers, IoT devices will generate transactions at a rate which current block chain solutions cannot handle. On the other hand, implementing BC peers onto IoT devices is impossible due to resource constraints. This prohibits direct integration of both technologies in their current state. In this paper, we propose a solution to address these challenges by using a local peer network to bridge the gap. It restricts the number of transactions which enters the global BC by implementing a scalable local ledger, without compromising on the peer validation of transactions at local and global level. The testbed evaluations show significant reduction in the block weight and ledger size on global peers. The solution also indirectly improves the transaction processing rate of all peers due to load distribution.

Original languageEnglish
Article number8481466
Pages (from-to)4650-4659
Number of pages10
JournalIEEE Internet of Things Journal
Volume6
Issue number3
DOIs
Publication statusPublished - Jun 2019

Keywords

  • Blockchain (BC)
  • Internet of Things (IoT)
  • Ledger size
  • Scalability
  • Security
  • Transaction rate

Fingerprint

Dive into the research topics of 'A scalable blockchain framework for secure transactions in IoT'. Together they form a unique fingerprint.

Cite this