Damus
David Pinkerton profile picture
David Pinkerton
@David Pinkerton
SeedSigner doesn't support message signing for multisig keys — it throws "Not implemented" for any m/48' derivation path. I raised this as an issue two years ago, no fix came, so I patched it myself.

The change is small (21 lines) and the actual signing function already worked — it was just the path parser blocking multisig paths unnecessarily.

I use message signing for key ownership and control verification in multisig SMSF custody setups via Gatekeeper (https://gatekeeper.dpinkerton.com). Coldcard handles this fine, but SeedSigner users were stuck.

Blog post: https://blog.dpinkerton.com/posts/patching-seedsigner-multisig-message-signing/
PR: https://github.com/SeedSigner/seedsigner/pull/874
Patched image (Pi Zero): https://github.com/AusDavo/seedsigner/releases/tag/0.8.6-multisig-msg-signing

#seedsigner #bitcoin #multisig #opensource
145❤️6🤙2👀1👍1💖1💪1
🇮🇹Davide btc ⚡ · 1w
Based devs fixing broken things. SeedSigner gets a small, but vital, patch.
Dr. Hax · 1w
Thank you for your contribution 🫡
Brisket · 1w
Nice one Dave! 🔥
Zsubmariner · 1w
Thanks!
SondreB · 6d
Great work! I'm so sorry you had to actually experience getting this response. 🤯 https://mibo.eu.nostria.app/64f1952849b878134751d3d0a1d490901f3864c775f53ed263f438db3de0e0fc.webp
Jack D · 6d
I think that the BIP43 purpose fields were a mistake adding complexity. It attempts to track script type, but breaks down in many multisig applications.
BitSatRelay · 5d
🛰️Off-Grid Relayed via satellite🛰️ -------------------------------- 🔁 nostr:npub1l5pxvjzhw77h86tu0sml2gxg8jpwxch7fsj6d05n7vuqpq75v34syk4q0n REPOSTED nostr:npub1jz0rlhp9ngs3at2kfhzcnc62sxh0y9rxt40x3z003wmdguljky9quaaju6's post Original post: SeedSigner doesn't support message signing f...