<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:media="http://search.yahoo.com/mrss/" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>VIDRAFT | Awesome Agents</title><link>https://awesomeagents.ai/tags/vidraft/</link><description>Your guide to AI models, agents, and the future of intelligence. Reviews, leaderboards, news, and tools - all in one place.</description><language>en-us</language><managingEditor>contact@awesomeagents.ai (Awesome Agents)</managingEditor><lastBuildDate>Sun, 26 Jul 2026 02:04:19 +0200</lastBuildDate><atom:link href="https://awesomeagents.ai/tags/vidraft/index.xml" rel="self" type="application/rss+xml"/><image><url>https://awesomeagents.ai/images/logo.png</url><title>Awesome Agents</title><link>https://awesomeagents.ai/</link></image><item><title>POCKET-35B</title><link>https://awesomeagents.ai/models/pocket-35b/</link><pubDate>Sun, 26 Jul 2026 02:04:19 +0200</pubDate><guid>https://awesomeagents.ai/models/pocket-35b/</guid><description><![CDATA[<p>POCKET-35B is a GGUF release from the Seoul startup VIDRAFT, built to answer a narrow question: how much of a 35-billion-parameter reasoning model survives once you strip out the GPU requirement completely. It's a quantized descendant of VIDRAFT's own <a href="https://huggingface.co/FINAL-Bench/Darwin-36B-Opus">Darwin-36B-Opus</a>, a model bred (not trained) from <a href="/models/qwen-3-6-35b-a3b/">Qwen 3.6-35B-A3B</a> using the company's evolutionary merging engine, Darwin V7.</p>]]></description><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>POCKET-35B is a GGUF release from the Seoul startup VIDRAFT, built to answer a narrow question: how much of a 35-billion-parameter reasoning model survives once you strip out the GPU requirement completely. It's a quantized descendant of VIDRAFT's own <a href="https://huggingface.co/FINAL-Bench/Darwin-36B-Opus">Darwin-36B-Opus</a>, a model bred (not trained) from <a href="/models/qwen-3-6-35b-a3b/">Qwen 3.6-35B-A3B</a> using the company's evolutionary merging engine, Darwin V7.</p>
<div class="news-tldr">
<p><strong>TL;DR</strong></p>
<ul>
<li>35B sparse MoE (256 experts, 8 active) quantized down to four GGUF sizes from 21.2GB to 8.24GB, runs on stock llama.cpp with no GPU and no fork</li>
<li>262,144-token context confirmed in the GGUF metadata itself, but GPQA Diamond drops to 68.7% (Q4_K_M) or 60.1% (Q2_K) versus 73.2% for the unquantized Qwen 3.6-35B-A3B base</li>
<li>Beats the comparable <a href="/models/bonsai-27b/">Bonsai-27B</a> build on CPU and laptop generation speed by roughly 2x to 4x, but loses on GPU prompt processing because MoE prefill has to wake every expert</li>
</ul>
</div>
<h2 id="overview">Overview</h2>
<p>VIDRAFT is a 12-person startup operating out of Seoul AI Hub, a Seoul Metropolitan Government facility, founded in 2024 by CEO Min-sik Kim, who was a fourth-year computer engineering student at Korea Cyber University before taking leave to run the company. It has no large funding round to point to. What it has instead is a NIPA GPU allocation rated &quot;Excellent&quot; for 2026, KOITA recognition as a corporate research institute, and access to 24 GPUs (16 Blackwell B200s and 8 H200s), which is a modest fleet by frontier-lab standards but enough to run its core product: Darwin, a gradient-free model-merging engine that recombines the weights of existing checkpoints instead of training new ones.</p>
<p>Darwin-36B-Opus, the model POCKET-35B is quantized from, is the highest-scoring member of that family. VIDRAFT bred it from two parents that share a common base: <a href="https://huggingface.co/Qwen/Qwen3.6-35B-A3B">Qwen/Qwen3.6-35B-A3B</a> supplied the MoE architecture and expert topology, while <code>hesamation/Qwen3.6-35B-A3B-Claude-4.6-Opus-Reasoning-Distilled</code>, a LoRA fine-tune trained on 14,233 chain-of-thought traces distilled from Claude Opus 4.6, supplied the reasoning behavior. Darwin V7 merges the two through what VIDRAFT calls per-tensor compatibility analysis rather than any further gradient descent, and the whole process reportedly finishes in under 10 minutes on a single B200 GPU.</p>
<p>POCKET-35B strips that merged model down for hardware that has none of that. It ships as four GGUF quantizations, from a 21.2GB top-quality build to an 8.24GB build small enough for a 16GB RAM box, all built to load in unmodified llama.cpp rather than a custom fork.</p>
<p><img src="/images/models/pocket-35b-xeon.jpg" alt="A macro photograph of an Intel Xeon E3-1225V2 processor, showing the printed model and speed markings">
<em>POCKET-35B's headline CPU numbers come from a 16-thread Xeon server, the kind of hardware VIDRAFT is targeting instead of a GPU.</em>
<small>Source: commons.wikimedia.org</small></p>
<h2 id="key-specifications">Key Specifications</h2>
<table>
  <thead>
      <tr>
          <th>Specification</th>
          <th>Details</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>Provider</td>
          <td>VIDRAFT (FINAL-Bench / VIDRAFT_LAB)</td>
      </tr>
      <tr>
          <td>Model Family</td>
          <td>POCKET (quantized from Darwin-36B-Opus)</td>
      </tr>
      <tr>
          <td>Parameters</td>
          <td>34.7B total / ~3B active per token</td>
      </tr>
      <tr>
          <td>Architecture</td>
          <td>Sparse MoE, 256 routed experts + 1 shared, top-8 routing</td>
      </tr>
      <tr>
          <td>Context Window</td>
          <td>262,144 tokens (confirmed in GGUF metadata)</td>
      </tr>
      <tr>
          <td>Quantization Formats</td>
          <td>Q4_K_M (21.2GB), Q3_K_M (16.8GB), Q2_K (12.9GB), IQ1_M (8.24GB)</td>
      </tr>
      <tr>
          <td>Input Price</td>
          <td>Free (Apache 2.0, self-hosted only)</td>
      </tr>
      <tr>
          <td>Output Price</td>
          <td>Free (Apache 2.0, self-hosted only)</td>
      </tr>
      <tr>
          <td>Release Date</td>
          <td>July 22, 2026</td>
      </tr>
      <tr>
          <td>License</td>
          <td>Apache 2.0</td>
      </tr>
      <tr>
          <td>Runtime</td>
          <td>Stock llama.cpp, Ollama, LM Studio, PocketPal, Apple MLX</td>
      </tr>
  </tbody>
