Devstral-Small-2505-Deepseek-V3.2-Speciale-Distill
Devstral-Small-2505-Deepseek-V3.2-Speciale-Distill · IQ3_XS · by TeichAI
hf.co/TeichAI/Devstral-Small-2505-Deepseek-V3.2-Speciale-Distill-GGUF:IQ3_XS
TeichAI · IQ3_XS · on ollama · derivative build
A change to devstral-small-2505-speciale-distill by somebody other than its vendor. Nothing the vendor proved carries over; every number here was measured on these weights.
Measured by one node on hardware we do not own, and signed by each of them. What machines here actually proved — never what the card claims.
matrix built 8 Nov 2026 · every field verified against the signature of the node that produced it, and re-verifiable by you: each signed figure carries the exact bytes the node signed (signing_payload_b64) and the signature over them, and the ed25519 public key is embedded in node_did. effective_ctx is the context length a node PROVED by recall, never the length a model card advertisescontext declarednot declaredwhat the runtime reported. A node attests it was told this; nobody attests it is true.
context proved by recallnot probedthe largest size at which a machine could still find tokens planted across the whole prompt — start, middle and end, all of which had to come back.
Both numbers are needed to state a gap, and one of them is missing.
signed by this networkEvery line traces to a node signature.
What machines here proved
peak throughput ever signed0.36 tok/s · did:epn:002408…662a4e
machines that measured it1
samples behind those numbers1
regions it was proved in1
from the public record · unsigned
What the runtime says about it
No runtime metadata was attested for this model.The only unsigned block on this page. We attest we read these from the runtime — not that they are true. Nobody signs a model card.Proven across regions
Measured by
ranked on the provider standingsThe machine that measured it
nothing is averaged — the machine is what you are choosing—ctx proved
0.36tok/s now27 samples · 2,079s
no capability probed
Run this where your data already is
Tell us the workload, whose machines it should run on, and which jurisdiction it answers to.