A post marked "Paid partnership": EdgeRock 30 days 995 stars, but those aren't community-given

Rock Matrix, under A-share listed company Stonehill / Yanshan Technology (002195), open-sourced a 4B inference model. Its pitch is that no matter how long the context, the KV cache stays fixed at 72 MiB. The GitHub repo picked up 995 stars in 30 days, from three sources: Chinese finance articles and tech media, paid promotion on X, and every model platform covering it at once. The star curve rose at an unusually even rate, and it dropped once along the way. So far there are 0 issues and 14 forks. If you want to get stars for your own open-source project, the useful takeaway is the launch template, and learning to spot this kind of library. The project itself isn't worth following.

A long post from Oct 30

On the morning of Oct 30, 2026, AI blogger Charly Wargnier (@DataChaz) posted a long thread on X, opening in all caps:

THIS 4B MODEL JUST MADE LONG-CONTEXT MEMORY WAY MORE INTERESTING. 256K context. A fixed 72 MiB KV cache.

It followed with four numbers: throughput was 6.42× that of Qwen3.5-4B, KV cache was 99.1% smaller at 256K context, 233.7 tokens per second with 128K input and 128K output, and an average AIME 2024–2026 pass@1 of 82.9%. The post was tagged "Paid partnership" by X, with about 25k views.

Over the next few days, accounts like @FutureStacked (290k followers), @AriaWestcott (550k followers), @testingcatalog and @AI_Reveals posted nearly identical content, and EdgeRock's official account @RockMatrix11 reposted them one by one. That official account was only registered in late October. On 10-31, digg.com grouped these posts into a single topic with 7 sources. Apart from DataChaz's post, I haven't verified whether the others were paid.

Here's how the repo's stars grew over those days: 10-29 +33,10-30 +34,10-31 +46,11-01 +52 (daily GitHub stars). Almost no change compared with the previous week.

What it is

EdgeRock is a model Rock Matrix (under Stonehill / Yanshan Technology) released with HKUST and CMU; the repo contains inference and evaluation code. It's built by modifying Qwen3.5-4B rather than training from scratch: it keeps the original Gated DeltaNet layers and replaces global attention with sliding-window attention plus a set of "memory anchors" (Rock Memory Anchors). That keeps the attention KV per sequence at 72 MiB no matter how long the context gets. The cost is a small drop in scores: AIME falls from the original model's 86.1 to 82.9.

The top of the README has three bolded numbers: 82.9%, 72 MiB, 6.42×. Those same three numbers later appeared verbatim in a QbitAI headline ("KV cache cut by 99%, single-card throughput up 6×", 10-26) and in DataChaz's post.

It compares itself against the "bounded state" family of models, RWKV, Mamba and ByteDance's AHN, which are already weak at inference. Against small full-attention models it doesn't come out ahead: MiniCPM5-2B scores 87.8 on AIME. All the scores are self-reported, and AlphaSignal's 10-23 article also notes they are "not independently reproduced".

Where the stars came from

Data from GitHub's daily star history and each outlet's article dates, as of 11-06.

Put this table and the curve side by side, and a few things are off:

• The curve doesn't match the coverage. A normal open-source hit's stars jump with a specific exposure event: a Hacker News post, or a big account reposting it, and the count multiplies that day. EdgeRock runs almost as a straight line from day two. There's no spike during the People's Finance piece, the QbitAI piece, or the X promotion days.
• It lost stars once. On 10-23 it dropped by 44. GitHub does this when it purges suspicious accounts, though there could be other causes (inference).
• It stalled just short of 1000. It went from 11-05 to 995, then gained nothing the next day.
• Nobody is using its code. The fork-to-star ratio is only 1.4%, where same-age new repos usually sit around 11%. It has 0 issues, 0 PRs, and 10 watchers. About half of the 14 forking accounts were registered this year, have 0 followers, and have names that look randomly generated.
• The community isn't talking about it. There's no related thread on Hacker News, and a search of r/LocalLLaMA turns up nothing.

I haven't checked the starring accounts one by one, so "bought stars" is only a suspicion, not a confirmed fact. It could also be internal staff and partners recruiting people. But these signals appearing together at least show that these 995 stars were not given by developers who read the code and clicked on their own.

There is some real usage, though. The main model on Hugging Face has 2,692 downloads, the GGUF quantized builds have 4,305, and each ONNX build has roughly 430 (HF, 11-06). Some people downloaded it and tried it. Nobody came back with questions.

Why this one: a listed company's launch event, not a cold-start open-source project

