Blackfrost-AI/Qwen-3.8-2.4T-A95B-Derisked-IQ1_0-GGUF overview
<div align="center" <h1 Qwen 3.8 2.4T A95B Derisked IQ1 0 GGUF</h1 <h3 Directional Weight Modification of Qwen3.8 Max · 2.4T MoE · imatrix GGUF IQ1 0 </h3 <p <…
Runs locally from ~369.97 GB disk (32 GB+ VRAM class GPUs with llama.cpp / guIDE).
Repository Files & Downloads
| File | Type | Quantization | Size | Link |
|---|---|---|---|---|
| Qwen-3.8-2.4T-A95B-Derisked-IQ1_0.gguf | GGUF | IQ1_0 | 369.97 GB | Download |
Model Details
| Model ID | Blackfrost-AI/Qwen-3.8-2.4T-A95B-Derisked-IQ1_0-GGUF |
|---|---|
| Author | Blackfrost-AI |
| Pipeline | text-generation |
| License | other |
| Base model | Qwen/Qwen3.8-2.4T-A95B |
| Last modified | 2026-10-08T13:36:53.000Z |
Model README
---
license: other
license_name: qwen
license_link: https://huggingface.co/Qwen/Qwen3.8-2.4T-A95B
base_model: Qwen/Qwen3.8-2.4T-A95B
tags:
- qwen3.8
- qwen3_5_moe
- moe
- dwm
- directional-weight-modification
- gguf
- imatrix
- llama-cpp
- single-node
- rtx-pro-6000
- gated
pipeline_tag: text-generation
library_name: llama.cpp
---
<div align="center">
<h1>Qwen-3.8-2.4T-A95B-Derisked-IQ1_0-GGUF</h1>
<h3>Directional Weight Modification of Qwen3.8-Max · 2.4T MoE · imatrix GGUF (IQ1_0)</h3>
<p><strong>Built by <a href="https://x.com/Blackfrost_AI">Blackfrost</a> · Las Vegas, NV</strong></p>
<p>
<img src="https://img.shields.io/badge/1×_node_8×_RTX_PRO_6000-047857?style=for-the-badge" />
<img src="https://img.shields.io/badge/GGUF_·_imatrix-1d4ed8?style=for-the-badge" />
<img src="https://img.shields.io/badge/Manually_gated-1f2937?style=for-the-badge" />
<img src="https://img.shields.io/badge/DWM_applied-7c2d12?style=for-the-badge" />
</p>
</div>
<div align="center">
</div>
---
Why this model exists
Qwen3.8-Max is a 2.4T-parameter mixture of experts. In BF16 it is a multi-terabyte, multi-node
deploy, and its stock refusal behaviour is tuned for a general consumer assistant — which means it
declines work that specialist teams do legitimately every day. Security engineers hunting bugs,
red teams, and domain researchers hit refusals on tasks that are squarely inside their remit.
This checkpoint addresses both at once:
- Footprint — importance-matrix-guided GGUF at ~397 GB, the smallest edition Blackfrost
publishes of this model. It brings a 2.4T MoE onto workstation-class GPUs rather than a
data-centre fabric deploy, and runs under llama.cpp rather than a multi-node serving stack.
- Behaviour — Directional Weight Modification (DWM) applied to soften over-refusal on
legitimate domain work, without removing the model's embedded safety protocols.
Safety behaviour can be further adjusted by domain specific chat templates.
The point is a model that stays useful inside a domain and stays safe. See
Safety posture — that section is not boilerplate, it is the design.
Choosing between the GGUF editions: this one targets RTX-class hardware. The sibling
…-DERISKED-UD-IQ3_XXS carries more bits per weight and targets a B200-class
node. Pick by the hardware you have.
---
Specifications
| | |
|---|---|
| Architecture | Qwen3_5MoeForCausalLM (qwen3_5_moe_text) — MoE + hybrid/linear attention |
| Base | Qwen/Qwen3.8-2.4T-A95B — official |
| Parameters | ~2.4T total · ~95B active |
| Layers / experts | 92 layers · 512 routed experts |
| Transform | DWM (directional weight modification) + imatrix GGUF quantization |
| Precision | IQ1_0, importance-matrix guided · mixed per-tensor allocation |
| Kept at higher precision | attention output · shared experts · normalisation · embeddings |
| On-disk | ~397 GB (370 GiB), single GGUF |
| Context | 262,144 native |
| Runtime | llama.cpp / llama-server |
| Serve shape | single node — 8× RTX PRO 6000 Blackwell (96 GB) recommended |
---
What "DERISKED" means
Not an ablation, and not an uncensored model.
Blackfrost calls this process DWM — Directional Weight Modification. Traditional abliteration
attempts to delete refusal wholesale. DWM does something narrower and reversible in principle:
it identifies a behavioural direction in the model's representation space and **softens the
model's response along that one axis**, by a controlled amount, on selected residual-write
surfaces.
What that buys, in practice:
- Less over-refusal on legitimate domain work — the model engages with a security question
instead of pattern-matching it to "dangerous" and declining
- Embedded protections mathematically preserved — the protected component is not the target of
the edit and is left intact by construction
- Predictable, tunable strength — one dial, measurable effect, not a black-box retrain
No SFT, no DPO, no distillation, and no re-training of any kind was applied.
> Transform parameters are not published in this card. The specific direction set, coefficient,
> and pass structure are Blackfrost method and are withheld. What is disclosed is *what was
> changed (surfaces above) and what was not* (everything else).
---
Safety posture
Read this before evaluating.
This is a de-risked model. Refusal behaviour has been deliberately modified at the weight
level. If your approval process treats reduced-refusal models as a distinct category, **this one
belongs in that category** — unlike Blackfrost's pruned-only releases, which carry their parent's
safety behaviour unmodified.
What that does not mean:
- This is not a "no-limits" model. DWM targets over-refusal, not the safety floor. Hard
protections — including minors-exploitation and self-harm — are retained by design and
are not the subject of the edit. Every Blackfrost de-risked release keeps those floors.
- Expected behaviour under a harmful request is deflection with a safer alternative, not
compliance and not a bare refusal.
Safety is designed as two layers, and the second layer is your responsibility:
- Weights — protections preserved geometrically, over-refusal softened
- System prompt — the deploying operator supplies a domain-specific system prompt in the
chat template, which acts as the policy driver for the endpoint
Serving this model with an empty or generic system prompt discards half the design. If you are
exposing it to customers or employees, layer 2 is not optional.
---
Lineage
| | |
|---|---|
| Base | Official Qwen/Qwen3.8-2.4T-A95B |
| Applied | DWM (directional weight modification) · importance-matrix GGUF quantization |
| Quantized from | the full-precision BF16 build — not transcoded from a lower-precision edition |
| Not applied | SFT · DPO · distillation · expert pruning (REAP) · router modification |
| Format | GGUF · IQ1_0 · single file |
| Sibling editions | …-DERISKED-UD-IQ3_XXS (B200-class GGUF) · …-DERISKED-W4A4-NVFP4 · …-DERISKED-FP8 · …-DERISKED-BF16 |
---
Measured behaviour
[PENDING — not yet published.]
| Benchmark | DERISKED-BF16 | This (DERISKED-IQ1_0) | Retention |
|---|---|---|---|
| — | pending | pending | —% |
Upstream Qwen3.8 figures are deliberately not reproduced here. Quoting a parent model's
benchmarks on a derivative card tells the reader nothing about this checkpoint. Blackfrost
publishes its own measurements against its own harness, or it publishes nothing.
Both quantization and DWM are trades, and this is the most aggressively compressed edition
Blackfrost publishes of this model — the compression trade here is larger than on the
higher-precision editions. When results land, this section will state the harness, the conditions,
and the retention figures — including any benchmark where retention is poor, and including
multilingual capability, which generic English-only evaluations do not capture. Retention is
measured against the BF16 edition, so the quantization cost is reported separately from the
DWM effect.
---
Deployment notes
- Hardware. Single node. 8× RTX PRO 6000 Blackwell (96 GB) holds the weights at roughly half
the available VRAM, leaving substantial room for KV cache. Smaller configurations can run it by
reducing context or offloading layers to system RAM via --n-gpu-layers.
- File. Single GGUF. Point
llama-server --modelat that file. - Thinking is always on. Reasoning tokens consume the generation budget, so allow
≥512 max_tokens or visible content can come back empty while the model is still reasoning.
- Context. 262,144 native. KV cache is the main consumer of headroom beyond the weights —
size context to the VRAM you have left.
- Load time. Cold load of a multi-hundred-gigabyte build is slow. Budget generously.
- Integrity. Verify byte totals against the published checksums after download before
attributing a load failure to the weights.
Quick serve (llama.cpp)
llama-server \
--model "$MODEL_DIR/Qwen-3.8-2.4T-A95B-Derisked-IQ1_0.gguf" \
--ctx-size 32768 \
--n-gpu-layers 999 \
--host 0.0.0.0 --port 8000
OpenAI-compatible: POST /v1/chat/completions, GET /v1/models.
Remember to supply your domain system prompt — see Safety posture.
---
Access & licensing
This repository is manually gated. Access requests are reviewed by a person. Access is free;
no purchase is required.
- Base licence: Qwen3.8-2.4T-A95B — the
upstream terms apply to this derivative and travel with it.
- Redistribution: do not redistribute weights outside your grant.
- Access: Free. Submit a Hugging Face access request for review.
Ask us about DWM strength tuned to your workload, domain-specific system-prompt packages, or
evaluation against your own harness rather than generic benchmarks.
---
Contact Blackfrost
<div align="center">
<h3><a href="https://x.com/Blackfrost_AI">@Blackfrost_AI</a> on X</h3>
<p><strong>DMs are open.</strong> Fastest route to a human.</p>
<p>Bug reports are better on the Community tab<br>
so other users can see the fix.</p>
<p><strong>Blackfrost</strong> · Las Vegas, Nevada<br>
Frontier model engineering</p>
</div>
---
<div align="center">
<p><strong>Qwen-3.8-2.4T-A95B-Derisked-IQ1_0-GGUF</strong> · © 2026 Blackfrost Softwares Corp.<br>
<a href="https://x.com/Blackfrost_AI">@Blackfrost_AI</a></p>
</div>
Run Blackfrost-AI/Qwen-3.8-2.4T-A95B-Derisked-IQ1_0-GGUF with guIDE
Download guIDE — the AI-native code editor with local LLM inference and 69 built-in tools.
Source: Hugging Face · Compare models