# 21 in 21: Rod Roudi Page: https://stenobird.com/podcast/21-in-21-7274084/21-in-21-rod-roudi Text version: https://stenobird.com/podcast/21-in-21-7274084/21-in-21-rod-roudi.md Podcast: [21 in 21](https://stenobird.com/podcast/21-in-21-7274084) Published: 2025-12-11T14:00:25+00:00 Episode link: https://feeds.fountain.fm/225QxxaXdKbEEjEXSha3/items/2i3DahSp86BrzsOBTII7/files/AUDIO---DEFAULT---accb9795-1bc4-4738-af9e-386f268ec17e.mp3 Audio file: https://feeds.fountain.fm/225QxxaXdKbEEjEXSha3/items/2i3DahSp86BrzsOBTII7/files/AUDIO---DEFAULT---accb9795-1bc4-4738-af9e-386f268ec17e.mp3 Processing state: not_requested JSON: https://stenobird.com/v1/public/podcasts/21-in-21-7274084/episodes/21-in-21-rod-roudi Duration seconds: 1464 ## Resource In this episode of 21 in 21, Haley sits down with Rod Roudi, co-founder of Bitcoin Park in Nashville and Austin. Rod breaks down how Bitcoin Park began, why in-person energy fuels strong communities, and how Nashville grew into a hub for bitcoiners, policymakers, founders, developers, and bitcoin-curious locals. He also shares what he’s learned about bitcoin payments from the business side, why reducing merchant friction is essential, and what he’s looking forward to in 2026. Episode Chapters 00:00 Welcome Rod 01:44 Bitcoin Park Description 03:39 Origin Story 07:08 Engaging Policymakers and Local Community 13:38 Accepting Bitcoin as a Business 16:22 Merchant Adoption and Reducing Friction 20:22 College Basketball Break 21:47 What Rod Is Excited About in 2026 23:06 Where to Follow Rod & Bitcoin Park https://x.com/bitkite https://x.com/bitcoinpark_ https://x.com/HBerkoe ## Actions - request_transcript: `POST https://stenobird.com/v1/public/podcasts/21-in-21-7274084/episodes/21-in-21-rod-roudi/transcription-requests` — Idempotently request low-priority transcript generation for this episode. - read_markdown: `GET https://stenobird.com/podcast/21-in-21-7274084/21-in-21-rod-roudi.md` — Read the agent-friendly Markdown representation of this episode resource. A page view does not enqueue transcription. Agents should invoke `request_transcript` explicitly when they need this episode processed. ## Transcript Full transcripts are not published on public pages unless there is a clear rights basis.