Resources. A listed company, with bylines from two well-known universities, can mobilize Chinese financial press releases, tech media, and paid overseas bloggers all at once. Shareholders of the listed company, Rock Mountain Tech, discuss the model on East Money and Xueqiu, where it is also a stock theme. The sister series "Yan" from the same group has been telling the "non-Transformer" story since 2024. EdgeRock is the first time that story has been told to the overseas open-source community.

Numbers that spread in a single sentence. "Reasoning gets longer, memory doesn't grow", "72 MiB", "6.42x". Memory prices have been rising through 2026, and Google's KV-compression paper even moved storage stocks for a round. QbitAI's article opened on exactly that. Saying "saving KV means saving money" at this moment is an easy sell.

Blanketing every channel. Paper, code, Chinese and English white papers, HF, ModelScope, and Ollama, plus 13 quantized builds (GGUF, MLX, ONNX, AWQ, GPTQ, NVFP4, and on-device LiteRT), all went live within the same window. The commit log includes entries like "Improve EdgeRock discovery metadata" and "make benchmark evidence easier to cite", changes made specifically so people can find it and cite it.

But being everywhere doesn't mean it works in practice. The GGUF builds need its own bundled backend, so stock llama.cpp and Ollama can't run them. The prebuilt binaries only support Linux x86-64 and Hopper GPUs. The MLX build hasn't been tested on Apple silicon, and the mobile version is still a preview. For the most common ways local-model hobbyists run models, none of them work.

The same idea, already explored for years

"Longer context, flat VRAM" is a crowded path, and most of these predate it:

The last row is a useful reference: when a big company or listed company launches a new repo, stars can quickly reach a thousand or two while the fork rate stays low. That's the typical profile of these repos.

If you want to follow this, what can you actually do?

Building an equivalent model is out of reach for an individual. Retraining a 4B model, running 29 benchmarks, and producing 13 quantization formats takes compute and a team. The press releases and paid promotion that earned these 995 stars aren't available to individuals either.

That leaves two paths:

• Fix what it got wrong. For example, get stock llama.cpp or Ollama running EdgeRock, or get the MLX build working on Apple silicon. That's a real gap, but only worth it if people want to use this model. Right now there are 0 issues, and there's no sign of that demand.
• Take a different approach that doesn't change the model. The LMCache, kvcached, and TurboQuant route (KV compression, offloading, quantization) has more stars and works with existing models directly, so the barrier for developers is much lower. But that path is already taken, so it's not an empty niche.

If it were you

My call: Don't follow it. Its stars came from a listed company's launch event plus paid promotion, and real usage is close to zero. Two things are worth taking away: a launch playbook, and a way to recognize "launch-driven repos."

Who it fits: Small teams or labs building models or inference tools that already have a paper or benchmark numbers. You can learn from its "every platform in the same week" launch rhythm.

Who it doesn't fit: Solo developers hoping to build a "fixed-VRAM model" to collect stars. Compute and distribution won't get you there. People hoping to build add-on tools on top of it are also a poor fit, since its user base doesn't show up.

How to do it (if you're copying the playbook): Launch the paper, code, model weights, mainstream-format quantized builds, and bilingual docs in the same week. Put only three quotable numbers at the top of the README, and state the test conditions for each one. But first, make sure stock llama.cpp, Ollama, and MLX can run it directly. EdgeRock breaks right there: users download it, try it, and leave.

How to get attention: It shows that pairing Chinese media with overseas X bloggers can buy a wave of exposure, and also that this doesn't buy issues or forks. A cheaper route for an individual project is to pick a result people can reproduce, post it to r/LocalLLaMA and HN, and let people test it themselves (inference).

Is there a window to catch: No window to rush for. KV memory savings have been a hot topic for 2026 years, but big companies and academia are both crowded into this route.

What would show I got this wrong: ① Independent third parties reproduce its AIME and throughput numbers, and it gets discussed on HN or r/LocalLLaMA. ② Real issues and PRs start appearing in the repo, or llama.cpp or Ollama officially merges its architecture support. ③ It keeps gaining hundreds of stars a week after paid promotion stops. If any one of these happens, it moves from a "launch-driven" project to one people actually use, and then building tools around it is worth reconsidering.

A final note for anyone watching GitHub stars: Stars climb at a steady rate, don't line up with coverage events, drop at least once, stall just before a round number, have a fork rate far below same-age repos, and have no issues. When these show up together, treat it as a "launched" repo, not a "breakout" one.