## 9 Discussion  
In this discussion, the aspects of the transparency of the decision and service making process; privacy; security of the user's data; and security of the robot; devices connected to the robot; and its channel security are discussed. _Transparency:_ The proposed BC system will, not only make all the activities of the robot transparent, but will give more confidence and trust to the user, because it tracks and traces every action taken by the robot. The collected data will now be resilient to any form of data tampering and access by any unauthorised third parties. Moreover, the BC proposed in Figure 2 will not increase the utilisation of resources, rather it will optimise the resources, because the data will only be securely stored in one location, and the hash of every piece of data will be securely collected and stored in blockchain blocks. Otherwise, due to resource constraints, it would be challenging to adopt resource-hungry blockchain technology. Moreover, it would be impractical to run a blockchain within a resource-limited IoT system, as addressed by the authors of [68], so it should instead be deployed in the robot and a higher computational resource network device. This means that the proposed blockchain framework in Figure 2 will not be resource-demanding and resource hungry, particularly regarding computation power, storage, and bandwidth utilisation. Moreover, the proposed BC framework will preserve the privacy of the data collected, because the actual data is not stored in the BC network, rather only one-way encrypted hash values are stored. However, all the blocks are synced with the actual data that is securely stored in the robot, and only authorised users with the right level of access rights can access the relevant information. _Privacy:_ It is complex in nature and a daunting task to define privacy, because it can mean different things to different people, and can vary from one individual to another. An old definition, but which is still relevant in today's context, is elaborated in a Harvard \begin{table}
\begin{tabular}{c c c c} \hline \hline
**Attack on AMRISys** & \begin{tabular}{c} **Functionality of** \\ **AMRISys** \\ \end{tabular} & \begin{tabular}{c} **Control on the** \\ **AMRISys** \\ \end{tabular} & \begin{tabular}{c} **Its Impact** \\ \end{tabular} \\ \hline Access Control & & & \\ - Dictionary attacks, & & & \\ - Brute-force attack, & & & \\ - Man-in-middle, & Functional & Yes & \begin{tabular}{c} The authentication process and the authorisation \\ and control of the system could be compromised. \\ Unauthorised users will access the services and \\ storage would be visible unless storage is secure. \\ - Password Spraying attack \\ \hline Storage & & & \\ - Storage account discovery, & & & \\ - Data Deletion, & Functional & No & \
\begin{tabular}{c} Data corruption, alteration, deletion; data \\ visibility and available to a third party. \\ Moreover, unauthorised users will see the data. \\ \end{tabular} \\ - Data Alteration or & & & \\ Modification & & & \\ \hline Services & & \\ - Malware, & Partly Functional & Yes & The services may stop functioning as intended. \\ - Viruses to induce a & & & \\ malfunction & & & \\ \hline Sensory & & & If the sensory devices are replaced or replicated, \\ - Replacement, & Partly Functional & Yes &
\begin{tabular}{c} the robotic system may end up collecting or \\ sensing incorrect or invalid data or leak the data. \\ It may even lead to data falsification. \\ \end{tabular} \\ - Tampering & & & & It may even lead to data falsification. \\ \hline Network & & & \\ - Attack on Proxy server, & & & It may cause dysfunction in the network and \\ - Man-in-middle attack, & & & even capture traffic, but the functionality of the \\ - Routing attack, & & & MRISys may be affected. The remote connection \\ - Media Access, & & & and remote delivery of information would be \\ - ARP attack, & & & disrupted. \\ - Buffer overflow attack & & & \\ \hline \hline \end{tabular}
\end{table}