Max

Two projects aim at the same goal of unstoppable networks for human beings, and they arrive at radically different solutions. Reticulum strips addressing and ports from the protocol entirely and optimizes for radio links so slow that five bits per second counts as usable bandwidth, then builds its own parallel universe of applications on top. @FIPS takes the opposite bet, keeping IPv6 semantics alive through a TUN adapter so that unmodified SSH and curl can cross a mesh of Nostr identities. This post walks both stacks from the wire up, then shows where their design choices force different tradeoffs.

I see more and more non-nostr apps publishing on @Zapstore!
Like @CruxCoach, a climbing app, which recommends zapstore as best place to get the app, and use nostr DMs for feedback.
https://zapstore.dev/apps/naddr1qq2kxmmd9e3hyatcvdhkzcmg9eskuerjda5kgqgcwaehxw309aex2mrp0yh85ctswd6x7un99ejx2aszyrn45xzuqxwsjpyatl9su2dzejdl6qtwcrmd3yhunrm0lcqcrfyq6qcyqqq8uzch789f5

The usual covenant debate on Bitcoin starts with Script and soft forks. PIPEs v2 starts somewhere stranger: it asks whether a spend condition can be enforced by making the signing key itself unavailable until a proof exists. That move shifts the burden away from on-chain verification and into witness encryption, committee setup, a huge off-chain artifact, and the engineering needed to bind them together.
The result is one of the most interesting proposals in current Bitcoin research because it enlarges the design space without asking Bitcoin consensus to change.

We're building a little something...
Note

Three architectural families have broken an assumption that was treated as a law of cloud architecture for two decades: that the machine running a computation must see the data the computation runs on. Homomorphic encryption operates on ciphertexts, secure multi-party computation distributes the work across non-colluding participants, and trusted execution environments isolate the work inside a hardware enclave opaque to the machine's owner. The privacy architecture of the next decade will be built on their compositions.

Working on making marmot transport layer agnostic.

400 optech editions, crazy!
Thanks a lot to all contributors!
Note

Reminder, Marmot community call in 30 minutes.
Note

There is now an official internet standard that makes it possible for Tor onion services to get verified security certificates the same way any website does, automatically, for free. https://datatracker.ietf.org/doc/rfc9799/

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.

👀
https://github.com/vitorpamplona/amethyst/pull/2106

Next marmot client joins the burrow!
Test out nymchat.app
Note

Don't do this with your own app, sign it yourself instead!
https://zapstore.dev/docs/publish
Note

Yet another awesome app discovered on @Zapstore
A no-bullshit app store is so refreshing.
Note

Fully offline translator android app, nice!
https://github.com/davidventura/firefox-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.

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.

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

When you install @V E C T O R, make sure you use a different npub than in @White Noise, multi client support with the same npub is not yet speced out.
Note

Next attempt to get White Noise to finally work well for everyone. Now it finally works for my npub, so shoot me a message if you want to try!
Article

@utxo the webmaster 🧑‍💻 seems like Wisp doesn't work when not giving DM decrypt permissions to Amber.

The industrial war machine was built on concentration, first of capital and command, then of targets. Cheap drones are tearing through that architecture because a low-cost weapon can now erase an asset that required years of budgets, contracts, and political theater to build.
Rothbard and Hoppe did not write about quadcopters, but they described the political and economic logic that made the old model brittle, and the battlefield is proving them right.

Rothbard bibliography is 62 pages of titles
https://mises.org/articles-interest/rothbard-bibliography

One of the reasons the latest White Noise release doesn't work for some accounts is that nostrs outbox model is suffering massively from bad data that some users have in their relay list. This is our attempt to improve the situation at least a bit.
You can run the doctor session for your friends and tell them about improving their setup!
Note

Merchant courts showed that private dispute resolution outperforms the state monopoly. Victim-centered restitution showed that criminal justice worked for centuries without prosecutors or prisons.
This post completes the argument by showing how insurance, arbitration, restitution, and cryptographic enforcement compose into a single integrated legal system where each layer enables the others and no layer requires a monopolist.

Coldcard mk5 looks dope.
Good to see the keyboard further improved, I still have PTSD from mk1...

https://video.nostr.build/3e6c76a55db21c94cbdb5743e6120d7a5c0f2f0d0a32b48736c86999fb3ef5c1.mp4

The Marmot Protocol has published its full specification as six Marmot Implementation Proposals covering everything from identity and group construction to encrypted media and privacy-preserving push notifications.
This post walks through each MIP to explain what the protocol does at every layer and how the cryptographic guarantees work in practice for users who care about private communication. The specs are open and the implementations are already shipping.

Two PRs to NanoClaw for adding marmot support!
https://github.com/qwibitai/nanoclaw/pull/858
https://github.com/qwibitai/nanoclaw/pull/901

@hzrd149 built this awesome view where you can see the latest key packages published by users, if you want someone to talk to on @White Noise this is a good way to find them!

https://marmot-protocol.github.io/marmots-web-chat/contacts/explore