DESTinE Block: Secure Storage for Power Systems

• DESTinE Block is a blockchain-based framework that segregates file data from cryptographically verified metadata for enhanced security.
• The framework employs a Proof of Authority consensus with dual ECDSA signatures to ensure tamper-evident and authenticated logging of power system data.
• Evaluations on both high-end and resource-constrained hardware demonstrate its efficiency, rapid upload/retrieval times, and suitability for grid-edge deployments.

DESTinE Block is a private blockchain-based data storage framework developed specifically for power system environments, targeting efficient, secure, and tamper-evident storage of measurement and logging data—especially in resource-constrained settings such as grid-edge deployments. It integrates a custom blockchain architecture with InterPlanetary File System (IPFS) for scalable file storage while guaranteeing metadata authenticity and provenance through collaborative cryptographic consensus. The framework has been evaluated on both high-end and low-power hardware, demonstrating substantial efficiency, low computational overhead, and resilience in distributed power system operations (Haque et al., 18 Oct 2025).

1. Architecture and Key Components

DESTinE Block employs a dual-layer system that robustly separates large-scale file data from cryptographically verified metadata. Files, such as grid measurement logs, are stored off-chain using IPFS, which produces a unique Content Identifier (CID) for each asset. The metadata—consisting of CID, uploader identity, administrator verification, and timestamp—is immutable and maintained on a dedicated private blockchain.

This blockchain is strictly decoupled from the IPFS storage layer: the chain records only a cryptographic summary and associated metadata per file, while actual file content remains outside the blockchain. This design enhances security by limiting exposure of sensitive information, supports efficient auditability, and optimizes for resource-constrained hardware (such as single-board computers).

Each new block is linked to the previous block’s hash (standard blockchain chaining), commencing from a genesis block created by the administrator alone. All subsequent blocks require cooperative signing by both the administrator and an uploader, enforcing a co-signature protocol.

2. Cryptographic Security Model

DESTinE Block incorporates several layered security mechanisms. The dual-blockchain abstraction ensures that file contents reside outside the chain, mitigating confidentiality risks and reducing attack surface. All metadata entered on-chain is protected using ECDSA (Elliptic Curve Digital Signature Algorithm) signatures with SHA-256 hashing. The block creation requires co-signatures: the uploader executes an initial signature on the block hash, which the administrator verifies and then adds a secondary signature. Both use distinct key pairs.

Each node’s local blockchain persistence is further secured using AES-GCM encryption: the blockchain data is encrypted on disk with authenticated encryption. Thus, even compromise of a node yields only ciphertext, not plaintext metadata. In this configuration, both authentication and integrity of the blockchain state are cryptographically enforced.

The ECDSA scheme in DESTinE Block is mathematically described via:

• Private key: $d\in\{1, \ldots, n-1\}$; public key: $Q=dG$
• Signature generation: $e = \text{int}(H(m)) \bmod n$; $r = x_R \bmod n$; $s = k^{-1}(e+rd) \bmod n$ AES-GCM persistence involves a series of computations for hash subkeys, counter blocks, and authentication tags.

3. Consensus Mechanism and Co-signature Protocol

DESTinE Block utilizes a Proof of Authority (PoA) consensus model. In PoA, validation and block addition privileges are restricted to trusted parties rather than general participants, reducing computational costs compared to Proof of Work/Stake.

Block creation is collaborative: both the uploader and administrator, operating separate ECDSA key pairs, must mutually approve each new block. The process consists of metadata compilation, SHA-256 hashing, uploader signature, administrator verification, and administrator signature. Block addition only completes if both signatures are authentic and valid. This enforces dual control, mitigates risks of unilateral block addition, and assures that recorded data is both externally authenticated and internally confirmed.

A summary of consensus steps: | Step | Actor | Mechanism | |-----------------------|--------------|-------------------------------------| | Metadata creation | Uploader | SHA-256 hash, ECDSA sign | | Verification & signing| Administrator| Signature check, ECDSA sign | | Block finalization | Both | Dual-signature requirement |

4. Resource Efficiency and Performance Evaluation

DESTinE Block is engineered for minimal computational footprint, verified by cross-platform deployments on x86-based and ARM64 Raspberry Pi 5 devices. File upload and retrieval tests show that DESTinE Block achieves:

• Upload times $\sim 10^{10}$ times faster than Multichain-based alternatives
• Retrieval times $\sim 10^{2}$ times faster than Multichain comparisons
• Lower RAM consumption with consistent performance across device architectures

Gaussian Mixture Model (GMM) analyses for small file sizes reveal that ARM64-based Raspberry Pi 5 performance is at least comparable to, and sometimes exceeds, that on x86 devices. This demonstrates practical viability for field deployment at grid edge locations.

5. Applications in Smart Grid Infrastructure

DESTinE Block’s targeted application domain is secure, tamper-evident distributed logging and measurement retention in smart grid infrastructure. By leveraging secure off-chain storage via IPFS and on-chain traceable metadata, it addresses power system requirements for decentralized (yet auditable) data management.

Typical deployment scenarios include:

• Logging measurement data from SCADA systems or remote terminal units
• Secure storage and retrieval with audit trail for operational records
• Lightweight field deployment for grid monitoring and forensics, supporting both x86 and low-power ARM devices

The framework’s security model is suited to environments requiring demonstrable data provenance and robust resistance to tampering.

6. Technical Workflow

DESTinE Block’s technical workflow is formalized in Algorithm 1 in the referenced paper, summarizing:

• ECDSA key pair initialization (dual roles: administrator/uploader)
• Genesis block creation (administrator only)
• File upload to IPFS and retrieval of CID
• Metadata compilation: CID, timestamps, previous hash, identities
• SHA-256 hashing and ECDSA signature by uploader
• Administrator verification and co-signature
• Blockchain persistence using AES-GCM encryption

The ECDSA signing and verification are strictly defined via explicit LaTeX expressions:

• $d\in\{1,\ldots,n-1\}$; $Q=dG$
• $e=\text{int}(H(m))\mod n$
• $r=x_R\mod n$
• $s=k^{-1}(e+rd)\mod n$

AES-GCM-based encryption and authentication ensure confidentiality and integrity of the blockchain’s stored state.

7. Comparative Framework Analysis

DESTinE Block is compared to Multichain-based frameworks under equivalent conditions. DESTinE Block shows marked improvements in upload/retrieval timing (10–100$\times$ faster) and substantially reduced RAM consumption. Its performance advantage, combined with low resource requirements and grid-edge hardware compatibility, suggests strong applicability in critical power system infrastructure.

Summary Table: DESTinE Block Key Features

Feature	Description	Implementation
Storage Abstraction	Dual-layer: IPFS for files, blockchain for metadata	Off-chain CID, on-chain signatures
Security	Dual ECDSA signature, SHA-256, AES-GCM encryption	Cooperative block creation
Consensus	Proof of Authority, dual approval	Administrator/uploader signatures
Hardware Support	x86, ARM64, Raspberry Pi 5 compatibility	Efficient on limited hardware

DESTinE Block represents an efficient, secure, and scalable blockchain-based data storage solution for distributed power systems, integrating modular cryptographic verification, robust consensus, off-chain storage abstraction, and resource efficiency suitable for field and edge deployment (Haque et al., 18 Oct 2025).