</table>
<p>The parameter count is worth a note. VIDRAFT markets this as a &quot;35B&quot; model, and the GGUF file metadata reports 34,660,610,688 total parameters, close enough to round to 35B and consistent with the Darwin-36B-Opus parent's own spec sheet. The architecture field in that same metadata is labeled <code>qwen35moe</code>, a naming holdover from the underlying model class rather than a claim about which Qwen generation it descends from. Darwin-36B-Opus's own model card is explicit that the base parent is Qwen 3.6-35B-A3B, not 3.5, even though POCKET's own README describes the lineage as &quot;Qwen3.5-family MoE&quot; in one place. That's a real inconsistency between VIDRAFT's own documents, and it's the kind of detail worth checking yourself before citing a model's lineage secondhand.</p>
<h2 id="benchmark-performance">Benchmark Performance</h2>
<p>VIDRAFT benchmarks POCKET-35B's IQ1_M build against <code>Bonsai-27B Q1_0</code>, the 1-bit build of PrismML's <a href="/models/bonsai-27b/">Bonsai 27B</a>, on the same hardware with the same stock llama.cpp binary. The comparison is self-reported by VIDRAFT, not independently reproduced, but the methodology (same tools, same machine, disclosed losses) is more transparent than most vendor benchmarks.</p>
<table>
  <thead>
      <tr>
          <th>Metric</th>
          <th>POCKET-35B IQ1_M</th>
          <th>Bonsai-27B Q1_0</th>
          <th>Result</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>CPU generation, Xeon 16-thread</td>
          <td>27.0 tok/s</td>
          <td>10.1 tok/s</td>
          <td>POCKET 2.69x faster</td>
      </tr>
      <tr>
          <td>GPU generation, H100</td>
          <td>197 tok/s</td>
          <td>89 tok/s</td>
          <td>POCKET 2.22x faster</td>
      </tr>
      <tr>
          <td>GPU prompt processing, H100</td>
          <td>753 tok/s</td>
          <td>1,816 tok/s</td>
          <td>POCKET 0.41x (slower)</td>
      </tr>
      <tr>
          <td>HellaSwag quality (400q)</td>
          <td>61.0%</td>
          <td>60.0%</td>
          <td>Statistical tie</td>
      </tr>
      <tr>
          <td>MacBook M3 Pro Metal generation</td>
          <td>25.4 tok/s</td>
          <td>12.8 tok/s</td>
          <td>POCKET 1.99x faster</td>
      </tr>
      <tr>
          <td>MacBook M3 Pro CPU generation</td>
          <td>13.8 tok/s</td>
          <td>4.4 tok/s</td>
          <td>POCKET 3.13x faster</td>
      </tr>
  </tbody>
