# Open-source Bitcoin multisig coordinator: shared signing queue, hardware wallets, live signet demo

**URL:** <https://delvingbitcoin.org/t/open-source-bitcoin-multisig-coordinator-shared-signing-queue-hardware-wallets-live-signet-demo/2957>\
**Category:** Implementation\
**Tags:** musig2, taproot\
**Created:** [October 13, 2026, 1:25pm UTC](https://delvingbitcoin.org/t/open-source-bitcoin-multisig-coordinator-shared-signing-queue-hardware-wallets-live-signet-demo/2957 "2026-10-13T13:25:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tom2o17](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/tom2o17/32/2421_2.png) [@tom2o17](https://delvingbitcoin.org/u/tom2o17)\
**Post date:** [October 13, 2026, 1:25pm UTC](https://delvingbitcoin.org/t/open-source-bitcoin-multisig-coordinator-shared-signing-queue-hardware-wallets-live-signet-demo/2957/1 "2026-10-13T13:25:48Z")

</div>

I’ve open-sourced **btc-safe** , a self-hosted, watch-only Bitcoin multisig coordinator. One owner proposes a transaction. Every co-signer sees it in a shared queue and signs from their own device. It broadcasts once M of N have signed.

• **Watch-only:** the server stores xpubs and descriptors only. It never holds keys and never signs.

• **Independent checks:** the browser re-derives change and receive addresses from the xpubs and cross-checks every PSBT against the server.

• **Signers:** Ledger (WebHID), Trezor, Sparrow and Caravan import, and PSBT files.

• **Accounts:** TOTP 2FA and per-wallet roles (admin, proposer, viewer). Reorg-aware confirmations.

• **Stack:** Rust (axum, bdk\_wallet, Postgres) and Next.js. MIT licensed.

**Try it (signet, no real funds):** [https://web-production-56752.up.railway.app](https://web-production-56752.up.railway.app). Sign up with any email, create a 2-of-3, and fund it from a signet faucet.

**Code:** [GitHub - tom2o17/btc-safe: Self-hosted, watch-only Bitcoin multisig coordinator with a shared proposal queue (signet only, experimental) · GitHub](https://github.com/tom2o17/btc-safe)

 ![telegram-cloud-photo-size-1-5059908105818279286-y](https://delvingbitcoin.org/uploads/default/original/2X/d/d4292ec5332c389705717afdddedc85376b7558b.jpeg)

---

<div class="post-metadata">

**Author:** ![Anzus\_GemWallet](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/anzus_gemwallet/32/2271_2.png) [@Anzus\_GemWallet](https://delvingbitcoin.org/u/Anzus_GemWallet)\
**Post date:** [October 15, 2026, 1:41pm UTC](https://delvingbitcoin.org/t/open-source-bitcoin-multisig-coordinator-shared-signing-queue-hardware-wallets-live-signet-demo/2957/2 "2026-10-15T13:41:03Z")

</div>

Nice to see this open-sourced. One question from the user side: if the coordinator server goes offline or stops being maintained, can co-signers still recover and spend with just their hardware wallets? And does the app prompt everyone to save a backup of the wallet setup when the wallet is first created?