Prime multisig not working with bluewallet

Passport Prime
1

Hi,

New user. I set up a multi-sig and in sparrow and like having it also on blue wallet. When I go to do a transaction on blue wallet, the prime is unable to sign the transaction. this is the error message i get on the device. The weird thing is it can sign a single sig transaction in blue wallet and if i was to use the primes seed and on a seed signer or a jade stateless it will work by signing transaction in blue wallet. Can anyone help?

image
image815×807 94 KB

2

Thanks for the report. I have reproduced it here on 1.3.1.

The cause is on our side. BlueWallet does not include a piece of optional wallet information in the PSBTs it builds, and Passport Prime currently relies on that information to work out which multisig wallet a transaction belongs to. Sparrow does include it, which is why Sparrow works. It is also why your seed signs the same transaction fine on a SeedSigner or a Jade, those do not require that field to identify the wallet. The field is optional in the PSBT standard, so this is ours to fix rather than anything BlueWallet is doing wrong.

While looking into it we found a second problem worth knowing about. If your multisig config on Passport Prime was imported from BlueWallet, Passport Prime may not recognise a Sparrow-built PSBT for that same wallet either, and will ask you to import a config you already have. Both are now logged with our engineers.

Until they are fixed, this gets you signing again:

  1. Delete the existing multisig account from Passport Prime.

  2. Export the multisig config from Sparrow and import that copy into Passport Prime.

  3. Build and sign your transactions in Sparrow.

You can still keep the wallet loaded in BlueWallet to watch balances and receive, you just cannot sign from it at the moment.

Nothing here puts your keys or funds at risk. It only affects whether the device will accept a transaction for signing, and no partially signed transaction is lost by retrying.

I will update this thread when the fix lands.

3

Expecting to have this fixed in 1.5.0 - catalogued as fixes SFT-7692 and SFT-7693, there’s a couple of things causing this but they have already been identified. Thank you for the report, and thank you for the patience!