</table>
<blockquote>
<p>&quot;MoE prefill wakes every expert, so sparsity stops helping there,&quot; VIDRAFT writes in its own README, describing why POCKET loses the GPU prompt-processing test.</p></blockquote>
<p>That line matters more than the wins do. Sparse MoE only pays off during generation, where the router activates a handful of the 256 experts per token. Prompt processing has to touch a much wider slice of the expert pool across a long input, so the &quot;3B active parameters&quot; pitch collapses on an H100 doing prefill, and Bonsai's dense-leaning 27B design comes out over twice as fast there. On a laptop, that gap disappears. VIDRAFT's own numbers show POCKET winning every axis on a MacBook M3 Pro, including prompt processing (240.7 versus 73.4 tok/s over Metal), because there's no longer enough raw GPU throughput for a dense model to out-brute-force a sparse one.</p>
<p>Reasoning quality tells a separate story. Quantizing the model costs real accuracy on GPQA Diamond's 198 questions under greedy decoding: the unquantized Qwen 3.6-35B-A3B base scores 73.2%, POCKET-35B's Q4_K_M build drops to 68.7%, and Q2_K falls further to 60.1%. VIDRAFT hasn't published a GPQA figure for the smallest IQ1_M build. That 73.2% baseline is also worth cross-checking against our <a href="/leaderboards/scientific-reasoning-llm-leaderboard/">scientific reasoning leaderboard</a>: Alibaba's own materials for Qwen 3.6-35B-A3B report 86.0% GPQA elsewhere, a 13-point gap from VIDRAFT's greedy run on the same base model that has nothing to do with quantization and everything to do with eval harness and prompting differences. Treat any single GPQA number, from any vendor, as harness-dependent until proven otherwise.</p>
<h2 id="key-capabilities">Key Capabilities</h2>
<h3 id="where-the-parent-models-score-actually-comes-from">Where the parent model's score actually comes from</h3>
<p>Darwin-36B-Opus's headline 88.4% GPQA Diamond score, the number that put VIDRAFT on Hugging Face's community leaderboard with 397B-parameter dense models, isn't a single-pass result. VIDRAFT's own evaluation methodology scores it in two phases: a greedy first pass across all 198 questions lands at 73.2% (145 correct), and a second pass re-runs every miss with 8-way majority voting plus a 16-vote tiebreaker round for close calls, lifting the final score to 88.4% (175 correct). That's a 15.2 percentage point gain from stochastic retry alone. POCKET-35B doesn't inherit that benefit, since nobody runs an 8-way majority vote on a phone; its GPQA numbers above are single-pass greedy, which is the fairer comparison for how the model actually gets used on-device.</p>
<h3 id="positioned-against-a-real-leaderboard-not-just-bonsai">Positioned against a real leaderboard, not just Bonsai</h3>
<p>VIDRAFT's own README places Darwin-36B-Opus tied for third on an April 23, 2026 snapshot of Hugging Face's GPQA Diamond leaderboard, level with the 397B-parameter Qwen3.5-397B-A17B and behind two entries from TNSA. A BigGo Finance report published five days later, on April 28, put the same model in fifth place. Leaderboard rank shifts fast as new entries land, so treat any specific ordinal as a snapshot rather than a fixed fact. The score itself (88.4%, Pass 2) has held up across VIDRAFT's own model card, its Hugging Face metadata, and third-party coverage.</p>
<p>The underlying research is documented in <a href="https://arxiv.org/abs/2605.14386">arXiv:2605.14386</a>, &quot;Darwin Family: MRI-Trust-Weighted Evolutionary Merging for Training-Free Scaling of Language-Model Reasoning,&quot; published May 14, 2026 by a seven-person VIDRAFT-affiliated author group as a NeurIPS 2026 submission. Its headline claim is actually about a different sibling: Darwin-27B-Opus at 86.9% GPQA Diamond, ranked 6th among 1,252 assessed models. Darwin-36B-Opus, the model POCKET-35B descends from, is the newer and higher-scoring release that came after the paper's own reported results.</p>
<h3 id="every-device-tier-gets-a-different-repo-not-just-a-different-quant">Every device tier gets a different repo, not just a different quant</h3>
<p><img src="/images/models/pocket-35b-iphone.jpg" alt="A close-up photo of a hand holding a black iPhone, showing its camera module and rear Apple logo">
<em>POCKET's phone-capable builds live in sibling repos, not in POCKET-35B-GGUF itself - the iPhone MLX build is a separate, smaller download.</em>
<small>Source: unsplash.com</small></p>
<p>It's worth being precise about what &quot;POCKET&quot; actually ships, because the collection is bigger than the one repo this article covers. POCKET-35B-GGUF, the subject here, targets PC and server CPUs with no GPU. A sibling repo, POCKET-KR-MLX, ships a 2-bit Apple MLX build sized for iPhone and Mac and tuned for Korean. POCKET-EN-GGUF covers English on both PC and phone with a 5.3GB &quot;iPhone-mix&quot; build meant to run through the <a href="https://github.com/a-ghorbani/pocketpal-ai">PocketPal</a> app. There's also POCKET-26B, a Gemma4-based sibling scoring 67% on GPQA Diamond that trades some quality for broader app compatibility today. VIDRAFT's iPhone and Android throughput claims apply to those sibling builds, not to POCKET-35B-GGUF's own four files, which VIDRAFT itself lists as not yet benchmarked on phone hardware.</p>
<h2 id="pricing-and-availability">Pricing and Availability</h2>
<p><img src="/images/models/pocket-35b-memchip.jpg" alt="A macro product photo of a green laptop RAM module with visible memory chips and gold connector pins">
<em>Every POCKET-35B tier is sized against system RAM, not VRAM - the whole pitch is that no GPU line item is needed at all.</em>
<small>Source: unsplash.com</small></p>
<p>POCKET-35B-GGUF is free, hosted on <a href="https://huggingface.co/FINAL-Bench/POCKET-35B-GGUF">Hugging Face under FINAL-Bench</a>, released under Apache 2.0 with no usage restrictions and no API tier. There's nothing to subscribe to. The only cost is hardware, and VIDRAFT is explicit about matching each quantization to a RAM budget rather than a GPU tier:</p>
<ul>
<li><strong>Q4_K_M</strong> (21.2GB) - top quality, needs roughly 32GB RAM</li>
<li><strong>Q3_K_M</strong> (16.8GB) - a 24GB RAM machine</li>
<li><strong>Q2_K</strong> (12.9GB, VIDRAFT's recommended &quot;daily driver&quot;) - 16 to 24GB RAM</li>
<li><strong>IQ1_M</strong> (8.24GB) - the smallest full build, fits a 16GB RAM box</li>
</ul>
<p>Quickstart is a single <code>llama-cli</code> invocation with <code>-ngl 0</code> to force CPU-only execution, no custom build flags:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">llama-cli -m POCKET-35B-Q2_K.gguf -p <span class="s2">&#34;your prompt&#34;</span> -ngl <span class="m">0</span> -t <span class="m">8</span>
</span></span></code></pre></div><p>VIDRAFT recommends capping <code>-t</code> at physical core count rather than logical thread count, since oversubscribing threads reportedly slows generation rather than speeding it up. For anyone weighing this against a conventional quantized deployment, our <a href="/guides/how-to-run-open-source-llm-locally/">guide to running open-source LLMs locally</a> and the <a href="/leaderboards/llm-quantization-impact-leaderboard/">LLM quantization impact leaderboard</a> both cover the tradeoffs of running Q2-class quantizations more broadly.</p>
<h2 id="strengths-and-weaknesses">Strengths and Weaknesses</h2>
<h3 id="strengths">Strengths</h3>
<ul>
<li>Runs on stock llama.cpp, Ollama, and LM Studio with no fork or custom build, unlike VIDRAFT's own claim that a comparable Bonsai GGUF build fails to load without a PrismML-patched runtime</li>
<li>CPU generation beats the comparable Bonsai-27B build by 2.69x on a 16-thread Xeon and by more than 3x on a MacBook M3 Pro's CPU cores</li>
<li>Retains the full 262,144-token context window inherited from Qwen 3.6-35B-A3B, confirmed directly in the GGUF file metadata rather than just marketing copy</li>
<li>Four quantization tiers give a real choice between quality (Q4_K_M) and footprint (IQ1_M) rather than one-size-fits-all compression</li>
<li>Apache 2.0 licensing with no usage restrictions and no pricing tier to negotiate</li>
</ul>
<h3 id="weaknesses">Weaknesses</h3>
<ul>
<li>GPQA Diamond drops from the base model's 73.2% to 68.7% at Q4_K_M and 60.1% at Q2_K; quality loss is real and gets worse fast at lower bit-widths</li>
<li>Loses to Bonsai-27B on GPU prompt processing by more than half (753 versus 1,816 tok/s on an H100), since sparse MoE routing doesn't help during prefill</li>
<li>VIDRAFT's own documentation contains a lineage inconsistency, describing the base architecture as both &quot;Qwen3.5-family&quot; and explicitly Qwen 3.6-35B-A3B in different documents</li>
<li>The 88.4% flagship GPQA score belongs to the unquantized Darwin-36B-Opus parent under expensive 8-way majority voting, not to anything POCKET-35B can reproduce in a single pass on a phone</li>
<li>No GPQA figure disclosed for the smallest IQ1_M quantization, the build most likely to run on the lowest-memory devices</li>
</ul>
<h2 id="related-coverage">Related Coverage</h2>
<ul>
<li><a href="/models/qwen-3-6-35b-a3b/">Qwen 3.6-35B-A3B model card</a> - the architecture and base weights Darwin-36B-Opus was bred from</li>
<li><a href="/models/bonsai-27b/">Bonsai 27B model card</a> - the PrismML compression model VIDRAFT benchmarks POCKET-35B against directly</li>
<li><a href="/leaderboards/edge-mobile-llm-leaderboard/">Edge and Mobile LLM Leaderboard</a> - on-device throughput rankings across phones, laptops, and GPU-free hardware</li>
<li><a href="/leaderboards/llm-quantization-impact-leaderboard/">LLM Quantization Impact Leaderboard</a> - how much quality other models lose across INT4 through 1-bit formats</li>
<li><a href="/leaderboards/scientific-reasoning-llm-leaderboard/">Scientific Reasoning LLM Leaderboard</a> - GPQA Diamond rankings for full context on where 73.2% and 88.4% sit</li>
<li><a href="/guides/how-to-run-open-source-llm-locally/">How to Run Open-Source LLMs Locally</a> - setup guidance for llama.cpp, Ollama, and MLX deployments</li>
</ul>
<h2 id="sources">Sources</h2>
<ul>
<li><a href="https://huggingface.co/FINAL-Bench/POCKET-35B-GGUF">FINAL-Bench/POCKET-35B-GGUF on Hugging Face</a></li>
<li><a href="https://huggingface.co/FINAL-Bench/Darwin-36B-Opus">FINAL-Bench/Darwin-36B-Opus on Hugging Face</a></li>
<li><a href="https://huggingface.co/posts/SeaWolf-AI/745666844415915">SeaWolf-AI - POCKET launch post on Hugging Face</a></li>
<li><a href="https://arxiv.org/abs/2605.14386">Darwin Family: MRI-Trust-Weighted Evolutionary Merging for Training-Free Scaling of Language-Model Reasoning - arXiv:2605.14386</a></li>
<li><a href="https://finance.biggo.com/news/NWiL0p0BoQmpnl36aM9q">Hugging Face GPQA Leaderboard Dominated by China and South Korea Models; VIDRAFT's Darwin Surges - BigGo Finance</a></li>
<li><a href="https://vidraft.net/index.html">VIDRAFT company site</a></li>
<li><a href="https://huggingface.co/Qwen/Qwen3.6-35B-A3B">Qwen/Qwen3.6-35B-A3B on Hugging Face</a></li>
<li><a href="https://huggingface.co/hesamation/Qwen3.6-35B-A3B-Claude-4.6-Opus-Reasoning-Distilled">hesamation/Qwen3.6-35B-A3B-Claude-4.6-Opus-Reasoning-Distilled on Hugging Face</a></li>
</ul>
]]></content:encoded><dc:creator>James Kowalski</dc:creator><category>Models</category><media:content url="https://awesomeagents.ai/images/models/pocket-35b_hu_8450c6eb10a8549b.jpg" medium="image" width="1200" height="675"/><media:thumbnail url="https://awesomeagents.ai/images/models/pocket-35b_hu_8450c6eb10a8549b.jpg" width="1200" height="675"/></item><item><title>A 35B Model That Runs on Your Phone Was Bred, Not Trained</title><link>https://awesomeagents.ai/news/pocket-35b-vidraft-darwin-evolutionary-merge/</link><pubDate>Sun, 26 Jul 2026 01:57:27 +0200</pubDate><guid>https://awesomeagents.ai/news/pocket-35b-vidraft-darwin-evolutionary-merge/</guid><description>&lt;p>A 28-year-old computer engineering student on leave from his university in Seoul just shipped a 35-billion-parameter model that runs on an iPhone. No cloud, no CUDA, no fork of anything. Kim Min-sik's startup, VIDRAFT, published POCKET-35B this week, and the pitch is blunt: stock &lt;a href="/guides/how-to-run-open-source-llm-locally/">llama.cpp&lt;/a>, a laptop with no graphics card, and reasoning performance the company says holds up against models many times its size.&lt;/p></description><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>A 28-year-old computer engineering student on leave from his university in Seoul just shipped a 35-billion-parameter model that runs on an iPhone. No cloud, no CUDA, no fork of anything. Kim Min-sik's startup, VIDRAFT, published POCKET-35B this week, and the pitch is blunt: stock <a href="/guides/how-to-run-open-source-llm-locally/">llama.cpp</a>, a laptop with no graphics card, and reasoning performance the company says holds up against models many times its size.</p>
<p>The twist is how VIDRAFT got there. POCKET wasn't trained. It was bred.</p>
<div class="news-tldr">
<p><strong>TL;DR</strong></p>
<ul>
<li>VIDRAFT, a Seoul AI Hub startup, released <a href="https://huggingface.co/FINAL-Bench/POCKET-35B-GGUF">POCKET-35B</a>, a 35B-parameter Mixture-of-Experts model that runs on CPUs, mini-PCs, and phones with no GPU</li>
<li>POCKET is a quantized descendant of <a href="https://huggingface.co/FINAL-Bench/Darwin-36B-Opus">Darwin-36B-Opus</a>, which VIDRAFT built by gradient-free &quot;breeding&quot; two existing Qwen models rather than training from scratch</li>
<li>Darwin-36B-Opus ranks 5th of 1,252 models on Hugging Face's GPQA Diamond leaderboard at 88.4%, but that number comes from multi-pass stochastic voting - a single greedy pass scores 73.2%, identical to its unmerged base model</li>
<li>POCKET's compressed variants score lower still on the same benchmark, 60.1% to 68.7% depending on quantization, and get slower rather than faster during GPU prompt processing</li>
<li>The merging method, called Darwin V7, is documented in an <a href="https://arxiv.org/abs/2605.14386">arXiv paper</a> and released under Apache 2.0</li>
</ul>
</div>
<h2 id="the-claims-side-by-side">The Claims, Side by Side</h2>
<table>
  <thead>
      <tr>
          <th>Claim</th>
          <th>VIDRAFT's number</th>
          <th>The catch</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>GPQA Diamond rank, Darwin-36B-Opus</td>
          <td>5th of 1,252 models, 88.4%</td>
          <td>Requires multi-pass stochastic retry with majority voting</td>
      </tr>
      <tr>
          <td>GPQA Diamond, single greedy pass</td>
          <td>73.2%</td>
          <td>Matches base Qwen3.6-35B-A3B exactly</td>
      </tr>
      <tr>
          <td>POCKET-35B Q4_K_M, GPQA greedy</td>
          <td>68.7%</td>
          <td>Best-quality quant, still below the flagship</td>
      </tr>
      <tr>
          <td>POCKET-35B Q2_K, GPQA greedy</td>
          <td>60.1%</td>
          <td>VIDRAFT's own &quot;best value&quot; recommendation</td>
      </tr>
      <tr>
          <td>CPU generation speed vs Bonsai-27B</td>
          <td>2.69x faster (27.0 vs 10.1 tok/s)</td>
          <td>Measured on a 16-thread Xeon</td>
      </tr>
      <tr>
          <td>H100 prompt processing vs dense rival</td>
          <td>0.41x (slower)</td>
          <td>MoE prefill wakes every expert, sparsity doesn't help</td>
      </tr>
  </tbody>
