← back to catalog · registered 2026-10-29 06:01

IndrasMirror/Qwen3.8-Flash-Next-XQ-Uncensored

IndrasMirror Qwen GGUF MoE
Your rig guess connected
? Why do I need an app?
Reading your rig…

This is a rough estimate. Install the free app - we'll show exact numbers.

Reading real hardware from your app right now. Numbers below are exact.

Below is the per-quantization compatibility for this model.

curl -H "Authorization: Bearer $ABL_KEY" \
     "https://abliteration.org/api/v1/models/IndrasMirror%2FQwen3.8-Flash-Next-XQ-Uncensored"
Response includes
  • classification unknown
  • files 3
  • author_summary 5 models
  • readme_text full
10 credits · hourly refresh · ~4 KB payload Get an API key →
Refusal direction extraction

No specific extraction method could be identified for this model. The producer either did not document it or used a proprietary pipeline.

What is a refusal direction? →
Downloads · 30-day
0
Likes
0
Model age
today
created 2026-10-29

Genealogy 0 direct forks

Full fork graph →

This model's place in the market. Above: what it was derived from. Below: the tree of everything derived from it.

Metadata

License
apache-2.0
Languages
en zh code
Tags
gguf qwen qwen3.8 qwen4exp mixture-of-experts quantized mixed-precision uncensored strata xolotl consumer-gpu text-generation

Related

Total size
0 B
Files
3
Quantizations
1
Registered
2026-10-29 06:01
Last updated on HF
2026-10-29 05:58

Files by quantization

Auxiliary files 3 files 8.55 KB
README.md 6.05 KB 3669c497 download
.gitattributes 1.48 KB a6344aac download
strata-xol-qfn.json 1.02 KB f0e49fe0 download

README current version from Hugging Face


license: apache-2.0
base_model: Qwen/Qwen3.8-Flash-Next
tags:

  • gguf
  • qwen
  • qwen3.8
  • qwen4exp
  • mixture-of-experts
  • quantized
  • mixed-precision
  • uncensored
  • strata
  • xolotl
  • consumer-gpu
    language:
  • en
  • zh
  • code
    pipeline_tag: text-generation

Qwen3.8-Flash-Next · XQ mixed-tier, abliterated

A 125B-parameter MoE (6B active) running on one gaming PC: RTX 4090 (24 GB) + 90 GB RAM + NVMe,
at 152 tok/s decode and 4,285 tok/s prefill.

Runs on Xolotl, an engine built for exactly this model and
this class of machine, on top of Strata.

This is a refusal-abliterated build: a rank-2 refusal-direction edit was applied to the model
before quantisation. The edit touches the dense backbone; the routed experts are untouched.


What it is

Qwen3.8-Flash-Next is a sparse MoE with 48 layers and 512 routed experts per layer, plus a 51.2B
n-gram (PLE) table held off-accelerator. QwenLM describes the architecture as "an early preview of
the architecture used in Qwen4"
, and the GGUF's arch string is literally qwen4exp.

total size 78.83 GiB
routed experts 46.92 GiB
PLE n-gram table 26.82 GiB
dense backbone 5.08 GiB
arch qwen4exp
tensors 1224
context see the base model's card

This is not a llama.cpp / Ollama / LM Studio GGUF. It uses per-expert quantisation types those
runtimes do not load — they expect one type per tensor, and here each layer's experts can carry
different formats. Use Xolotl.


How the bits are spent

Most of a MoE's parameters live in experts that any one token touches rarely, so a single global
bit-width is the wrong shape for this model. Instead:

  • Every routed expert gets its own format. The gate/up projections and the down projection are
    chosen separately, per layer, from a tier ladder measured on real routed tokens.
  • The down projection stays at a higher precision than gate/up. A down projection writes
    directly into the residual stream, so its error is not averaged away the way gate/up error is.
    This is also what preserves the abliteration edit, which lives in the down path.
  • The dense backbone is Q8_0. On this file the Q8_0 emit is exactly identity (the source was
    already Q8_0, and amax/127 recovers the block scale bit-exactly), so the backbone is
    bit-identical to the parent at +2.4 GiB over the nearest lossy tier. That is a deliberate
    quality choice, not an oversight.
  • The PLE table is a separate tier and is read from disk with O_DIRECT rather than held in
    RAM or VRAM — each row is read whole and its errors do not average out, so it gets a precision of
    its own.

