Marmot
Protocol
Development Kit
Documentation
Apps
Awesome
Releases
Community
GitHub
Donate
Contact
Protocol
Development Kit
Documentation
Apps
Awesome
Releases
Community
GitHub
Donate
Contact

Marmot releases.

Follow releases of the tools behind Marmot. Read the original notes, explore improvements, and check what matters before upgrading.
15 November 2026

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.

Original notesGitHub release
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-proto 0.11.19 and quinn-udp 0.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 createTaggedPoll and sendTaggedSticker. Poll replies show reply previews like chat messages.
  • stickerPackShareLink builds 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 StorageBlocked until 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. groupCommitDelivery lists the refusedRelays with a cause, and further group changes fail with GroupCommitUndelivered until 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: or auth-required: and then refused stays pending and keeps retrying instead of failing.
  • Markdown turns a bare note1, nevent1 or naddr1 reference with a valid checksum into a NostrUri token, 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.isDm matches 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-shot wn commands 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 GroupCreationResultFfi or DetailedGroupCreationResultFfi, and invites return InviteMembersResultFfi or GroupInviteResultFfi, in place of a group id string, CreatedGroupFfi, SendSummaryFfi or GroupMutationResultFfi. Read the optional operation and the memberOutcomes list before reporting success.
  • The v4 whole-file audit upload is gone. Replace setAuditLogTrackerConfig with setAuditLogSource, called on every launch before opening accounts. postAuditLogFile and postAuditLogTrackerUpdate are removed; keep calling postAuditLogTrackerUpdateV5, whose result drops v4Uploaded and v4SkippedReason.
  • MarmotKitError gains CreatedGroupMemberReportUnavailable { groupIdHex }. Exhaustive error switches must add it.
  • AppPerformanceSnapshotFfi drops accountGroupReadSnapshot.
  • GroupCommitDeliveryFfi gains refusedRelays (default empty).
  • HistoryNoticeCauseFfi.UnprovenHistory is 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 with android-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.

12 November 2026

0.16.0

MDK 0.16.0 releases the Rust workspace, WN Agent, MarmotKit (iOS, macOS and Android), and Marmot C from one source commit. See the 0.15.0 → 0.16.0 client upgrade guide for required enum, error, event, deployment, storage, C NIP-46 and Rust API changes.

Original notesGitHub release
Read full notes

MDK 0.16.0 releases the Rust workspace, WN Agent, MarmotKit (iOS, macOS and Android), and Marmot C from one source commit. See the 0.15.0 → 0.16.0 client upgrade guide for required enum, error, event, deployment, storage, C NIP-46 and Rust API changes.

Security

  • OpenMLS moves from the erskingardner/openmls fork to upstream main, with the fixes released in OpenMLS 0.9.1 and 0.9.2. A Welcome, GroupInfo, Proposal or Commit with deeply nested extensions could abort the process (GHSA-gc79-23g3-8g52), and anyone can gift-wrap a Welcome to a user. A rejected private message could advance its sender's ratchet and block that sender's later messages (GHSA-p276-g3f3-wwgh). Stored groups load unchanged, and members on 0.15.0 and 0.16.0 interoperate. No action is needed.
  • Hermes creates inbound attachment staging private (0700 directory, 0600 files) and writes its gateway config.yaml, backup and temporary files 0600 regardless of umask.

