Intel Unveils Starfire Chip Designed for AI Processing on US Military Satellites in Orbit
Intel has introduced a new system-on-chip called Starfire that is intended to operate not in data centers but in Earth orbit, where it must endure temperature swings from -55 °C to 125 °C and continuous exposure to cosmic radiation.
The chip was developed under contract for the US government and combines eight general-purpose CPU cores, a three-die neural-network accelerator, and a graphics block inside a single Foveros package. Two power variants are offered: a 10 W version rated at up to 45 TOPS and a 35 W version rated at up to 75 TOPS.
Manufacturing processes are deliberately split inside the same package. The CPU cores and neural accelerator are fabricated on Intel’s leading-edge Intel 18A node, while the graphics module uses the more mature Intel 3 process—the same heterogeneous approach Intel previously employed in the server processor Clearwater Forest. Because smaller transistors hold less charge, they are more susceptible to single-event upsets from space radiation; therefore, reliability will be achieved through circuit-level and architectural hardening rather than process maturity alone.
For decades the space-grade processor market has been dominated by BAE Systems’ RAD750, a 200 MHz device flying on Mars rovers and the Kepler and Fermi telescopes. Newer offerings such as the RAD5545 and a forthcoming Microchip design for NASA promise roughly an order-of-magnitude performance increase, yet they remain focused on telemetry and control. Starfire, with its dedicated neural accelerator, is aimed at a different mission: performing artificial-intelligence inference and real-time data analysis directly on board the satellite.
The device is still a demonstration vehicle. Radiation-tolerance figures are still being measured, and the chip has not yet received formal space-radiation certification. Intel cautions that final specifications may change. First engineering samples are slated for delivery in the third quarter of 2026 through the company’s Intel Government Technologies division.
The project carries strategic weight for Intel, which remains the only US company capable of producing chips of this complexity. It participates in the Pentagon’s RAMP-C and SHIP programs. Company roadmaps indicate that 18A process yields are expected to reach industry parity only in 2027, potentially affecting the timeline for volume production of space-qualified parts.
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.