Skip to main navigation Skip to search Skip to main content

Lessons Learned from Developing Permissioned Blockchains

  • Wei Tek Tsai
  • , Lian Yu
  • Beijing Tiande Technologies
  • National Big Data Comprehensive Experimental Area
  • Andrew International Sandbox Institute
  • Arizona State University
  • Peking University

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

Abstract

We have been developing permissioned blockchains (BC) since 2015 and encountered numerous issues. Some of these issues are well known, but some are unknown before. This paper summarizes these lessons learned including communication and consensus protocols. Even though communications protocols and consensus protocols have been under development and experimentation for over forty years, we still encountered issues not addressed before. These issues require innovative solutions to ensure that dependable BC will be operating at a high speed.

Original languageEnglish
Title of host publicationProceedings - 2018 IEEE 18th International Conference on Software Quality, Reliability, and Security Companion, QRS-C 2018
PublisherInstitute of Electrical and Electronics Engineers Inc.
Pages1-10
Number of pages10
ISBN (Print)9781538678398
DOIs
StatePublished - 9 Aug 2018
Event18th IEEE International Conference on Software Quality, Reliability, and Security Companion, QRS-C 2018 - Lisbon, Portugal
Duration: 16 Jul 201820 Jul 2018

Publication series

NameProceedings - 2018 IEEE 18th International Conference on Software Quality, Reliability, and Security Companion, QRS-C 2018

Conference

Conference18th IEEE International Conference on Software Quality, Reliability, and Security Companion, QRS-C 2018
Country/TerritoryPortugal
CityLisbon
Period16/07/1820/07/18

Keywords

  • Blockchain
  • Communication-protocol
  • Consensus-protocol
  • Permissioned-blockchains

Fingerprint

Dive into the research topics of 'Lessons Learned from Developing Permissioned Blockchains'. Together they form a unique fingerprint.

Cite this