SCPF-Chain Experimental Data for Priority-Aware Consensus in Two-Layer IoT Blockchains
Description
This dataset accompanies the manuscript “Smart Contract Policy Finality-Chain (SCPF-Chain): Hardware Evaluation of Priority-Aware Consensus for Two-Layer IoT Blockchains.” It contains experimental input workloads and selected hardware evaluation data from the SCPF-Chain Raspberry Pi testbed. The repository includes four synthetic replay traces generated with seeds 58657, 59693, 60240, and 61563, together with protocol configuration files defining the equal-priority baseline and full priority-aware scheduling modes. Each synthetic trace contains 932 timestamped IoT events covering temperature, gas, fire, and healthcare sources over a 120-second workload window. The dataset also includes real-sensor experimental data, authentication-related outputs, power measurements, authenticated idle-power runs, and results from a 35-run authenticated negative-case security campaign. Additional files provide trace manifests, generator provenance information, priority-range definitions, workload-generation parameters, and campaign metadata. The synthetic traces contain no personal or human-subject data, and healthcare values are experimental sensor readings rather than clinical records. The dataset supports the evaluation of priority-aware scheduling, sensor ingestion, authentication, security rejection behavior, and energy consumption reported in the manuscript.
Files
Steps to reproduce
Extract the dataset archives and preserve the original directory structure. Use the replay traces in SCPF-Chain_Data/traces/ together with the protocol configuration files in protocol/. The equal-priority baseline is defined by phase_a_no_priority.json, while the priority-aware mode is defined by phase_b_with_priority.json. Replay each JSONL trace according to its t_offset_s field over the 120-second workload window. The included traces correspond to seeds 58657, 59693, 60240, and 61563, with 932 events per trace. For the real-sensor experiments, use the archived run data to inspect sensor readings, submitted events, blockchain outputs, authentication records, and CT-3 power measurements. For the authenticated negative-case evaluation, aggregate the 35 run summaries to reproduce the reported counts of valid, replayed, tampered, forged-priority, and flood requests. For the authenticated idle-power evaluation, analyze the 12 CT-3 power runs using their corresponding power markers and run logs to reproduce the idle-power statistics reported in the manuscript. Verify file integrity using the supplied SHA-256 manifests where available. Full re-execution of the hardware experiments requires the SCPF-Chain implementation and an equivalent eight-node Raspberry Pi testbed with the sensor, authentication, networking, and power-measurement configuration described in the manuscript. The deposited files provide the experimental inputs and archived measurements used to support the reported analyses.