# IoT Blockchain Data Vercity with Data Loss Tolerance
## 3 Results
### Result of IoT Blockchain Data Veracity with Data Loss Tolerance
The simulation conducted on the first administrator node is done with the script below:  
_IoT blockchain daemon creation:_  
_Sudo multichain-util create utp-chain01_  
_Start-up IoT blockchain daemon:_  
_Sudo multichaind utp-chain01 -daemon_  
_Displayed \"Starting up mode: Other nodes can connect to this node using: Multichaind [EMAIL_ADDRESS]:7761\"_  
_On new node:_  
_Sudo multichaind [EMAIL_ADDRESS]:7761_  
_New node address which is shown when the command is input_  
_1 RsxcCZpVdhk9 Zdsf6 amNWiZDCxvV3 XPAPccNAv_  
_Submit the new node address to the administrator node_  
_On Administrator node:_  
_multichain-cli utp-chain01 grant 1 RsxcCZpVdhk9 Zdsf6 amNWiZDCxvV3 XPAPccNAv contect, send, receive_  
_If the new node address is invalid, no node joining with error invalid address......__If the new node address is valid, node joining successful with a unique key returned 4331c32a39 754 fc8005e2858e14d70d642 ckdf6230d5292 eab7f1 beab2147c37f_  
_Sudo multichain-cli utp-chain01 grant 1 RsxcCZpVdhk9 ZdsfgamNWiZDCxV3 XPAPccNAv connect, send, receive_  
Figure 13 shows the result of the connectivity evaluation in IoT blockchain P2P network. Once the P2P network has been established, simulation proceeds to the algorithm of secured distributed storage. The algorithm is evaluated on transaction publishing and replication to all nodes. In IoT blockchain upt-chain01, a stream storage needs to be created in the IoT blockchain. upt-stream01 is created, established and excepting transaction from the peer nodes. The script written to publish the transaction to IoT blockchain stream is as below (Figure 14):  
Once the IoT blockchain transaction was successfully published, the transaction is replicated to all the active nodes whenever they come active. Data veracity with data loss tolerance verification was conducted according to the flow diagram of data veracity with data loss tolerance (Figure 6) using intelligent small computing resources. The Raspberry Pi acted as IoT blockchain nodes are all started up. The verification was conducted on traversal nodes; transaction items stored were retrieved  
Figure 14: Transaction successfully published to IoT blockchain. Figure 13: New node joined into IoT blockchain. for verification. The verification process started with picking up the first node, its transaction items were retrieved and verified against the master copy (Figure 15). If any any discrepancy is found, the data loss error is disposed of. The examined node will then be shut down and the process will proceed to the next node if no discrepancy is found. The traversal is repeated until the last active node. A true result was returned on data veracity with data loss tolerance as no discrepancy was found during the entire process. The liststreamitems command returns all the transactions published to the IoT blockchain nodes. The same results can be seen when the liststreamitems command was performed on all nodes. This proved that the transaction data was captured and stored in a secured distributed IoT blockchain model. The verification process proved that the transactions published to IoT blockchain were secured in the nodes distributed within the P2P network. The transactions can be retrieved as long as one node survives. IoT blockchain data veracity with data loss tolerance was further evaluated with the LISPICE simulation. LISPICE was set up with a single capacitor-cluster (as IoT blockchain node), comprising of 10 capacitors (as transaction stream item) in the capacitor-cluster. When the circuit breaker triggered in the middle of the simulation process to simulate node failure, the simulation showed that the capacitance which was measured by the inductance current immediately returned to zero (Figure 16), this was indicated as data loss. Data loss tolerance was subsequently evaluated with another LISPICE setup with multiple capacitor-clusters, where the result showed that node failure only caused capacitance reduction but no data loss.