The Internet of Vehicles (IoV) and privacy-preserving systems Authors: Nabeeha Zahid, Shahzaib Tahir, Fahad Algarni, Hasan Tahir, Saqib Saeed, Adeel M Syed Published: 2026 ABSTRACT AbstractThe Internet of Vehicles (IoV) is changing the contemporary mobility, as it allows real-time communication between vehicles, infrastructure, and cloud services. Nevertheless, such growing connectivity brings on serious privacy, regulatory, and trust issues especially because sensitive behavioral and location information is exposed. The current IoV-security systems tend to be based on identity-based checks, or centralized trust authorities, which can lead to infringement of user privacy and cause surveillance and profiling threats. The paper is inspired by privacy-preserving architectures in the Metaverse to suggest a decentralized trust system of IoV systems on the basis of zero-knowledge proofs, namely zk-SNARKs. The suggested solution allows vehicles to cryptographically verify that they meet regulatory or operational regulations- i.e. valid insurance, safety test, or emissions- without revealing personal identifiers or raw information. The framework enables building scalable, low-latency and audible trusts and following data minimization principles through combining zk-SNARK verification and Layer 2 blockchain solutions.Keywords: Internet of Vehicles (IoV), zk-SNARK, Privacy Preservation, Blockchain, Layer 2 Solutions, Decentralized Trust, Ethical Design, Smart Contracts, Federated Learning, Verifiable ComputationSubject terms: Engineering; Mathematics and computing; Science, technology and society Introduction The Metaverse has been described as the future of convergence of virtual, augmented, and physical worlds where people can engage in immersive digital worlds by controlling their identities using avatars, digital assets, and decentralized infrastructures1. It offers new social, economic, and governance possibilities with the help of undeterred identity, real-time interaction, interoperability, and blockchain-enabled ownership in the infrastructure of digital twin technologies2. Nonetheless, they are the same features that present complicated issues concerning data ownership, privacy protection, and belief building within distributed ecosystems3. The Internet of Vehicles (IoV) is no different as similar structural and ethical issues arise, with vehicles acting as intelligent, networked systems in smart mobility systems. The IoV systems are used to improve road security, autonomous communication, real-time navigation, and proactive maintenance with the help of constant Vehicle to Vehicle (V2V), Vehicle to Infrastructure (V2I), and Vehicle to Network (V2N) communications4. As much as such connectivity enhances operational efficiency it also exposes sensitive behavioral, biometric and location information. The continued identity connection and the centralized compliance checking systems cause concerns about the long-term profiling, surveillance and abuse of personal data5. Trust architectures, which maintain user autonomy but allow verifiable compliance are needed therefore to support ethical and secure IoV deployment. Even though the research on the IoV security is making significant progress, there are some significant limitations of the current methods. A lot of present-day frameworks are based on identity-centric authentication principles according to which vehicles are required to reveal persistent identifiers to find a common language. Others rely on the centralized certificate authority or some trusted third parties which pose scalability point and single point of failure6. IoV systems based on blockchain enhance the level of transparency and resistance to tampering, but they usually demand the partial or complete disclosure of transaction metadata to validate transactions, which weakens the privacy guarantees. These solutions demonstrate a major void: the existing IoV architectures do not have a mechanism that would allow verifiable regulatory compliance without revealing the identity of vehicles or confidential operation data7. In an attempt to fill this gap, this paper conceptually informs itself with privacy-preserving mechanisms discussed in the Metaverse and suggest a decentralized, zk-SNARK-based trust system in the context of IoV. Based on previous applications of zero-knowledge proof systems; specifically, Zero-knowledge Succinct Non-Interactive Arguments of Knowledge (zk-SNARKs), in Metaverse security frameworks, the paper suggests a decentralized, privacy-protected trust framework of IoVs settings. The suggested system attempts to empower conditional compliance checking without divulging identities, and helps to provide scalable, auditable and regulation aware trust formation in interconnected vehicular networks. The proposed framework can be used to facilitate scalable, auditable, and low-latency, trust-establishment using zk-SNARK verification and Layer 2 blockchain infrastructures, and comply with the principles of data minimization (Fig. 1). Overlap of privacy and trust issues in metaverse and IoV. The authors investigate the following goals: To come up with a privacy preserving IoV trust architecture that will permit compliance checks without identity revelation. To come up with a privacy preserving IoV trust architecture that will permit compliance checks without identity revelation. To examine the viability and performance of implementation of zk-SNARK-based proofs in real-time automobile environments with Layer 2 blockchain solutions. To examine the viability and performance of implementation of zk-SNARK-based proofs in real-time automobile environments with Layer 2 blockchain solutions. In order to incorporate ethical and regulatory design concepts in the technical architecture, it is essential to make sure that it aligns with the data protection framework and forms trust that is mindful of fairness. In order to incorporate ethical and regulatory design concepts in the technical architecture, it is essential to make sure that it aligns with the data protection framework and forms trust that is mindful of fairness. The paper is structured in the following way. Section 2 provides an in-depth literature review of the topic of privacy, trust, and security concerns in IoV systems and Metaverse, including blockchain and zero-knowledge technologies. Section 3 presents the system model and architecture, the adaption of zk-SNARK-based verification mechanisms of the Metaverse identity systems to IoV systems. Section 4 deals with regulatory and ethical aspects, which have to do with privacy, consent and accountability in data-driven vehicular networks. Section 5 outlines the suggested structure and end-to-end workflow, i.e. proof generation, on-chain verification and conditional access control. Part 6 examines performance, scalability, and feasibility factors, especially when it comes to the Layer 2 blockchain implementation. Section 7 addresses the ethical design principles, Section 8 and 9 sum up the paper and provide the direction of the future research. Literature review This literature review critically analyzes the previous literature on privacy and trust in the Internet of Vehicles (IoV) and the Metaverse, which are two data-intensive, real-time ecosystems that have similar issues of surveillance, profiling, identity exposure, and regulatory compliance. Although the current researches have achieved significant milestones in achieving communications security and enhancing transparency by using blockchain and cryptographic tools, they still usually fail in achieving verifiable trust without infringing user privacy. This review is structured into four thematic areas, including privacy and trust in the IoV, security and privacy in the Metaverse, zk-SNARKs and attribute privacy, and gaps that remain unresolved which justify the offered framework. Security and privacy in the metaverse Security and privacy issues of the Metaverse are similar to those of IoV because they are based on real-time communication, decentralized networks, and sustained digital identities. Chen et al. and others stressed that privacy computing is a precondition of the Metaverse, and that centralized verification models are unsustainable rather than a solution since they compromise the autonomy of the user, and was the critic of the latter. Nonetheless, their taxonomy is effective in grouping together privacy threats, although it does not go further to suggest any specific, practical cryptographic enforcement systems8. Systemic risks were also outlined in the study by Fernandez and Hui3, where systemic risks like surveillance capitalism and lack of sufficient accountability in virtual space were recognized as problematic areas of governance and ethics in the virtual world. Kang et al.9 have also cautioned that the existing Metaverse applications do allow profiling on a very large scale because identity and actions are closely coupled. Although Gupta et al.10 has suggested a Zero Trust Architecture to be used in Metaverse settings, the model that they have offered still presupposes the precaution of constant authentication and surveillance, which could contradict the principles of privacy-by-design. Survey studies by Huang et al.11 and Huynh-The et al.12 identified blockchain as an important enabler of decentralized trust in their survey studies, but presented the outstanding tension between transparency and privacy as identity information is stored on-chain. Taken together, the works indicate that even though the Metaverse literature is highly sensitive to the dangers of privacy, the available solutions are either still at the concept phase or lack decoupling identity and compliance checking. zk-SNARKs and attribute privacy The zk-SNARKs (Zero-Knowledge Succinct Non-Interactive Arguments of Knowledge) has become one of the most promising cryptographic primitives that may be able to overcome the trust-privacy trade-off. Di Francesco Maesa et al.13 have shown how zk-SNARKs can be used to enable attribute-based access control in self-sovereign identity systems to enable users to verify the claims of credentials without disclosing underlying data. They are useful but are mainly concerned with access control situations and not with real time and continuous compliance controls. Sarang, Alawami, and Park2 examined the issue of security threats in commercial off-the-shelf (COTS) Metaverse applications by deploying avatar-based honeypots and cautioned that there is a significant risk of privacy and behavioral data exposure in immersive digital settings. Their paper has shown that the data of user interaction can be abused in a virtual ecosystem, thus necessitating privacy-saving verification systems in cyber-physical systems. In the IoV domain, Liu, Pan, and Chen14 suggested a hierarchical blockchain-based threat assessment architecture in the IoV area, but they did not discuss the issue of threat verification without exposing sensitive vehicles or driver information. All of these studies identify the theoretical appropriateness of zero-knowledge proofs, although none of them realizes them in scalable, latency-sensitive IoV trusts. Recent advances in federated learning for IoT decision-making In recent studies, the issue of how to improve trust, privacy, and efficiency in edge systems built based on IoT on Federated Learning (FL) has been addressed. In their work, Rehman et al.15 suggested the Trust-Oriented Federated Learning Framework of IoT (TOFL-IoT) that provides a combination of FL and a multi-level trust assessment system to realize a set of reliable, scalable, and privacy-safe consumer electronics decision-making processes. In simulations with 100 IoT devices and 10 edge servers, TOFL-IoT achieved up to 92.2% model accuracy, demonstrated resilience under high device dropout rates (84.5%) and adversarial conditions (87.6%), and reduced communication overhead by 20% relative to baseline approaches. Privacy preservation remained robust across varying scenarios. Similarly, Tariq et al.16 presented a lightweight and reliable FL architecture to support resource-constrained Edge-IoT settings. They use a combination of adaptive pruning of models, quantization, and optimization of communication frequency, selective homomorphic encryption, and verifiable model trust assessment. Experiments showed high efficiency of communication, strong convergence and high accuracy when using different network and computation constraints. These papers point to practical solutions to trust-conscious, privacy-sensitive edge decision making, dealing with the heterogeneity of devices, lack of reliable networks, and adversarial threats. Such solutions integrated into the IoV scenarios supplement the zk-SNARK-based systems, thus enhancing the real-time verification of compliance at the cost of user privacy. Gaps and future directions Although a lot of research has it been done on blockchain-based security, privacy-sensitive compliance checking in the IoV system and in the Metaverse is an unexplored field. Current research in the field of the IoV is mainly aimed at secure data transmission, reputation systems, or trust-based coordination, which commonly presupposes persistent identities or trusted third-parties4,14,17,18, although the latest developments in federated learning of IoT suggest that they present promising solutions to distributed decision-making with privacy consideration, such solutions are not yet built into latency-aware, real-time IoV systems15,16. On the other hand, a substantial body of literature exists on privacy risks and ethical issues in Metaverse research studies, but often lacks practical cryptographic mechanisms that can balance accountability with anonymity8. Though zk-SNARKs theoretically prove to be powerful, there is a lack of integration of zk-SNARKs into real-time, decentralized trust architectures, especially in IoV settings. The synergistic nature of this gap is what drives the current study which proposes an implementation of an IoV using zk-SNARKs based on real-life applications of privacy-sensitive design in the Metaverse and novel approaches to trust-sensitive IoT12,13. System model This part provides a system model of privacy-preserving trust over the Internet of Vehicles (IoV) based on architecture ideas and implementation experiences with zk-SNARK-based security deployments in the Metaverse. Based on previous experience with ZoKrates-based circuit design and Solidity-based verifier contracts, the given model implements privacy-enabling cryptographic mechanisms that were originally devised in the virtual environment into vehicles, which share a set of similarities with regards to real-time decision-making, scale, and regulatory adherence. Although the framework is conceptual in form, it is based on practical implementation requirements to implementations in the Metaverse, which enables the naturalization of realistic assumptions about the feasibility, latency tolerance, and cryptographic overhead in the IoV context. Transfer of security principles from the metaverse to IoV The security issues experienced in Metaverse systems, such as unauthorized data disclosure, integrity risks of decentralized transactions, and bottlenecks problems, are similar to those experienced in IoV environments. zk-SNARKs were used in Metaverse implementations to check user attributes (e.g. age or eligibility to access) without exposing sensitive personal information, and as such promote trust without identity being constantly exposed. These principles are applied to the systems of the Internet of Vehicles so that vehicles could cryptographically verify their adherence to the rules or conditions of operation (e.g., have appropriate insurance, be emitted properly, be inspected, etc.) without revealing their identity, location history, or behavioral records. It is also applicable to IoV in the application of this adaptation, wherein there are tight privacy and latency requirements where frequent verification is necessary. The conceptual framework design involves designing the framework to be followed during the study process. Conceptual framework design The suggested framework consists of the following entities: Prover (Vehicle): Class triggers the creation of zk-SNARK proofs by a local method on circadian means, through on-vehicle resources. Prover (Vehicle): Class triggers the creation of zk-SNARK proofs by a local method on circadian means, through on-vehicle resources. Verifier (Roadside Unit or Smart Contract): Roadside verifier gatheringProofs using smart-contracts on L2 blockchain infrastructure. Verifier (Roadside Unit or Smart Contract): Roadside verifier gatheringProofs using smart-contracts on L2 blockchain infrastructure. Blockchain Network (e.g., Polygon): Proof verification results and minimal metadata are logged (blockchain Network) in such a way that they can be audited and the exposure of data on the chain is minimal. Blockchain Network (e.g., Polygon): Proof verification results and minimal metadata are logged (blockchain Network) in such a way that they can be audited and the exposure of data on the chain is minimal. Each transaction is modeled as: The transaction , where is the vehicle ID, is the action, is the timestamp, and is nonce, is encoded. The zk-SNARK proof π for compliance is generated as: And verified via: A rollup mechanism aggregates transactions into a single batch: Adapted experimental setup (from metaverse implementation) Although the IoV prototype is conceptual, it follows this process tested in the real-world: Cryptographic circuit design Based on the ZoKrates circuit used for age verification in the Metaverse (assert (age > 13)), the IoV circuit could assert: zk-SNARK expiry compliance circuit The above algorithm represents a simplified compliance circuit in which the constraint is encoded into a zk-SNARK arithmetic circuit, ensuring that proof generation succeeds only when the regulatory condition holds. Proof generation and verification The generation of proof is done locally on the Trusted Execution Environment (TEE) which is the secure areas of the processors protecting critical data in software of such vehicles, or in the secure processing module. Proof generation versus proof verification Proof generation is computationally expensive, and is necessarily based on computational complexity as it uses the circuit in a specific manner (e.g., content verification with a circuit). zk-SNARK proof generation is computationally expensive and relies on computational complexity as it requires hundreds of milliseconds to a few seconds on embedded processors on lightweight attribute-verification programs (e.g., insurance validity or inspection timestamp checks). Nevertheless, it can be verified much more efficiently and can take a few milliseconds, so it can be used in the real-time validation of smart contracts or the smart devices placed along roads called roadside units (RSUs)6. Increasingly, the hardware security modules and the multi-core ARM-based processors with the capability of executing lightweight cryptography workloads are integrated into the modern automotive Electronic Control Units (ECUs) and Telematics Control Units (TCUs). To simple circuits of compliance with a single boolean predicate, e.g. expiry-date or threshold checking, zk-SNARK generation of proofs can be done with latency constraints of the regulatory or access-control regime (in the range of milliseconds-to-seconds), especially asynchronous before interaction events (e.g., toll entry or zone access). Ultra-safety-critical functions, e.g. collision avoidance functions, are not on-chain and are not within the realm of this cryptography verification layer19. Layer 2 deployment and latency considerations Verifier contracts are presupposed to run on Layer 2 blockchain networks like Polygon, where the rollup techniques, in turn, allow them to be implemented with low-cost and high-throughput validation. This design option is a solution to the latency limitations of safety-adjacent IoV through lowering the block confirmation times, as well as a lack of congestion associated with Layer 1 networks. Although the ultra-safety-critical domain (e.g., collision avoidance) is likely to be off-chain, the suggested framework is adequate for regulatory and access-control decision-making with milliseconds-to-seconds CT. Trusted setup and key management assumptions The model presupposes that the needed parameters of zk-SNARK are generated in a single trusted setup, which is the case with several existing applications. Verification keys are deemed to be publicly accessible, owned and operated by infrastructure entities or control bodies, and proving keys are safely installed in vehicles. Nevertheless, as much as the use of trusted setup brings about governance concerns, this is an assumption of contemporary practical use of zk-SNARKs and is known to be a potential future enhancement with the use of other tools like zk-STARKs. User interaction layer The system is used via vehicle interfaces on board to allow interaction with vehicle users, thereby allowing the cryptographic operation to be abstracted, to provide usability, and to ensure driver distraction is minimized. Such a design resembles user interfaces of Metavarse that manage to hide the cryptographic complexity from the end users. Overall, the proposed system model is designed to ensure: Privacy preservation through zero-knowledge compliance proofs without raw data transmission, Privacy preservation through zero-knowledge compliance proofs without raw data transmission, Scalability via rollups and Layer 2 verification, Scalability via rollups and Layer 2 verification, Integrity and accountability through tamper-evident on-chain logs, Integrity and accountability through tamper-evident on-chain logs, Practical feasibility informed by prior zk-SNARK implementations in Metaverse environments, while explicitly acknowledging computational, latency, and governance constraints. Practical feasibility informed by prior zk-SNARK implementations in Metaverse environments, while explicitly acknowledging computational, latency, and governance constraints. Regulatory and ethical challenges in the internet of vehicles (IoV) With the growth of the IoV ecosystem, vehicles have taken the role of full-fledged elements of a massive, decentralized system. They are constantly sharing information to improve road safety, maximize traffic, and make navigation autonomous. However, this stream of information has created complicated regulatory and ethical dilemmas, especially in the collection process, transverse processing, and subsequent action of the information in terms of personal and behavioral processes11. Some of the areas of concern and how zk-SNARKs could alleviate them include data privacy and consent, decentralized trust, and surveillance risks, as discussed below: Data privacy and consent Challenges Vehicles in IoV systems communicate via Vehicle-to-Vehicle (V2V), Vehicle-to-Infrastructure (V2I), and Vehicle-to-Network (V2N) links. These interactions often involve sharing GPS locations, driving behavior, biometric indicators, and route history. Such data, while necessary for coordination, represents personal identifiable information (PII), increasing the risks of tracking and surveillance6. Ethical and legal implications Decentralized trust systems in which a priority scoring is based on historical data could enhance discrimination against older vehicles or people who cannot obtain enough historical information. Poor labeling will result in denial of service or discrimination in pricing7. Solution direction The zk-SNARKs enable automobiles to exhibit some conditions that can be associated with the emission setup or insurance-in-use without the compromise of data involved. This is quite acceptable with respect to GDPR provisions, which will allow user anonymity and make them less susceptible to the service providers. Decentralized trust and reputation Challenges Vehicles will have to collaborate and trust strangers on the road or infrastructure. Problems with scalability and single point of failure occur with centralized certificate authorities (CAs), whereas reputation systems can become a problem in terms of trust bootstrapping and their manipulation4. Ethical concern Different scoring systems will be biased toward older or statistically underserved vehicles, or people who do not generate enough historical data because they trust decentralized systems. This labeling malpractice may result in denial of services or discrimination in pricing12. Solution direction An alternative comes in trust logs using blockchain attested using zk-SNARKs, which is privacy-sensitive. Vehicles show evidence of behavior rather than trust scores associated with identities. This will curb discrimination and make it more transparent without altering security. Surveillance, profiling, and overreach Challenges The IoV data can be used for commercial profiling or law enforcement surveillance in addition to its intended purpose. Collection of data in a central place increases the possibility of global surveillance, social ranking, or discrimination20. Ethical concern Behavior that is constantly monitored is likely to shrink liberty and contribute to the possibility of being locked out not of the toll but of the services for which the algorithms judge, not of the crimes committed but of the risks inferred. Solution direction With the use of zk-SNARKs, compliance can be retained without disclosures. The vehicles can prove that they are in a speed range or permitted in a certain area, but the identity of the driver and their place of origin will not be shown. This negates profiling but still promotes the safety of the population and the adherence to policies. Proposed privacy-preserving IoV framework Overview of framework The need to ensure privacy with decentralized and trustless systems is also increasing as IoV systems advance. This proposed architecture rests on the effectiveness of zk-SNARKs adopted in the context of the Metaverse, namely, where users prove their identity and qualities cryptographically but do not disclose confidential information. When adapting this methodology to the IoV ecosystem, the design consumes cryptographic privacy, blockchain audibility, and Layer 2 scalability21. Within the framework, every vehicle will act as a zero-knowledge proof generator. Vehicles autonomously build zk-SNARK verification of adherence to regulations or policies, e.g., by demonstrating the existence of a valid emissions certificate, without letting us know anything about related certificate data, which vehicle, or trips10. Such zk-proofs are confirmed by smart contracts residing in a Layer 2 blockchain network such as Polygon to limit latency, guarantee low gas expenses, and high throughput. These contracts are interrogated by the verifier infrastructure (e.g., Roadside Units or toll booths) in real time to make access decisions- e.g., provide a vehicle with access to a low-emission zone, or discount tolls. Moreover, the system complies with the principles of the data minimization approach, such that only the outcome of the verification of zk-proofs (e.g, pass or fail) is recorded in a tamper-proof manner on-chain records. There is never raw or raw information–the identity of the driver or his or her whereabouts, to adhere to the GDPR and CCPA data protection frameworks22. As illustrated in Fig. 2, the proposed architecture enables secure and privacy-preserving interactions between vehicles, infrastructure, and smart contracts through a layered design leveraging zero-knowledge proofs and blockchain. zk-SNARK proof lifecycle in IoV. This architecture guarantees a secure, scalable, and regulation-conforming IoV network, where compliance is identified with the help of cryptography rather than being inferred or assumed. Workflow The suggested framework consists of a three-step workflow, which allows adopting trust decisions on the basis of privacy-consciousness in IoV settings in real time as illustrated in Fig. 3: zk-SNARK-enabled workflow for privacy-preserving trust in IoV. Step 1: Proof generation Each vehicle has an onboard system which has a cryptographic circuit, which can generate zk-SNARKs. Regulatory or safety conditions are encoded in these circuits including: “My insurance time is now valid.” “My insurance time is now valid.” “This is a car that has undergone a safety check within the past six months.” “This is a car that has undergone a safety check within the past six months.” “It is a transport producing no harmful pollutants i.e., zero-emission vehicle (ZEV).” “It is a transport producing no harmful pollutants i.e., zero-emission vehicle (ZEV).” The vehicle produces a zk-proof of a claim using such tools as ZoKrates. The verifiable content (e.g. certificate details or timestamps) itself is confidential, and only the computer mathematical validation of compliance is produced. This calculation can be performed securely in the vehicle in the trusted execution environment (TEE) or secure processing module without the use of the online system or uploading data. Step 2: On-chain verification During the second step, the final contractor verifies that the learning process was completed successfully and obtained the required information. In the second step, the final contractor confirms that the learning process has been done successfully and that they have received the necessary information. After the generation of the proof, it is relayed to a layer 2 blockchain smart contract verifier like Polygon. This has been employed in verifying the truth of a particular proof of a desired piece of information by using previously known verification keys (produced in a trusted setup stage). The process is: Deterministic (identical outcome each time), Deterministic (identical outcome each time), Non-interactive (there is no back-and-forth communication), and Non-interactive (there is no back-and-forth communication), and Scalable, as the time it requires to verify a particular proof remains the same, no matter the size of the data used. Scalable, as the time it requires to verify a particular proof remains the same, no matter the size of the data used. This communication can take place through RSUs (e.g., toll-booths, intersections, parking gates) or can be through secure vehicle-to-network (V2N) communication in the event of access to broader services. Step 3: Response issued On verification of the zk-proof: Conditional access is carried out (e.g. a gate opens, a toll is reduced, or the network is permitted to access). Conditional access is carried out (e.g. a gate opens, a toll is reduced, or the network is permitted to access). Denial of access or is a route caused by failure to verify (e.g. expired insurance). Denial of access or is a route caused by failure to verify (e.g. expired insurance). Privately, the system records a cryptographic digest (the transaction hash and the status of success) on-chain to get audit and compliance verification, but still- NEVER stores the personal object it records. Privately, the system records a cryptographic digest (the transaction hash and the status of success) on-chain to get audit and compliance verification, but still- NEVER stores the personal object it records. This real-time means that they can easily engage in smart mobility services without losing user privacy and control of this mechanism Key advantages of framework Verification is done based on cryptographic proofs; hence no personal information or sensitive information is revealed in the transmission or processing. Real-Time Verification: Layer 2 blockchain systems allow sub-second validation of proofs, which is desirable when it comes to interactions that are time-sensitive to the vehicle. Real-Time Verification: Layer 2 blockchain systems allow sub-second validation of proofs, which is desirable when it comes to interactions that are time-sensitive to the vehicle. Regulatory Compliance: The framework will facilitate data protection regulations such as GDPR and CCPA, since the framework will implement data minimization and user anonymity. Regulatory Compliance: The framework will facilitate data protection regulations such as GDPR and CCPA, since the framework will implement data minimization and user anonymity. Tamper Resistance: Good results that are recorded during audit trials on the blockchain have strong protection against tampering or manipulation. Tamper Resistance: Good results that are recorded during audit trials on the blockchain have strong protection against tampering or manipulation. Trust without Identity: Vehicles are authenticated on the condition of cryptographic satisfaction without using personal identity and this is possible to avoid profiling which is being unjust to such access. Trust without Identity: Vehicles are authenticated on the condition of cryptographic satisfaction without using personal identity and this is possible to avoid profiling which is being unjust to such access. Performance and scalability considerations Computational overhead and practical feasibility Although zk-SNARK proofs offer high privacy assurances, their computational complexity should be put into consideration well in the vehicles setting. The size of proofs increases with the size of the circuit, but the proposed IoV applications are based on lightweight attribute-verification circuits, but not complicated arithmetic operations. These circuits usually contain condition checks (e.g. timestamp correctness, threshold correctness), which means that they yield manageable constraint sizes. The empirical standards of zk-SNARK implementation show that small circuit generation of proofs can be done in sub-second to low-second times on embedded ARM-based hardware, and verification is constant-time and computationally cheap. Moreover, the implementation of Layer 2 rollups will help to make sure that on-chain verification does not add serious congestion and latency penalties. In order to further abate overhead, proofs can be: Computed in advance in case of regulatory status change, (e.g. insurance renewed), Computed in advance in case of regulatory status change, (e.g. insurance renewed), Collected through rollup aggregation, Collected through rollup aggregation, Produced as a result of circuit design optimization and minimization of constraint. Produced as a result of circuit design optimization and minimization of constraint. Such design features guarantee that the privacy-conscious compliance checking will be efficient in the case of non safety-critical regulation-based interactions between the IoV without requiring an unwarranted amount of computational power in vehicles23. Layer 2 rollups for fast, cost-efficient verification To make zk-SNARK-based verification a viable solution at the scale of IoV, Layer 2 (L2) rollup should be used. Rather than taking a transaction in isolation and placing it in a Layer 1 blockchain, zk-rollups will run hundreds or thousands of transactions simultaneously to create one batched proof. This evidence is later confirmed after being on-chain, maintaining cryptographic integrity with a great deal of decreasing congestion and transaction costs. In a zk-rollup model: A number of compliance evidence is put in a batch. A number of compliance evidence is put in a batch. A single succinct zk-proof is a statement of the validity of all the batch. A single succinct zk-proof is a statement of the validity of all the batch. Very few on-chain accesses to state updates and verification outcomes are stored. Very few on-chain accesses to state updates and verification outcomes are stored. The proposed framework can achieve: Less than one second to less than five seconds confirmation times, Less than one second to less than five seconds confirmation times, Considerable discounts on transaction costs, Considerable discounts on transaction costs, Reduced energy usage as compared to execution in Layer 1. Reduced energy usage as compared to execution in Layer 1. This architecture gives assurance that privacy preserving compliance checking will be cost effective and technically feasible in large scale implementation of the IoV. Succinct proofs reduce blockchain bloat zk-SNARKs are exceptionally compact–proof sizes are often less than 300 bytes, and verification takes constant time regardless of input complexity. This is vital in IoV where bandwidth and storage efficiency matter. Benefits include: Graduated V2I and V2N data transmissions overhead. Graduated V2I and V2N data transmissions overhead. Low on-storage storage demands. Low on-storage storage demands. Reduced processing load on verifier smart contracts and RSUs. Reduced processing load on verifier smart contracts and RSUs. This enables green blockchain industry even in the dense urban settings with thousands of vehicles sending the proofs at the same time. High throughput in real-time mobility systems The current IoV systems are asked to support thousands of transactions a seconds (TPS) in particular in heavy-traffic areas such as toll highways, intelligent intersections, or crossings. This architecture ensures high system availability and service quality, even during traffic spikes or unexpected increases in vehicle interaction volume as shown in the Table 1. Table 1Comparison of ethereum layer 1 and proposed system (polygon + zk-SNARKs).ParameterLayer 1 (Ethereum)Proposed system (polygon + zk-SNARKs)TPS∼15∼7000Block time∼13–15 s∼2 sCost per Transaction$10–100+∼$0.001ScalabilityLimited by gas & Block sizeHigh, via rollup aggregationPrivacyWeak (transparent data)Strong (zk-proofs; no PII revealed) Comparison of ethereum layer 1 and proposed system (polygon + zk-SNARKs). Ethical design principles Ethics should not remain a secondary consideration in the design of privacy-preserving systems used in the Internet of Vehicles (IoV); they should be among the cornerstones. Along with the introduction of real-time data transmission, cryptographic validation, and decentralization of infrastructure, ethical models guarantee that the system promotes not only technical purposes but also human dignity, autonomy, and justice20. Here, there are three main principles; Privacy by Default, Accountability without Exposure, and Equity and Access, and the relevant zk-SNARK-based IoV framework is operationalized. Privacy by default Principle Systems should collect, process, and store only the data that is strictly necessary for a specific, pre-defined purpose, aligning with the GDPR’s “privacy by design and by default” mandate. Application in IoV The proposed system does not allow vehicles to transmit or reveal raw data (e.g., license numbers, route history, or identity of the driver). They instead provide cryptographic proofs that show adherence to certain conditions, such as eligibility of emissions or safety inspection17. This practice: Minimizes data exposure Minimizes data exposure Reduces attack surfaces Reduces attack surfaces Supports user control and consent Supports user control and consent Unlike conventional IoV systems, characterized by full-data disclosure or behavioral surveillance, the zk-SNARK-based method makes users incognito but compliant, accomplishing both practical efficiency and moral acceptability. Accountability without exposure Principle Systems must ensure accountability and verifiability of behavior without necessitating identity disclosure or permanent profiling. Application in IoV The actions of vehicles in the IoV ecosystem are verified in terms of behaviors and not identity. For example, a car could be digitally signed to be compliant with emission regulation or insurance requirements, without exposing the name of the driver or the vehicle ID4. This enables: Non-repudiation of verified claims Non-repudiation of verified claims Pseudonymity, protecting users from mass surveillance Pseudonymity, protecting users from mass surveillance Transparent yet privacy-respecting governance Transparent yet privacy-respecting governance This design prevents misuse of data for unintended purposes, such as insurance discrimination or law enforcement profiling, while still ensuring system integrity. Equity and access Principle Provision of services and access to digital infrastructure must be based on verifiable behavior, not on personal traits including place of residence, affluence, or origin7. Application in IoV The framework decouples identity and the mechanisms of trust, so that vehicles are evaluated on cryptographic-level merits only, e.g., whether they passed safety inspection or not, not their owner or the region they belong to. This design reduces: Algorithmic bias from historical data Algorithmic bias from historical data Exclusion of rural or underrepresented populations Exclusion of rural or underrepresented populations Structural inequality in access to smart mobility services Structural inequality in access to smart mobility services Equity is built into the system by default, promoting fairness across all participating entities in the IoV ecosystem. Future work and research directions The given zk-SNARK-based Internet of Vehicles (IoV) framework has good theoretical potential based on successful application in the field of the Metaverse. Nevertheless, a number of focused research and engineering activities have to be undertaken in order to shift the level from a conceptual model to a conceptual reality in terms of the presence of the infrastructure. Among the steps that should be undertaken, there is a need to implement the generation of zk-proofs directly into the vehicle firmware. Moreover, integrating these functions in Electronic Control Units (ECUs) and Telematics Control Units (TCUs) would facilitate the ability to generate proofs in real time with very low latency independently of the network. This is because such native integration is able to improve the security of a system and responsiveness, besides minimizing third-party middleware dependency19. Commercialization of this vision will involve intensive cooperation with automotive makers in order to develop low-weight, energy-saving zk-SNARK circuits to accommodate resource-shrunken, embedded impoverishments. At the same time, the question of compatibility between various traffic infrastructures governed by distinct jurisdictions and vendors is unavoidable. Zk-proofs have to be verified in an efficient manner between vehicles and road infrastructure, including tolling and access control, access control barriers, as well as emissions inspection locations. This requires some open standardization of proof formats, metadata schemas, and verifier APIs to be developed. The current standardization efforts by organizations like W3C DID, ISO TC 204, and EBSI may also step in as the platform on which to define such protocols to enable the governments and smart mobility vendors to have a uniform vehicle compliance checking place across regions and platforms12. A promising opportunity is also in the level of integration of AI-based trust scoring systems, and more so, federated learning. Potentially, vehicles can train contextual-behavior-based trust models locally (without sharing raw behavioral data) and, hence, completely replace the anonymized behavioral data10. Federated aggregation of such models can produce privacy-preserving adaptive trust scores, via driving patterns changing over time. The issue is to support secure model synchronization and verifying of the update by means of zk-proofs to make sure that such decentralized learning operations are tamper-resistant and verifiable in the context of the trust ecosystem in the whole of IoV. To continue future-proofing the framework, it is important to explore post-quantum cryptographic primitives, decentralized models of identity. A promising alternative to zk-SNARKs is zk-STARKs, which do not require a trusted setup and whose guarantees are resistant to quantum attacks12. At the same time, Decentralized Identifiers (DIDs) can be used to demonstrate only selective identity information that the user controls what needs to be revealed to make a given transaction or request5. To achieve long-term resilience and regulatory alignment, the hybrid architecture should be designed as a method of identifying long-term resilience and regulatory alignment, where the zk-STARKs are used to conduct scalable proof generation, and the DIDs are used to provide consent-based identity sharing. Conclusion As adoption of Internet of Vehicles (IoV) gives rise to security, trust, and privacy challenges. This paper presents an amalgamation of Metaverse and IoV to mitigate these challenges. This research explored the application of a privacy-centered framework using zero-knowledge proofs (zk-SNARKs) to secure user data without compromising functionality, offering insights into how similar methods could be applied to the IoV. The paper presented a conceptual model that preserves privacy that protects personal identifiable information in the IoV established on the experience of deploying smart contracts with zk-SNARKs in a Metaverse environment. The paper has discussed the ethical design, performance and scalability considerations that could lead to the adoption of this technology in the future. Acknowledgements The authors are thankful to the Deanship of Graduate Studies and Scientific Research at University of Bisha for supporting this work through the Fast-Track Research Support Program. Author contributions N. Z.: Conceptualization, Methodology, Data Curation, Investigation, Visualization, and Writing - Original Draft. S. T.: Conceptualization, Supervision, Project Administration, Writing - Review Editing, and Validation. F. A.: Funding Acquisition, Formal Analysis, Software Development, and Writing - Review Editing. H. T.: Data Curation, Resources, and Visualization. S. S.: Methodology, Validation, and Writing - Review Editing. A. M. S.: Data Curation, Writing - Review Editing. All authors reviewed the manuscript. Data availability All data generated or analysed during this study are included in this published article. Declarations Competing interests The authors declare no competing interests. Footnotes Publisher’s note Springer Nature remains neutral with regard to jurisdictional claims in published maps and institutional affiliations. These authors contributed equally: Nabeeha Zahid, Shahzaib Tahir, Fahad Algarni, Hasan Tahir, Saqib Saeed and Adeel M. Syed. References Associated Data Data Availability Statement All data generated or analysed during this study are included in this published article.