Can't sign multisig wallet transaction

BlackHatCoiner

legendary

Activity: 1512

Merit: 7340

Farewell, Leo

Quote from: hosseinimr93 on October 13, 2021, 08:55:51 AM

Because, each coin will be always 1 input.

As you said, coins are unspent transaction outputs (UTXOs). An UTXO cannot have inputs for the simple reason that it's an output. Transactions have inputs & outputs, but a coin is essentially the output.

Quote from: hosseinimr93 on October 13, 2021, 08:55:51 AM

Shouldn't it be "Each address can have many inputs"?

No, because addresses have no inputs neither outputs. The transactions do have.

Quote from: hosseinimr93 on October 13, 2021, 08:55:51 AM

Assuming someone has received all transactions into a single address, now all UTXOs (will be called input when using for making a transaction) are in 1 address and "Addresses" tab wouldn't be helpful and you have to use "Coins" tab.

Correct. The addresses' tab generally doesn't offer anything other than the direct projection of all your addresses. You could use the “Receive” and “Coins” tab instead.

hosseinimr93

legendary

Activity: 2380

Merit: 5213

Quote from: o_e_l_e_o on October 13, 2021, 08:39:48 AM

No, you're right. The coins tab shows all your individual UTXOs, whereas the addresses tabs just shows you the cumulative balance on each address. ..........

So, why did LoyceV say

Quote

Each "Coin" can still have many inputs. If that's the case, use the Addresses tab instead.

Shouldn't it be "Each address can have many inputs"? Because, each coin will be always 1 input.
I still don't get why LoyceV suggested using "Addresses" tab instead of "Coins" tab.

Assuming someone has received all transactions into a single address, now all UTXOs (will be called input when using for making a transaction) are in 1 address and "Addresses" tab wouldn't be helpful and you have to use "Coins" tab.

o_e_l_e_o

legendary

Activity: 2268

Merit: 18771

Quote from: hosseinimr93 on October 13, 2021, 08:29:37 AM

Correct me If I'm wrong, please.

No, you're right. The coins tab shows all your individual UTXOs, whereas the addresses tabs just shows you the cumulative balance on each address. If you have received coins to the same address on more than occasion and you want to spend them separately, then you need to use the coins tabs to select which UTXOs to spend.

OP, use the coins table to manually select inputs which are below the size threshold, and send all the inputs to a new address you own using a fee of 1 sat/vbyte. Repeat this as many times as needed to consolidate all your coins. Then figure out why you have ended up with hundreds of inputs, because you will be losing loads of money in fees. Are you withdrawing these coins from an exchange or other service? Better to build up to a decent amount and withdraw it in one go rather the end up with hundreds of small inputs.

hosseinimr93

legendary

Activity: 2380

Merit: 5213

Quote from: LoyceV on October 13, 2021, 05:57:49 AM

Each "Coin" can still have many inputs. If that's the case, use the Addresses tab instead.

Doesn't each coin represent exactly 1 UTXO (called input when they are used for making a transactions)?
Let's say I have received 100 transactions into a single address. If I go to "Coins" tab, I should see 100 rows and I can select or freeze any of them.
Correct me If I'm wrong, please.

LoyceV

legendary

Activity: 3290

Merit: 16489

Thick-Skinned Gang Leader and Golden Feather 2021

Quote from: hosseinimr93 on October 05, 2021, 02:59:26 PM

