# EP55 - Multisig Setup with Svrgnty

Page: https://stenobird.com/podcast/navigating-bitcoin-s-noise-4356332/ep55-multisig-setup-with-svrgnty
Text version: https://stenobird.com/podcast/navigating-bitcoin-s-noise-4356332/ep55-multisig-setup-with-svrgnty.md
Podcast: [Navigating Bitcoin's Noise](https://stenobird.com/podcast/navigating-bitcoin-s-noise-4356332)
Published: 2024-09-04T13:08:29+00:00
Episode link: https://www.spreaker.com/episode/ep55-multisig-setup-with-svrgnty--61261713
Audio file: https://dts.podtrac.com/redirect.mp3/api.spreaker.com/download/episode/61261713/ep55_multisig_setup_with_svrgnty.mp3
Processing state: not_requested
JSON: https://stenobird.com/v1/public/podcasts/navigating-bitcoin-s-noise-4356332/episodes/ep55-multisig-setup-with-svrgnty
Duration seconds: 2437

## Resource

Welcome to Navigating Bitcoin's Noise, the podcast where we cut through the clutter and bring you the most insightful perspectives in the world of Bitcoin. I'm your host, Kane McGukin, and today we will be discussing Multisig with Svrgnty. In our conversation, we discussed the value and security of a multisig setup and how it can be done at the individual level. If you’re looking to better understand Bitcoin’s past and future potential as an economic network, this is the episode for you. So, sit back, relax, and let’s dive in. Kane McGukin X: https://twitter.com/kanemcgukin kanemcgukin.substack.com Svrgnty X: https://x.com/svrgnty https://svrgnty.com/ Bitcoin Node post: https://x.com/svrgnty/status/1713977979766780201

## Actions

- request_transcript: `POST https://stenobird.com/v1/public/podcasts/navigating-bitcoin-s-noise-4356332/episodes/ep55-multisig-setup-with-svrgnty/transcription-requests` — Idempotently request low-priority transcript generation for this episode.
- read_markdown: `GET https://stenobird.com/podcast/navigating-bitcoin-s-noise-4356332/ep55-multisig-setup-with-svrgnty.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.