Submission Deadline: 30 November 2017
IEEE Access invites manuscript submissions in the area of Research Challenges and Opportunities in Security and Privacy of Blockchain Technologies.
Blockchain is an increasingly popular networking technology for streamlining business processes, which uses a peer-to-peer (P2P) network. In other words, no central authority (e.g. traditional financial institution) is required to conduct a transaction. Due to the decentralized nature, blockchain allows one to undertake and verify transactions in real-time. In recent times, many applications based on the blockchain technology have been proposed. One such popular real-world example application is Bitcoin. However, there are underlying security and privacy issues. For example, once a public key has been linked with an individual’s identity, one could browse previous transactions on the blockchain and view all transactions associated with the particular public key. One key research challenge is how to balance security and privacy of an individual with accountability. For example, how can we allow the tracing of illegal activities or users (e.g. money laundering and cybercrime) without breaking the decentralization property of the system?
This Special Section in IEEE Access solicits state-of-the-art technical research results and survey on secure and privacy-preserving blockchain technology, as well as novel applications providing security and privacy-preserving features/functionalities in the blockchain technology.
We also highly recommend the submission of multimedia with each article as it significantly increases the visibility, downloads, and citations of articles.
Associate Editor: Kim-Kwang Raymond Choo, The University of Texas at San Antonio, USA
Relevant IEEE Access Special Sections:
IEEE Access Editor-in-Chief: Michael Pecht, Professor and Director, CALCE, University of Maryland
Paper submission: Contact Associate Editor and submit manuscript to:
For inquiries regarding this Special Section, please contact: firstname.lastname@example.org