Your signal. Your price.
Max Hillebrand says White Noise uses the Messaging Layer Security standard with Nostr keys to authenticate identities and the Marmot protocol to order encrypted group changes without a central delivery server. Rotating message keys are discarded after decryption, so a leaked Nostr key does not expose past messages.
Marmot MDK version 0.11.0 updates MLS-encrypted group account recovery, flagging history gaps as closed only after complete comparison across required relays. The update also introduces optional encrypted polls.
White Noise Android integrated Marmot-encrypted group polls and account-specific disappearing message default timers. The application transitioned its source code licensing to the GNU Affero General Public License version 3.0.
Max highlights major updates to Marmot-based applications. MDK version 0.10.0 moves username display and logic into the library core to simplify frontend implementations, while Myco version 0.7.0 introduces full support for single-file NIP-5D napplets over localized mesh networks.
The Marmot group messaging specification clarified its key package flow, declaring that read-only NIP-65 entries cannot be key package destinations. A new moderation proposal introduces kind 1,984 encrypted group reports, allowing administrators to delete messages using kind 4,891 events.
The Marmot Protocol ecosystem achieved multi-client interoperability across distinct codebases, including White Noise in Rust, Scramble in C#, and Amethyst in Kotlin. The Marmot DevKit version 0.10.4 update also resolved a critical bug that caused repeated automatic attachment downloads.
MDK optimized encrypted group chats by scanning admin events in a single member walk. Zap.cooking now restricts NIP-46 signer traffic to configured bunker relays, while Nostwort enabled device-wide decryption of NIP-17 gift wraps.