## On-Chain Monitoring for Blockchain Activities The [[ZKP/Data Marketplace/Intro|Data Marketplace]] monitors on-chain activities like [[ZKP/Data Marketplace/Tokenized Datasets/Tiered Access Control|dataset access]] and [[Proof Pods in the Data Marketplace|Proof Pod]] performance via [[ZKP/Data Marketplace/Tokenized Datasets/Smart Contract for Dataset Tokenization/DatasetToken Smart Contract|smart contract]] event logs and the native event system (e.g., AccessExtended, ProofRewardDistributed). These events log crucial data such as dataset IDs and timestamps. Off-chain indexing tools coordinate through off-chain workers to aggregate this into KPIs including throughput (aligned with the [[ZKP/ZKP Base Layer/ZKP Blockchain/Performance/Consensus Layer|base layer's 100-500 TPS capacity]]), weight usage, and token volume. This monitoring framework ensures the marketplace operates efficiently within the constraints and capabilities of the underlying blockchain. For example, an AccessExtended event might log a dataset ID and timestamp, tracking 1,000 accesses/hour for a popular dataset. Testnet will assess scalability with 1,000 users, targeting <1-second updates. ## Off-Chain Monitoring for Infrastructure Health Off-chain monitoring focuses on [[ZKP/Data Marketplace/High-Level Overview/Off-Chain Storage with IPFS|IPFS availability]] (target: 99.9% uptime, consistent with the base layer specifications) and [[ZKP/Data Marketplace/Generation of ZK Proofs/Specialized Hardware Implementation|Proof Pod performance metrics]] that align with the ZKP Blockchain's performance parameters, coordinated through off-chain workers [87]. IPFS probes could measure retrieval latency (<1 second for 1 GB, illustrative) across 5 nodes/dataset, flagging downtime. APIs (e.g., REST) might track network health, with testnet validating 100 nodes for >99% coverage. ## Privacy-Preserving Monitoring Monitoring aims to potentially ensure confidentiality by logging anonymized data (e.g., dataset IDs), avoiding user identities. Future [[ZKP/ZKP Base Layer/Core Concepts/Zero-Knowledge Proofs|zero-knowledge proofs]] verified through the verification infrastructure might enhance privacy [77], with testnet targeting <1% linkage risk (illustrative) for 100 users. ## Practical Implications The system seeks to potentially offer insights, possibly informing tier adjustments (e.g., 1,000 accesses/hour) and workload optimization (>90% Proof Pod completion, illustrative), with testnet refining privacy and scalability. See also: [[ZKP/Data Marketplace/Federated Learning/Federated Learning within the Data Marketplace|Federated Learning within the Data Marketplace]]