Highlights

  • A chat no longer stops receiving new messages after its account's live subscriptions are rebuilt. A late end-of-stored-events reply from a relay held the group's live messages until unrelated activity woke recovery, and on an idle account nothing did.
  • Relay size limits. MDK no longer sends an event to a relay known to refuse it for size. Hosts can list limits in the deployment (relayEventLimits); the White Noise preset sets 2 MiB on its two relays, and for events over 64 KiB a relay's advertised NIP-11 message size also counts. A group create or invite whose Welcome fits none of an invitee's inbox relays fails up front as EventTooLarge { artifact: Welcome }, before anything is created or sent. KeyPackage, block-list, sticker, profile, follow-list and relay-list publishes report size refusals as EventTooLarge too.
  • A queued group change that no relay will take is retired once and announced as QueuedIntentRefused with reason event_too_large, the artifact and its size class, instead of being retried on every drain.
  • Direct chats: start_direct_conversation (C marmot_start_direct_chat) reuses or creates the direct chat with a peer, with both accounts as founding admins, and a retry reuses the same group.
  • Relay liveness for settings screens: per-account relay state, a live subscription and a reconnect for one configured relay.
  • Audit log delivery and retention. v5 delivery no longer stalls on devices that keep many segments or retries silently forever. Hosts can read each account's delivery status, and set retention by age (1–30 days) and a per-account size budget, 256 MiB by default.
  • Stuck groups. A group no longer stalls behind a full deferred-peel backlog (caps raised fourfold), and the recovery runner's hourly breaker rises from 720 to 7,200 quanta, so a first catch-up of many groups no longer pauses the account. A group whose read of past state cannot restore its live state is quarantined as RewindRestoreFailed rather than running on stale state; the next open tries to restore it, and it stays quarantined if that fails.
  • Commits settle correctly when a group relay is refused by the host-safety rule, when a relay URL is spelled with an upper-case host or explicit default port, and when a crash interrupted the send.
  • WN Agent: group_admin reads, promotes, invites and removes a group member.
  • NIP-46 remote signers are shared by Swift, Kotlin and C. MDK owns each account's signer session and credentials, restores them at startup without a host callback, and requires the user to approve the exact permission set before pairing.
  • Swift: MarmotKit ships nextCancellable() for its five snapshot subscriptions, which forwards task cancellation to the native receive. Apps with their own copy delete it.
  • Media replies: Hermes and the agent-control send_media request can send attachments as a reply, and durable app media uploads keep their reply target.
  • Fixes: joining several groups quickly no longer records history loss and a needless re-sync; a leave blocked by a rival branch is re-driven, so sign-out no longer waits out its 30 s deadline; a chat the account was removed from no longer wakes its worker every 10 ms; a manual relay reconnect no longer stalls for the 5 s retry interval; wiping a generated identity mid-setup, or before a delayed setup handoff, no longer creates a stray account; an invite decline that timed out while still queued no longer leaves the group later (one already started still completes, so read the group's state before offering Accept); offline accounts stop repeating replay sync on every idle tick; an audit file a receiver's 409 blocked under 0.15.0 resumes delivery; relay replay storms no longer fill the audit log; live notifications reuse lookups across events, and directory queries overlap.

Compatibility

Ship generated Swift/Kotlin, native libraries and C headers from this exact cohort together.

  • AppGroupHydrationQuarantineReasonFfi gains REWIND_RESTORE_FAILED (.rewindRestoreFailed). Exhaustive switch/when statements must add it.
  • GroupEventKindFfi.QueuedIntentRefused gains artifact and sizeClass. Positional Swift patterns and Kotlin constructors or destructuring add them.
  • MarmotDeploymentFfi gains relayEventLimits (default empty).
  • rotate_key_package, republish_key_package, account setup's KeyPackage publish, block_user, unblock_user and sync_sticker_packs now fail as EventTooLarge when every relay refuses for size, where they returned Runtime, BlockListUnavailable or StickerNetwork.
  • MarmotKitError gains Nip46(reason:). Exhaustive error switches must add it. No MarmotEventFfi case or C status is added.
  • Swift apps that define their own nextCancellable() on these subscriptions must delete them: the Swift asset now defines the same methods.

C hosts must recompile: MarmotGroupEventKind's QueuedIntentRefused body appends three fields, and enum values are appended; none is renumbered. NIP-46 hosts must review and approve permissions before pairing or connecting, import each 0.15.0 vault export once, then resume restored sessions with marmot_nip46_resume. marmot_nip46_free now releases only the handle, and marmot_nip46_cancel stops a session without removing its stored credentials; revoke with marmot_nip46_logout, marmot_nip46_remove or account sign-out.

Rust hosts: onboarding moves to MarmotAppRuntime::account_setup(); AppClient and MarmotApp::client need the test-support feature; and MarmotDeployment, KeyPackagePublishError, PreparedSessionSend, RuntimePerformanceOperation, AuditOtlpSendResult, AppError, submit_media_attachments, AgentControlRequest::SendMedia and the engine's create calls change. See the upgrade guide.

Storage: account databases are unchanged (no account migration). The shared database migrates from schema 3 to 4 (0004_audit_log_retention) on first open, and the local audit delivery cursor moves to version 2. Downgrade is unsupported: 0.15.0 refuses both. Keep a device-local copy of the MDK data directory before upgrading, taken while the app and every extension are stopped, so no database or WAL file is open while it is copied.

WN Agent and its plugins must be upgraded together: a 0.15.0 connector closes the socket on group_admin and sends a reply-targeted send_media as ordinary media.

Known issues

  • Follow-ups from the relay-safety work are open in #3305: refused relays on the legacy Welcome path, a typed no-usable-relay error, and more. Push-trigger gift wraps ignore known relay limits and can still be sent to a relay over its limit. Sibling Welcomes, chosen-id device-group creates and recovery or own-device commits skip the up-front size check, but their events are still withheld from relays over a known limit.
  • Still open from 0.15.0: #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: CI adds a flake leaderboard (just flake-report, just flake-stress) and a test-timing ratchet, and Windows CI verifies tool checksums; none of this ships.

Release artifacts

  • v0.16.0: MDK source snapshot; workspace crates remain unpublished to crates.io.
  • wn-agent-v0.16.0: WN Agent, terminal harness binaries, gateway plugins and checksum-paired installers.
  • marmotkit-v0.16.0: iOS/macOS XCFrameworks, shared Swift source, platform privacy resources, Android Kotlin and all four JNI ABIs with android-elf.json, manifests and checksums.
  • marmotc-v0.16.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.16.0-nightly.* builds are for testing only; pin this release instead.

9 November 2026

0.15.0

MDK 0.15.0 releases the Rust workspace, WN Agent, MarmotKit (iOS, macOS and Android), and Marmot C from one source commit. See the 0.14.0 → 0.15.0 client upgrade guide for required record, error, event, header, storage and interoperability changes.

Original notesGitHub release
Read full notes

MDK 0.15.0 releases the Rust workspace, WN Agent, MarmotKit (iOS, macOS and Android), and Marmot C from one source commit. See the 0.14.0 → 0.15.0 client upgrade guide for required record, error, event, header, storage and interoperability changes.

Highlights

  • Accounts with several devices. Creating a group or inviting adds every device of each account (up to 20 KeyPackages published in the last 30 days, or the single best valid one when none is that recent), and members are listed once per account with a device_count. A device joins only through the Welcome that names its own KeyPackage. New groups whose founding devices all support it require the account-devices component (marmot.group.account-devices.v1); an admin can turn it on in an existing group with enable_account_devices.
  • Automatic rejoin. An account worker rejoins a group copy that became Unrecoverable through an authenticated handshake with an admin device over the account inbox, with bounded retries.
  • Recovery owns account history. Catch-up after time offline is bounded and paced, history arrives in order, newer live messages wait until the fetched backlog is admitted, and account_recovery_status reports groups still catching up. A rejoined group raises one BeforeRejoin history notice.
  • Chat-list queries. Typed filters (unread, pinned, archived, direct, group, muted, chat text, message text and more) combine with AND/OR/NOT, and hosts can select every chat a filter matches for bulk actions.
  • Timeline search filters by sender, date range and attachment type, and matches non-ASCII text case-insensitively.
  • Sonar-compatible sticker packs, NIP-51 custom emoji sets with pinned local installs, and custom reaction artwork lookup.
  • Leaving as an admin. A blocked leave (the last active admin) is shown and can be cancelled with cancel_leave. sign_out_and_wipe steps an admin down and leaves the chats another account also administers before wiping.
  • Push notifications reach every device of a member, newly added members learn existing tokens, and devices repair missed tokens inside each group.
  • Sends: queued offline sends publish after reconnect, a send never overtakes one queued before it, a Welcome waits until its Commit is published, failed convergence retries back off and park, and refused queued intents are retired with QueuedIntentRefused. Oversized events report EventTooLarge.
  • KeyPackages are valid for 30 days and refreshed weekly. Sign-out deletes only this device's KeyPackage slot instead of every device's.
  • External signers are no longer asked to sign the identity proof again on every reopen.
  • Pasted note1, hex and author-only nevent references now resolve through the deployment's discovery indexers and the author's write relays.
  • WN Agent: wn-agent doctor, a connector-only install-wn-agent.sh for your own control-socket client, historical attachment download with leases, founding co-admins, and default relays with published relay-list adoption.
  • Lower idle cost: maintenance ticks with nothing to do no longer open write transactions, wnd no longer grows about 3 MB per request, and cached user search ranks in SQL and finds people past the 10,000th cached identity.
  • Security: the pinned Nostr SDK rejects tampered events even when their id is cached, directory events are verified before they are forwarded or stored, account records are written owner-only, local audit files expire after 30 days, and elliptic-curve/HPKE (RUSTSEC-2026-0387), openssl and the OpenClaw plugin's npm dependencies are updated.

Experimental device groups (pairing, linked devices, sign-in review, history transfer and backups) continue behind the dev-device-groups build feature and new_with_experimental_device_groups. Ordinary builds and constructors keep them off and refuse accounts that already use them.

Compatibility

Ship generated Swift/Kotlin, native libraries and C headers from this exact cohort together.

  • Interoperability: every 0.15 device advertises the account-devices component. A new group requires it when the creator and every device added at creation advertise it, and 0.14 or older clients cannot then be invited into it. Existing groups are unchanged until an admin enables it.
  • TimelineMessageQueryFfi adds sender, since, until and cursorGroupId with no binding defaults. MarmotDeploymentFfi drops keyPackagePreferredClients and keyPackageLastClients.
  • MarmotKitError gains 22 cases, including EventTooLarge, MediaReferenceStaleEpoch, MediaReferenceEpochUnsettled, LeaveNotBlocked, InvalidChatListQuery, AccountUnlinked, the sticker and emoji-set errors, and GroupRecoveryUnsettled/GroupRecoverySourceMismatch. Some failures that used to arrive as Runtime, Publish or InvalidMediaReference now use them, and busy, closed or full storage arrives as StorageBusy, StorageClosed or StorageFull.
  • MarmotEventFfi gains eight cases, and WelcomeDeliveryPending gains sizeClass. HistoryNoticeCauseFfi gains UnprovenHistory and BeforeRejoin; SelfMembershipFfi and ConversationParticipationFfi gain DeviceRemoved; GroupEventKindFfi gains QueuedIntentRefused.
  • Media references saved by 0.14 lack sourceEpochIdentity; sending one is refused with MediaReferenceStaleEpoch, so re-upload instead.
  • Admin invitees must step down before declining an invitation, and OnboardingIssueFfi::MultiDeviceUnsupported is no longer produced.

C hosts must recompile. marmot_deployment_set_key_package_client_preference is removed. MarmotMediaAttachmentReference gains source_epoch_identity mid-struct; message, timeline, chat-list preview and notification records gain a sticker pointer mid-struct; MarmotTimelineMessageRecord gains recipient_confirmed mid-struct; MarmotClientOptions and MarmotTimelineMessageQuery gain trailing fields. Statuses 108–129 and enum values are appended; none is renumbered.

Rust hosts: cgka-session is now marmot-session, TimelineMessageQuery and chat-list query types gain fields and variants, AppError gains variants, and the diagnostics exporters move to marmot-observability. See the upgrade guide.

Account databases migrate from schema 116 through 201 on first open. Downgrade is unsupported: 0.14.0 refuses the migrated database. Keep a device-local copy of the account directory before upgrading. See the storage-format contract.

Building from source now needs the Odin compiler (scripts/install-odin.sh, or set ODIN), because Markdown parsing moved to Odin. Published artifacts are unaffected.

WN Agent and its plugins must be upgraded together: a 0.15.0 client sending a new request, such as group_create_capabilities, to a 0.14.0 connector sees the socket close without an error. The OpenClaw plugin requires OpenClaw 2026.10.10 or newer and Node 24.22.1+ (24.x) or 26.12.1+.

Known issues

  • Still open from 0.14.0: #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 is best effort: a device whose KeyPackage a relay does not return in time is left out until the account is invited again, and an account for which one relay returns a full page (500) of KeyPackages or of KeyPackage deletion requests cannot be invited.
  • Right after a reconnect, a new send can still go out ahead of older unsent ones.
  • A failed legacy group create in an earlier release can have left orphaned MLS state; 0.15 stops creating it but does not purge it.
  • Migration 0175 refuses to open an account whose saved outbound fanout or group evolution does not decode, rather than risk reusing a send reference.
  • The automatic-rejoin handshake's inner event kind is still under discussion (marmot#451).

Release artifacts

  • v0.15.0: MDK source snapshot; workspace crates remain unpublished to crates.io.
  • wn-agent-v0.15.0: WN Agent, terminal harness binaries, gateway plugins and checksum-paired installers, now including install-wn-agent.sh.
  • marmotkit-v0.15.0: iOS/macOS XCFrameworks, shared Swift source, platform privacy resources, Android Kotlin and all four JNI ABIs with android-elf.json, manifests and checksums.
  • marmotc-v0.15.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.15.0-nightly.* builds are for testing only; pin this release instead.

23 October 2026

0.14.0

MDK 0.14.0 releases the Rust workspace, WN Agent, MarmotKit (iOS, macOS and Android), and Marmot C from one source commit. See the 0.13.0 → 0.14.0 client upgrade guide for required constructor, record, error, header, storage and backup changes.

Original notesGitHub release
Read full notes

MDK 0.14.0 releases the Rust workspace, WN Agent, MarmotKit (iOS, macOS and Android), and Marmot C from one source commit. See the 0.13.0 → 0.14.0 client upgrade guide for required constructor, record, error, header, storage and backup changes.

Highlights

  • Encrypted media files. Attachment bodies, download checkpoints, avatars and group images move out of the account database into encrypted per-file storage under the account's media/ directory. Bodies already in the database move in the background, and a one-time compaction returns the freed space when the account is small enough.
  • Manage storage. Hosts can show per-account and per-chat attachment usage, list the largest retained attachments, and remove a chat's attachments or everything older than a date. "Keep media" removes attachments past a chosen window (one year, six months or thirty days) on this device.
  • Attachment handoff leases give the OS share sheet or another app a plaintext copy of one attachment, released explicitly.
  • Account-wide attachment history pages list media across every chat with filters, bounded pages and change tokens.
  • Public event previews resolve and cache nostr: references in messages, and report when the author deleted the event.
  • Faster database opens. App databases now present their derived key to SQLCipher as a raw key instead of a passphrase, skipping a 256,000-iteration KDF on every open. Each existing database is rekeyed once on first open.
  • Group changes can pause with a prompt: GroupCatchingUp while the device is still catching up, and GroupCommitUndelivered when the previous commit has not reached its relays for two minutes. The host acknowledges and retries; messages and leaving are never held.
  • Invitations explain failures: a recipient whose only KeyPackages are obsolete, a lookup that ran out of time, or a member with no inbox route.
  • Follow and unfollow edit the current follow list in place, keeping petnames, relay hints and other tags, and refuse instead of truncating a list of 2,048 or more.
  • WN Agent can edit an agent's own message (edit_message), and OpenClaw exposes it. Edits of messages that cannot be edited are refused before anything is published.
  • MarmotKit runs MDK on its own two-to-four-thread runtime, so async calls awaited from the main thread no longer run MDK work there.
  • Deployment services that used to be compiled in for White Noise (recovery relays, discovery indexers, media and image servers, Open Ranking, KeyPackage client preference, moderation namespace, keychain service) are now one host-supplied deployment record with a White Noise preset.
  • Catch-up and delivery: ordered, complete offline catch-up; live group subscriptions batched 50 per REQ so accounts in many groups stay under relay REQ limits; epoch-gap recovery pages backwards through clamped relays; terminal relay rejections are no longer retried; stalled recovery routes stay retryable; self-update commits retry every missed relay.
  • Onboarding relay diagnostics say which check produced each finding, why it ran, what it found and which actions apply to it.
  • An unreachable relay no longer fails an account's activation or group sync, taking the inbox and every healthy group offline; its subscription is sent when the relay reconnects, and a group sync re-sends only the relay sets it changes. Sends and group changes no longer fail when the pre-send subscription refresh cannot reach a group's relays; convergence retries and signed-out accounts still require it. Opt-in relay telemetry exports activation and group-sync outcome counters.
  • Fixes: the retention sweep no longer deletes messages still counted unread; a quarantined group no longer stalls every conversation's receives; iOS suspension no longer risks 0xdead10cc termination; a Welcome built from a just-replaced KeyPackage can still be joined.
  • QUIC agent-stream brokers are verified against bundled Mozilla roots, fixing an Android abort on the first handshake.
  • Security updates: quinn-proto, rustls, rustls-webpki, webpki-roots, negentropy and ctutils.

Compatibility

Ship generated Swift/Kotlin, native libraries and C headers from this exact cohort together.

  • Every MarmotKit constructor takes a MarmotDeploymentFfi, and MarmotOptions.deployment is required. White Noise apps pass marmotDeploymentWhiteNoise(). Other hosts that used the platform keychain without a SecretStore must keep keychainService = "com.marmot.whitenoise", or their existing account secrets are no longer found.
  • MarmotKitError gains InvalidEditTarget, InvalidPublicEventReferences, DirectoryLookupIncomplete, FollowListTooLarge, GroupCatchingUp, GroupCommitUndelivered and StorageFull; MissingKeyPackage gains a reason. Some failures that used to arrive as Runtime or InvalidKeyPackageEvent now use the new variants.
  • AttachmentTransferStateFfi gains StorageBlocked and CleanedBySetting; RetentionSweepStatusFfi loses DeferredScanExhausted.
  • OnboardingFindingFfi gains context, purpose, outcome, declaredCapability, actions and observedRevision with no binding defaults, and OnboardingIssueFfi gains InspectionCompleted.

C hosts must recompile and update every marmot_client_new* call: each takes a required const struct MarmotDeployment *. MarmotRetentionSweepStatus drops DEFERRED_SCAN_EXHAUSTED, so FAILED moves from 5 to 4. MarmotOnboardingFinding changes layout, MarmotOnboardingIssue appends InspectionCompleted (21), and statuses 101–107 are new. No other existing struct layout changed.

Rust hosts: MarmotAppConfig::default() is now the neutral deployment; use MarmotAppConfig::white_noise() to keep White Noise's services. MarmotApp's directory methods moved to app.directory() and return DirectoryError. AppError gains six variants, ingestion borrows its input, and NostrAdapterMetrics and RelayTelemetryRollup gain counter fields.

Account databases migrate from schema 107 through 116 on first open, the directory cache from 1 to 2, and every app database is rekeyed to a raw SQLCipher key. None of this rewrites message history, but the rekey rewrites every database page once. Downgrade is unsupported: 0.13.0 cannot open the rekeyed databases. Keep a device-local copy of the account directory before upgrading, and exclude the account directory, including media/ and handoff/, from iCloud and Android backups. See the storage-format contract.

WN Agent and its plugins must be upgraded together: a 0.14.0 plugin calling edit_message on a 0.13.0 connector sees the socket close without an error.

Known issues

  • #2237: a message that arrives more than five epochs too late stays undecryptable without a "history may be incomplete" notice.
  • Group-change prompts: undecryptable traffic can hold a group's changes behind GroupCatchingUp (#2277), no bounded catch-up runs before the refusal (#2283), and an acknowledgement cannot be withdrawn (#2389). Healthy relays can look owed for a short time after a commit (#2286); the two-minute grace keeps that from prompting.
  • #2253: group data updates move the app-data extension to the end of the group context, which implementations that preserve extension order reject.
  • #2158: an upload still in flight when the group epoch advances is lost.
  • The one-time rekey has not been measured on large databases or on devices beyond a Pixel 8 Pro fixture; see the upgrade guide.
  • WN Agent's control socket still grants its whole API to any authenticated client (#1445), and reports the new group-change refusals as a generic app_error.

Release artifacts

  • v0.14.0: MDK source snapshot; workspace crates remain unpublished to crates.io.
  • wn-agent-v0.14.0: WN Agent, terminal harness binaries, gateway plugins and checksum-paired installers. This track keeps its existing prerelease status.
  • marmotkit-v0.14.0: iOS/macOS XCFrameworks, shared Swift source, platform privacy resources, Android Kotlin and all four JNI ABIs with android-elf.json, manifests and checksums.
  • marmotc-v0.14.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.14.0-nightly.* builds are for testing only; pin this release instead.

12 October 2026

0.13.0

MDK 0.13.0 releases the Rust workspace, WN Agent, MarmotKit (iOS, macOS and Android), and Marmot C from one source commit. See the 0.12.0 → 0.13.0 client upgrade guide for required record, error, event, header and storage changes.

Original notesGitHub release
Read full notes

MDK 0.13.0 releases the Rust workspace, WN Agent, MarmotKit (iOS, macOS and Android), and Marmot C from one source commit. See the 0.12.0 → 0.13.0 client upgrade guide for required record, error, event, header and storage changes.

Highlights

  • Large attachments. uploadMediaFiles uploads from a file path with progress and cancellation instead of passing whole files as byte arrays, and large downloads stream into private files with resumable checkpoints.
  • Private moderation reports. submitModerationReport sends a NIP-56 report, gift-wrapped per NIP-59, to the deployment's moderation team. Relays cannot see who reported whom, and reports carry no message, group or relay identifiers.
  • Onboarding: createIdentityWithInitialProfile publishes the chosen name as a new account's first profile, so contacts never see the generated default. proposeOnboardingRelayRepair previews a lossless relay-list repair before approval, and manual relay edits keep untouched tags as they were.
  • Message details: messageReactions returns every reaction on one message. Markdown gains local-time timestamp nodes. Attachment history marks inline custom-emoji artwork so galleries can leave it out.
  • Polls can be created in direct conversations.
  • Chat list: presented rows carry an opaque draft version, so a host can tell a newer draft from the one it captured for sending.
  • Opt-in SOCKS5 routing (WN_SOCKS5_*) covers relays, media, directory reads, collectors and C NIP-46 sessions, and never falls back to a direct connection.
  • Opt-in native startup diagnostics report anonymous startup and migration phases for slow-open investigations.
  • Catch-up: missed group history arrives in batched requests of up to 256 events and, when the backlog is larger than one pass, oldest first. Commits no longer routinely move a member more than five epochs past messages it has not downloaded yet (#2086).
  • Relays that refuse a live subscription with CLOSED no longer leave it counted as live. Refusals are audited and counted in relay stats, and sync drains stop waiting for them.
  • Sends: a message queued while the group converged is no longer shown as failed after everyone else received it, and durable sends keep progressing through recovery and relay retries.
  • Invitations recover a member's KeyPackage from discovery relays when their advertised outboxes do not have one.
  • Marmot C adds per-account NIP-46 signer sessions (beta).
  • WN Agent adds the wn-goose harness for Goose and carries account relay-list reads and edits on the control surface.

Compatibility

Ship generated Swift/Kotlin, native libraries and C headers from this exact cohort together. No existing exported method changed its signature, but:

  • MarmotKitError gains five moderation-report variants.
  • Native events gain LocalGroupCopyTerminated, LocalGroupCopyRestored and GroupMemberLeavesRemoved; MarkdownInlineFfi gains Timestamp.
  • AttachmentEntryFfi.role, PresentedChatRowFfi.draftVersion and OnboardingRepairProposalFfi.relayRepair are new fields without binding defaults. Update exhaustive handling and host-constructed records.

C hosts must recompile: MarmotAttachmentEntry, MarmotPresentedChatRow and MarmotOnboardingRepairProposal change layout, new event and Markdown inline tags are appended, statuses 96–100 are new, and relay-repair preview strings are JSON-encoded.

Rust hosts: AppError, GroupEvent, MarmotAppConfig, AttachmentEntry, RelaySyncSnapshot, NostrAdapterMetrics and NostrReconciliationSummary gain variants or fields. External-signer account database keys move into the host SecretStore on first open, so those accounts cannot be downgraded either.

relay.damus.io is no longer a retired relay; relay.nostr.band remains retired.

Account databases migrate from schema 101 through 107 on first open. The attachment migrations keep payloads in place, so opening does not copy message or attachment history. Back up before upgrading; downgrade is unsupported. See the storage-format contract.

Known issues

  • #2237: batched, oldest-first catch-up makes the #2086 loss much rarer, but it can still happen, for example when the only relay holding an old message is down. A message that arrives more than five epochs too late stays undecryptable without a "history may be incomplete" notice.
  • WN Agent's control socket still grants its whole API to any authenticated client; capability-scoped grants remain tracked in #1445.

Release artifacts

  • v0.13.0: MDK source snapshot; workspace crates remain unpublished to crates.io.
  • wn-agent-v0.13.0: WN Agent, terminal harness binaries (now including wn-goose), gateway plugins and checksum-paired installers. This track keeps its existing prerelease status.
  • marmotkit-v0.13.0: iOS/macOS XCFrameworks, shared Swift source, platform privacy resources, Android Kotlin and all four JNI ABIs with android-elf.json, manifests and checksums.
  • marmotc-v0.13.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.

2 October 2026

0.12.0

MDK 0.12.0 releases the Rust workspace, WN Agent, MarmotKit (iOS, macOS and Android), and Marmot C from one source commit. See the 0.11.0 → 0.12.0 client upgrade guide for required record, error, header and storage changes.

Original notesGitHub release
Read full notes

MDK 0.12.0 releases the Rust workspace, WN Agent, MarmotKit (iOS, macOS and Android), and Marmot C from one source commit. See the 0.11.0 → 0.12.0 client upgrade guide for required record, error, header and storage changes.

Highlights

  • NIP-30 custom emoji. sendTaggedText, sendTaggedMedia and reactWithMedia send chats and reactions carrying ["emoji", shortcode, url] tags whose images are encrypted Marmot media. Conversation-window chat rows keep those tags, and reactions name the kind-7 whose image listMedia returns. Peers on 0.12.0 can send them, so render them.
  • Per-voter poll results. pollVotes pages who chose each option, using the same rules as the poll tally.
  • Application-owned group components. groupAppComponent and updateAppComponent read and admin-update opaque settings (ids 0xf000 and up) carried in MLS group state, so they survive message expiry and reach new members in their Welcome.
  • Hosts can declare a kind-10050 inbox relay list separately from default_relays on identity creation, login, relay-list publication and onboarding.
  • Attachments: agent-sent files no longer stay downloading forever, missing-key deferrals end after about eight minutes, an explicit tap (requestExplicitAttachment) promotes demand without resetting retry budgets, and successfully sent files are retained locally for the sender.
  • A muted chat still notifies on a direct mention of the account.
  • Recovery: a route change no longer resets recovery for every route, recovery parks behind a required relay that never answers, catch-up no longer holds the account worker for recovery, and group creation no longer rebuilds the routing table.
  • Publishing: retained per-account publishers cut a measured complete send-with-push call from about 1.9 s to 0.14 s mean against the operated relays.
  • WN Agent: admin agents can rename groups and edit descriptions (group_profile_update, Hermes marmot_group_profile); account_publish_profile merges into the published profile instead of replacing it; files work in both directions for Codex, OpenCode and Pi.

Compatibility

Ship generated Swift/Kotlin, native libraries and C headers from this exact cohort together. MarmotKitError gains InvalidAppComponent, and ConversationReactionFfi gains reactionMessageIdHex with no binding default. Update exhaustive error handling and host-constructed reaction records. Six account methods gained a trailing inboxRelays parameter that defaults to empty in Swift and Kotlin.

C hosts must recompile: the six account entry points gain trailing inbox_relays / inbox_relays_len arguments, MarmotMediaUploadRequest and MarmotConversationReaction gain trailing fields, and MARMOT_STATUS_INVALID_APP_COMPONENT (95) is new.

Rust hosts: AccountSetupRequest, AccountRelayListBootstrap, OnboardingOptions, MediaUploadRequest and ConversationReaction gain fields, AppError gains InvalidAppComponent, and the engine's GroupEvent::MessageReceived gains encrypted_media_secret. An expired account worker ready-wait now reports account worker startup timed out at <stage>.

Account databases migrate from schema 98 through 101 on first open. Back up before upgrading; downgrade is unsupported. See the storage-format contract.

Known issues

  • #2086: during a large catch-up, a member can advance more than five epochs past application messages it has not yet downloaded and lose them silently. This release fixes the related attachment-key case but not the message case.
  • The Apple required-reason and SDK-signing questions remain tracked in #1874.
  • WN Agent's control socket still grants its whole API to any authenticated client; capability-scoped grants remain tracked in #1445.

Release artifacts

  • v0.12.0: MDK source snapshot; workspace crates remain unpublished to crates.io.
  • wn-agent-v0.12.0: WN Agent, terminal harness binaries, gateway plugins and checksum-paired installers. This track keeps its existing prerelease status.
  • marmotkit-v0.12.0: iOS/macOS XCFrameworks, shared Swift source, platform privacy resources, Android Kotlin and all four JNI ABIs with android-elf.json, manifests and checksums.
  • marmotc-v0.12.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.

29 September 2026

0.11.0

MDK 0.11.0 releases the Rust workspace, WN Agent, MarmotKit (iOS, macOS and Android), and Marmot C from one source commit. See the 0.10.4 → 0.11.0 client upgrade guide for required record, schema, configuration and host UI changes.

Original notesGitHub release
Read full notes

MDK 0.11.0 releases the Rust workspace, WN Agent, MarmotKit (iOS, macOS and Android), and Marmot C from one source commit. See the 0.10.4 → 0.11.0 client upgrade guide for required record, schema, configuration and host UI changes.

A post-tag documentation supplement corrects both documents: polls are required, and v5 audit delivery replaces v4 for hosts that record audit logs. Host performance stages and pending-send edits are strongly recommended. Use the merged documentation commit for published links; the tagged copies predate this correction.

Highlights

  • Account recovery v2 completes lost or incremental history only when every required relay finishes an untruncated NIP-77 comparison that covers the gap. Recovery runs off the account worker and reuses live subscriptions instead of replaying history, and one comparison job replaces the inline executor.
  • When recovery cannot prove history complete, it stops retrying and raises a durable "history may be incomplete" notice. Hosts should show these notices and let the user dismiss them.
  • A full account delivery queue now spills to the account database instead of dropping deliveries. A relay notification lag no longer closes the account route, and end-of-stored-events notifications lost in a lag are repaired.
  • The transport cursor advances on live delivery, so a restart no longer re-downloads what the account already received live. History REQs for post-join maintenance and retained routes now start from a floor instead of fetching full history.
  • Encrypted NIP-88 polls. Every client must render, vote on and create them, because peers on 0.11.0 can send them.
  • Audit v5 replaces v4. With audit enabled, only v5 files are written, and the v4 Goggles whole-file route rejects them. Hosts that record audit logs must deploy a v5 OTLP receiver and configure it with setAuditOtlpConfigV5 on every launch. v5 adds Welcome, group-baseline, app-outcome and account recovery event kinds.
  • Strongly recommended: 37 new host performance stages for recordHostPerformance and durable edits of pending token-aware sends. Stateless Nostr event verification is optional.
  • OpenClaw enforces an inbound sender policy that denies every sender until one is configured. Hermes adds opt-in presence reactions, and Codex accepts non-image attachments.
  • Android 64-bit JNI libraries use 16 KB ELF load-segment alignment. Apple archives no longer ship LLVM bitcode.

Compatibility

Ship generated Swift/Kotlin, native libraries and C headers from this exact cohort together. MarmotEventFfi / MarmotEvent, GroupRecoveryStatusFfi / MarmotGroupRecoveryStatus, timeline records (poll projection) and HostPerformanceOperationFfi changed. Rebuild consumers and update exhaustive matches and manually constructed records; the new timeline poll field has no binding default. No existing method signature changed.

Rust hosts: MarmotAppConfig removes dev_epoch_backfill_eose_wait_ms and dev_epoch_backfill_execution_quantum_ms, adds recovery_operated_relays (it defaults to the two whitenoise.chat relays), and AppPriorNostrRoute gains replaced_at. nostr / nostr-sdk now come from a pinned fork revision.

Account databases migrate from schema 89 through 98 on first open. Back up before upgrading; downgrade is unsupported. Re-upgrade or restore a pre-upgrade database/export instead of removing migration rows. See the storage-format contract. After upgrade, an account that overflowed on 0.10.4 can show a "history may be incomplete" notice. A group that 0.10.4 already reported as automatic-recovery-failed keeps that warning until authenticated peer recovery or a rejoin clears it. The upgrade guide describes both.

Known issues

  • #2086: during a large catch-up, a member can advance more than five epochs past application messages it has not yet downloaded. Those messages cannot then be decrypted, and no notice is raised. The failure is intermittent and was already present before this release.
  • The Apple required-reason and SDK-signing questions remain tracked in #1874.

Release artifacts

  • v0.11.0: MDK source snapshot; workspace crates remain unpublished to crates.io.
  • wn-agent-v0.11.0: WN Agent, terminal harness binaries, gateway plugins and checksum-paired installers. This track keeps its existing prerelease status. Install only from the versioned release; the mutable wn-agent-latest alias is retired.
  • marmotkit-v0.11.0: iOS/macOS XCFrameworks, shared Swift source, platform privacy resources, Android Kotlin and all four JNI ABIs with android-elf.json, manifests and checksums.
  • marmotc-v0.11.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.

20 September 2026

0.10.4

MDK 0.10.4 releases the Rust workspace, WN Agent, MarmotKit (iOS, macOS and Android), and Marmot C from one source commit. See the 0.10.3 → 0.10.4 client upgrade guide for required record, schema and lifecycle changes.

Original notesGitHub release
Read full notes

MDK 0.10.4 releases the Rust workspace, WN Agent, MarmotKit (iOS, macOS and Android), and Marmot C from one source commit. See the 0.10.3 → 0.10.4 client upgrade guide for required record, schema and lifecycle changes.

Highlights

  • Token-aware text, reply, draft and media-send APIs return after durable local acceptance and preserve an opaque caller token through restart, engine handoff and timeline reprojection. Existing send APIs keep their completion semantics.
  • Optional host-managed automatic attachment acquisition adds generation-fenced permission, idempotent demand and durable attempt limits. Existing clients stay in native automatic mode by default.
  • Chat-list message previews carry the selected message's pinned retention duration and expiry so clients can hide expired content before periodic pruning.
  • WN Agent control protocol v2 can create groups with optional founding relay routes. Hermes adds opt-in, sender-authorized reactions for approval prompts.
  • Deferred pre-peel wrappers remain redeliverable, and epoch-backfill overflow uses execution-based exponential retry backoff. The latter is a pacing mitigation, not resumable or proven-lossless history recovery.
  • MarmotKit builds compile target slices in parallel and verify their provenance agreement without changing published bundle names or layouts.

Compatibility

Ship generated Swift/Kotlin, native libraries and C headers from this exact cohort together. MarmotOptions / MarmotClientOptions, chat-list message previews, timeline rows, attachment transfer states and error/status enums changed. Rebuild consumers and update exhaustive matches and manually constructed records. Existing non-token send APIs and native automatic attachment behavior remain supported.

Account databases migrate from schema 86 through 89. Migration 87 adds durable automatic-acquisition history and budgets, 88 adds the draft descriptor covering index, and 89 adds durable local submissions. Back up before upgrading; downgrade is unsupported. Re-upgrade or restore a pre-upgrade database/export instead of removing migration rows. Upgrades that skip older cohorts must also follow the previous guide and storage-format contract.

Preserve the matching Apple privacy resource in every consuming wrapper. Existing required-reason and SDK-signing questions remain tracked in #1874; SDK artifact checks do not establish consuming-app adoption, device performance or App Store acceptance.

Release artifacts

  • v0.10.4: MDK source snapshot; workspace crates remain unpublished to crates.io.
  • wn-agent-v0.10.4: WN Agent, terminal harness binaries, gateway plugins and checksum-paired installers. This track retains its existing prerelease status.
  • marmotkit-v0.10.4: iOS/macOS XCFrameworks, shared Swift source, platform privacy resources, Android Kotlin and all four JNI ABIs, manifests and checksums.
  • marmotc-v0.10.4: 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.

19 September 2026

0.10.3

MDK 0.10.3 releases the Rust workspace, WN Agent, MarmotKit (iOS, macOS and Android), and Marmot C from one source commit. See the 0.10.2 → 0.10.3 client upgrade guide for adoption steps.

Original notesGitHub release
Read full notes

MDK 0.10.3 releases the Rust workspace, WN Agent, MarmotKit (iOS, macOS and Android), and Marmot C from one source commit. See the 0.10.2 → 0.10.3 client upgrade guide for adoption steps.

Highlights

  • Prepared chat rows select draft, message, invitation or empty previews and expose advisory row actions. Draft changes refresh both live list APIs without changing activity order or unread state. Draft previews contain bounded text and attachment summaries, with no attachment bytes or filenames.
  • C client free on ordinary host threads drains worker cleanup before returning, preventing database teardown from racing SQLCipher process-exit cleanup.
  • Public profile searches tolerate optional relay authentication challenges.
  • Android identity-salt publication supports API 26 without hard links or renameat2, retaining a single canonical salt under concurrent creation.
  • Hermes gains a privacy-safe, read-only installation doctor, connector diagnostic status and plugin ACK/lifecycle observations. Configuration precedence and welcomer behavior remain aligned with the existing adapter path.

Compatibility

Ship generated Swift/Kotlin, native libraries and C headers from this exact cohort together. Prepared chat-row records have changed layout; rebuild clients and update manually constructed records and exhaustive preview handling. Existing lower-level methods remain supported. Row actions are display hints; leave still requires authoritative preflight and deletion requires host confirmation.

No database migration is added after 0.10.2; schema remains at migration 86. For upgrades skipping earlier releases, follow their backup and unsupported- downgrade requirements in the previous guide and storage-format contract. Preserve the matching Apple privacy resource in every consuming wrapper. Existing required-reason and SDK-signing questions remain tracked in #1874; SDK artifact validation is separate from consuming-app adoption and App Store acceptance.

Release artifacts

  • v0.10.3: MDK source snapshot; workspace crates remain unpublished to crates.io.
  • wn-agent-v0.10.3: WN Agent, terminal harness binaries, gateway plugins and checksum-paired installers. This track retains its existing prerelease status.
  • marmotkit-v0.10.3: iOS/macOS XCFrameworks, shared Swift source, platform privacy resources, Android Kotlin and all four JNI ABIs, manifests and checksums.
  • marmotc-v0.10.3: 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.

19 September 2026

0.10.2

MDK 0.10.2 updates the Rust workspace, WN Agent, MarmotKit (iOS, macOS and Android), and Marmot C from one source commit.

Original notesGitHub release
Read full notes

MDK 0.10.2 updates the Rust workspace, WN Agent, MarmotKit (iOS, macOS and Android), and Marmot C from one source commit.

For detailed client changes, default download policy, API adoption and validation, read the 0.10.1 → 0.10.2 integration guide. That guide was added as a post-tag documentation supplement; published release links must use its merged documentation commit, not the original v0.10.2 tree.

Highlights

  • Accepted conversations acquire attachments in the background, including retained history. Protected checkpoints resume interrupted downloads when servers support validated ranges. Authentication completes before local bytes become available to clients.
  • Swift/Kotlin and C expose bounded attachment history, local reads, progress, and durable cancel, retry, remove, and download-again controls. Automatic acquisition defaults on with per-account policy, storage quotas, disk reserve, and one transfer across accounts.
  • Message projections expose accepted deletion provenance and preserve custom-event tags. Historical tombstones without evidence remain unknown.
  • Local-first KeyPackage inventory distinguishes local ownership from relay observations. Compatible White Noise packages are preferred, and missing invitation packages produce an explicit error.
  • Conversation opening and timeline projection avoid repeated account, profile, and message work. Readiness and contention measurements make delays easier to diagnose.
  • Losing-branch messages remain parked for possible revival; retained replay and deferred-peel budget fixes avoid premature retirement.
  • Account identity creation handles concurrent database initialization. Size-rotated audit segments retain source metadata.
  • QUIC broker subscriber writes are bounded. Optimized macOS C libraries preserve Mach-O alignment for Xcode 27.

Compatibility and adoption

Update generated Swift/Kotlin source and native libraries together from the same immutable release. C consumers must update headers and libraries together because message records have new fields. Rebuild downstream apps to adopt the new APIs and behavior. The integration supplement also corrects C retry/compatibility guidance: not every failed mutation is safe to retry, and C headers/libraries must match exactly.

Apple consumers must stage the matching shared Swift source and platform privacy asset in their wrapper, rename the latter to PrivacyInfo.xcprivacy, and declare resources: [.copy("PrivacyInfo.xcprivacy")]. Every consuming app and extension must depend on that wrapper. See the distribution guide and consumer adoption tracking. The existing native required-reason and SDK-signing questions remain open for host App Store submission; resource validation does not resolve them.

Account databases advance through migrations 81–86: attachment history, deletion provenance, retained attachment acquisition, worker demand, protected partial downloads, and durable attachment controls. Back up or export before upgrading. Downgrade after migration is unsupported; re-upgrade or restore a pre-upgrade account database/export. Never remove migration rows. See the storage-format definition and compatibility evidence. Upgrades from before migration 47 also require at least 3.25 times the account database size in free space for its table rebuild and gradual promotion.

Release artifacts

  • v0.10.2: MDK source snapshot.
  • wn-agent-v0.10.2: WN Agent and terminal harness binaries, gateway plugins, and checksum-paired installers; this track retains prerelease status.
  • marmotkit-v0.10.2: iOS/macOS XCFrameworks, shared Swift source, platform privacy assets, Android Kotlin and all four JNI ABIs, manifests and checksums.
  • marmotc-v0.10.2: C ABI bundle and checksum.

Verify sibling SHA-256 files and manifest source/version metadata. Apple binary ZIPs also provide SwiftPM checksums. Use matched release inputs.

Protocol
Development Kit
Documentation
Apps
Awesome
Releases
Community
GitHub
Donate
Contact
©2025–2026 Internet Privacy Foundation. All rights reserved.
Marmot