Table 7.

Use Cases of the Analyzed Solutions.

Category	Sub-Category	By Means of	Papers
Transaction or	Energy	(i) Transactive (a distributed consensus system	[10]
Sharing		for Microgrids) and Ethereum-based BC
Systems		to regulate energy transactions.
		(ii) Token-based BC for Bitcoin payments,	PriWatt [60]
		ECDSA-based multi-signature approach
		and anonymous encrypted messages
		(Bitmessage [112]).
		(iii) Smart contracts deployed on permissioned	[78]
		BC. Each node (ETSE module), interacting with
		smart meters and other nodes, stores energy
		transactions on BC.
		(iv) Distribution of energy through a decentralized	[79]
		algorithm by implementing Alternating Direction
		Method of Multipliers (ADMM) on an
		Ethereum-based BC.
		(v) A merging of the Smart grid model with the	[80]
		ElectricChain [113] and smart contracts
		to manage strategies and consumption patterns.
		(vi) BC storing and publishing energy offers and	[86]
		energy transactions. As future work, conjunction
		of the J-Park Simulator (JPS) is planned.
	Data	(i) M2M transactions based on	[62]
		smart contract exploitation.
		(ii) A merging of BC, BitTorrent and Telehash	ADEPT [64]
		protocol.
		(iii) Types of BC: Smart Home and	[67,68]
		Overlay network BCs. Cloud Storage to save
		smart home devices’ data.
		(iv) BC storing transactions about device	Chain-
		commissioning.	Anchor [71]
		(v) Three layers system. Tokens-based BC	[72]
		system.
		(vi) A customized token-based BC to manage	[73]
		software validation.
		(vii) Flexible permissioned smart contract-	Hyper-
		based BC.	Fabric [76]
		(viii) Distributed Ledger implemented by a	IOTA [83]
		tangle or directed acyclic graph (DAG).
		(ix) BC and Distributed File System (DFS) (e.g.,	[89]
		Hadoop Distributed File System (HDFS)) as
		Object storage system.
		(x) Token-based BC to manage data	[90]
		ownership transactions.
		(xi) BC, DHT and other communication	Enigma [91],
		protocol to develop data storage system.	[85],
			Storj [87]
		(xii) Ethereum token-based BC to store	Moeco [93]
		data transfers and payments.
	Goods	(i) BC, Telehash protocol and radio hardware	[59]
		to create an interaction layer between devices.
		(ii) Monitoring real-time transactions to read	[67,68]
		real-time device’s data.
		(iii) Smart objects and buyers and sellers able	[90]
		to transact with the BC (Smart Property).
Ownership	Data	(i) Enhanced Privacy ID (EPID) protocol	Chain-Anchor [71]
		& BC as anonymous device commissioning
		and decommissioning register.
		(ii) Master Bitcoin Model the pair “Vendor-	[73]
		PubKey/Bitcoin” as proof of ownership.
		(iii) ColoredCoin/Tokens (Smart Property).	[90]
	Goods	(i) CIA	[70]
		(to get a private & public key pair) +
		BC transaction payments.
		(ii) Smart contracts and tokens.	[90]
Identity	PKI-Based BC	(i) Separation of the identity value from a	[61]
Management		series of short-term public keys
		posted to a BC.
		(ii) Built-on Namecoin BC where identities	Certcoin [69,110]
		and public keys are posted in pairs. Use of
		Cryptographic accumulators &
		DHTs [114].
		(iii) Combination of a decentralized WoT,	Authcoin [77]
		BC and bidirectional Challenge-response
		validation and authentication process
		of public keys.
	BC-Based	(i) The anonymous identity protocol	Chain-Anchor [71]
		RSA-based EPID and DAA schemes.
		(ii) Implicit authentication by adding of	[74]
		allowed signature and public key
		within smart contracts.
		(iii) Membership modules manage	Hyper-Fabric [76]
		registration and authentication tasks.
		(iv) BC as a backbone; Device to	[84]
		Device authentication.
		(v) An off-chain technology (DHT)	Enigma [91]
		linked to a BC.
Access Control	Data	(i) Data owners issue the tokens to	[72]
		regulate the data access.
		(ii) Data Broker and Provenance Verifier	Chain-Anchor [71]
		(DB-PV), semi-permissioned BC and
		ChainAnchor consensus nodes.
		(iii) A local home BC. An access control	[67,68]
		list stored into a policy header of the BC.
		(iv) Tokens (IoTCoins) bought with Bitcoins.	[90]
		IoTCoins represent the data access. The seller
		encrypts data with the buyer public key.
		(v) FairAccess model based on smart contract to	[81]
		define policies & authorization decisions.
		(vi) Smart contracts stored in external BC.	Enigma [91]
		(vii) Each block of the BC contains data	[85]
		for access permissions.
		(viii) Announcement or Smart Contracts	[92]
		approaches.
	Device	(i) Ethereum-based BC , smart contracts and	Slock.it [13]
		physical “Slock” devices.
		(ii) JSON-based privacy policies and smart	[65]
		contracts for the devices registered within the BC.
Other		(i) A BC-based communication layer and networking	[63]
		protocols (Ethereum, NXT, Telehash).
		(ii) BC-based routing system.	Moeco [93]