Episode
24: Building FIPS w/ Johnathan Corgan
- Podcast
- No Solutions
- Published
- Apr 16, 2026
- Duration seconds
- 2146
- Processing state
not_requested
Actions
POST https://stenobird.com/v1/public/podcasts/no-solutions-7206062/episodes/24-building-fips-w-johnathan-corgan/transcription-requests
Idempotently request low-priority transcript generation for this episode.GET https://stenobird.com/podcast/no-solutions-7206062/24-building-fips-w-johnathan-corgan.md
Read the agent-friendly Markdown representation of this episode resource.
Summary
“Don’t be afraid of going your own way.” Johnathan Corgan & Gigi take a walk in Madeira. Recorded during SEC-07 . Listen on sovereignengineering.io In this dialogue: Why FIPS started with Arjen asking for networking that does not depend on registrars, central authorities, or yankable domain names Johnathan disappearing for a month after Costa Rica, then returning with a protocol design that scratched the itch FIPS as a self-organizing peer mesh: no privileged coordinator, only what each node can enforce locally Transport-agnostic networking: Ethernet, Bluetooth, UDP overlays, Tor, serial links, and whatever else can move packets A hilariously impractical but very useful test: tunneling FIPS over Nostr relays, with ping times measured in seconds, and it still worked Why robustness under ugly conditions matters more than looking elegant on the happy path 150 nodes already on the FIPS testnet, and what has to change to get from 150 to 1,500 to 15,000 Friday Demo Day as the forcing function: build it, show it, let other people poke holes in it The next FIPS release: fewer unnecessary pieces, stronger protocol negotiation, harder internals, more battle testing “Try to break it” so friends can fix it before hostile actors do Costa Rica and SEC-07 as a return to the early Cypherpunk and early Bitcoin energy: do not reform the old system, route around it Why Nostr feels miraculous if you remember the world before it, even if normies still see it as half-baked “Rough consensus and running code”: academic rigor, design review, and why code still has to survive contact with reality Johnathan’s critique of “shower thought to ZapStore in six hours” culture: speed helps, but engineering still matters Claude Code wrote most of FIPS only after two months of protocol iteration and…