license: other license_name: qwen-community-1.0 license_link: LICENSE base_model: orcarouter/Qwen3.8-Flash-Next-Uncensored base_model_relation: quantized tags:
- gguf
- rocm
- vision
- speculative-decoding
- qwen3.8
- abliterated
- uncensored
- ced
Qwen3.8 Flash Next Uncensored R9V IQ4_XS
Ready-to-arrange model bundle for the R9V dual-RDNA4 inference profile. It uses the same layout as Qwen3.8-Flash-Next-R9V-IQ4_XS. The difference is that the target and vision projector come from orcarouter's abliterated (uncensored) build of Qwen3.8 Flash Next, and that the package also carries the CED projector for faster long-prompt prefill, which R9V turns on by default (see Long-prompt prefill (CED)).
Uncensored model: read first
orcarouter removed the model's refusal behaviour by abliteration: it projected a single "refusal direction" out of the weights. In orcarouter's words, the model has had its safety alignment substantially removed and will comply with harmful, unethical or illegal requests that the original Qwen3.8 Flash Next would refuse. orcarouter releases it strictly for research: interpretability, refusal-mechanism study, red-teaming and robustness evaluation. You are responsible for how you use it and for everything it generates. Add your own safety and moderation layers before putting it in front of anyone. See the orcarouter model card for their method and evaluations.
Contents and provenance
target/:UD-IQ4_XStarget GGUF shards, quantized for this package from orcarouter's Q8_0 GGUF of the abliterated weights. The per-tensor types follow Unsloth'sUD-IQ4_XSrecipe exactly (1,224 of 1,224 tensors). Unsloth did not produce these files. They were quantized from Q8_0 rather than BF16, and no importance matrix is recorded for them. Their quality has not been measured against Unsloth's ownUD-IQ4_XS.vision/: orcarouter's F16 vision projector, unchanged. orcarouter states that abliteration did not touch the vision tower.mtp/: R9V-assembled minimal MTP checkpoint, byte-identical to the reference package. Dense/nonexpert tensors come from the official BF16 checkpoint and routed experts from the official block-FP8 checkpoint. R9V did not train these weights. This is Qwen's original MTP head, not an abliterated one. It only drafts tokens, and the target checks every one, so output comes from the uncensored target.ced/: the split-16 CED prefill projector, fitted by R9V to this exact quant. It is byte-identical toced-projector-split16.safetensorsin Qwen3.8-Flash-Next-Uncensored-CED-Projector (revisiona588077a52b7c0061f7f38d0b05730a523ecd88d).metadata/: official Qwen tokenizer, processor, and model configuration.manifests/: the reference dual-R9700 hot-expert placement, bound to this package's target files. Abliteration leaves the MoE routers untouched.sources.lock.json: exact upstream revisions, sizes, and hashes.
Qwen remains the model author and upstream rights holder. orcarouter is
credited for the abliteration, the Q8_0 source and the vision projector.
Unsloth is credited for the UD-IQ4_XS recipe.
Install with R9V
Use R9V v0.4.0 or later with the profile qwen38-mtp4-uncensored. Setup does
everything: it downloads and SHA-256 verifies every file in this package,
extracts the PLE table, loads the pinned runtime image and checks the host.
The first start qualifies the placement on your machine.
./r9v setup qwen38-mtp4-uncensored --model-dir "$MODEL_DIR" -- --accept-model-license
./r9v start qwen38-mtp4-uncensored -- --timeout 2400
The first start compiles the model, so give it a long timeout. See the R9V installation guide.
When start reports ready, the OpenAI-compatible API is at
http://127.0.0.1:8004/v1 (health: http://127.0.0.1:8004/health) with the
served model name qwen3.8-flash-next. The API has no authentication, so R9V
publishes it on 127.0.0.1 only. To reach it from another machine, run setup
with R9V_HOST_BIND=0.0.0.0 (all interfaces) or one interface's IPv4/IPv6
address; setup saves it together with the port (R9V_HOST_PORT, default
8004). Anyone who can reach an exposed port gets a model with no refusals, so
put your own authentication and moderation in front of it first.
The 26.82 GiB per_layer_token_embd.weight (PLE) payload is already present
inside target shard 2 and is intentionally not uploaded again. Setup extracts
it with R9V's metadata-driven tool. The extracted file's SHA-256 is
34fa36f83de4216fe2aa78b5602aea1ba8007f959710c94bc4fbaff3e75fb9f0.
Reference configuration
- Two Radeon AI PRO R9700 32 GiB GPUs, TP2.
- 128 GiB DDR5.
- MTP depth 4.
- 131,072-token capacity, one request at a time.
- F16 vision input, one image/request.
- SSD PLE and tiered expert placement: experts outside the VRAM-resident hot set are served from a host-RAM cache.
Measured performance
Measured on the reference configuration above with the consolidated 1.3.0 runtime that R9V v0.4.0 ships.
Decode, greedy, warm runs:
| Prompt | ms per decode step | Tokens per step (MTP 4) |
|---|---|---|
| Short prose | 34.6 | 2.54 |
| Short code | 37.4 | 3.96 |
| ~8K context | 38.8 | 3.45 |
Exact prefill (CED not used) is about 1,780 tok/s on ~4K-token prompts and 1,870 tok/s on ~12K-token prompts. With CED on, as R9V ships it, ~12K-token prompts prefill at about 3,020 tok/s; prompts under 8,192 tokens are unchanged. These prompts are synthetic word lists. Real text measured roughly 15–20% slower on earlier R9V builds.
BetterBench 0.6.0, single stream, 20 runs per category, temperature 0.7: median decode ranged from 62 tok/s (reasoning) to 94 tok/s (JSON).
Long-prompt prefill (CED): on by default
CED approximates the late layers for the early part of a long prompt. Layers
0–15 run exactly on every prompt token. The projector in ced/ predicts what
layers 16–47 would see, and those layers only fill their caches from the
prediction. The last ~2K prompt tokens and every decode step run the full model
exactly.
R9V loads the projector at start and uses CED on prompts of 8,192 tokens or more, with a 2,048-token exact tail. The tradeoff, measured on the reference configuration:
- Faster: prefill is about 1.5× faster at ~13K tokens, rising to about 1.8× at 32K tokens and above. The R9V v0.4.0 clean install measured 1.47× at 12,960 tokens (the exact tail rounds up to 3,264 tokens there) and 1.80× at 31,987 tokens.
- Quality cost: about ×1.051 perplexity on prompts that depend on their long context (ΔNLL +0.050 ± 0.037 nats/token on the last 512 prompt tokens).
- MTP cost: on the first answer after a CED prefill, MTP accepts about 10% fewer tokens per step, so that answer decodes about 10% slower. A follow-up turn is back to normal.
- VRAM: the projector takes 1.76 GiB per GPU (bf16), with no steady-state decode cost from the loaded projector.
- Not approximated: prompts with images, prompts shorter than 8,192 tokens, and requests for prompt logprobs run exactly.
To turn CED off for the whole server, run ./r9v setup or ./r9v start with
--ced off. The projector is then not loaded. To keep one request exact, send
"vllm_xargs": {"r9v_ced": false} (OpenAI Python client:
extra_body={"vllm_xargs": {"r9v_ced": False}}).
The CED projector was fitted on English-heavy code, docs and prose of up to ~20K tokens. See the CED projector repository for the method, the full grade and its limitations.
Status
The immutable 24-file model package is public and remotely hash-verified
at revision b06687cb2f83ea38039cadd249341a7bd5b76fa3.
The clean-host install passed on the reference hardware with
R9V v0.4.0: fetch and
SHA-256 verification of all 20 package artifacts without a token, setup, a cold
first start with the placement qualification (including a 130,941-token prompt
at 131,072 context, minimum free VRAM 1.771 / 2.087 GiB against the 1.5 GiB
target), CED on (projector loaded, 1.47× / 1.80× prefill as above, exact
requests after CED requests bitwise identical) and --ced off, then a restart
that reused its receipt. The profile remains experimental: each new machine
qualifies on its own first start. The first ~1,200 decode tokens after a
fresh start run slower while caches warm up (about 45–49 ms/step with CED on,
38–41 with CED off); warm decode with CED on measured 34.3 ms/step. See the
qualification note.
License
These model artifacts are distributed under Qwen Community License 1.0; see
LICENSE. orcarouter's model card labels the abliterated weights Apache-2.0.
However, orcarouter's own repository LICENSE file is the Qwen Community License,
and the weights are a derivative of Qwen3.8 Flash Next, so this package follows
the upstream Qwen license. The R9V Apache-2.0 code license does not apply to
model weights. Users are responsible for reviewing the Qwen license, including
its separate terms for certain commercial MaaS/AI-work-assistant uses and scale
thresholds. Artifact attribution and exact upstream revisions are recorded in
THIRD_PARTY_NOTICES.md.