# Motrix v2.0.0-beta.16

- Product: Motrix (https://whatsnew.fyi/product/motrix)
- Vendor: agalwood
- Date: 2026-08-16
- Version: v2.0.0-beta.16
- Original notes: https://github.com/agalwood/Motrix/releases/tag/v2.0.0-beta.16
- Permalink: https://whatsnew.fyi/product/motrix/releases/v2.0.0-beta.16
- Labels: Pre-release

What's New is an index, not a publisher: every entry below links to the vendor's own release notes, which are the authoritative source. Entries are labelled where they are hand-curated sample data, pre-releases, or drawn from a secondary source such as a developer blog.

Reuse: the summaries, labels and curation here are © What's New. Quote freely with attribution and a link back; wholesale republication of the corpus is not permitted — terms: https://whatsnew.fyi/terms. The vendors' own release notes remain their publishers'.

---

- **fixed** — Repair container checks for linux/amd64 and linux/arm64 platforms with improved validation of Docker Buildx flat image configuration and platform metadata
- **changed** — Implement strict platform-keyed validation that fails closed on missing, unexpected, multiple, ambiguous, or conflicting platform data before metadata acceptance
- **added** — Add local BitTorrent fixture verification through aria2 JSON-RPC to prove exactly one active torrent has all bytes available and seeder port is reachable
- **changed** — Push each successful platform only by untagged content-addressed OCI digest to Docker Hub and GHCR, preventing single architecture from becoming official release independently
- **added** — Implement anonymous registry pulls and full Server runtime smoke tests on native runners before platform metadata upload
- **added** — Bind each platform record to exact version, source commit, workflow run and attempt, native runner identity, raw OCI index hash, image manifest, attestation manifest, provenance, and SPDX SBOM
- **changed** — Require single finalize job to proceed only after complete amd64/arm64 build set succeeds with rejection of missing, duplicate, unexpected, cross-wired, shared, or future-attempt digests
- **added** — Recheck both immutable version tags immediately before finalization with recovery logic to resume identical results or repair missing registries
- **changed** — Require Docker Hub and GHCR to expose identical final index digest, platform manifests, and attestation manifests with max-level BuildKit provenance validation
- **added** — Sign final index digest with protected tag-workflow identity and verify signatures anonymously before running public runtime smoke tests
- **changed** — Restrict Snap beta publication to source validation only, skipping Snap artifact builds and Store revision uploads
- **added** — Implement ground-up desktop rebuild with Electron 43, React 19, and TypeScript 7 featuring customizable Dashboard, dark mode, cross-platform application menu, and improved task-inspector feedback
- **added** — Add host-neutral download core supporting both desktop app and Node/Web Server with SQLite session recovery, tracker management, UPnP/NAT-PMP, HTTP, FTP, BitTorrent, and magnet support
- **added** — Implement MDXP-based integration for official CLI and browser handoff including local discovery and device-code pairing for remote Server instances
- **added** — Add QuickJS plugin sandbox with capability consent, bundled builtin plugins, and in-app plugin marketplace
- **added** — Publish persistent multi-platform Server containers for NAS and home-server deployments after complete native architecture verification

#### Motrix 2.0.0-beta.16

English | [简体中文](https://github.com/agalwood/Motrix/blob/v2.0.0-beta.16/docs/release-notes/2.0.0-beta.16.zh-CN.md)

Motrix 2.0.0-beta.16 is the next Motrix Turbo beta intended for public
distribution only after every protected release gate passes. It repairs the
two independent fail-closed container checks observed during beta.15 without
moving or reusing the immutable `v2.0.0-beta.15` tag.

The [beta.15 historical record](https://github.com/agalwood/Motrix/blob/v2.0.0-beta.16/docs/release-notes/2.0.0-beta.15.md)
documents the successful desktop, GitHub prerelease, and R2 distribution, the
two successful native container builds, and the incomplete container result.

##### Container inspection and smoke recovery

- Builds `linux/amd64` on `ubuntu-22.04` and `linux/arm64` on
  `ubuntu-22.04-arm`. Each job verifies its GitHub-hosted Linux runner and
  native architecture before Buildx starts. The container release path does
  not install or invoke QEMU.
- Validates Docker Buildx's documented flat image configuration for a
  single-platform source and the platform-keyed form used by multi-platform
  inspection. Missing, unexpected, multiple, ambiguous, or conflicting
  platform data fails closed before metadata can be accepted.
- Makes the local BitTorrent fixture prove through aria2 JSON-RPC that exactly
  one active torrent has all bytes available, then proves the seeder port is
  reachable from the Server container before creating the real download task.
  Tracker mutation is exercised only after the transfer and file hash pass;
  bounded failures report task, tracker, peer, and byte-progress diagnostics.
- Pushes each successful platform only by its untagged, content-addressed OCI
  digest to Docker Hub and GHCR. A single architecture never receives the
  public version tag and cannot become the official release on its own.
- Anonymously pulls the exact staged digest from both registries and runs the
  full Server runtime smoke on its native runner. Immutable platform metadata
  can be uploaded only after both registry smokes succeed.
- Binds each platform record to the exact version, source commit, workflow run
  and attempt, native runner identity, raw OCI index hash, image manifest,
  attestation manifest, provenance, and SPDX SBOM.
- Allows one finalize job to proceed only after the complete amd64/arm64 build
  set succeeds. It rejects missing, duplicate, unexpected, cross-wired, shared,
  or future-attempt digests before creating either versioned index.
- Rechecks both immutable version tags immediately before finalization. A clean
  run creates both indexes from the verified platform digests; a rerun resumes
  an identical complete result or repairs one missing registry from the
  verified existing index. Any conflicting immutable tag fails closed.
- Requires Docker Hub and GHCR to expose the same final index digest, platform
  manifests, and attestation manifests. It validates max-level BuildKit
  provenance, the exact source revision and builder run, and a non-empty SPDX
  SBOM for both architectures before signing.
- Signs each final index digest with the exact protected tag-workflow identity,
  verifies both signatures anonymously, and then runs the full public runtime
  smoke on native amd64 and arm64 runners against both registries.
- Stable floating aliases are handled by the final recovery-safe job only after
  every build, index, signature, provenance, SBOM, anonymous pull, and runtime
  gate succeeds. Beta releases publish only their immutable version tag, so
  beta.16 does not update `latest`, `stable`, or another stable alias.

The GitHub prerelease, R2 update feed, container registries, and Snap Store
remain independently gated publication channels. Their individual safety and
recovery rules are strict, but this release does not claim cross-channel
atomicity.

##### Snap beta policy

Snap is not part of the beta.16 distribution. Protected prerelease Snap runs
stop after source vali

_[Truncated at 4000 characters — full notes: https://github.com/agalwood/Motrix/releases/tag/v2.0.0-beta.16]_