pull down to refresh
I remember hearing that Nunchuk supported MuSig2, but when I did some looking just now, I saw something that said it is only supported for software wallets...which seems to imply that none of the hardware signers support it.
Ledger claims they support MuSig2 via their Bitcoinapp, and I thought that BitBox supported it, but their blog post about musig doesn't explicitly say they support it. I'm not aware of others that have rolled out MuSig2 support.
I've not personally used a Ledger, but Salvatore seems to keep them on the cutting edge.
The larger question of using purpose-specific signing device is very interesting to me. I still feel a little that it is a bigger target than the safety it provides. I know lots of people use them with no problem, but I still get nervous about the idea of a device that has no other purpose than to sign bitcoin transactions -- how are they not massive honey pots?
I guess the solution is multi-vendor multisig.
how are they not massive honey pots?
In the case of Ledger... they are. This was a whole scandal a few years back and it made me regret using that (and telling others to use it).
It all comes down to the secure element being sufficiently hard to extract data from (and arguably since any ledger app can extract a key, that isn't "hard", it's trustmebro). Hardware security buys you time to move funds; that's really all it does.
For now I'm still sticking to old school scripted multisig, but I was wondering if there is a place that tracks MuSig2 (and added PSBT fields from BIP-373 implementation across signing libs / devices?
I know that Core has had the fields implemented for a couple of months now, but what field-usable implementations (as in not-Core wallet) can we play with today?