Leveraging blockchain with zero knowledge proofs in wearable health technologies for personalized healthcare Authors: Abdullah Ayub Khan, Asif Ali Laghari, Hamad Almansour, Teerath Kumar, Ines Hilali Jaghdam, Fahima Hajjej, Mohamad Afendee Mohamed Published: 2025 ABSTRACT Wearable health technology has revolutionized remote monitoring and personalized healthcare by allowing real-time surveillance of patient health measurements and vital signs. However, their widespread acceptance is hampered by issues with security, privacy preservation, data protection, and interoperability. Blockchain Technology (BT), in particular Zero-Knowledge Proofs (ZKPs) and smart contracts, present a viable way to enhance the privacy, provenance, and integrity of wearable health data. This paper proposes a BT-enabled system that guarantees decentralized, unforged data management, transparency, immutability, and dynamic traceability for wearable health devices, particularly smartwatches with biosensors. To evaluate the effectiveness of the proposed work, the main performance-related metrics—latency, throughput, computational overhead, security robustness, and scalability—are looked at. The experiment’s simulated findings show that BT integration is effective, with a 99.33% improvement in data integrity and protection. Automated access control protocols demonstrate data protection by utilizing smart contracts, and ZKPs guarantee verifiable data exchanges without jeopardizing patient privacy. These results demonstrate improved interoperability, decreased processing time, and increased security in comparison to comparable cutting-edge centralized platforms. Introduction The healthcare industry has encountered significant transformation due to the strong advancements in digital health technology, particularly in the areas of remote patient continuous monitoring and personalized healthcare1. Wearable medical technology, such as smart watches, fitness trackers, biosensor-enabled nanotechnology, and implementable medical Internet of Things (IoT) and related devices, has become widely popular due to its capacity to provide dynamic vital sign monitoring1,2. Such devices provide proactive healthcare management, early disease identification, and enhanced patient engagement. They include the assessment of heart rate, blood pressure, ECG data, glucose levels, and oxygen saturation3,4. However, their full-scale implementation in contemporary healthcare ecosystems is still hampered by a number of significant limitations pertaining to interoperability, privacy protection, security, and scalability. On the other end, some of the most pressing concerns in wearable health monitoring systems are data protection, privacy preservation, and transparency. Such highlighted IoT-enabled devices continuously collect and transmit critical patient records in terms of sensitive personal information; they become targets for data breaches, cyberattacks, and unauthorized access. In the cloud-based environment, it is mainly calculated as a centralized system architecture for data management and preservation5–7. This cloud-based storage system, which is most probably used in the wearable healthcare environment for managing wearable data, is vulnerable to a single point of failure, along with insider threats, and unauthorized data manipulation5,6. In addition, the reliance on vendor-enabled service providers creates concerns about the data ownership and consent regarding the patients, as users often have restricted controls over how their health data is critically accessed, managed, and utilized7,8. Fig. 1Working Mechanism of Public Blockchain Network for Privacy and Secure Data Preservation. Working Mechanism of Public Blockchain Network for Privacy and Secure Data Preservation. In recent times, another major limitation is counted as interoperability, as existing healthcare platforms often struggle with data inconsistency in terms of formatting, lack of standardized protocols, and restricted integration across different platforms9,10. Various IoT-enabled wearable devices operate on proprietary frameworks, making it difficult for healthcare providers to seamlessly exchange, across, and analyze patient data from multiple sources. This lack of interoperability not only hampers the effectiveness of personalized treatment plans but also limits the working objective of clinical decision-making11,12. In addition, IoT-enabled wearables generate huge amounts of data, which become the raising concerns regarding the storage efficiency, scalability, and capabilities of processing in real time. In order to address such mentioned challenges, Blockchain Technology (BT) has been raised as a transformative solution for securing, organizing, managing, and optimizing wearable health data, as shown in Fig. 1. It is due to offering decentralization, forged-resistance facilities, transparency, and secure infrastructure that mainly eliminates the need for intermediaries of centralization. However, the current integration of smart contracts enables automated access control and protected data exchange, which ensures that only authorized entities can access patient records. In addition, Zero-Knowledge Proofs (ZKPs) improve privacy concerns by improving data verification and validation, which means it cannot reveal sensitive information without permission. Thereby preserving patient confidentiality, integrity, provenance, and immutability. Throughout this, BT’s immutable ledger ensures that once health data is recorded, it cannot be manipulated or changed which significantly enhances trust and makes a trustworthy environment, where gaining reliability twice a time as compared to the centralized platform, especially for healthcare applications. Fig. 2Multidisciplinary DApp Involvement. Multidisciplinary DApp Involvement. Nevertheless, various research has illustrated the effectiveness of BT-enabled solutions in enhancing security, reducing operational costs, and enhancing patient trust, especially in the healthcare environment, as shown in Fig. 2. The Distributed Application (DApp) of BT in wearable health monitoring remains an emerging area of research, with different limitations related to computational overhead, latency, throughput, and energy efficiency, which still requiring optimization. Motivation and research questions It is worth noting that the increase in the prevalence of the aging population, chronic diseases, and the growing rate of remote healthcare solutions, along with reliability, have accelerated the adoption of wearable health technologies. Till now, various IoT-enabled devices offer real-time continuous patient health monitoring, improve patient engagement, and early disease diagnosis, enabling healthcare providers to create data-driven decisions and improve patient outcomes effectively. Undoubtedly, despite such significant advantages, current wearable health applications face critical limitations that limit their capabilities due to scalability, effectiveness, and security. However, IoT-enabled wearable continuously collects, transmit, and manage highly sensitive patient records, including blood pressure, ECG signals, glucose levels, and heart rate. Preserving and organizing such records in centralized systems, especially in a cloud environment, increases the risk of cyberattacks, data breaches, and control access. It is worth noting that, till now, more than 55% of healthcare data breaches have surged in recent years, exposing millions of patient records to privacy preservation threats. All such applications provide access to patients who often have limited control over how their data is preserved, exchanged, and utilized, which increases the concerning factor regarding the ownership of the data and related consent. In this manner, this paper also evaluates the biggest challenge in the current healthcare ecosystem, which is the lack of standardization in terms of communication protocols between different wearables, governmental integration, ministries, and healthcare providers. Various wearable health devices operate and help in continuous health monitoring in real-time, especially to handle data that cannot be modified or tampered with at various steps, such as leading to inaccurate diagnoses and compromised healthcare services. Such type of raising problem becomes the major motivation of this paper. Fig. 3The Steps to Achieve Wearable Data Privacy and Security. The Steps to Achieve Wearable Data Privacy and Security. On the other side, wearable healthcare technologies generate massive amounts of real-time data, which not only requires efficient preservation but needs dynamic processing, along with analytics. Undoubtedly, the classical centralized systems struggle with scalability problems, latency, and high computational costs integrated with organizing large-scale health records. In addition, existing healthcare platforms often prioritize institutional control over patient data, which limits patient autonomy in managing their health records. The primary motivation for this research stems from the urgent requirement to overcome current challenges in wearable health monitoring systems by collaborating with BT-enabled solutions, as shown in Fig. 3. In order to make it more reliable in terms of privacy preservation, security, interoperability, and scalability, BT-enabled wearable technologies have the potential to redefine the futuristic need regarding personalized healthcare and remote patient monitoring, as shown in Fig. 3. Due to evaluating these highlighting prospects, this paper critically addressed the list of research questions mentioned as follows: Research Question #1: How can we evaluate the most effectiveness regarding the cryptographic techniques for ensuring privacy protection, preservation security, and control access reliability in BT-enabled healthcare data exchange?Research Question #2: What impact did the system receive while integrating the edge computing and BT on the real-time process?Research Question #3: What challenges are going to receive while implementing BT interoperability standards across different healthcare institutes and the role of IoT? Research Question #1: How can we evaluate the most effectiveness regarding the cryptographic techniques for ensuring privacy protection, preservation security, and control access reliability in BT-enabled healthcare data exchange? Research Question #1: How can we evaluate the most effectiveness regarding the cryptographic techniques for ensuring privacy protection, preservation security, and control access reliability in BT-enabled healthcare data exchange? Research Question #2: What impact did the system receive while integrating the edge computing and BT on the real-time process? Research Question #2: What impact did the system receive while integrating the edge computing and BT on the real-time process? Research Question #3: What challenges are going to receive while implementing BT interoperability standards across different healthcare institutes and the role of IoT? Research Question #3: What challenges are going to receive while implementing BT interoperability standards across different healthcare institutes and the role of IoT? Based on the identified current limitations, this paper aims to answer the following questions in the next subsection as follows: Contributions and outline of the study The major contribution of this paper is discussed as follows: This paper design and create a BT-enabled framework for wearable health monitoring that ensures secure, private, an efficient data management.The proposed work implements smart contracts for automated access control, authentication, and secure data exchange.This paper improves privacy preservation, protection, and security using ZKPs to enable verifiable yet confidential integrity while data sharing and exchange.Due to such integrational implication, this solution improves data integrity and system reliability, which helps in achieving 93.33% enhancement in security and trustworthiness.This paper ensures scalability and real-time processing efficiency, which address the limitations of classical centralized frameworks. This paper design and create a BT-enabled framework for wearable health monitoring that ensures secure, private, an efficient data management. This paper design and create a BT-enabled framework for wearable health monitoring that ensures secure, private, an efficient data management. The proposed work implements smart contracts for automated access control, authentication, and secure data exchange. The proposed work implements smart contracts for automated access control, authentication, and secure data exchange. This paper improves privacy preservation, protection, and security using ZKPs to enable verifiable yet confidential integrity while data sharing and exchange. This paper improves privacy preservation, protection, and security using ZKPs to enable verifiable yet confidential integrity while data sharing and exchange. Due to such integrational implication, this solution improves data integrity and system reliability, which helps in achieving 93.33% enhancement in security and trustworthiness. Due to such integrational implication, this solution improves data integrity and system reliability, which helps in achieving 93.33% enhancement in security and trustworthiness. This paper ensures scalability and real-time processing efficiency, which address the limitations of classical centralized frameworks. This paper ensures scalability and real-time processing efficiency, which address the limitations of classical centralized frameworks. The remainder of this paper is aligned and organized as follows: Sect. Related work examines state-of-the-art previously published papers on the topic of BT-enabled healthcare solutions and related developments. Section Mathods and material discusses the methods and material utilized to propose the problem formulation. Section Proposed framework presents the proposed framework and its key components. Along with that, the section discusses experimental outcomes and evaluates the performance of the proposed framework. However, Sect. Implementation challenges and open research issues explores implementation challenges raised during the design and deployment. The list of derivations regarding future research directions is also included. Finally, this paper concludes with the statement of conclusion and future direction in Sect. Conclusion and future direction. Related work The successful integration of wearable IoTs with advanced computing frameworks has been extensively explored in recent years, especially in the field of dynamic monitoring, protected data exchange networks, and BT-enabled healthcare platforms. Nevertheless, current research13–15 often received challenges related to platform interoperability and scalability based. The next two sections highlight the reviews, where the key research studies related to wearable health monitoring and remote patient care and BT-enabled public network architecture for secure healthcare data management are mentioned. In this investigation, this paper evaluates the criteria of privacy-preservation solutions available, the functioning of smart contracts, and cryptographic updates, like the NuCypher Threshold Re-Encryption Mechanism and their associations. Wearable health monitoring and remote patient care Undoubtedly, IoT-enabled wearable health monitoring devices, like nano-biosensors, smartwatches, and implantable gadgets have transformed personalized healthcare by enabling continuous health monitoring, early diagnoses, and dynamic data transmission to ministry of health, along with healthcare industries. According to16, wearable devices of healthcare have significantly enhanced remote monitoring ad patient care up to trice and reduced hospital readmissions by over 33%, especially for patients with chronic diagnosis, like diabetes, cardiovascular diseases, and hypertension. On the other side, various studies indicate that data protection, privacy vulnerabilities, and interoperability remain the main limitations in current IoT-enabled wearables16,17. The reliance on a centralized cloud-based environment for patient record preservation and processing that are exposes wearable health data to cyberattacks, single point of failure, and reliable access control. The paper18 highlighted that more than 70% of healthcare wearable applications lack adequate encryption, making them susceptible to data breaches. Such limitations necessitate the adoption of a BT-enabled platform for decentralized, secure, and forged-resistant health data organizations. The successful selection of a BT network in real-time healthcare monitoring requires high throughput, scalable architectures, and low latency18,19. Classical public networks of blockchain, like Bitcoin and Ethereum, still struggle with high consumption of power and transactional bottlenecks, making them unsuitable for wearable health applications. One of the solutions is explored by19, where consensus protocols and Layer-2 solutions improve BT performance. The paper20 proposed a Delegated Proof-of-Stake and Proof-of-Stake consensus mechanism, which reduces transactional cost in terms of time of validation down to 40% while maintaining information security. In a similar manner, the paper21 created a lightning consortium network based on off-chain processing hierarchy, which reduced BT-enabled transaction latency to 60% in wearable health data transmission. Nevertheless, despite such developments, this paper highlights the challenges are remaining in current development, like energy efficiency, network congestion, and BT-enabled DApp adoption in limited resource-constrained environment. Moreover, various research is focused on the creation of lightweight consensus protocols, and AI-driven data organization and optimization hierarchies to improve BT scalability for wearable healthcare applications20–22. Blockchain-enabled public network architecture for secure health data management BT has been widely explored in healthcare to improve data integrity, privacy, and protection preservation. The nature of decentralization and immutability of BT ensures the healthcare records confidentiality, along with transparency and remain tamper-proof and auditable23. And so, it reduces fraudulence activities in medical research, insurance claims, and patient health record organization and optimization. However, the paper23,24 proposed a BT-enabled electronic health record application that demonstrated a 90% plus improvement in terms of data integrity and a 42% reduction in unauthorized data access compared to other classical centralized cloud-enabled storage. In a similar manner, the paper25 developed a private permissioned BT framework using Hyperledger Technology (HT) for secure patient data exchange, achieving an increase in transaction efficiency by 35% while maintaining robust security protocols. On the other hand, Blockchain-enabled healthcare solutions face performance-related and scalability-based limitations, especially when handling large amounts of real-time wearable health records. The paper26 highlighted that high transaction latency and computational overhead are still key problems to BT adoption in real-time healthcare monitoring prospects. However, a major concern in BT-enabled healthcare applications is privacy preservation and protection. As publicly accessible BT may expose sensitive patient information. The paper27 discussed different privacy-enhancement solutions, like homomorphic encryption, multi-party computation, and ZKPs related in order to enable secure yet verifiable data exchange processes. Mathods and material To oversee and distribute data storage and processing in real-time, a decentralized BT infrastructure is being developed. In addition, it maintains low latency while reducing the existing transactional constraints, such as node-enabled block-based data management. The combination of ZKPs validation hierarchy with BT-based off-chain storage solution further aids in scaling and quick action controls. Because of the improved efficiency, interoperability, and data integrity through wearable IoT devices, the DApp is now more dependable. This proposed solution empowers patients with greater control over their own data which can significantly improve engagement, adherence, and trust to medical treatments. However, the association of the self-sovereign identity method and decentralized identity management helps in access control during the verification of patient requests for permission. It revokes data exchange rights, along with ensuring full integrity and transparency in overall healthcare transactions. The performance of this work is assessed by testing the suggested solution across various datasets while maintaining the general criteria of transactional scheduling, delivery, block management, ledger management, optimization, scaling, throughput fluctuation, and latency. The following is listed in the list of datasets: Dataset #1: IoT-Healthcare Security Dataset (Link: https://www.kaggle.com/datasets/faisalmalik/iot-healthcare-security-dataset). This dataset proposed by Kaggle with more than 1000 + data points from more than a dozen of interconnected devices.Dataset #2: Healthcare_IoT_Data (Link: https://www.kaggle.com/datasets/ziya07/healthcare-iot-data). This dataset is also proposed by Kaggle with more than of 3000 + data points from more than 10 interconnected IoT-devices.Dataset #3: IoT-Healthcare-Security-Data (Link: https://github.com/imfaisalmalik/IoT-Healthcare-Security-Dataset). This dataset is proposed by GitHub in 2022–2024 with more than of 10,000 data points from more than 50 + interconnected IoT devoices.Dataset #4: CIC IoMT Dataset 2024 (Link: https://www.unb.ca/cic/datasets/iomt-dataset-2024.html). This dataset is proposed in accordance with the American Standards with more than 5000 + data iterations regarding the IoT-enabled medical wearable devices, which is more than 20 + units. Dataset #1: IoT-Healthcare Security Dataset (Link: https://www.kaggle.com/datasets/faisalmalik/iot-healthcare-security-dataset). This dataset proposed by Kaggle with more than 1000 + data points from more than a dozen of interconnected devices. Dataset #1: IoT-Healthcare Security Dataset (Link: https://www.kaggle.com/datasets/faisalmalik/iot-healthcare-security-dataset). This dataset proposed by Kaggle with more than 1000 + data points from more than a dozen of interconnected devices. Dataset #2: Healthcare_IoT_Data (Link: https://www.kaggle.com/datasets/ziya07/healthcare-iot-data). This dataset is also proposed by Kaggle with more than of 3000 + data points from more than 10 interconnected IoT-devices. Dataset #2: Healthcare_IoT_Data (Link: https://www.kaggle.com/datasets/ziya07/healthcare-iot-data). This dataset is also proposed by Kaggle with more than of 3000 + data points from more than 10 interconnected IoT-devices. Dataset #3: IoT-Healthcare-Security-Data (Link: https://github.com/imfaisalmalik/IoT-Healthcare-Security-Dataset). This dataset is proposed by GitHub in 2022–2024 with more than of 10,000 data points from more than 50 + interconnected IoT devoices. Dataset #3: IoT-Healthcare-Security-Data (Link: https://github.com/imfaisalmalik/IoT-Healthcare-Security-Dataset). This dataset is proposed by GitHub in 2022–2024 with more than of 10,000 data points from more than 50 + interconnected IoT devoices. Dataset #4: CIC IoMT Dataset 2024 (Link: https://www.unb.ca/cic/datasets/iomt-dataset-2024.html). This dataset is proposed in accordance with the American Standards with more than 5000 + data iterations regarding the IoT-enabled medical wearable devices, which is more than 20 + units. Dataset #4: CIC IoMT Dataset 2024 (Link: https://www.unb.ca/cic/datasets/iomt-dataset-2024.html). This dataset is proposed in accordance with the American Standards with more than 5000 + data iterations regarding the IoT-enabled medical wearable devices, which is more than 20 + units. Notations and problem formulations In order to justify the novelty of the proposed work, a blockchain-enabled wearable healthcare monitoring solution, we define key parameters, mathematical tunning, and security formulations. The list of formal definitions of utilized notations is discussed as follows (as mentioned in Table 1): Table 1Notations and related Explanation.NotationsExplanationUiNumber of Users wearing a health monitoring devices, such as smartwatchDiGeneration of health dataBCNetwork of BTSCDesign of smart contractAauthAuthorized entitiesPtxProcessing of transactionsTbcTime to process the transactionCencTotal cost of computation while doing encryptionH(D)Applied hash functionSigmaDigital signatureKKey generation for cryptographySBCTotal storage cost.ZKPZero-Knowledge Proof Table 1Notations and related Explanation.NotationsExplanationUiNumber of Users wearing a health monitoring devices, such as smartwatchDiGeneration of health dataBCNetwork of BTSCDesign of smart contractAauthAuthorized entitiesPtxProcessing of transactionsTbcTime to process the transactionCencTotal cost of computation while doing encryptionH(D)Applied hash functionSigmaDigital signatureKKey generation for cryptographySBCTotal storage cost.ZKPZero-Knowledge Proof Notations and related Explanation. However, the health data ‘D’ is encrypted using H(D) before adding it to the blockchain, is defined as follows:1\documentclass[12pt]{minimal} \usepackage{amsmath} \usepackage{wasysym} \usepackage{amsfonts} \usepackage{amssymb} \usepackage{amsbsy} \usepackage{mathrsfs} \usepackage{upgreek} \setlength{\oddsidemargin}{-69pt} \begin{document}$$\:H\left(D\right)=SHA\left(D\right)$$\end{document} where SHA = 256 bits. This ensures data confidentiality and integrity, along with prevents tampering. The transaction ‘t’ that includes the encrypted data is then signed using a digital signature:2\documentclass[12pt]{minimal} \usepackage{amsmath} \usepackage{wasysym} \usepackage{amsfonts} \usepackage{amssymb} \usepackage{amsbsy} \usepackage{mathrsfs} \usepackage{upgreek} \setlength{\oddsidemargin}{-69pt} \begin{document}$$\:sigma=Digital\:Signature\:(K,\:H(D\left)\right)$$\end{document} where K is the key generation as private key of the user. However, the transaction is verified by an authorized node ‘Aauth’ using the following criteria (as illustrated in Fig. 4):3\documentclass[12pt]{minimal} \usepackage{amsmath} \usepackage{wasysym} \usepackage{amsfonts} \usepackage{amssymb} \usepackage{amsbsy} \usepackage{mathrsfs} \usepackage{upgreek} \setlength{\oddsidemargin}{-69pt} \begin{document}$$\:Verification\:(sigma,\:H\left(D\right),\:K(public)$$\end{document} If the verification succeeds, the transaction is added to the blockchain ‘BD’ using the designed private network. On the other side, a smart contract ‘SC’ is designed, implemented, and deployed to manage data access permissions. The access control function is elaborated as follows (as illustrated in Fig. 4): Fig. 4Healthcare Records Management and Verification. 4\documentclass[12pt]{minimal} \usepackage{amsmath} \usepackage{wasysym} \usepackage{amsfonts} \usepackage{amssymb} \usepackage{amsbsy} \usepackage{mathrsfs} \usepackage{upgreek} \setlength{\oddsidemargin}{-69pt} \begin{document}$$\:Access\:\left(U,\:Aauth\right)=\left\{1,\:if\:Aauth\:has\:valid\:access\:right,\:0\:otherwise\right\}$$\end{document} Healthcare Records Management and Verification. Whereas the transaction processing probability is modeled as a function of blockchain designed network congestion and processing energy in accordance with the following prospect (as shown in Fig. 4):5\documentclass[12pt]{minimal} \usepackage{amsmath} \usepackage{wasysym} \usepackage{amsfonts} \usepackage{amssymb} \usepackage{amsbsy} \usepackage{mathrsfs} \usepackage{upgreek} \setlength{\oddsidemargin}{-69pt} \begin{document}$$\:Ptx=\left\{\right(N*tx\left(confirmed\right)\left)*\right(N*tx\left(total\right)\left)\right\}$$\end{document} where N * tx(confirmed) = the number of successfully confirmed transactions and N * tx(total) = the total number of submitted transactions. In order to ensure privacy, this paper implement ZKP authentication without revealing sensitive data. Given a statement ‘S’, like users are authorized, the prover ‘P’ and verifier ‘V’ interact, is defined as follows:6\documentclass[12pt]{minimal} \usepackage{amsmath} \usepackage{wasysym} \usepackage{amsfonts} \usepackage{amssymb} \usepackage{amsbsy} \usepackage{mathrsfs} \usepackage{upgreek} \setlength{\oddsidemargin}{-69pt} \begin{document}$$\:ZKPs\left(P,\:V,\:S\right)\to\:Prover$$\end{document} While generation of data from wearable is designed as follows:7\documentclass[12pt]{minimal} \usepackage{amsmath} \usepackage{wasysym} \usepackage{amsfonts} \usepackage{amssymb} \usepackage{amsbsy} \usepackage{mathrsfs} \usepackage{upgreek} \setlength{\oddsidemargin}{-69pt} \begin{document}$$\:D*ZKPs\left(P,\:V,\:S\right)\to\:Prover$$\end{document} Conversely, the total cost of preservation for adding a transaction to the BT is defined as follows:8\documentclass[12pt]{minimal} \usepackage{amsmath} \usepackage{wasysym} \usepackage{amsfonts} \usepackage{amssymb} \usepackage{amsbsy} \usepackage{mathrsfs} \usepackage{upgreek} \setlength{\oddsidemargin}{-69pt} \begin{document}$$\:SBC=storage\:size+size\:of\:digital\:signature+hash\:encryption+metadata\:for\:transaction\:execution$$\end{document} Whereas the load of computation and their consumption while transactions are executing, along with hash calculation is mentioned as follows:9\documentclass[12pt]{minimal} \usepackage{amsmath} \usepackage{wasysym} \usepackage{amsfonts} \usepackage{amssymb} \usepackage{amsbsy} \usepackage{mathrsfs} \usepackage{upgreek} \setlength{\oddsidemargin}{-69pt} \begin{document}$$\:Cenc=Cost\:of\:Encryption\:\left(CoE\right)+Cost\:of\:Computing\left(CoC\right)$$\end{document} In order to maintain untampered data management, we design the proposed solution as per the following criteria:10\documentclass[12pt]{minimal} \usepackage{amsmath} \usepackage{wasysym} \usepackage{amsfonts} \usepackage{amssymb} \usepackage{amsbsy} \usepackage{mathrsfs} \usepackage{upgreek} \setlength{\oddsidemargin}{-69pt} \begin{document}$$\:\mathrm{P}\mathrm{r}\mathrm{o}\mathrm{b}\mathrm{a}\mathrm{b}\mathrm{i}\mathrm{l}\mathrm{i}\mathrm{t}\mathrm{y}\:\mathrm{I}\mathrm{n}\mathrm{t}\mathrm{e}\mathrm{r}\mathrm{a}\mathrm{c}\mathrm{t}\mathrm{i}\mathrm{o}\mathrm{n}\:\left(\mathrm{P}\mathrm{I}\right)=1-\mathrm{P}\mathrm{r}\mathrm{o}\mathrm{b}\mathrm{a}\mathrm{b}\mathrm{i}\mathrm{l}\mathrm{i}\mathrm{t}\mathrm{y}\:\mathrm{T}\mathrm{a}\mathrm{m}\mathrm{p}\mathrm{e}\mathrm{r}\mathrm{i}\mathrm{n}\mathrm{g}\:\left(\mathrm{P}\mathrm{T}\right)$$\end{document} For managing data immutability, the equation is defined as follows: 11\documentclass[12pt]{minimal} \usepackage{amsmath} \usepackage{wasysym} \usepackage{amsfonts} \usepackage{amssymb} \usepackage{amsbsy} \usepackage{mathrsfs} \usepackage{upgreek} \setlength{\oddsidemargin}{-69pt} \begin{document}$$\:Probability\:Tamper=0\:\left|\:Probability\:Tamper=1\:\right|PI$$\end{document} The BT-enabled transaction confirmation time ‘Tbc’ depends on the number of network nodes ‘N’, block ‘B’, block size ‘BS’ and transaction rate ‘Rtx’.12\documentclass[12pt]{minimal} \usepackage{amsmath} \usepackage{wasysym} \usepackage{amsfonts} \usepackage{amssymb} \usepackage{amsbsy} \usepackage{mathrsfs} \usepackage{upgreek} \setlength{\oddsidemargin}{-69pt} \begin{document}$$\:Tbc=\left\{BS*Ttx\right\}*N$$\end{document} A larger number of nodes enhances security but increases transactions time. Optimizing consensus mechanism of PBFT reduces ‘Tbc’. By integrating ZKPs, such improvement in privacy preservation can be represent as follows:13\documentclass[12pt]{minimal} \usepackage{amsmath} \usepackage{wasysym} \usepackage{amsfonts} \usepackage{amssymb} \usepackage{amsbsy} \usepackage{mathrsfs} \usepackage{upgreek} \setlength{\oddsidemargin}{-69pt} \begin{document}$$\:ZKPs=\left(D*Protected\:\:\left(hash\right)\right\}*\left\{D*Total\right\}*\left\{100*Processes\right\}$$\end{document} As a result, the proposed method shows a 93.33% improvement in privacy protection using ZKPs for dependable and lightweight authentication. Proposed framework Figure 5 shows how the anticipated procedure in the suggested framework for utilizing ZKPs and smart contracts in wearable healthcare for secure remote monitoring using smart watches and personalized healthcare is carried out. Four distinct information technology (IT) opportunities are integrated into the architecture of the proposed framework: BT, IoT-enabled medical devices, preservation units and processing, and communication amongst involved parties for customization. By integrating the cost-effective InterPlanetary File Storage (IPFS) system, this innovative solution offers customers a simple authentication method in the BT network that is more dependable in terms of security and privacy preservation. Fig. 5The Proposed Framework. The Proposed Framework. In order to get the secure access and permission verification, the environment of participating stakeholders is made separated, where ZKPs is integrates for create a lightweight authentication process for stakeholder enrollment and grant access, as shown in Fig. 5. The process of ZKPs is defined as follows: The interaction between the prover (P) and verifier (V) given a statement (S), such as that users are authorized, ZKPs (P, V, S) → Prove. Table 2 discusses the wearable data generating design, D→ Prover *ZKPs (P, V, S). Figure 6 illustrates how such an intercommunication request is transferred from the off-chain channel (also known as an explicit transaction). Conversely, the processing unit and preservation are positioned as the middleware, and all logs are kept in storage (stored as immutable records in IPFS) for ongoing monitoring and analysis. Figure 6 illustrates how these logs are gathered via IoT-enabled healthcare devices, primarily smart watches, omnipresent data collecting, and other sensor linkages through DApp. On-chain channel implication, which is utilized for implicit data transfer, makes all of this intercommunication possible. Figure 5 illustrates how each node communicates in the blockchain public network architecture as a block-based schedule medical transaction. These transactions are hash encrypted and arranged chronologically with a 4 MB block size to make transmission lighter. The role of transaction processor is critical, it manage fault tolerance, along with the probability of lead and candidate node selection in the following criteria: the definition of the total preservation cost for adding a transaction to the BT: SBC is equal to storage size plus digital signature size plus hash encryption plus transaction execution metadata. On the other hand, hash calculation and the computational load and consumption during transaction execution are described as follows: Cost of Computing (CoC) + Cost of Encryption (CoE) = Cenc. The following parameters are taken into consideration when designing the suggested approach to ensure untainted data management: Interaction Probability (PI) = 1.-Tampering with probability (PT). It is used to manage data immutability: Probability Tamper = 0 | Probability Tamper = 1 | PI. The number of network nodes (N), block size (B), transaction rate (Rtx), and block size (BS) all affect the BT-enabled transaction confirmation time (Tbc): Tbc is equal to {BS * Ttx} * N. Fig. 6Working Steps of the Proposed Solution. Working Steps of the Proposed Solution. In terms of using smart contracts and ZKPs in wearable healthcare for safe remote monitoring and personalized treatment, this integration produces innovative applicational results. Therefore, increase patient interaction by learning about their health activities in order to diagnose and treat them further. Table 2Smart contract Implementation.Important Key Assumption:• At each step of the process, the BT-enabled wearable connectivity, where the specialist/expert or the patient/consultant is in charge of generating/requesting scheduled transactions.• Following validation and verification, the expert can add new authentications to the proposed BT-enabled wearable connection for IoMT availed medical things and schedule transactional requests.Data Input: Int main(): File[new]-> A[a.txt]File[new]-> IoMT (authentication/registration of IoMT devices)File[read/write]-> BT-wearable (processes that enable the edge)Read/write file -> save (IPFS)Initialization and Declaration:DApp processing; EP();cloud storage, CS();update exchange, UE();transaction block size, TBS();devices registration, DR();stakeholder registration, SR();IoMT transaction, IoMTT();on-chain preservation (implicit), OCT();off-chain preservation (explicit), OfCT();new authentication records with ZKPs, NAR();update authentication records, UAR();timestamp for blockchain, [execute];Procedures for Working Operations:if DR() is not = true, check and validate the request; if so, add a new DR and record SR(); and, exchange logs;if IoMTT() = = to start the transaction and schedule, then executions are recorded = NAR();Consensus queries: lightweight APBFT() rules;For the transaction block = = BoT -> 4 MB (Block-Based Medical Data Transmission);Working:• The transaction channels are OCT (implicit) and OfCT (explicit);• The approval of an updated transaction by a digital signature• 51% of the votes must be cast in order for the transaction to be updated.• Blockchain gateways = = decentralized interoperable consortium• The nodes are organized in chronological order.• Proxy (C1-> C2) = = Hash Encryption FunctionActor Role:• Patient (s)• Consultant (s)• Medical staff (s)• Hospital• Ministry of Health• BDLT Expert (maintaining fault tolerance) Table 2Smart contract Implementation.Important Key Assumption:• At each step of the process, the BT-enabled wearable connectivity, where the specialist/expert or the patient/consultant is in charge of generating/requesting scheduled transactions.• Following validation and verification, the expert can add new authentications to the proposed BT-enabled wearable connection for IoMT availed medical things and schedule transactional requests.Data Input: Int main(): File[new]-> A[a.txt]File[new]-> IoMT (authentication/registration of IoMT devices)File[read/write]-> BT-wearable (processes that enable the edge)Read/write file -> save (IPFS)Initialization and Declaration:DApp processing; EP();cloud storage, CS();update exchange, UE();transaction block size, TBS();devices registration, DR();stakeholder registration, SR();IoMT transaction, IoMTT();on-chain preservation (implicit), OCT();off-chain preservation (explicit), OfCT();new authentication records with ZKPs, NAR();update authentication records, UAR();timestamp for blockchain, [execute];Procedures for Working Operations:if DR() is not = true, check and validate the request; if so, add a new DR and record SR(); and, exchange logs;if IoMTT() = = to start the transaction and schedule, then executions are recorded = NAR();Consensus queries: lightweight APBFT() rules;For the transaction block = = BoT -> 4 MB (Block-Based Medical Data Transmission);Working:• The transaction channels are OCT (implicit) and OfCT (explicit);• The approval of an updated transaction by a digital signature• 51% of the votes must be cast in order for the transaction to be updated.• Blockchain gateways = = decentralized interoperable consortium• The nodes are organized in chronological order.• Proxy (C1-> C2) = = Hash Encryption FunctionActor Role:• Patient (s)• Consultant (s)• Medical staff (s)• Hospital• Ministry of Health• BDLT Expert (maintaining fault tolerance) Smart contract Implementation. Important Key Assumption: • At each step of the process, the BT-enabled wearable connectivity, where the specialist/expert or the patient/consultant is in charge of generating/requesting scheduled transactions. • Following validation and verification, the expert can add new authentications to the proposed BT-enabled wearable connection for IoMT availed medical things and schedule transactional requests. Data Input: Int main(): File[new]-> A[a.txt] File[new]-> IoMT (authentication/registration of IoMT devices) File[read/write]-> BT-wearable (processes that enable the edge) Read/write file -> save (IPFS) Initialization and Declaration: DApp processing; EP(); cloud storage, CS(); update exchange, UE(); transaction block size, TBS(); devices registration, DR(); stakeholder registration, SR(); IoMT transaction, IoMTT(); on-chain preservation (implicit), OCT(); off-chain preservation (explicit), OfCT(); new authentication records with ZKPs, NAR(); update authentication records, UAR(); timestamp for blockchain, [execute]; Procedures for Working Operations: if DR() is not = true, check and validate the request; if so, add a new DR and record SR(); and, exchange logs; if IoMTT() = = to start the transaction and schedule, then executions are recorded = NAR(); Consensus queries: lightweight APBFT() rules; For the transaction block = = BoT -> 4 MB (Block-Based Medical Data Transmission); Working: • The transaction channels are OCT (implicit) and OfCT (explicit); • The approval of an updated transaction by a digital signature • 51% of the votes must be cast in order for the transaction to be updated. • Blockchain gateways = = decentralized interoperable consortium • The nodes are organized in chronological order. • Proxy (C1-> C2) = = Hash Encryption Function Actor Role: • Patient (s) • Consultant (s) • Medical staff (s) • Hospital • Ministry of Health • BDLT Expert (maintaining fault tolerance) Simulation, results and discussion The list of hardware and software that are used for implementing the proposed solution, is mentioned as follows: The necessary hardware includes: the Intel Iris-Xe, a 13th generation Intel V-Pro processor with a clock speed of 4.2 GHz, and a 4 GB dedicated graphics card. A minimum of 16 GB is required, in addition to a 1 TB SSD and a 2 TB HDD.In order to integrate edge units, additional accessories including cables and connectors are required.However, the present simulations areconducted in a controlled laboratory environment. Software resources and requirements: System software includes Windows 11 Professional, Virtual Box, Hyperledger Docker, and associative extensions like Container and NuCypher. Network requirements and resources include: 4 Mbps is the minimum network bandwidth. The necessary hardware includes: the Intel Iris-Xe, a 13th generation Intel V-Pro processor with a clock speed of 4.2 GHz, and a 4 GB dedicated graphics card. A minimum of 16 GB is required, in addition to a 1 TB SSD and a 2 TB HDD.In order to integrate edge units, additional accessories including cables and connectors are required.However, the present simulations areconducted in a controlled laboratory environment. The necessary hardware includes: the Intel Iris-Xe, a 13th generation Intel V-Pro processor with a clock speed of 4.2 GHz, and a 4 GB dedicated graphics card. A minimum of 16 GB is required, in addition to a 1 TB SSD and a 2 TB HDD.In order to integrate edge units, additional accessories including cables and connectors are required.However, the present simulations areconducted in a controlled laboratory environment. A minimum of 16 GB is required, in addition to a 1 TB SSD and a 2 TB HDD. A minimum of 16 GB is required, in addition to a 1 TB SSD and a 2 TB HDD. In order to integrate edge units, additional accessories including cables and connectors are required. In order to integrate edge units, additional accessories including cables and connectors are required. However, the present simulations areconducted in a controlled laboratory environment. However, the present simulations areconducted in a controlled laboratory environment. Software resources and requirements: System software includes Windows 11 Professional, Virtual Box, Hyperledger Docker, and associative extensions like Container and NuCypher. Network requirements and resources include: 4 Mbps is the minimum network bandwidth. Software resources and requirements: System software includes Windows 11 Professional, Virtual Box, Hyperledger Docker, and associative extensions like Container and NuCypher. Network requirements and resources include: 4 Mbps is the minimum network bandwidth. Fig. 7Simulation Result (1)-Latency Evaluation. Simulation Result (1)-Latency Evaluation. Figure 7 illustrates the simulation test of the proposed BT-enabled healthcare wearable with ZKPs are installed for evaluating the rate of medical data collection from IoT-enabled devices, whose main prospect is to examine the rate of total data transmit/s for the sake of latency check. In this test, we analyze that more than 400 block-based medical data collected (from smartwatch) and transmitted (in the BT-network to consultant), which is 4 MB * 400 = 1600 MB total size, in less than 800/s. Fig. 8Simulation Test (2)-Throughput Test. Simulation Test (2)-Throughput Test. On the other end, the simulation test is done on the evaluation of total throughput received while DApp is running for collecting medical data from the smartwatch, whose rate of total data transmit/s. The total collection and transmission of data to the BT-ledger environment was 400 blocks in the 2000s, which is equal to 0.2 data-blocks/s, as shown in Fig. 8. Similarly, in order to determine the rate at which the DApp collects medical data from the smartwatch, a simulation test was conducted to evaluate the overall computing overhead received throughout its operation. As seen in Fig. 9, the total amount of data collected and transmitted to the BT-ledger environment is 400 blocks in 2500s, resulting in a discrepancy of up to 0.16 data-blocks/s. Fig. 9Simulation Test (3)-Computation Overhead Test. Simulation Test (3)-Computation Overhead Test. In a similar manner the simulation test of the scalability offered by this proposed DApp is shown in Fig. 10, with each block-based medical transaction corresponding to the increment between block-to-block distributions. The outcome varies from 400 block-based data travelling across the environment to 300s, and it can offer twice as much scalability when data from IoT-enabled devices increases. Due to this, The primary performance-related metrics—latency, throughput, computational overhead, security resilience, and scalability—are examined in order to assess the efficacy of the proposed work. With a 99.33% increase in data integrity and protection while running more than 20 iterations on a similar manner, the simulated results of the trial demonstrate the effectiveness of BT integration. Fig. 10Simulation Test (4)- Scalability Test. Simulation Test (4)- Scalability Test. Nevertheless, Fig. 11 shows the outcome of a simulation test called “PP” that is conducted on the proposed BT-enabled ZKPs for healthcare wearable management in order to obtain a strong privacy preservation solution. The evaluation’s metrics include the rate at which medical data is gathered and stored with management and organization per second. We receive over 250 block-based medical data sets that are stored in 788s, ensure that they are properly managed and organized in IPFS, and guarantee complete privacy with no data tampering, alteration, manipulation, or forgery. To get a lightweight authentication, request verification, validation, and security solution, a simulation test named “AS” is performed on the proposed BT-enabled ZKPs for healthcare wearable management. The results are displayed in Fig. 12. The pace at which patients and consultants authenticate, and access verification and validation is one of the evaluation’s KPIs. In less than 2000 s, 293 stakeholders are authenticated and allowed grant access, yielding a total score of 0.146 stakeholders who participated. The proposed BT-enabled ZKPs for healthcare wearable management undergo a simulation test called “AS” in order to obtain an unforged and tamper-proof resistance and security solution. Figure 13 presents the findings. The speed at which every piece of data is examined to ensure that the ledger is secure, that no duplicate, tempering, or manipulation takes place while the transaction is being processed for preservation. Fig. 11Simulation Test (5)- Collected Data Preservation for Further Investigation and Real-Time Monitoring. Simulation Test (5)- Collected Data Preservation for Further Investigation and Real-Time Monitoring. In order to evaluate the effectiveness of the proposed system, we compare the proposed solution with the current state-of-the-art BT-enabled and non-BT-enabled health monitoring frameworks based on the key performance metrics28–32, such as (as mentioned in Tables 3 and 4): Privacy preservation.Security.Scalability.Latency.Computational overhead.Interoperability. Privacy preservation. Privacy preservation. Security. Security. Scalability. Scalability. Latency. Latency. Computational overhead. Computational overhead. Interoperability. Interoperability. Fig. 12Simulation Test (6)- Patients/Consultants Secure Authentication. Simulation Test (6)- Patients/Consultants Secure Authentication. Table 3Comparative analysis (1).MethodsBlockchain Technology UsedSecurityPrivacyScalabilityLatencyComputational OverheadInteroperabilityClassical Cloud-Based Monitoring SystemsNot applicableLowLowHighLowLowHighPublic Network (Permissionless)EthereumHighModerateModerateHighHighModerateThe Proposed Smart Contract-enabled ZKPs Blockchain IntegrationSolidity + ZKPsVery HighVery highHighModerateModerateHigh Table 3Comparative analysis (1).MethodsBlockchain Technology UsedSecurityPrivacyScalabilityLatencyComputational OverheadInteroperabilityClassical Cloud-Based Monitoring SystemsNot applicableLowLowHighLowLowHighPublic Network (Permissionless)EthereumHighModerateModerateHighHighModerateThe Proposed Smart Contract-enabled ZKPs Blockchain IntegrationSolidity + ZKPsVery HighVery highHighModerateModerateHigh Comparative analysis (1). Table 4Comparative analysis (2).MethodsBlockchain Technology UsedSecurityPrivacyScalabilityLatencyComputational OverheadInteroperabilityPrivate Cloud-Based Monitoring SystemsNot applicableLowLowHighLowLowHighHyperledger Technology AssociationHyperledger Fabric, Sawtooth, and BesuHighHighLowLowModerateHighZKPs IntegrationZKPs (applied only for authentication purpose)Very HighVery HighModerateModerateHighLowThe Proposed Smart Contract-enabled ZKPs Blockchain IntegrationSolidity + ZKPsVery HighVery highHighModerateModerateHigh Table 4Comparative analysis (2).MethodsBlockchain Technology UsedSecurityPrivacyScalabilityLatencyComputational OverheadInteroperabilityPrivate Cloud-Based Monitoring SystemsNot applicableLowLowHighLowLowHighHyperledger Technology AssociationHyperledger Fabric, Sawtooth, and BesuHighHighLowLowModerateHighZKPs IntegrationZKPs (applied only for authentication purpose)Very HighVery HighModerateModerateHighLowThe Proposed Smart Contract-enabled ZKPs Blockchain IntegrationSolidity + ZKPsVery HighVery highHighModerateModerateHigh Comparative analysis (2). In order to quantify the effectiveness of the proposed solution, this paper present the key performance enhancement over the classical approaches33–35 as follows (as discussed in Table 5): Table 5Comparative analysis (3).Performance MetricsCurrent Blockchain PlatformsProposed SystemsEnhancement RatioData Privacy85%93.33%Up to 10% improvedLatency20s12sImproved in 40%Computational CostHighModerateImproved in 30%Scalability200+300+Improved in 50% Table 5Comparative analysis (3).Performance MetricsCurrent Blockchain PlatformsProposed SystemsEnhancement RatioData Privacy85%93.33%Up to 10% improvedLatency20s12sImproved in 40%Computational CostHighModerateImproved in 30%Scalability200+300+Improved in 50% Comparative analysis (3). Implementation challenges and open research issues Fig. 13Simulation Test (6)- Tamper-Proof Resistance and Security. Simulation Test (6)- Tamper-Proof Resistance and Security. The proposed BT-enabled framework for IoT-based wearable health monitoring offers improved privacy preservation, security, transparency, integrity, provenance, and scalability; its real-world deployment presents various regulatory, technical, and operational limitations. Such raising limitations must be addressed to ensure effective implementation and adoption as follows: Computational overhead and processing cost BT operations, like cryptographic hashing, encryption, and smart contract execution, require significant computing constraints, such as computational resources (computational power, high network usage, and cost of preservation). Wearable devices often have limited computational processing, which directly affects battery life36–38. It makes continuous BT transactions impractical. However, use off-chain computation for non-critical data and only preserve hashes on-chain to reduce IoT-enabled wearable workload. Along with that, the support of lightweight cryptographic algorithms in order to optimize energy efficiency. On the other side, public permissionless BT like Bitcoin or Ethereum experience high network congestion and slow transaction speed, which not only hinder real-time healthcare monitoring but also create unreliability in terms of efficiency and effectiveness. Processing bulky data from wearable healthcare with BT could increase latency and transaction costs. Compliance with data regulations and privacy Undoubtedly, healthcare data is subject to strict regulatory procedures, such as the Association of General Data Protection Regulation and Health Insurance Portability and Accountability39–41. However, the immutability of BT has created conflicts due to the nature of regulatory requirements for data erasure for the right to be forgotten. Preserving critical healthcare records, such as personal information on a public blockchain could raise privacy concerns. In this manner, only encrypted has-based data can be recorded via on-chain channels, while personal information can be preserved in off-chain storage, especially InterPlanetary File Storage (IPFS). Throughout this, the designed ZKPs are placed to allow data verification without exposure. On the other end, most of the hospitals manage electronic healthcare records via designing applications and use legacy databases that do not support BT. Due to this, integrating a decentralized solution with centralized management systems is critical. In order to achieve this, develop standardization regarding APIs for seamless communication between BT and electronic healthcare systems. Transaction fees and scheduling cost These days, public blockchains like Ethereum demand a hefty gas fee for each transaction, which complicates the ledger update process and makes frequent wearable device data updates costly42–45. Despite this, healthcare data is constantly updated, which not only results in constant generation but also raises transaction costs, which affects ledger management. The application of Layer-2 architecture, such as Polygon, which lowers petrol expenses, is one of the possibilities. Furthermore, sidechains have the potential to handle these health-related transactions off-chain, or off to the main blockchain. Conversely, wearable technology and BT-nodes can communicate securely by using end-to-end encryption. In order to keep an eye on BT network activity, it is also essential to implement an intrusion detection system in the middle. Conclusion and future direction This paper proposed a BT-enabled IoT-based wearable health monitoring platform that leverages smart contracts and ZKPs to improve scalability, security, and privacy protection. Throughout the analysis of comparison, the proposed solution achieves 93.33% improved privacy, protected preservation, lower latency, and higher scalability with other state-of-the-art methods of BT-enabled healthcare applications, especially consortium and public permissionless network architectures. It is worth noting that ZKPs and smart contracts, two components of blockchain technology (BT), offer a practical means of improving the integrity, provenance, and privacy of wearable health data. For wearable health devices, especially smartwatches with biosensors, this study suggests a BT-enabled system that ensures decentralized, unforged data management, transparency, immutability, and dynamic traceability. The primary performance-related metrics—latency, throughput, computational overhead, security resilience, and scalability—are examined in order to assess the efficacy of the proposed solution. ZKPs ensure verifiable data exchanges without endangering patient privacy, and automated access control methods use smart contracts to show data protection. However, the future development of BT-powered wearable health monitoring can mainly focus on the following key domains: AI-powered BT for predictive healthcare.Federated learning for privacy protection and preservation of health data sharing and exchange.Quantum resistance cryptographic proposal for healthcare data management and security.Interoperability standards for global adoption.The role of 6G and edge computing for real-world health data processing and reliability. AI-powered BT for predictive healthcare. AI-powered BT for predictive healthcare. Federated learning for privacy protection and preservation of health data sharing and exchange. Federated learning for privacy protection and preservation of health data sharing and exchange. Quantum resistance cryptographic proposal for healthcare data management and security. Quantum resistance cryptographic proposal for healthcare data management and security. Interoperability standards for global adoption. Interoperability standards for global adoption. The role of 6G and edge computing for real-world health data processing and reliability. The role of 6G and edge computing for real-world health data processing and reliability.