<oembed><type>rich</type><version>1.0</version><author_name>David Pinkerton (npub1jz…aaju6)</author_name><author_url>https://nostr.ae/npub1jz0rlhp9ngs3at2kfhzcnc62sxh0y9rxt40x3z003wmdguljky9quaaju6</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>SeedSigner doesn&#39;t support message signing for multisig keys — it throws &#34;Not implemented&#34; for any m/48&#39; derivation path. I raised this as an issue two years ago, no fix came, so I patched it myself.&#xA;&#xA;The change is small (21 lines) and the actual signing function already worked — it was just the path parser blocking multisig paths unnecessarily.&#xA;&#xA;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.&#xA;&#xA;Blog post: https://blog.dpinkerton.com/posts/patching-seedsigner-multisig-message-signing/&#xA;PR: https://github.com/SeedSigner/seedsigner/pull/874&#xA;Patched image (Pi Zero): https://github.com/AusDavo/seedsigner/releases/tag/0.8.6-multisig-msg-signing&#xA;&#xA;#seedsigner #bitcoin #multisig #opensource</html></oembed>