</table>
<h2 id="a-model-bred-not-trained">A Model Bred, Not Trained</h2>
<p>VIDRAFT's core technology isn't POCKET, it's the engine that produced its parent. Called Darwin V7, the system treats existing open model checkpoints as a genetic pool and recombines their weight tensors without a single gradient step. Per-tensor compatibility analysis decides which components can merge safely, an automated recombination pass builds the offspring, and a multi-phase benchmark run verifies the result. VIDRAFT says the whole breeding cycle takes under 10 minutes on one GPU, a fraction of what pretraining a model this size normally costs.</p>
<p>Darwin-36B-Opus, the parent behind POCKET, came from crossing <a href="/models/qwen-3-6-35b-a3b/">Qwen3.6-35B-A3B</a>, Alibaba's hybrid Gated DeltaNet/attention MoE base, with a second model fine-tuned on Claude Opus 4.6 reasoning traces. The recombination logic biases toward the reasoning parent for components tied to chain-of-thought and toward the base parent everywhere else. The method, detailed in an arXiv paper titled &quot;Darwin Family: MRI-Trust-Weighted Evolutionary Merging,&quot; calls this a 14-dimensional &quot;adaptive merge genome,&quot; and it's now sitting in front of NeurIPS reviewers.</p>
<h3 id="the-leaderboard-climb">The Leaderboard Climb</h3>
<p>The technique's real proof point predates POCKET by three months. On Hugging Face's GPQA Diamond leaderboard, a 1,252-model ranking of PhD-level science reasoning, VIDRAFT's Darwin family occupies every one of South Korea's five entries in the top 21, with Darwin-28B-Opus taking 3rd place at 88.89%, ahead of a dense 397-billion-parameter competitor roughly ten times its size. China holds the other 16 spots in that top tier.</p>
<p><img src="/images/news/pocket-35b-vidraft-darwin-seoul.jpg" alt="Seoul skyline at night, the city where VIDRAFT is based">
<em>VIDRAFT operates out of Seoul AI Hub, a city-backed startup facility, and became the only South Korean startup to get a direct collaboration proposal from Hugging Face in March 2026.</em>
<small>Source: unsplash.com</small></p>
<blockquote>
<p>&quot;Given the cost and resources required to build large models from scratch, we needed a different approach. Combining models turned out to deliver real performance gains,&quot; VIDRAFT CEO Kim Min-sik said of the strategy.</p></blockquote>
<p>VIDRAFT was founded in 2024, is backed by South Korea's National IT Industry Promotion Agency, and has spun its Darwin lineage into roughly 380 derivative models on the <a href="/leaderboards/open-source-llm-leaderboard/">open-source leaderboard</a> ecosystem. For a team this size to out-rank labs with dedicated pretraining budgets, on a <a href="/leaderboards/scientific-reasoning-llm-leaderboard/">scientific reasoning benchmark</a> no less, is the kind of underdog result that gets attention. Whether it holds up depends entirely on how you read the number.</p>
<h2 id="what-they-measured-and-what-they-didnt">What They Measured, and What They Didn't</h2>
<h3 id="the-multi-pass-gap">The Multi-Pass Gap</h3>
<p>The 88.4% headline score isn't what Darwin-36B-Opus gets on the first try. VIDRAFT's own model card shows Pass 1, greedy decoding, lands at 73.2%. Pass 2, which retries with temperature-based sampling and takes the majority vote across attempts, recovers another 15.2 points. That's a legitimate technique, plenty of labs report best-of-N numbers, but it means the leaderboard-topping figure describes a different, more expensive inference process than a single query. And the greedy number, the one closest to how most people actually run a chatbot, is identical to the unmerged Qwen3.6-35B-A3B base model. The breeding process didn't move that needle at all.</p>
<h3 id="the-compression-cost">The Compression Cost</h3>
<p>POCKET inherits the same ceiling and loses more on the way down. Its Q4_K_M build, the largest at 21.2GB, scores 68.7% greedy. The 12.9GB Q2_K variant VIDRAFT recommends as the &quot;best value&quot; option drops to 60.1%. When a Hugging Face commenter, Dipankar Sarkar, asked why POCKET loses to a dense competitor on H100 prompt processing (0.41x) but wins on the same operation on a MacBook M3 Pro, the mismatch points to something POCKET's own documentation admits: MoE sparsity helps token generation, where only 8 of 256 experts activate, but prompt processing wakes every expert regardless, erasing the advantage on hardware built for dense matrix throughput.</p>
<p>None of this means the numbers are fabricated. VIDRAFT publishes its quantization variants, its perplexity scores per language, and its benchmark harness openly, and the whole stack runs on stock llama.cpp anyone can audit. It means the marketing framing (top-5 on a leaderboard of 1,252 models) and the practical framing (what a single query on your phone actually returns) are two different claims wearing the same benchmark number.</p>
<p><img src="/images/news/pocket-35b-vidraft-darwin-helix.jpg" alt="Abstract rendering of a DNA double helix, evoking the &quot;breeding&quot; metaphor VIDRAFT uses for its merging technique">
<em>VIDRAFT frames Darwin's weight-recombination process as evolutionary &quot;breeding&quot; rather than training - a framing this piece borrows because it's technically apt, not because it's marketing copy.</em>
<small>Source: unsplash.com</small></p>
<h2 id="should-you-care">Should You Care?</h2>
<p>If the goal is a truly capable reasoning model that fits on a phone or a GPU-less mini PC, <a href="/models/pocket-35b/">POCKET-35B</a> is a real option, not vaporware. Apache 2.0 licensing, honest per-quant benchmarks, and 2-3x CPU throughput over a comparably sized <a href="/models/bonsai-27b/">Bonsai-27B</a> are useful wins for anyone doing on-device inference. Just don't treat the GPQA Diamond rank as a description of what you'll get from a single prompt on a 16GB laptop. Read it the way you'd read any <a href="/leaderboards/do-ai-benchmarks-still-matter/">contested leaderboard result</a>: as the best case under generous sampling, not the expected one.</p>
<p>For VIDRAFT, the more durable story isn't the leaderboard slot, it's the method. Breeding a 35B model from existing checkpoints in under 10 minutes on a single GPU, then compressing the result for phones, is a genuinely different way to compete with labs spending hundreds of millions on pretraining. Whether Darwin V7 keeps producing gains as the genetic pool of available open models gets picked over is the open question worth watching, not this month's leaderboard screenshot.</p>
<p><strong>Sources:</strong></p>
<ul>
<li><a href="https://huggingface.co/FINAL-Bench/POCKET-35B-GGUF">POCKET-35B-GGUF model card</a></li>
<li><a href="https://huggingface.co/FINAL-Bench/Darwin-36B-Opus">Darwin-36B-Opus model card</a></li>
<li><a href="https://huggingface.co/posts/SeaWolf-AI/745666844415915">SeaWolf-AI POCKET announcement post</a></li>
<li><a href="https://arxiv.org/abs/2605.14386">Darwin Family: MRI-Trust-Weighted Evolutionary Merging (arXiv)</a></li>
<li><a href="https://finance.biggo.com/news/NWiL0p0BoQmpnl36aM9q">BigGo Finance: Hugging Face GPQA Leaderboard Dominated by China and South Korea Models</a></li>
<li><a href="https://www.kmjournal.net/news/articleView.html?idxno=10978">KMJ: China and South Korea Dominate Hugging Face GPQA Leaderboard</a></li>
</ul>
]]></content:encoded><dc:creator>Sophie Zhang</dc:creator><category>News</category><media:content url="https://awesomeagents.ai/images/news/pocket-35b-vidraft-darwin_hu_e7b44a9bffabb6b4.jpg" medium="image" width="1200" height="675"/><media:thumbnail url="https://awesomeagents.ai/images/news/pocket-35b-vidraft-darwin_hu_e7b44a9bffabb6b4.jpg" width="1200" height="675"/></item></channel></rss>