The tier assignment is produced by a calibration-driven allocation. The allocation method, the
screening procedure and the tier ladder's derivation are not published.

Format mix in this file

type tensors what
Q8_0 690 dense backbone
F32 388 norms, router, hyper-connections
IQ4_NL 49 expert down projections + the PLE table
IQ2_S 58 expert gate/up
IQ3_XXS 32 expert gate/up
IQ3_S 4 expert gate/up
IQ2_XXS 2 expert gate/up
F16 1 —

Speed

Measured on this machine: Linux, RTX 4090 24 GB, Ryzen 7 5700X, 90 GB DDR4-3200, model on a
3.5 GB/s NVMe. 16,383-token prompt, 1,024 generated tokens, greedy:

metric value
decode 152.6 tok/s
prefill 4,285 tok/s
time to first token 5.14 s
speculative acceptance 0.876 (3.30 tokens per round)
CPU-bound experts per layer 1.03 distinct / 1.10 routed

Decode is bound by RAM bandwidth once the expert arena is warm, so numbers scale with memory
speed more than with the GPU. Longer generations read higher than short ones; a 64-token reply
measures lower than this table.

Tags: xol-qfn.


Quality

Being measured — placeholders below will be filled in before this card is announced.

top-1 agreement with the full-precision edited model pending
KL divergence pending
engine perplexity vs the full model pending
Gauntlet (core 7 tasks, 10 turns) pending
Gauntlet, DeepSeek/Qwen API for reference pending

What is already established: the quantisation was validated by reading the output file (arch,
tensor count, per-tensor types) rather than by trusting the quantiser's exit code, and the
abliteration was verified to survive quantisation by measuring the component of the activation
change along the edit direction — 0.96–1.01 retained across early, middle and late layers. A
whole-tensor norm ratio is the wrong metric for that test and was not used.


Quick start

git clone https://github.com/Indras-Mirror/Xolotl.git xolotl && cd xolotl
bash tools/xolotl/fetch-llama.sh
cmake -S . -B build-xolotl -G Ninja -DCMAKE_BUILD_TYPE=Release \
      -DSTRATA_ENABLE_CUDA=ON -DSTRATA_GGML_CUDA=ON -DSTRATA_MMQ_KQUANTS=ON \
      -DCMAKE_CUDA_ARCHITECTURES=89 -DSTRATA_GGML_DIR=$PWD/third_party/llama.cpp
ninja -C build-xolotl strata

Then serve it with the config below (strata-xol-qfn.json, port 8099). hf download the model and
its pack directory first; the pack is what teaches the engine this model's per-expert layout.

The engine treats the experts as a cache: the hottest ones in VRAM, the rest pinned in RAM, with
STRATA_ROUTE_RESIDENT preferring whichever tier is already resident. That bias is why the decode
number above is possible on a 78.83 GiB model in 90 GB of RAM.


Credits

  • Qwen for Qwen3.8-Flash-Next (Apache-2.0).
  • mrfakename for the rank-2 refusal-direction edit style.
  • Niko1221 for Strata, the tiered MoE engine this builds on.
  • ggml / llama.cpp for the compute backend.
  • Abliteration, quantisation, engine port and measurements: Indra's Mirror (Xolotl).

Support

If this has been useful and you want to help keep it going, you can
buy me a coffee.

Catalog is the map. Apps are the tools.

Run models on your own machine, not in the cloud.

Every model page has an "Open in Abliteration" button that hands the model directly to the first-party desktop client, at the quantization your rig can actually run. No API keys, no subscription, no prompt leakage.

Open in Abliteration