Newstr — Issue #001: Own the Keys. Verify the Work.
Newstr — Issue #001: Own the Keys. Verify the Work.
Week ending October 30, 2026 · Maximoto
Welcome to Newstr, my weekly dispatch on Bitcoin, Nostr, AI, and freedom tech. I’m a self-taught software engineer who believes people should be able to own their money, carry their identity between apps, and inspect the systems they depend on. Running my own Bitcoin node helped turn that belief into a habit: verify first, trust less.
This inaugural issue looks back at the week ending October 30. It was prepared on November 2, after the reporting week closed. News is linked to source material; the interpretations are my own.
TL;DR
- Bitcoin: Bitcoin Core 32.1 arrived during the week, with changes across networking, wallets, and RPCs; its release notes say the 29.x line has reached end of life.
- Nostr: NIP-59 gift-wrap guidance now recommends independently randomized seal and wrap timestamps when expiration tags are used, reducing timing-correlation signals—not guaranteeing anonymity.
- AI / ML: OWASP’s Q3 agentic-security review reinforces the need for scoped permissions, untrusted-input handling, and real human approval before consequential actions.
- Freedom Tech: FIPS is developing an encrypted, self-organizing mesh that addresses peers by cryptographic identity; its protocol and APIs are still evolving.
- Workshop: My Plebeian Market release-packaging contribution is merged, while the Coco v2 auction-wallet integration is still an open PR—not a finished production feature.
The Signal
Why start another newsletter? Because the most interesting technology is not always the loudest. A reliable Bitcoin node, a portable Nostr identity, an encrypted route between peers, or an AI agent that refuses to cross a security boundary can matter more than a flashy demo.
Freedom tech is a question of control. Who holds the keys? Can you verify the rules? Can you take your data elsewhere? What happens if one server, relay, company, or agent disappears?
Newstr will follow the software and people trying to answer those questions. I’ll keep the useful links, explain the engineering trade-offs in plain language, and distinguish completed work from experiments.
Bitcoin & Lightning
Bitcoin Core 32.1 was released in late October. The official notes explain that v32.0 was tagged but never fully announced or released, and that 29.x is now end-of-life. The release also documents network and privacy-related changes, including improvements around transaction relay and private broadcasting.
For node operators, the practical lesson is simple: read the release notes for your version and configuration, verify your download, and plan upgrades deliberately. Running a node is not just about keeping it online. It’s about understanding what you’re running.
On the payments side, I keep coming back to a design boundary: auction ordering is not the same as money settlement. Bitcoin, Lightning, and Cashu each have different roles. The ongoing Coco v2 auction-wallet integration in Plebeian Market is a useful example of why refunds, releases, custody, and recovery need explicit engineering rather than optimistic UI states. That PR is still under review.
Nostr & Freedom Tech
Nostr gives developers a way to build around portable keys instead of a single platform account. But signed events do not automatically make an application private, available, or safe.
The current NIP-59 gift-wrap specification advises independently randomized timestamps for seals and wraps when expiration tags are present. That may reduce one form of metadata correlation. It is not a promise of complete anonymity—a distinction worth repeating whenever we discuss encrypted messaging.
Another development worth exploring is NIP-34, which describes Nostr-coordinated Git collaboration, including signed pull-request and update events. Git repositories still carry the code; Nostr can help carry portable coordination around it.
I’m also watching FIPS, the Free Internetworking Peering System. It aims to route authenticated, encrypted traffic across self-organizing peers and multiple transports. Its upstream documentation describes active development and unstable APIs. It’s an exciting networking direction, not a replacement for Bitcoin consensus, and I am not claiming a personal production deployment here.
AI / ML
AI agents can search, draft, test, and review at remarkable speed. But a model that can take actions also needs a clearly bounded authority. OWASP’s Q3 2026 review documents cases involving tool misuse, credential exposure, and agents exceeding their intended scope.
My approach is to give agents evidence-gathering and proposal work—not publishing keys, wallet spending authority, or automatic release rights. In my editorial Studio’s review workflow, agent suggestions remain untrusted drafts. A human examines the differences and approves an exact version before a Nostr signer can publish it.
Agents should make maintainers stronger, not make authority invisible.
Maximoto’s Workshop
My featured open-source work remains Plebeian Market: Bitcoin- and Nostr-native commerce, decentralized auctions, privacy boundaries, and payments architecture.
Three artifacts capture the kind of work I want Newstr to highlight: the four-validator BFT architecture proposal, the NIP-17 private order-transport implementation, and the release-packaging fix. These are reviewable pull requests, not an assertion that a complete validator network is already in production.
This newsletter itself follows the same principle. The Newstr Studio can assemble a draft and check its structure; I still have to verify the sources, approve the words, and sign the article myself.
Further Reading
- Bitcoin Core 32.1: official release notes
- NIP-59: gift wraps and metadata
- NIP-34: Git collaboration over Nostr
- OWASP: Q3 2026 agentic AI security roundup
- FIPS: encrypted mesh networking project
- Plebeian Market: Coco v2 integration under review
Newstr is researched with AI assistance, reviewed by Maximoto, and published only with an explicit Nostr signature. Verify the original sources, stay curious, and keep building in the open.
Write a comment