0.17.0
MDK 0.17.0 releases the Rust workspace, WN Agent, MarmotKit (iOS, macOS and Android), and Marmot C from one source commit. See the 0.16.0 → 0.17.0 client upgrade guide for the required create/invite, audit, error, performance-snapshot, storage and Rust API changes.
Read full notes
MDK 0.17.0 releases the Rust workspace, WN Agent, MarmotKit (iOS, macOS and Android), and Marmot C from one source commit. See the 0.16.0 → 0.17.0 client upgrade guide for the required create/invite, audit, error, performance-snapshot, storage and Rust API changes.
Security
quinn-proto0.11.19 andquinn-udp0.5.16 fix RUSTSEC-2026-0523, RUSTSEC-2026-0524 and RUSTSEC-2026-0538. Every artifact links them through the QUIC preview transport. No action is needed.- Fresh, correctly signed envelopes that miss the live key no longer make a receiver rebuild past group state once per envelope. Live ingest reuses the cached historical contexts instead on SQLite storage (#2492).
Highlights
- Creates and invites go ahead with the members who are available. A member
with no usable KeyPackage or inbox route no longer fails the whole call:
results carry ordered per-account
memberOutcomes, and the group id or send summary is optional. A nonempty request with no available member creates no group and no commit. - Account and group reads no longer wait behind the account worker. Members, member-id pages, MLS state, roster and conversation snapshots, app components, quarantined groups, KeyPackage status, maintenance, commit delivery and backup restore status answer at once from the read state the worker publishes, even during a send, catch-up or convergence pass. During startup, a read that names a group still awaiting hydration waits for the worker to hydrate it, so keep startup loading and timeout handling.
- No more "history may be incomplete" notices without evidence. The notice appears only when MDK has evidence that messages are missing, or after a rejoin. A relay that cannot prove a route's history is retried quietly, an hour after it breaks and then on a backoff up to a day. Units broken before the upgrade probe right after it; if that fails, one that broke for lack of progress usually waits a day, and one that broke on a relay refusal or in the coverage-ledger conversion waits an hour. This ends the notice that flashed about once a second in busy groups and the inbox notice that came back a second after every dismissal.
- Failed sends can be discarded locally with
discardFailedSend, which publishes nothing. A failed send the user deletes now leaves the timeline instead of staying as a "deleted" row that still reports failure. - Polls and stickers can carry reply, thread (NIP-22) and effect tags with
createTaggedPollandsendTaggedSticker. Poll replies show reply previews like chat messages. stickerPackShareLinkbuilds a Sonar pack link offline, with up to eight relay hints.- Attachments download four at a time, and the ones on screen go first. A
download that lacks disk space waits as
StorageBlockeduntil free space covers it, instead of retrying every 15 seconds. - A group relay that refuses one of your confirmed changes for good now
warns until the user acknowledges it, even across restarts.
groupCommitDeliverylists therefusedRelayswith a cause, and further group changes fail withGroupCommitUndelivereduntil then. - Large group changes no longer stay pending for good. A commit over 64 KiB is
not sent to a relay whose size limit is unknown, because the relay could close
its socket on the frame and leave the commit possibly seen. A message that a
relay answered
rate-limited:orauth-required:and then refused stays pending and keeps retrying instead of failing. - Markdown turns a bare
note1,nevent1ornaddr1reference with a valid checksum into aNostrUritoken, so a copied note id can render as an event card. - The v5 audit log records what the recovery runner does for each group: fetches, races, and when it breaks, parks or stops trying. The White Noise audit receiver accepts the new kinds.
- Fixes: archive, forget and delete for an external-signer account's chat no
longer come undone; a foreground send no longer waits behind a retry to a
slow optional relay;
NotificationUpdate.isDmmatches the chat list; outgoing attachment promotion resumes without waiting for the maintenance tick; a crash inside a rewind window no longer quarantines the group on storage without savepoints; timeline updates name the right trigger after a withdrawn delete; and one-shotwncommands no longer delay a co-hosted account's next messages by 30 seconds.
Compatibility
Ship generated Swift/Kotlin, native libraries and C headers from this exact cohort together.
- Group creates return
GroupCreationResultFfiorDetailedGroupCreationResultFfi, and invites returnInviteMembersResultFfiorGroupInviteResultFfi, in place of a group id string,CreatedGroupFfi,SendSummaryFfiorGroupMutationResultFfi. Read the optional operation and thememberOutcomeslist before reporting success. - The v4 whole-file audit upload is gone. Replace
setAuditLogTrackerConfigwithsetAuditLogSource, called on every launch before opening accounts.postAuditLogFileandpostAuditLogTrackerUpdateare removed; keep callingpostAuditLogTrackerUpdateV5, whose result dropsv4Uploadedandv4SkippedReason. MarmotKitErrorgainsCreatedGroupMemberReportUnavailable { groupIdHex }. Exhaustive error switches must add it.AppPerformanceSnapshotFfidropsaccountGroupReadSnapshot.GroupCommitDeliveryFfigainsrefusedRelays(default empty).HistoryNoticeCauseFfi.UnprovenHistoryis no longer emitted. Keep it in exhaustive switches.
C hosts must recompile. Create and invite outputs are new result structs,
each freed by its own function (marmot_group_creation_free,
marmot_detailed_creation_free, marmot_invite_members_free,
marmot_group_invite_free); marmot_created_group_free is removed.
marmot_set_audit_log_source replaces both tracker-config setters, and the
v4 upload calls and types are removed. MarmotAuditLogTrackerUpdateResultV5
and MarmotAppPerformanceSnapshot change layout, and
MarmotGroupCommitDelivery appends refused_relays. Status 130
(MARMOT_STATUS_CREATED_GROUP_MEMBER_REPORT_UNAVAILABLE) is appended.
Rust hosts: creates and invites return GroupMemberResult<T>; a custom
TransportPeeler takes a PreparedGroupMessage; GroupStorage::put_group
is replaced by put_group_with_roster and put_group_keeping_roster, and
StorageProvider requires CommittedRosterStorage;
TransportEndpointFailure gains pre_send; and the directory's member
resolution takes a MemberResolutionPolicy. See the upgrade guide.
Storage: account databases migrate from schema 201 to 207 (migrations 0202 to 0207) on first open. The shared database is unchanged. Downgrade is unsupported: 0.16.0 refuses the upgraded account database. Keep a device-local copy of the MDK data directory before upgrading, taken while the app and every extension are stopped.
WN Agent: the agent-control protocol is unchanged, and creates and invites
through it stay all-or-nothing, failing as before when any requested member
is unavailable. wn CLI JSON for creates and invites adds
member_outcomes, and its operation fields can be null.
Known issues
- A photo in a NIP-22 thread reply stops decrypting once retention prunes the chat messages from its epoch (#3410).
- Startup hydration re-drives every outstanding fanout after each batch of four groups, which delays live transport on accounts with many groups (#3367).
- Pending Welcomes and a few other reads still go through the account worker's queue; moving them is the rest of #3273.
- Still open from 0.16.0: #3305 (relay-safety follow-ups), #2237 (late messages more than five epochs behind), #2277, #2283, #2389 and #2286 (group-change prompts), #2253 (group data extension order), #2158 (an upload in flight across an epoch change is lost) and #1445 (WN Agent's control socket grants its whole API to any authenticated client).
- Adding every device of an account remains best effort, a new send right after a reconnect can still go out ahead of older unsent ones, and the automatic-rejoin handshake's inner event kind is still under discussion (marmot#451).
Internal: history recovery's ledger side moves under one component, the
incident-replay crate and the v4 stand-in audit receiver are removed, the
identity and public-event preview parsers share one Nostr reference decoder
with unchanged results, and CI adds a native-host MarmotKit smoke; none of
this changes shipped behavior.
Release artifacts
v0.17.0: MDK source snapshot; workspace crates remain unpublished to crates.io.wn-agent-v0.17.0: WN Agent, terminal harness binaries, gateway plugins and checksum-paired installers.marmotkit-v0.17.0: iOS/macOS XCFrameworks, shared Swift source, platform privacy resources, Android Kotlin and all four JNI ABIs withandroid-elf.json, manifests and checksums.marmotc-v0.17.0: C library/header bundle and checksum.
Verify sibling SHA-256 files and source/version manifests; Apple binary ZIPs also
have SwiftPM checksums. Follow the
distribution guide. Dated
0.17.0-nightly.* builds are for testing only; pin this release instead.