I got my music tutor to accept Bitcoin payment a while back. That was with Muun. I thought that I was helping to nudge him onto Breez but regretted it today when he couldn't send me an invoice. Any had the same problem?

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:

David Pinkerton

Patching SeedSigner to Support Multisig Message Signing

I run CertainKey, a service that provides ownership and control verification reports for self-managed super funds (SMSFs) holding bitcoin. Part of ...

PR:

GitHub

Support BIP48 multisig derivation paths for message signing by AusDavo · Pull Request #874 · SeedSigner/seedsigner

Summary Removes the raise Exception("Not implemented") block for m/48' paths in parse_derivation_path() Adds BIP48 path parsing: rea...

Patched image (Pi Zero):

GitHub

Release v0.8.6 + BIP48 Multisig Message Signing · AusDavo/seedsigner

What is this? This is SeedSigner v0.8.6 with a single patch to enable message signing for BIP48 multisig derivation paths (e.g. m/48'/0'/0'/2'/0/0)...

#seedsigner #bitcoin #multisig #opensource