{"type":"rich","version":"1.0","author_name":"David Pinkerton (npub1jz…aaju6)","author_url":"https://nostr.ae/npub1jz0rlhp9ngs3at2kfhzcnc62sxh0y9rxt40x3z003wmdguljky9quaaju6","provider_name":"njump","provider_url":"https://nostr.ae","html":"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.\n\nThe change is small (21 lines) and the actual signing function already worked — it was just the path parser blocking multisig paths unnecessarily.\n\nI 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.\n\nBlog post: https://blog.dpinkerton.com/posts/patching-seedsigner-multisig-message-signing/\nPR: https://github.com/SeedSigner/seedsigner/pull/874\nPatched image (Pi Zero): https://github.com/AusDavo/seedsigner/releases/tag/0.8.6-multisig-msg-signing\n\n#seedsigner #bitcoin #multisig #opensource"}