Go to "Coins" tab. (If the "coins" tab is not available, click on "View at top of the window and select "Show coins".)

~~Each "Coin" can still have many inputs. If that's the case, use the Addresses tab instead.~~ Sorry, it's the exact opposite. Hosseinimr93 is right.

@spencericassidy: if your transaction is really above 100 kbyte, you're going to want to read how to consolidate at low fee. Manually setting the fee (and checking the transaction details before sending) can save you a lot of money.

HCP

legendary

Activity: 2086

Merit: 4363

Quote from: spencericassidy on October 05, 2021, 07:47:18 AM

I'm still getting an error even after restoring both 2 wallets (the multisig wallet and co-sign wallet) I'm getting this error on electrum

The server returned an error when broadcasting the transaction.
Consider trying to connect to a different server, or updating Electrum.

The transaction was rejected because it is too large (in bytes).

If you preview the transaction in Electrum... what is the size in bytes that it is displaying? Also how many inputs are listed? Huh

nc50lc

legendary

Activity: 2618

Merit: 6452

Self-proclaimed Genius

Quote from: spencericassidy on October 05, 2021, 02:33:00 PM

Quote from: nc50lc on October 05, 2021, 08:34:42 AM

-snip-

Excuse me for my ignorance how can I reduce the number of inputs with electrum (or control them)

To expand the post above, about "shift" and "ctrl":

Holding SHIFT will select everything in between the last clicked highlighted coin and the coin that you'll click next.
Holding CTRL will enable you to highlight one coin at a time.

hosseinimr93

legendary

Activity: 2380

Merit: 5213

Quote from: spencericassidy on October 05, 2021, 02:33:00 PM

Excuse me for my ignorance how can I reduce the number of inputs with electrum (or control them)

Go to "Coins" tab. (If the "coins" tab is not available, click on "View at top of the window and select "Show coins".)

Select the coins you want to spend using Ctrl and Shift buttons and after that right-click and select "Spend".
Now if you go to "send" tab, electrum will only spend selected UTXOs.

The other way is to right-click on the coins you don't want to spend and select "Freeze".

spencericassidy

newbie

Activity: 3

Merit: 4

Quote from: nc50lc on October 05, 2021, 08:34:42 AM

Quote from: spencericassidy on October 05, 2021, 07:47:18 AM

Thank you for your response.
I'm still getting an error even after restoring both 2 wallets (the multisig wallet and co-sign wallet) I'm getting this error on electrum

The server returned an error when broadcasting the transaction.
Consider trying to connect to a different server, or updating Electrum.

The transaction was rejected because it is too large (in bytes).

How can I use the another option you metioned.

Okay, now that's unrelated to the previous issue and not limited to Electrum,
the error: "The transaction was rejected because it is too large (in bytes)" is because of Bitcoin's "standard rule".

Your transaction must have reached the maximum standard transaction size of 400,000 Weight or 100kvB (virtual kilobytes).
You'll have to reduce the number of inputs in order to create a transaction that can be broadcast successfully.
The expensive workaround is to ask a pool or solo miner to directly include your transaction to the blocks that they're mining.

Source Code: https://github.com/bitcoin/bitcoin/blob/master/src/policy/policy.h#L23-L24

Excuse me for my ignorance how can I reduce the number of inputs with electrum (or control them)

nc50lc

legendary

Activity: 2618

Merit: 6452

Self-proclaimed Genius

Quote from: spencericassidy on October 05, 2021, 07:47:18 AM

Thank you for your response.
I'm still getting an error even after restoring both 2 wallets (the multisig wallet and co-sign wallet) I'm getting this error on electrum

The server returned an error when broadcasting the transaction.
Consider trying to connect to a different server, or updating Electrum.

The transaction was rejected because it is too large (in bytes).

How can I use the another option you metioned.

Okay, now that's unrelated to the previous issue and not limited to Electrum,
the error: "The transaction was rejected because it is too large (in bytes)" is because of Bitcoin's "standard rule".

Your transaction must have reached the maximum standard transaction size of 400,000 Weight or 100kvB (virtual kilobytes).
You'll have to reduce the number of inputs in order to create a transaction that can be broadcast successfully.
The expensive workaround is to ask a pool or solo miner to directly include your transaction to the blocks that they're mining.

Source Code: https://github.com/bitcoin/bitcoin/blob/master/src/policy/policy.h#L23-L24

spencericassidy

newbie

Activity: 3

Merit: 4

Quote from: nc50lc on October 03, 2021, 10:34:35 PM

After version 4.0.1, electrum dropped support for the old export format and use "psbt" similar to Bitcoin Core.
Here's the release notes: https://github.com/spesmilo/electrum/blob/master/RELEASE-NOTES#L302-L306
The solution is also written there - all co-signers should have the same version or at least v4.0.1

Quote from: spencericassidy on October 03, 2021, 12:00:37 PM

there is any solution or workaround for this problem?

If the raw transaction came from other source that outputs raw transactions in hex.
You can try to convert it into psbt through Bitcoin Core using the command: converttopsbt "raw_transaction", the output should be compatible with the latest version of Electrum. It could fail depending on the encoding of the raw txn.
Note: you wont need the blockchain to use the command, just install, open Bitcoin Core then go to 'Window->Console' or use cli.

Thank you for your response.
I'm still getting an error even after restoring both 2 wallets (the multisig wallet and co-sign wallet) I'm getting this error on electrum

The server returned an error when broadcasting the transaction.
Consider trying to connect to a different server, or updating Electrum.

The transaction was rejected because it is too large (in bytes).

How can I use the another option you metioned.

Ty

HCP

legendary

Activity: 2086

Merit: 4363

Quote from: spencericassidy on October 03, 2021, 12:00:37 PM

now that I can't open wallets on version 3.X (I'm getting error that the version is too old) I can't sign the transactions.

Electrum wallet files have a built in "version" number. When modifications are made to the wallet file format (adding/removing fields etc), Electrum "upgrades" this wallet file version and once your wallet file is "upgraded", you can't open it in a lower version of the application.

This is the reason why you are getting the "version is too old" error message. Your wallet file was opened in a newer version of Electrum and has been updated. The only way back would be to use an old backup copy of the wallet file, or to recreate the wallet in an older version of Electrum using your seed.

nc50lc

legendary

Activity: 2618

Merit: 6452

Self-proclaimed Genius

After version 4.0.1, electrum dropped support for the old export format and use "psbt" similar to Bitcoin Core.
Here's the release notes: https://github.com/spesmilo/electrum/blob/master/RELEASE-NOTES#L302-L306
The solution is also written there - all co-signers should have the same version or at least v4.0.1

Quote from: spencericassidy on October 03, 2021, 12:00:37 PM

there is any solution or workaround for this problem?

If the raw transaction came from other source that outputs raw transactions in hex.
You can try to convert it into psbt through Bitcoin Core using the command: converttopsbt "raw_transaction", the output should be compatible with the latest version of Electrum. It could fail depending on the encoding of the raw txn.
Note: you wont need the blockchain to use the command, just install, open Bitcoin Core then go to 'Window->Console' or use cli.

Pmalek

legendary

Activity: 2730

Merit: 7065

What transaction files are you exporting exactly?
You need to import the required amount of master private keys. I assume you have those and you are the only person with access to that wallet so you don't the master public keys of other co-signers.

spencericassidy

newbie

Activity: 3

Merit: 4

Hi,
I create a bitcoin wallet with electrum 3.X.
while I could open this wallet (both the multisig wallet and the other wallet that I could sign with) I could sign transactions.

now that I can't open wallets on version 3.X (I'm getting error that the version is too old) I can't sign the transactions.

I'm exporting the transaction files and then trying to sign them but it wont let me sign on electrum 4.X

there is any solution or workaround for this problem?

Topic: Can't sign multisig wallet transaction (Read 231 times)