Bitcoin settles payments without counterparty permission, and Nostr coordinates action without censorship. Together they enable spot transactions and real-time coordination across the parallel economy. What they cannot do is create credit, and without credit, the parallel economy cannot finance production across time. View article →

👀

GitHub

Add MLS (Messaging Layer Security) implementation for Marmot by vitorpamplona · Pull Request #2106 · vitorpamplona/amethyst

Summary This PR adds a complete implementation of the Messaging Layer Security (MLS) protocol (RFC 9420) to the Quartz library, enabling end-to-end...

Next marmot client joins the burrow! Test out nymchat.app View quoted note →

Don't do this with your own app, sign it yourself instead!

Zapstore

Publishing apps — Zapstore Documentation

Zapstore documentation

View quoted note →

Yet another awesome app discovered on @Zapstore A no-bullshit app store is so refreshing. View quoted note →

Fully offline translator android app, nice!

GitHub

GitHub - DavidVentura/offline-translator: Use Firefox Translation Models for on-device translation on Android

Use Firefox Translation Models for on-device translation on Android - DavidVentura/offline-translator

This turned into a long one... A comparative analysis of financial privacy across ten systems: Bitcoin's transparent baseline, WabiSabi CoinJoin, Lightning Network, Spark, Ark, shielded client-side validation, Monero RingCT, Monero's upcoming FCMP++, Zcash's Sapling and Orchard pools, and DarkFi's anonymous-everything architecture. Each system stakes its design on a different anonymity set, trust model, and architectural layer. The result is a spectrum from adequate plausible deniability to full untraceability, and your threat model determines which point on that spectrum you need. View article →

Want to install an app but it's not on @Zapstore? Just paste the GitHub repo link in the zapstore search bar, hit enter, and wait a couple minutes, it will be automagically indexed in the background!

Multi-device support in an encrypted messenger is an authorization problem. It is not a sync problem, not a UX problem, not a storage problem. The question that must be answered before anything else can proceed is simple: how does a second device prove it belongs to the same person, in a way that every group member can independently verify, without any central authority vouching for the claim? Marmot PR #44 introduces MIP-06 to answer exactly this question for White Noise. View article →

Dev/Hack/Day + Cypherpunk Meetup = @FreedomTechSummit If you're coming to @BTC Prague, don't miss it. Get your early bird tickets at freedomtechsummit.com