Doubling GPT-3 Inference Speed and Eliminating Silicon Furnaces: Vertical Memory Architectures V-Die and MOSAIC Revolutionize HBM Cooling and Bandwidth for AI Accelerators
Future AI accelerators may soon feature memory chips literally standing on their edges. Researchers from South Korea and Japan have proposed rotating DRAM dies vertically to boost both the speed and capacity of HBM without turning multilayer stacks into poorly cooled silicon furnaces.
Two new architectures, V-Die and MOSAIC, were presented in June 2026 at the IEEE Symposium on VLSI Circuits. Both teams abandoned the conventional approach of stacking dynamic memory dies horizontally on top of a base die and connecting them through TSV (through-silicon via) channels. Instead, the engineers assemble the package first and then rotate the entire structure so that individual dies stand vertically, functioning like the fins of a radiator.
Current HBM places multiple memory dies above a base die and links the layers with short, wide TSV buses that deliver several terabytes per second of bandwidth, making it the foundation of powerful AI accelerators. However, increasing the number of layers makes heat removal increasingly difficult. Lower dies become extremely hot, and heat must travel through silicon, solder, insulating materials, and additional package layers. The TSVs themselves also consume valuable die area that could otherwise be used for memory cells.
The Korean V-Die architecture removes TSVs from the memory dies altogether. Each vertical die receives its own input/output lines along the bottom edge and connects directly to the substrate. According to the researchers’ calculations, the design provides four times more connections than HBM4 and cuts data read time by 37 percent. Microfluidic channels running between the dies maintain temperatures around 45 °C, whereas dense conventional HBM packages can exceed 80 °C under heavy load.
Simulations of a 16-die system demonstrated significant performance gains. When processing GPT-3-scale workloads, the V-Die architecture achieved 540 tokens per second compared with 296 tokens per second for an equivalent-capacity HBM4 configuration. First-token latency dropped by 32 percent, or roughly 24 milliseconds. These results are currently simulation-based; the research team is now preparing physical prototypes to validate thermal and electrical characteristics.
The Japanese MOSAIC project addresses a different challenge of vertical assembly: even small thickness variations among dozens of dies can misalign contact pads. Engineers from the University of Tokyo, Tohoku University, and RIKEN proposed transmitting data without direct metal contact. Miniature coils on the dies and substrate exchange signals through electromagnetic induction, eliminating the need for perfect physical alignment during assembly.
The experimental MOSAIC interface reached speeds of up to 4 Gbit/s per channel. Researchers expect to double the memory volume of HBM4 by placing the vertical block directly above the GPU while increasing maximum temperature by only about one degree. One configuration accommodates 98 dies and 294 GB of memory; further thinning of the dies could theoretically push capacity to 882 GB.
Neither V-Die nor MOSAIC is yet ready to replace production HBM. The Korean architecture exists primarily as calculations, while the Japanese prototype must still demonstrate acceptable cost, reliability, and high manufacturing yield. Nevertheless, both developments outline a promising route around the thermal barrier that increasingly constrains memory scaling for AI accelerators. Instead of endlessly stacking dies higher, engineers are proposing to rotate the entire structure and turn the memory dies themselves into an integrated heat-dissipation system.
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.