Access Official Technical PDF

Share Summary:LinkedInEmail

Post-quantum cryptography is a strategic security consideration for industrial automation teams exploring blockchain and distributed ledger technology (DLT). These systems can support shared records across organizations, but their security depends on cryptographic mechanisms—including digital signatures—that may be affected by advances in quantum computing. For engineers and system integrators, the issue is not simply whether a future machine can break today’s cryptography. It is how to understand dependencies, evaluate alternatives, and plan for a controlled transition across connected systems.

Why industrial blockchain security depends on digital signatures

In a distributed ledger, participants use cryptographic keys and digital signatures to establish who authorized a transaction and to help other nodes verify it. A ledger’s consensus and record structure do not remove the need to protect those keys and signatures. If the cryptographic scheme underpinning identity or authorization becomes unsuitable, the integrity of applications that rely on it may also be affected.

The 2019 research examined the Elliptic Curve Digital Signature Algorithm (ECDSA), used by Bitcoin and a range of other blockchain and DLT implementations at the time. It also discussed applications of blockchain technology in sectors such as transportation, healthcare, finance, and government. The industrial lesson is broader than any one platform: organizations should understand which cryptographic algorithms their systems use rather than assuming that a distributed architecture is inherently secure.

Quantum computing is relevant because it could undermine some widely used public-key cryptography. The timing and capabilities of future fault-tolerant quantum computers are uncertain. That uncertainty makes it difficult to set a precise deadline, but it does not remove the need to assess systems with long service lives or complex dependencies.

What post-quantum cryptography changes—and what it does not

Post-quantum cryptography (PQC) refers to cryptographic approaches intended to resist attacks from both conventional and quantum computers. The research focused on lattice-based cryptography, including qTESLA, a candidate evaluated in the National Institute of Standards and Technology (NIST) standardization process described in the paper. Its security basis involved the Ring Learning With Errors problem.

A candidate algorithm is not a drop-in replacement merely because it is designed for a post-quantum environment. A signature scheme must be assessed for its security assumptions and its practical effects on the systems that use it. Relevant measures include:

  • Public-key and signature sizes: Larger cryptographic data may affect storage, communication, and integration requirements.
  • Key generation, signing, and verification costs: These operations have to fit the workload and computing environment.
  • Implementation security: Side-channel protections and other implementation details remain important.
  • Compatibility and migration: The algorithm must be integrated into applications, protocols, and public-key infrastructure.

The paper’s tests of qTESLA implementations found important tradeoffs among performance, security categories, and key and signature sizes. In particular, the provably secure parameter sets had substantially larger public keys than ECDSA in the comparisons reported. This is a reminder that cryptographic strength alone does not establish operational suitability, especially where devices or communications are constrained.

Assess cryptographic dependencies before selecting a replacement

Industrial automation environments can combine control systems, edge devices, enterprise applications, and external services. Where blockchain or DLT is part of that architecture, teams need a clear view of which components depend on public-key cryptography and where keys and signatures are used. This assessment should distinguish ledger functions from connected services such as identity, communications, software signing, and gateways; the research specifically notes that PQC could affect broader technologies and protocols, not only blockchain.

A practical review can start with these questions:

  • Which DLT platforms and associated libraries use ECDSA or other public-key schemes?
  • Which systems issue, store, rotate, or validate the relevant keys and signatures?
  • Where could larger keys or signatures affect device resources, message handling, or system integration?
  • What dependencies exist on protocols and infrastructure such as Transport Layer Security (TLS), Internet Key Exchange (IKE), or public-key infrastructure?
  • How will candidate algorithms be tested and validated in the actual target environments?

These questions help teams turn a broad technology concern into an engineering and governance task. They do not presume that every system needs an immediate replacement. Instead, they support informed prioritization and expose where further testing is required.

Plan migration as an engineering lifecycle

Cryptographic change can involve far more than updating one software library. The research emphasizes independent testing and validation, coordinated work among academia, government, and industry, and the need to consider compatibility with existing applications. It also highlights the challenge of deploying a new public-key infrastructure, which can take years to build and deliver.

For plant and operations leaders, this points to the value of beginning with inventory and evaluation. Technical teams can document cryptographic use, identify systems with long lifecycles or constrained resources, and establish a way to compare candidate algorithms on relevant hardware. Testing should consider security, performance, key and signature size, and implementation protections—not just headline claims or results from a different platform.

The paper’s qTESLA evaluation was tied to its particular candidate and test conditions; it should not be treated as a current recommendation or a universal benchmark. PQC standardization and implementation choices evolve. Organizations should therefore consult applicable standards and evaluate the algorithms and implementations appropriate to their systems at the time of deployment.

Conclusion: make cryptographic readiness part of system planning

For industrial automation, the practical implication is clear: blockchain and DLT security depends on the cryptography beneath the ledger, and future migration may affect connected protocols, infrastructure, and constrained devices. Uncertainty about quantum computing timelines is not a reason to assume either imminent failure or permanent safety. It is a reason to map dependencies, test alternatives in context, and plan for compatibility and validation. Treating cryptographic agility as part of system lifecycle planning can help technical decision-makers prepare for change without confusing a promising candidate algorithm with a production-ready solution.

Access Official Technical PDF

About The Author