GPTware (@GPTWare) header
GPTware (@GPTWare) profile picture

🇨🇦 Obsessed with all things Ai Agents, Loops, LLMs, Fine-Tuning https://teapaw.org/t.co/9thyt19bL5 - Entrepreneur. Builder.

Canada
Joined May 2026
I built QMesh to run DSV4.1-Flash-1017 locally on 1× RTX PRO 6000 MAX-Q + 1× ASUS GX10. • 128.1 tok/s peak single-user • 214.9 tok/s peak aggregate, 8 users • 1017-panel PPL: 1.5861 (original: 1.5720) Official base. 100 GbE RoCE. 2.935 bpw quant. Here’s how it works 🧵
3
1
3
8
1,139
Is this actually shocking???
I have a major result to share. I’ve found conclusive forensic evidence that the top 4 Chinese AI labs—DeepSeek, Moonshot, MiniMax and Ant Group—have built their newest models on NVIDIA’s most advanced Blackwell chips, which are barred from export to China. This sounds insane, but I discovered that almost every AI model carries a hidden signature of the GPU that trained it. When a model is first set up, the starting values of its weights are laid out in a pattern that depends on the exact GPU. Each combination of GPU and seed number produces a unique pattern—a sort of fingerprint of the hardware used to create the model. Traces of that pattern survive training into the published model. Again, this evidence isn’t based on any insider information or leaking. It’s based on a forensic analysis of the model weights released by the companies themselves. I searched more than six trillion combinations of chip layout and seed number and matched them to open-weights models. In doing so, I found conclusive evidence that six Chinese AI models—including DeepSeek-V4-Pro, Kimi K3, and MiniMax-M3—were initialized on NVIDIA Blackwell systems. Four of the models match Grace Blackwell, the GB200 and GB300 parts in NVIDIA’s flagship liquid-cooled rack-scale systems. I then verified these results on real hardware. Running unmodified PyTorch with the seeds I’d recovered, a Blackwell B300 reproduced DeepSeek-V4-Flash’s untouched starting weights bit for bit, and a rented GB200 reproduced Kimi K3’s to a correlation of 0.999995. A Hopper H100 reproduced none of DeepSeek-V4-Flash’s, and changing the seed by one broke the match. (DeepSeek’s seed is 953049583 by the way.) The method also was verified to match 24 known open-weights models to the hardware that developers said they used. It is exceedingly unlikely that these results are a coincidence. Across six trillion combinations, the best accidental match should reach only about 8 sigma (i.e., eight standard deviations above what random chance would produce). The real matches range from 49 to 1,385 sigma, and even the weakest single test hits 20. These were data-center-scale training runs. With some analysis of release schedules and model details, I estimate that the largest, Kimi K3 and DeepSeek-V4-Pro, used 2,000 to 3,000 Blackwell GPUs each. Clusters of this size cost on the order of $150 to $200 million each to buy, and across these labs alone would add up to more than half a billion dollars of export-controlled GPUs, not counting experimental compute or otherwise. It’s quite likely that we see multi-billion dollar expenditure on export-controlled GPUs. I am highly confident in this result, and it has been independently verified by senior researchers at OpenAI and Anthropic. You can read the full report at unemploymentlabs.com/checkpo…. There is much more I’ve identified about these models through other forms of checkpoint forensics like this, and will have more to share soon.
1
1
98
Update dropping soon...
This is a great repo by @turboderp_ at 3.18 bpw. Puts the entire model (engram on SSD) on 1 RTX Pro 6000. - 254.6 tok/s Decode (code) - single - 4700 tok/s Prefill (long prompt - 3200 tok/s shorter) - 2.4M context space github.com/GPTwareAiTeam/Qwe…
2
108
The response I imagine when I ask @elonmusk to work on @grok @SpaceX
Replying to @zerohedge
That would be an honor
1
79
In fact he is so committed to open source that he open sourced his marriage!
Jensen was so committed to open source models
1
2
175
DDH's X account got massively nerfed!
I'm starting to think "nerfing" is the evil spirits of the AI world. Every rustling of the leaves, demonic. Every prompt response not to your liking, nerfing.
1
271
GPTware retweeted
🚀 Qwen, Kimi, GLM are all betting on linear attention. But it's still slow: the recurrent state is read & rewritten every token. Meet LeapQuant: the first training-free method to make 8-bit or 4-bit recurrent states work. 📈 Across Qwen, Kimi, and GLM models: • Matches FP32 accuracy • 4.25× faster linear attention kernels • Up to 2× higher inference throughput • Cuts memory by up to 56%
26
97
13
625
61,429
Ooooh things getting interesting...
Me and @cynoder got CUDA kernels to execute on an Intel GPU We did this by building a Rust CUDA compatibility layer that translates PTX → SPIR-V → Level Zero Code: github.com/amw720386/cuda-fo… Demo below
3
200
Introducing Gemini Decision 1, our new frontier decision model in the Gemini API. It is $0.10 per 1M input tokens with no additional cost. With support for image, audio, video, and PDF natively, 256K context window, & 1K questions. You can try it for free in the API!
584
609
349
10,320
749,718
Our independent X community literally changing the inference game over here, first @ashxhart now Nerv. Splitting requests across multiple concurrent sessions for incredible speeds. 🚀🚀🚀 👀👀👀
🚨 I'VE DONE IT!! does anyone want 1600tps on a single 5090 running Qwen 3.8 27b?! oh and i saw someone else was posting about 700tps as a big milestone recently? interesting.😁
7
440
1 RTX Pro 6000 + 1 GB10 version here: teapaw.org/GPTWare/status/2120640…
DeepSeek-V4.1-Flash-1017 on 1× RTX PRO 6000 Blackwell + 2× GB10, using QMesh AFD-TP3 + DSpark: Full NVFP4 Quant ⚡ 119.78 tok/s peak single-request (code) ⚡ 200.24 tok/s peak at 8 concurrent requests 2M context window.
90
10/ More performance work Fixed-order sums: 3.6% less time/token. bf16 replies: half the traffic. Batched attention: 6–7% less time/token. Plus FP4 KV, adaptive prefill and persistent tuner caches
1
33
11/ Credits Built on turboderp’s ExLlamaV3 and Zeuss5’s cuda-exl3. Evaluation: sudoingX. Ideas and foundations: Niko1221/Strata, KTransformers, CarouselAether and diffbot. Credits & Foundations: github.com/GPTwareAiTeam/QMe… @turboderp_ / ExLlamaV3 The engine underneath QMesh: EXL3 quantization, cooperative MoE kernels, HC-mix, attention, DSpark implementation, CUDA graph capture, paged caching and batched generation. My scheduling, memory and execution changes build on that foundation. Zeuss5 / cuda-exl3 The GX10 expert GEMM foundation. I extended it with fractional-bitrate tiles, a shared fp32 accumulator and a partial-routing-map fix, then built the native expert path, consolidated layer execution and fixed-order combination on top. @sudoingX The evaluation panels, panel protocol, KLD harness and published comparison results. I reproduced the panel protocol and ran the KLD harness unmodified to evaluate this build. @coldniko / Strata Adaptive GPU expert caching and cost-aware heterogeneous execution ideas informing ColdSteal. KTransformers contributors Foundations for computing experts where their weights reside and overlapping execution across different devices. CarouselAether An optimization to ExLlamaV3’s fused HC-mix kernel that my HC fold extends, plus inherited ROCm work. @diffbot Earlier confidence-gated DSpark work acknowledged as related work. I independently developed QMesh’s confidence-and-cost controller; no diffbot code or weights were used. Songlin Yang, Yu Zhang & Zhiyuan Li / FLA Linear-attention kernels inherited through ExLlamaV3, retained with their license. Additional inherited and reference work Adel Johar / rocm_wmma_gemm; p-e-w and llama.cpp for DRY sampling semantics; llama.cpp’s WikiText-2 evaluation protocol; philbert440 for the optional drafter tap-scaling idea.
1
68