Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Importing Multisignature transaction from Electrum Fails in Specter #1046

Closed
kaspar-nl opened this issue Mar 23, 2021 · 2 comments
Closed

Importing Multisignature transaction from Electrum Fails in Specter #1046

kaspar-nl opened this issue Mar 23, 2021 · 2 comments
Labels
bug Something isn't working

Comments

@kaspar-nl
Copy link

I created a multisig wallet (2-of-2), create a tx, and signed the tx in Electrum, and exported the raw PSBT transaction to clipboard.
Next, I pasted the raw PSBT transaction in Specter Desktop (Send > Import) in the dedicated box and clicked on 'import transaction' and get the error "Exception: 'dict object' has no attribute 'witness_utxo'" (see below). So this means, I cannot sign the transaction first in Electrum and send it to somebody else so sign in with Specter.

I tried it the other way (first sign with Specter, then export the PSBT tx, and then import it by Electrum and sign) and that works fine, but that means the Specter needs to sign always first, which is not very practical.

Setup:

  • Electrum (Testnet) 4.0.9
  • Specter Desktop v1.2.2
  • Create 2-of-2 Multisign wallet

image

@ben-kaufman ben-kaufman added the bug Something isn't working label Mar 23, 2021
@k9ert
Copy link
Collaborator

k9ert commented Apr 20, 2021

Seems to be related to spesmilo/electrum#6429 which has been fixed in the meantime. Which version of electrum did you use for that? Maybe an upgrade helps?

@k9ert
Copy link
Collaborator

k9ert commented Nov 30, 2021

Please reopen if this is still an issue.

@k9ert k9ert closed this as completed Nov 30, 2021
SomberNight added a commit to spesmilo/electrum that referenced this issue Oct 31, 2022
Until now we have been only putting PSBT_IN_NON_WITNESS_UTXO (="UTXO", full tx)
in segwit witness v0 txins, as signers wanted the full tx anyway due to
bip-143 sighash issue [0], and as WITNESS_UTXO can be calculated from UTXO.

My reading of bip-174 is that either behaviour is correct, but
achow101 said bip-174 expects PSBT_IN_WITNESS_UTXO for segwit inputs.
Regardless, including both fields does not increase the tx size too much
(UTXO can be very large ofc but we were already including that, WIT_UTXO is small).
This also might increase compatibility with some other software - I've found
some issues where this might have been the culprit [1][2][3].

closes #8039

related:
[0] #6198
[1] cryptoadvance/specter-desktop#868
[2] cryptoadvance/specter-desktop#1046
[3] cryptoadvance/specter-desktop#1544
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants