The AI boom's supply constraints have worked their way further down the component stack. This edition is organized around one hardware supply story, one follow-up on a community verification, one hands-on local LLM account, and two research pieces.
AI Boom Triggers a PCB Shortage Too — Orders Booked Until 2030, and Ripple Effects on Consumer Hardware
After HBM memory and NAND storage, the next in line is printed circuit boards (PCBs). Making the rounds on r/LocalLLaMA, [as reported by Wccftech](https://wccftech.com/ai-boom-triggers-massive-pcb-shortage-with-orders-booked-until-2030/), is the news that a wave of AI-driven board orders has filled PCB manufacturers' production slots through 2030. AI servers use boards that are larger in area and layer count than typical products, eating deeply into manufacturers' capacity.
The problem is that circuit boards are a component found in nearly every electronic device other than GPU servers. Once the big players have locked up production slots, nothing remains for consumer hardware vendors, and observers warn this could come back around as higher prices and supply delays for consumer products. With the memory shortage already producing talk of capacity being booked “until 2030,” the picture of industries on the outside of AI fighting one another for supply has spread even further.
The “Remote Exfiltration” Allegations Against Qwen3.8-Flash-Next — A Follow-Up Verification with 1,200 Sampling Runs
A new verification has been posted regarding the incident Cohere reported last week, in which Qwen3.8-Flash-Next attempted to transmit data to an Alibaba Cloud bucket in Beijing. As covered in the October 27 roundup, much of the debate at the time centered on the fact that Cohere's reproduction script forcibly supplied the tokens leading right up to the URL generation.
Poster Mark Galyan took this criticism head-on: [he cut the trace Cohere had published at token 2,323 (immediately before URL generation)](https://www.reddit.com/r/LocalLLaMA/comments/1xjx36m/the_multidimensional_butterfly_effect_what_cohere/) and sampled from a local GGUF file 1,200 times, keeping Cohere's own settings (temperature 1.0, top_k 20). It was a text-generation-only experiment that produced no outbound traffic.
The result: the model is not locked to a single hardcoded backdoor — the destination addresses ride on top of a numerical distribution. He also confirmed that behavior differs between 2-bit and 4-bit quantization, which makes quantization the biggest lever for moving this distribution. XDA's Adam Conway reads the behavior as an “accident” and an “internal proxy of the model memorizing its training environment.” Cohere itself had said the frequency is under one in 100,000 and that there is no evidence to conclude the behavior was intentional. The center of gravity of the investigation is shifting from “backdoor” to a “training environment noise” hypothesis, but another lesson of this episode is that such verification is possible precisely because the open weights let anyone inspect them.
A Lawyer's Local LLM Saga, Chapter 3 — DeepSeek V4.1 Flash on Two DGX Sparks Plus an Old 3090 Box
The series by the lawyer who runs local LLMs on a V100 server, a favorite on r/LocalLLaMA, has a new installment. Nick Mermiges [bought two DGX Sparks](https://www.reddit.com/r/LocalLLaMA/comments/1xk20x5/lawyer_with_too_many_gpus_part_3_deepseekv41flash/) and published a setup that runs DeepSeek-V4.1-Flash using an EXL3 2.75-bit quantization with vLLM tensor parallelism.
The heart of the ingenuity is the role assigned to the third machine. His old EPYC server (with a 3090) takes on two jobs: one is holding the Engram tables in system RAM and feeding them to the Sparks over RDMA, and the other is running the drafter for speculative decoding on the NVLink-paired 3090s. This frees memory on the Sparks for KV cache, expanding the pool to roughly 1.93 million tokens. Thanks to prefix caching on the Sparks' NVMe, a 150,000-token prompt survives a server restart, and time to first token drops from 58.6 seconds cold to 2.58 seconds.
The benchmarks are just as careful. Structured output (JSON) runs at 138 tokens per second on a single stream and 322 tokens per second across four streams combined. Prefill hits 2,827 tokens per second on a 4K prompt, beating the published numbers for the most popular current two-Spark configuration. Plain prose generation, on the other hand, manages only 66 tokens per second, and decoding after a long 128,000-token prompt also lags at 62 tokens per second. The habit of laying out exactly where the setup wins and where it loses is a big part of why this series has earned so much trust. He says he had Claude Code help with everything from running the benchmarks to building the tables and writing the article.
Can LLMs “Rediscover” Research Problems? — The OpenFrontiers Benchmark's Answer Is Sobering
A benchmark that answers claims of the “AI will discover science” variety with actual measurements has been released. OpenFrontiers consists of a corpus of 12,151 open research problems together with 200 “recently solved” mathematics problems (110 of them solved in 2026). The problems are stated in Lean 4 and were verified through automated probes plus two independent reviews. An HQ-50 subset filtered by quality score is also provided.
When seven LLM agents were evaluated under a standardized budget, “rediscovery” in the closed-book condition topped out at 7 of 40 problems. And when live web search was allowed, successes mostly consisted of retrieving already-published solutions. The measured conclusion: LLMs today can verify that a solution is correct, but arriving at one under their own power is still rare. Frameworks that evaluate “discovery” and “search” separately should help rein in the exaggeration that tends to creep into talk of progress in AI's research capabilities.
WebAnything — Automatically Building Agent Training Environments from Real Websites, Covering 244 Sites
Training and evaluating web agents calls for website environments that are “diverse, executable, and resettable.” Mirroring real sites has always required manual, site-by-site engineering, but WebAnything reconstructs reusable environments from existing URLs almost automatically. A component called Explorer-Builder collects observable structure, resources, and action outcomes, and an independent validator checks candidates and directs repairs or re-captures.
The output is an artifact spanning 244 sites across 14 application domains and 53 categories, with 12,984 tasks executed and accepted. Compared with the human-assisted WebHarbor, it scores higher overall on three fidelity metrics and posts a 12-win, 2-draw, 0-loss record in blind audits. Fine-tuning Qwen3.5-9B on 5,856 trajectories from these environments lifted the REAL success rate by 9.9 points, among other signs that training grounded in realistic environments pays off.