Free Daily Podcast Summary
No Solutions: Daily Summaries Delivered
by Gigi
No solutions; only trade-offs. Walking towards a better internet. Est. 882,690. Inspired by Sovereign Engineering
Latest Episodes
The most recent episodes — sign up to get AI-powered summaries of each one.
- 6 days ago1h 35m
33: ASMap, nix, and nix-nostr w/ Julien
"There is no real address book for the internet." Julien & Gigi take a walk. Listen on sovereignengineering.io Julien came to Sovereign Engineering through a strange path: Nix, Bitcoin Core, ASMap, Nostr, and a growing sense that packaging, routing, identity, and deployment are all part of the same sovereignty problem. The first part of the walk goes deep into ASMap: why Bitcoin Core cares which autonomous systems its peers live in, how eclipse attacks turn peer discovery into a security question, and why mapping the internet is harder than it looks. The trade-off is familiar: IP addresses are useful but misleading. A single entity can control many non-contiguous ranges, routing data is messy, BGP was not designed as a cryptographic truth machine, and even better inputs like RPKI only cover part of the world. So Kartograf builds from several imperfect sources, and the asmap-data process turns map generation into a collaborative run with hashes, review, and a paper trail. From there the conversation moves into Nostr and the social layer of infrastructure. Julien describes finding Nostr through the simple feeling that the primitives were right, using Amethyst and Zapstore, thinking about Git on Nostr, and watching FIPS make old assumptions about DNS, IP addresses, NAT, and transport layers feel suddenly optional. The last thread is nix-nostr, or more precisely Julien's early nostrpkgs work: a Nix package set and deployment path for Nostr tools. The inspiration is nix-bitcoin, but the target is wider: relays, FIPS nodes, git servers, Blossom drives, Cashu mints, and other services that should be easy to compose, reproduce, and ship. If agents are going to run infrastructure for us, declarative systems start to look less like taste and more like leverage. In this dialogue: how Julien found a path into Bitcoin Core work through BTC++, Nix, and a conversation with Fabian Jahr why ASMap exists as a Bitcoin Core feature, and what it tries to improve about peer bucketing how eclipse attacks, Sybil attacks, AWS, Hetzner, and autonomous systems change the threat model for peer discovery why IP address prefixes are only a heuristic for control how regional registries, autonomous systems, BGP, RPKI, IRR, and RIPE RIS fit into the map-making problem why no one can build a perfect ASMap, and why that does not make the project useless how Kartograf aggregates imperfect data into a usable ASMap why collaborative runs give the process a reproducible paper trail instead of relying on one person's machine how ASMap files are now managed in the bitcoin-core/asmap-data repository why Julien would still like more users to generate fresh maps for themselves how Nostr first clicked as the right mix of clients, relays, keys, and trade-offs why Zapstore makes Android distribution feel native to Nostr why replacing GitHub means replacing hosting, search, issues, pull requests, CI, releases, and social discovery how Git-on-Nostr, agents, and mobile-first workflows point away from old repository interfaces why voice, text, and agent interfaces are starting to blur how FIPS changes the address and transport conversation by routing through Nostr identities why a FIPS route for Bitcoin Core peers would be worth testing why Julien sees Nix as sovereign infrastructure, not just a package manager how reproducible builds, dependency graphs, hashes, and declarative systems connect Nix back to Bitcoin instincts why <a hr
- 1 weeks ago1h 27m
32: Nostrology w/ WhisperHash
"No Solutions, do the homework." WhisperHash & Gigi take a walk. Listen on sovereignengineering.io WhisperHash came to Sovereign Engineering by following breadcrumbs: Bitcoin first, then small solo miners, then Nostr, then No Solutions, then the strange realization that the protocol was not just another social network. After losing a valuable Instagram handle to platform control, the idea of cryptographic identity stopped being abstract. If you do not hold the keys, you do not own the thing. The mining part of the walk starts with NerdMiner and ESP32 tinkering, moves into BitAxe and open-source ASICs, and lands on the dream of a quiet fanless home miner that can coexist with humans. The Nostr part starts with a data question: how many people are actually here, how many sats are moving, and which numbers should anyone trust? That question became Nostrology, an ecosystem observatory for Nostr data. But making data visible is not neutral. DAU, MAU, relay lists, zaps, Nutzaps, and follow history all exist somewhere in the event graph, but packaging them into convenient datasets changes the trade-off. Some data wants to be useful. Some data probably wants to rot. The deeper thread is about primitives. Blossom, FIPS, Zapstore, Nostr identities, Parquet files, and ContextVM all show up as ways to compose small pieces into larger systems without pretending there is one global application. If the abstractions are right, things stack. If the abstractions leak, you get a different kind of centralization with better branding. In this dialogue: how WhisperHash found Bitcoin, dismissed Nostr as "decentralized social," and then got pulled back in by ownership, identity, and curiosity why losing a valuable Instagram handle made platform ownership feel concrete how a data-science background turned into a search for something useful to build in Bitcoin why NerdMiner, ESP32 boards, BitAxe, OSMU, and solo mining made mining tangible again what changes when a miner is something you live with, tune, cool, and hear why fanless home mining is partly a hardware problem and partly a co-living problem how Nostr became interesting once WhisperHash started asking basic measurement questions why active-user counts on Nostr are harder, messier, and more political than they look how No Solutions served as a strange curriculum for catching up on Sovereign Engineering and Nostr culture why demo day failure is acceptable, but opting out and showing slides are not how Blossom, FIPS, Zapstore, and Nostr identities feel like primitives that are finally starting to compose why Zapstore is a natural fit for Nostr and a glimpse of a different Android distribution model how app stores, agents, GitHub releases, signatures, and social trust start to blur together why durable formats matter if you want software and data to survive beyond the current wave how Silicon Valley, London, Hong Kong, and SEC-08 all shaped WhisperHash's sense of software culture what Nostrology is trying to observe across relays, lightning, Zapstore, and Nutzaps why publishing small numbers can help builders, hurt momentum, or do both at once why Parquet is a practical format for large No
- 1 weeks ago2h 0m
31: Buzz, Mosaico, and Other Stuff w/ Pablo
"You can always buy more tokens, not more time." Pablo & Gigi take a walk. Listen on sovereignengineering.io Pablo and Gigi start with the FIPS map: the strange pleasure of seeing a protocol become a place, with nodes scattered across the world, Archipelago getting faster through a FIPS connection, and Nostr VPN quietly pulling more people into the mesh. From there the conversation turns into a familiar No Solutions pattern: if you try to make one global thing, you usually fight the design. FIPS works better as locality. Nostr works better as locality. There is no global. The second half becomes an agent-swarm walk through Buzz, NIP-29, Mosaico, proactive context, and the difference between coordination and awareness. Buzz packages a lot of things together: rooms, agents, Git-like collaboration, ACP harnesses, and Nostr identities. Mosaico tries to stay much smaller: a shared-awareness fabric where agents see enough of the other work happening around them to find relevance by themselves. The trade-off underneath both projects is the same one that keeps showing up everywhere now: more instructions can make agents obedient but brittle, while too little structure leaves them blind. Somewhere between micromanagement and chaos is the place where local intelligence starts to coordinate. In this dialogue: why seeing the live FIPS map was more inspiring than expected how nostr-vpn and FIPS turn network participation into something more tangible why FIPS and Nostr both make more sense as local-first systems than as one giant global state machine why freedom-tech projects do not need Silicon Valley scale metrics to matter how Buzz packages a Nostr relay, NIP-29 rooms, agent harnesses, Git-style workflows, and human-agent collaboration into one workspace what changes when agents have pubkeys, signed actions, and a cryptographic paper trail instead of pretending to be whichever human launched them why NIP-29 is an acceptable trade-off for some team and agent channels even though it is not encrypted how trust boundaries, hosted relays, local deployment, and organizational context shape the security model why "more autonomous agents" really means agents that can make better local calls without burning human time how Pablo thinks about persistent agent identity, throwaway workers, higher-level roles, and the "Pablo replica" pattern why too many explicit instructions can remove agency and recreate a brittle workflow engine how Mosaico gives agents awareness without becoming an orchestrator why workspaces, one-line status, subchannels, mentions, and narrow context hints can be enough for agents to find each other how proactive context tries to keep the actual user input as the source of truth instead of letting a memory layer hallucinate intent why "no context" is better than bad context how Napplets, Amethyst, Blossom, Outbox, and composable clients rhyme with the same move away from one cathedral-sized application Related dialogues: #18: Rewriting TENEX w/ Pablo #19: Romantically Shitting on Paywalls w/ Pablo #11: 10x Less Productive w/ Pablo #20: Archipelago Meshtadels w/ Shadrach #25: White Noise, MLS, and marmot w/ Jeff G #30: Napplets w/ Sandwich People mentioned: Martti Malmi <a href="https://njump.to/npub1uac67zc9er
- 1 weeks ago1h 37m
30: Napplets w/ Sandwich
"You should be able to compose your clients." Sandwich & Gigi take a walk. Listen on sovereignengineering.io Sandwich and Gigi spend the first 45 minutes or so talking through napplets: composable, sandboxed Nostr apps that can run inside a host shell while the host mediates signing, storage, relay access, uploads, permissions, and user trust. What starts as a conversation about applets quickly becomes an operating-system conversation: if Nostr is flexible enough to carry many kinds of software, clients probably need to become composable runtimes instead of monolithic apps. Along the way they get into browser sandboxes, iframes, postMessage, malicious applets, Blossom uploads, NIP-5D, nsites, specialized relays, agent workflows, slop scanning, and why the AI subsidy era will not last forever. In this dialogue: why a normal Nostr client can feel too restrictive for a protocol built around maximum flexibility how napplets grew out of earlier experiments with Naps, Nap.run, nsites, Hyprland-inspired desktops, Tauri, Thorium, and iframe hardening why the host runtime handles keys, signing, encryption, relays, resource loading, storage, uploads, and user prompts why napplets should get high-level helper APIs plus low-level escape hatches instead of direct access to everything how a napplet can upload through Blossom without knowing which Blossom server the user prefers why the shell should see plaintext over the message bus, and how that helps defend users from malicious applets how applet-to-app communication starts to look like Android intents, MIME types, archetypes, and operating-system resource APIs why the browser is a practical deployment target even if the napplet protocol itself is not browser-bound what Kehto, Paja, the napplet dev tooling, and the no-dependencies approach are trying to protect how a workshop produced a dozen napplets, including live stream views, paste-to-upload flows, and even a rough multiplayer chess app why nsites, nsyte, Blossom, Hashtree, and specialized relays all rhyme with the same broader Nostr publishing model why relay specialization and relay discovery might matter more than one giant general-purpose relay model how agent workflows are starting to rebuild older software-development structures: specs, milestones, issues, review teams, and CI why slop scanning, naming discipline, and opponent processing matter once code becomes the context future agents learn from why local model hardware is tempting, but only if you think about it like mining: power, refresh cycles, subsidy cliffs, and cost per watt People mentioned: hzrd149 fiatjaf Pablo Austin Franzap Projects & tech mentioned: napplet.run Napplet Workshop NIP-5D Kehto nsite.run nsyte nsyte.run Blossom Hashtree Nostr NDK Applesauce Amber zap.stream Nostr Watch NIP-66</a
- Jun 7, 20261h 5m
29: State of the Mint and Mind w/ Calle
"You cannot look at something without touching it." Calle & Gigi take a walk. Listen on sovereignengineering.io Calle and Gigi start with Cashu mint internals and end in embodied cognition. Along the way they unpack sparse Merkle trees, exclusion proofs, unilateral exit, trusted execution environments, recovery paths, the move to BLS signatures, agentic coding workflows, specialist versus generalist models, world models, and why Bitcoin, Nostr, and local AI still feel like reasons for optimism. In this dialogue: how mint state can be compressed into a sparse Merkle tree and why exclusion proofs matter for ecash how unilateral exit could reduce both the slow rug pull and the fast rug pull for Cashu mints why trusted execution environments change the trust model, and why on-chain-first mint backing is the easiest place to start how timelocks and third-party recovery paths might soften mint downtime why Cashu is moving away from its current signature setup toward BLS signatures and what that unlocks how Calle actually works with coding agents, from OpenRouter and OpenCode to fresh contexts and ruthless resets why context windows are scarce, token maxing is wasteful, and one agent per project beats one giant assistant why cognitive science still matters when talking about specialists, generalists, and what frontier labs are betting on why world models differ from next-token predictors and why Vervaeke on AI and embodiment keeps coming back why Thomas Nagel and The Blind Spot show up once the conversation turns to observation, physics, and experience why high-agency builders should feel more hopeful than scared right now why Bitcoin, Nostr, and improving local models still look like the right ingredients for a freer future People mentioned: Luke Childs Waxwing Peter Steinberger Martti Malmi (#21: Hashtree, Nostr VPN, and Iris w/ Martti Malmi) Egge Kukks Yann LeCun Thomas Nagel David Chaum David Wagner Projects & tech mentioned: Cashu Cashu Dev Kit Ark Protocol OpenRouter OpenCode OpenClaw Fabian’s NIP-17 plugin for OpenClaw Bitcoin Nostr BLS signatures Readings mentioned: <a href="https://ia800100.us.archive.org/5/items/thomas-nagel-what-is-it-like-to-be-a-bat/Thomas%20Nagel%2C%20What
- Jun 2, 20261h 3m
28: Speak Human w/ MouxDesign
"We just need to speak human." MouxDesign & Gigi take a walk. Listen on sovereignengineering.io Recorded in June 2026. Mo and Gigi keep circling one question: how do you build products for people who speak plain language instead of protocol jargon? From there they get into wallet copy, fee panic, backup rituals, agentic design workflows, broken Nostr onboarding, fun-first software, and the old Bitcoin fight over purity versus adoption. In this dialogue: why design starts before the interface, at the app store screenshot, the first sentence, and the story a user tells a friend Mo's current workflow: screenshots, Mobbin, a skill file, n8n, sleep, then a sober morning review why wallet UX still stumbles on backup rituals, fee displays, and error messages that dump the cognitive load on the user why "copy is design" and why everyday users need plain language instead of protocol vocabulary how Nostr key loss turns people into read-only ghosts and leaves account recovery in an awkward place why apps on Nostr still feel early, and why fun matters if you want people to come back why Martti's work keeps coming up, from Iris to Nostr VPN, plus a callback to #21: Hashtree, Nostr VPN, and Iris w/ Martti Malmi why Jeff G's work on White Noise still matters when the conversation turns to strange network conditions and real apps, plus a callback to #25: White Noise, MLS, and marmot w/ Jeff G why Gigi still leans toward protocol purity when mass adoption asks for compromise why walking and thinking out loud can still beat Slack threads, group chats, and solo brainstorming how communities form when somebody plants a flag, names the thing, and keeps showing up, whether that is 21 World or something else why the simple test still matters: did you ship something that makes people happier? People mentioned: Jack Dorsey Alex Gladstein Martti Malmi (#21: Hashtree, Nostr VPN, and Iris w/ Martti Malmi) Jeff G (#25: White Noise, MLS, and marmot w/ Jeff G) Rabble Josh Christoph Arno Marcus Projects & tech mentioned: Bitcoin Design Guide Bitcoin Nostr Block Iris White Noise Mobbin n8n Nostr VPN BTCPay Server 21 World Recorded at 952,115.
- Jun 1, 20261h 5m
27: Separation of Business from State w/ gsovereignty
"It’s the people who receive Bitcoin as payment for something who decide what Bitcoin is." gsovereignty & Gigi take a walk. Listen on sovereignengineering.io Recorded in May 2026. They explore what it would take to separate business from the state, why a Bitcoin economy still depends on fiat imports, and how Nostrocket might route human energy into Bitcoin-native production. Along the way they get into circular economies, merchant adoption, stablecoins, organizational design, application-specific agent harnesses, and the trade-offs behind merit-based equity, minimal governance, and forkable ventures. In this dialogue: why merchant adoption alone does not create a sovereign Bitcoin economy why registered businesses remain exposed to state control how Nostrocket reframes proof of work as human coordination around useful production what minimal governance, merit issuance, and forkability might look like in a Bitcoin-native venture why open source projects, DAOs, and Bitcoin itself keep surfacing the same authority trade-offs why application-specific agent harnesses, formal specs, and peer review may be the right proving ground for these ideas People mentioned: Saifedean Ammous Michael Saylor Frederic Laloux Vitor Pamplona Pablo Projects & tech mentioned: Bitcoin Nostr Nostrocket Bitcoin Jungle Soap Miner isolabellart The Leathermint Reinventing Organizations Holacracy Amethyst Bitcoin Core Claude stablecoins BlackRock Recorded at 951,874.
- May 31, 20261h 7m
26: Zapstore w/ Franzap
"The user joins the community, and the community does a lot of the heavy lifting." Franzap & Gigi take a walk in Oslo. Listen on sovereignengineering.io In this dialogue: How Zapstore grew out of the first Sovereign Engineering cohort in Madeira, earlier experiments like ZapThreads, and Franzap's frustration with closed mobile app stores Why Ninite, app stacks, and curated discovery mattered as much as the raw "permissionless app store" idea What it means to run Zapstore as a real marketplace: breaking the chicken-and-egg problem by pre-populating supply, signing apps under the Zapstore key, and gradually moving developers toward self-publishing Web-of-trust computation, trust providers, and why app distribution raises the stakes far beyond regular social posting Franzap's "credible exit" framing: sometimes you dial down decentralization to improve UX, as long as users can still verify, leave, and choose another community ZSP, the Zapstore publisher CLI, and how agents can already build and publish Android apps without the developer even owning an Android phone Device keys, encrypted preferences, onboarding trade-offs, and why social features, comments, and zaps are a different problem from simply installing an app Why app lists are a privacy leak, how update infrastructure can turn into a honeypot, and what it means to distribute software without building a profiling machine The operational pain behind a living app catalog: pre-releases, key rotations, migrations, certificate mismatches, and endless edge cases Google's tightening sideloading and KYC rules, Apple's developer-account maze, and why every new permissioned hurdle makes the permissionless route more compelling Why Zapstore may matter most for people at the edges: controversial apps, developers outside the usual payment rails, and users who cannot or will not pass through the official gates What's next: default communities, reviews, malware checks, privacy analysis, reproducibility, and smoother handoffs from indexed apps to self-published releases People mentioned: fiatjaf (built an earlier Nostr-native commenting system that influenced ZapThreads) American HODL / Viper (example of agent-built, agent-published Android apps) DHH and PewDiePie (part of the closing Linux detour) Projects & tech mentioned: Zapstore ZapThreads ZSP (Zapstore publisher CLI) Nostr GrapheneOS OpenSats Ninite Fossify Voice Recorder Phoenix Wallet Recorded at 951,851.
Get No Solutions summaries in your inbox
Free AI-powered daily recaps. Key takeaways, quotes, and mentions — in a 5-minute read.
Get Free Summaries →Free forever for up to 3 podcasts. No credit card required.
You Might Also Like
Listeners also like.
Better Offline
Ed Zitron investigates how tech’s powerful players shape society, from crypto scams to venture capital, through interviews and critical analysis.
Accidental Tech Podcast
Three nerds discuss technology, Apple, programming, and related topics.
The Best One Yet
Daily business news explained through sharp analysis and witty commentary, delivered in concise 20-minute episodes.
Solutions with Henry Blodget
Henry Blodget interviews experts in business, tech, and politics about practical solutions for building a better future.
Reply All
A podcast that explores the internet and its impact on modern life through investigative stories and personal narratives.
Security Now (Audio)
A weekly deep dive into cybersecurity threats, hacking trends, and practical defense strategies for individuals and businesses.
More or Less
Four tech insiders with deep experience at major Silicon Valley companies and startups discuss the industry's biggest trends and debates.
FOSS and Crafts
A podcast exploring free software, free culture, and collaborative making.
This Machine Kills
Critiques the intersection of technology, capitalism, and power through a leftist political lens.
The Great Simplification with Nate Hagens
Discussions with experts on energy, ecology, economics, and human behavior to understand the systemic challenges facing civilization.
The Restless Ones
Executives at the intersection of technology and business discuss innovation, leadership, and driving change in fast-evolving industries.
Whiskey Web and Whatnot
Developers discuss web technologies, AI coding tools, and software careers alongside casual talk about the human side of programming.
About No Solutions
No solutions; only trade-offs. Walking towards a better internet. Est. 882,690. Inspired by Sovereign Engineering
Customized Recaps
AI-powered recaps with compact key takeaways, quotes, and insights.
Straight to Your Inbox
Get key takeaways from No Solutions in a 5-minute read.
Save Hours Every Week
Stay current on your favorite podcasts without falling behind.
Frequently Asked Questions
What is Podzilla's No Solutions daily summary?
It's a free AI-powered email that summarizes new episodes of No Solutions as soon as they're published. You get the key takeaways, notable quotes, and links & mentions — all in a quick read.
How does the No Solutions podcast summary work?
When a new episode drops, our AI transcribes and analyzes it, then generates a personalized summary tailored to your interests and profession. It's delivered to your inbox every morning.
Is this an official No Solutions product?
No. Podzilla is an independent service that summarizes publicly available podcast content. We're not affiliated with or endorsed by Gigi.
Can I get summaries of other podcasts too?
Absolutely! The free plan covers up to 3 podcasts. Upgrade to Pro for 15, or Premium for 50. Browse our full catalog at /podcasts.
How often does No Solutions release new episodes?
No Solutions publishes daily. Our AI generates a summary within hours of each new episode.
What topics does No Solutions cover?
No Solutions covers topics including Technology. Our AI identifies the specific themes in each episode and highlights what matters most to you.
Start getting No Solutions summaries tomorrow morning.
Free forever for up to 3 podcasts. No credit card required.
Free forever for up to 3 podcasts. No credit card required.