Near Absolute Zero and 0.55% Efficiency: World's First Superconducting Quantum Heat Engine Demonstrated by Aalto University Researchers
Researchers at Aalto University have experimentally realized the world’s first cyclic superconducting quantum heat engine that converts heat into useful work inside a quantum circuit cooled to near absolute zero. The tiny device marks the first time a complete, repeatable thermodynamic cycle has been demonstrated in a superconducting platform, opening new possibilities for managing heat and control signals in future quantum processors.
Unlike earlier quantum heat machines, the Finnish team achieved a full experimental cycle using a transmon qubit—one of the most common types of superconducting qubits—as the working substance. The circuit was placed inside a cryostat and cooled to temperatures approaching absolute zero. A resonator and a voltage-controlled quantum refrigerator were coupled to the transmon, allowing researchers to switch between heating and cooling phases with a single component instead of two separate thermal reservoirs.
The engine follows the Otto cycle, the same thermodynamic cycle used in conventional internal-combustion engines. In the experiment, the team first lowered the qubit’s transition frequency to let the system perform work, then used the quantum refrigerator to extract heat. After raising the frequency again (compression), the refrigerator reheated the qubit to return the system to its initial state. This sequence was repeated multiple times while the qubit state was read out after each step.
To obtain reliable statistics, the researchers performed 10,000 individual measurements for each data point and calculated average energy flows. The results matched numerical simulations and demonstrated genuine positive output power rather than a mere simulation of thermodynamic behavior. Measured performance remained modest: average power reached only 0.039 electronvolts per second, while efficiency stood at roughly 0.55 percent—about 27 percent of the theoretical Otto-cycle limit for the chosen parameters. Modeling indicates that efficiency could rise to approximately 2.2 percent once the device operates in a steady regime.
The primary value of the technology lies not in large-scale power generation but in on-chip thermal management and autonomous control of quantum processors. Modern superconducting quantum computers rely on numerous microwave lines that connect millikelvin qubits to room-temperature electronics; these cables increase complexity, cost, and noise. A quantum heat engine could eventually perform local operations such as state initialization or readout without requiring every control signal to travel outside the cryostat, thereby reducing wiring density and enabling processors with hundreds of thousands of physical qubits.
In addition to practical applications, the superconducting platform offers physicists a powerful testbed for quantum thermodynamics. Precise control over temperature, heat flow, and energy levels allows direct comparison between experimental observations and theoretical models, potentially revealing whether quantum effects such as superposition or interference can enhance the performance of microscopic heat machines.
Related articles
OAuth Authorization Server Built Without Storing User Profiles
The article details the evolution of an OAuth Authorization Server that deliberately avoids storing user profiles, relying instead on external identity providers for authentication. It addresses three core constraints: hundreds of dynamically created isolated APIs, a public SPA client without a BFF, and the inability of resources to query the AS on every request. The design separates concerns so the AS handles only clients, tenants, grants, audiences, scopes, keys, sessions, and token issuance while the Main API owns profiles and roles. Tokens are managed securely inside a Service Worker using a custom FedCM grant, eliminating races across tabs and reducing XSS exposure. The approach minimizes blast radius, simplifies compliance, and keeps the AS replaceable without affecting product domain logic.
Why a 202-Character License Key Uses ECDSA P-256 Instead of Ed25519 or RSA
A developer building offline license verification for a .NET desktop application evaluated Ed25519, RSA, and ECDSA P-256 before selecting the last option. The decision was driven by the requirement for zero external dependencies, keys short enough for manual entry from email, and support for key rotation without breaking existing licenses. Although Ed25519 offers faster verification and a smaller public key, it is absent from System.Security.Cryptography in both .NET 8 and .NET 10, with API approval only targeted for version 11. RSA-2048 produces signatures too long for practical use, resulting in a 571-character Base32 string that users would find cumbersome. ECDSA P-256 with SHA-256 delivers a fixed 64-byte signature that becomes a manageable 202-character key when encoded in Base32, while remaining fully available in the runtime. The article also covers performance measurements, the risks of ECDSA nonce generation, and the deliberate choice of the IEEE P1363 signature format to guarantee fixed-length output.
Pilcrow Publishes Free Comprehensive Guide on Web Authentication
Author Pilcrow has released a detailed, ad-free handbook covering authentication and authorization practices for web applications. The resource draws on personal experience and includes practical examples in JavaScript and Go. It examines password-based methods, email verification, multi-factor authentication, passwordless flows, and passkeys while highlighting associated risks and usability trade-offs. The book also provides in-depth guidance on session management, token security, expiration policies, and email address handling as account identifiers. Recommendations emphasize choosing methods that match application security requirements and user expectations. Additional context is given on OWASP resources and community support channels.
redb 3.4.0 Adds Replay Checkpoints, Shared Runtime Layer and Declarative Secrets Handling for .NET Ecosystem
redb 3.4.0 delivers operational improvements for the .NET integration platform that includes typed storage over Postgres, MSSQL and SQLite, the redb.Route engine modeled after Apache Camel, the Tsak runtime with dashboard and clustering, and redb.Identity for OIDC and OAuth 2.1. The release focuses on post-deployment resilience with replay checkpoints that capture message state at named points inside routes, allowing safe re-execution of downstream steps without duplicating side effects. A shared runtime layer moves framework assemblies into a separate Libs/shared directory so that individual DLLs can be replaced without rebuilding or redeploying the entire Tsak or Identity packages. Secrets are now declared with a [Sensitive] attribute on endpoint options, ensuring URIs containing passwords or keys are sanitized before they reach logs, metrics or health checks. Additional controls include role-based access to management APIs, persistent audit trails and cryptographic signing of dynamically loaded modules. All Pro features remain free on the entire 3.x line with no licensing server required.