Topic: Can I remove multisig function from wallet? - page 2. (Read 1195 times)
I have trouble understanding you. Maybe ask someone who is fluent in English to post on your behalf?
This is all very confusing. Only thing I can say is that the last co-signer of a 2fa wallet is usually trusted coin so you won't get the xprv of cosigner 3 if that's what you need.
Once you've completed, you should be able to use: "Wallet -> Master Public Keys" and you should see CoSigner 1, 2 and 3
And when restored with the original 2FA on Google Authenticator ( I remembered this eventually) I get the correct cosign 1.
(I had not remembered first of all which email that I used for Google 2FA, setting up another, with new email address, but this produced NO correct xpub keys i.e. all were new)
So,
In the latest attempt I have:-
Mac wallet type (2FA)
cosig 1 ....... xpub67z ...etc
cosig 2 .......
cosig 3 .......
Where, Linux wallet is:-
x1/self ............ xpub661 ...etc
x2/cosigner .... xpub67z ...etc
I think I need the xpub661 ...F etc shown in the restored Mac wallet using the multisig choice (not 2FA)using xpub from my Linux Ubuntu wallet.
As seen in this one I had created: wallet type (1of2)
cosig 1: .....
cosig 2: ..... xpub661 ...F etc
Basically... you want to do:
1. File -> New\Restore (Pick a name)
2. Select - "Wallet with Two Factor Authentication" (option 2)
3. Select - "I already have a seed"
4. Enter your seed (it should say "Seed Type: 2fa", next to "Options" button)
5. Select - "Keep"
6. After clicking "Next" a couple of times, enter the email you originally used
7. Either put in your GAuth Code... or tick the "I have lost my Google Authenticator Account" box and keep going.
Once you've completed, you should be able to use: "Wallet -> Master Public Keys" and you should see CoSigner 1, 2 and 3
1. File -> New\Restore (Pick a name)
2. Select - "Wallet with Two Factor Authentication" (option 2)
3. Select - "I already have a seed"
4. Enter your seed (it should say "Seed Type: 2fa", next to "Options" button)
5. Select - "Keep"
6. After clicking "Next" a couple of times, enter the email you originally used
7. Either put in your GAuth Code... or tick the "I have lost my Google Authenticator Account" box and keep going.
Once you've completed, you should be able to use: "Wallet -> Master Public Keys" and you should see CoSigner 1, 2 and 3
Have you tried restoring your 2FA wallet with the 2FA seed and "Keep"ing the 2FA functionality... rather than "Disable"? After it is restored, checking what xpubs it has... see if any of the three xpubs in the 2FA wallet are "xpub67z"
Yes I have the original word seed from the Mac. I need to be clearer on what I should do to set up the wallet. I get a little confused still when it is a 2FA, or multi sig wallet - for isntance how many cosigs to have.
So, if there are any (more) steps I must follow , like >"Keep"ing the 2FA functionality< please let me know> I will then give it a go.
That's unfortunate... you need the seed/private key that matches that xpub... without it, you will not be able to co-sign any transactions from your Linux wallet...
Have you tried restoring your 2FA wallet with the 2FA seed and "Keep"ing the 2FA functionality... rather than "Disable"? After it is restored, checking what xpubs it has... see if any of the three xpubs in the 2FA wallet are "xpub67z"
Have you tried restoring your 2FA wallet with the 2FA seed and "Keep"ing the 2FA functionality... rather than "Disable"? After it is restored, checking what xpubs it has... see if any of the three xpubs in the 2FA wallet are "xpub67z"
These are all the wallets on the Mac.
As I said it was trial and mostly error. This last wallet in my list was probably made using the expub key, copied from the Linux wallet.
As I said it was trial and mostly error. This last wallet in my list was probably made using the expub key, copied from the Linux wallet.
The one you really need to find is the EXACT copy of the "xpub67z" co-signer from the Linux wallet.
That last one... the wallet type (std, watching only)... xpub67z... is that the EXACT same xpub as reported by the Linux wallet? If so, how did you create that wallet?
That last one... the wallet type (std, watching only)... xpub67z... is that the EXACT same xpub as reported by the Linux wallet? If so, how did you create that wallet?
Thank you HCP.
Yes I do have other wallets on the Mac frOm having tried to restore one that might work. They are all unrelated, when I choose to load a tx from the Linux wallet. (Regardless whether I open the old or new version of Electrum, that's fine, I can bring up all wallets through OPEN on the Mac
Yesterday I tried to focus and look through them all to see the MPK links between the two computer's wallets.
The Linux wallet, althuogh does not show in the boarder the type of wallet, eg '2fa', '1of2' etc. But when I drop down the MPK from menu, I do see this
x1/self ............ xpub661 ...etc
x2/cosigner .... xpub67z ...etc
In my attempts to create/restore these wallets on the Mac, I have failed, and produced only the following, all unrelated:-
wallet type (1of2)
cosig 1: .....new xpub6Br...etc
cosig 2: ..... xpub661 ...etc
wallet types (std) and (std, watching only)
... xpub661 ...etc
wallet type (1of2, watching only)
cosig 1 ....... xpub67z ...etc
cosig 2 .......new xpub69Y...etc
wallet type (std, watching only)
.... xpub67z ...etc
I'm now thinking, what exactly are the right steps for the new wallet - I clearly don't want thexpub keys marked
Yes I do have other wallets on the Mac frOm having tried to restore one that might work. They are all unrelated, when I choose to load a tx from the Linux wallet. (Regardless whether I open the old or new version of Electrum, that's fine, I can bring up all wallets through OPEN on the Mac
Yesterday I tried to focus and look through them all to see the MPK links between the two computer's wallets.
The Linux wallet, althuogh does not show in the boarder the type of wallet, eg '2fa', '1of2' etc. But when I drop down the MPK from menu, I do see this
x1/self ............ xpub661 ...etc
x2/cosigner .... xpub67z ...etc
In my attempts to create/restore these wallets on the Mac, I have failed, and produced only the following, all unrelated:-
wallet type (1of2)
cosig 1: .....
cosig 2: ..... xpub661 ...etc
wallet types (std) and (std, watching only)
... xpub661 ...etc
wallet type (1of2, watching only)
cosig 1 ....... xpub67z ...etc
cosig 2 ......
wallet type (std, watching only)
.... xpub67z ...etc
I'm now thinking, what exactly are the right steps for the new wallet - I clearly don't want the
Ok... so it seems to me, that the issue here is that you are unable to recreate a wallet that has the private key(s) to be able to sign transactions created by your Linux wallet.
With 2.9.3 on Linux, you should be able to use the following menu option: "Wallet" -> "Master Public Keys"
You should see a window popup with a list of all the Master Public Keys. I assume there are only 2... "co-signer 1" (The Linux wallet) and "co-signer 2" (which should be the Mac wallet). is that correct?
The trick is to identify which seed/wallet that the MPK came from... once you do that, you'll be able to use that wallet to sign the Linux transactions. Are you sure you don't have any other wallets (non 2FA) on your Mac? Have you tried clicking "Open" and see if any other wallet files are listed?
With 2.9.3 on Linux, you should be able to use the following menu option: "Wallet" -> "Master Public Keys"
You should see a window popup with a list of all the Master Public Keys. I assume there are only 2... "co-signer 1" (The Linux wallet) and "co-signer 2" (which should be the Mac wallet). is that correct?
The trick is to identify which seed/wallet that the MPK came from... once you do that, you'll be able to use that wallet to sign the Linux transactions. Are you sure you don't have any other wallets (non 2FA) on your Mac? Have you tried clicking "Open" and see if any other wallet files are listed?
2.6.4 - Yes, it is the propriety Lite version that comes with Ubuntu Store. I have since used Python to install another wallet* 2.9.3 which seems to be the latest available for Linux on the Electrum website
Quote
HCP:
I suspect that you had the the "co-signer pool" plugin loaded and running... this plugin sends the transaction to a central Electrum server waiting for the co-signer to open their wallet and automagically sends them the transaction to sign.
.. when you setup the Linux wallet, was that setup as 2FA as well?
I suspect that you had the the "co-signer pool" plugin loaded and running... this plugin sends the transaction to a central Electrum server waiting for the co-signer to open their wallet and automagically sends them the transaction to sign.
.. when you setup the Linux wallet, was that setup as 2FA as well?
-Just as a "normal" MultiSig wallet on the Linux. No 2FA,
In fact the Mac wallet required Google Authn, at some point, but I recall never having been asked to use it - I thought it was just to log in with nothing more. It's definitely something I started with, since it is there in Google Authn on my phone. I don't recall using it again, perhaps it wasn't set up right, so maybe we should ignore that.
*In attempts to find a remedy, I tried to create a wallet from my word seed in on my Linux PC. Nothing shows (just a zero balance) - no inputs.
Going back to the 2.5.4 wallet (the original one), I cannot see any further info to help matters. Am I in the wrong pool? I am connecting with the automatic connection.
All the tile says is that it is Electrum 2.6.4
2.6.4?? That is quite old... is that the version on Linux or Mac?Quote
HCP:
I recall setting up the co-sig as the Mac Wallet with MPK, I either sent a test amount to myself from Linux to Mac, or it was to an exchange (I can't remember) but upon opening the Mac Wallet (which leads me to believe that first test was to myself and I went into the wallet on the Mac to see), I was immediately asked to sign the transaction, it just popped up to do.
That initial test did not require the save transaction process, and loading in the other wallet.
I suspect that you had the the "co-signer pool" plugin loaded and running... this plugin sends the transaction to a central Electrum server waiting for the co-signer to open their wallet and automagically sends them the transaction to sign.I recall setting up the co-sig as the Mac Wallet with MPK, I either sent a test amount to myself from Linux to Mac, or it was to an exchange (I can't remember) but upon opening the Mac Wallet (which leads me to believe that first test was to myself and I went into the wallet on the Mac to see), I was immediately asked to sign the transaction, it just popped up to do.
That initial test did not require the save transaction process, and loading in the other wallet.
To be honest, I'm still struggling with the idea of using a MPK from a 2FA wallet as a co-signer for a completely different MultiSig wallet... when you setup the Linux wallet, was that setup as 2FA as well? Or just as a "normal" MultiSig wallet?
Abdussamad:
All the tile says is that it is Electrum 2.6.4
HCP:
I recall setting up the co-sig as the Mac Wallet with MPK, I either sent a test amount to myself from Linux to Mac, or it was to an exchange (I can't remember) but upon opening the Mac Wallet (which leads me to believe that first test was to myself and I went into the wallet on the Mac to see), I was immediately asked to sign the transaction, it just popped up to do.
That initial test did not require the save transaction process, and loading in the other wallet.
All the tile says is that it is Electrum 2.6.4
HCP:
I recall setting up the co-sig as the Mac Wallet with MPK, I either sent a test amount to myself from Linux to Mac, or it was to an exchange (I can't remember) but upon opening the Mac Wallet (which leads me to believe that first test was to myself and I went into the wallet on the Mac to see), I was immediately asked to sign the transaction, it just popped up to do.
That initial test did not require the save transaction process, and loading in the other wallet.
Then the real question is how did you set up the Linux wallet in the first place? It would appear that it is a MultiSig, as it is only "partially" signing the transaction. The question is, what Master Public Key did you use as the co-signer?
I had made a previous successful transfer of BTC from Linux to Mac to check it was all working. It was, there came up in the Mac wallet automatically the transaction to counter sign. I had not even been made aware then of the use of loading a saved transaction as I hadn't needed it.
Your previous transfer of BTC from Linux to Mac... did you just send to the address that the Mac was displaying under "receive" and the BTC came up in the Mac wallet? Or did you actually create a partially signed transaction and then transfer that to the Mac and then sign and broadcast from the Mac?
the wallet type is mentioned in the electrum window title. tell us what it says there for the wallet with the bitcoins in it.
When I first set up 2FA on the Mac it was with Google Authenticator 2FA to open the wallet.
I cannot remember every step I took to set up this original Mac wallet but I stored pertinent info, just in case... eg seed (plus extension), master public key
I had made a previous successful transfer of BTC from Linux to Mac to check it was all working. It was, there came up in the Mac wallet automatically the transaction to counter sign. I had not even been made aware then of the use of loading a saved transaction as I hadn't needed it.
I subsequently send before the first BTc fork funds to the Linux wallet and just recently returned to the Linux wallet to move them to the Mac wallet and encountered this problem. I think I have gone to the new version in this time.
I cannot remember every step I took to set up this original Mac wallet but I stored pertinent info, just in case... eg seed (plus extension), master public key
I had made a previous successful transfer of BTC from Linux to Mac to check it was all working. It was, there came up in the Mac wallet automatically the transaction to counter sign. I had not even been made aware then of the use of loading a saved transaction as I hadn't needed it.
I subsequently send before the first BTc fork funds to the Linux wallet and just recently returned to the Linux wallet to move them to the Mac wallet and encountered this problem. I think I have gone to the new version in this time.
Anyhow, I '' .....restored from seed, and it contains two master private keys. Therefore, two-factor authentication is disabled. ''
Wait... you're trying to use a 2FA wallet as a cosigner to another MultiSig wallet? 
I'm very confused... That is like effectively like using an (already created) MultiSig wallet as a co-signer to another MultiSig wallet... Is that even possible? The normal process is:
- Start creating Electrum MultiSig1 wallet on computer1 (Linux) - Save the seed1, get the xpub1
- It will ask for the xpub for your co-signer
- Start creating Electrum MultiSig2 wallet on computer2 (Mac) - Save the seed2, get the xpub2
- It will ask for the xpub for your co-signer
At this point, you put xpub2 (from Mac) into MultiSig1 wallet (Linux)... and xpub1 (from Linux) into MultiSig2 wallet (Mac). This should then finished generating MultiSig wallets on both Linux and Mac that have the same addresses etc.
However, you seem to have originally created a 2FA wallet on you Mac?
Can you please explain how you originally setup your two MultiSig wallets on the Linux wallet and Mac wallet?
Thank you HCP.
I downloaded and installed Electrum 2.9.2, having had originally Electrum.2.8.3.
In fact I had an issue at the time of the new wallet (2.9.2) not connecting. I wrote here (last entry) https://github.com/spesmilo/electrum/issues/2726
I cannot now remember what I did to the old version, whether I deleted it and re-installed it... when I had a connection problem for instance.
Anyhow, I '' .....restored from seed, and it contains two master private keys. Therefore, two-factor authentication is disabled. ''
Perhaps this did something to the old version? I have tried, just a few days ago to use Time Machine, to go back to the old version as it was before I installed the newer one. But still have the problem.
With both versions of the wallet, when I load the transaction I wish to sign this is how it looks:
Transaction ID ...unknown
Status.... partially signed (3/6)
Amount received.....xxx mBTC
Size.....822 bytes
Fee ...unknown
Inputs....3
[Box] three inputs infront of the Linux address
Outputs...(1)
Address highlight of the recipient followed by amount xxx
Copy QR Save xSign (..is not available) xBroadcast (..is not available) Close
I downloaded and installed Electrum 2.9.2, having had originally Electrum.2.8.3.
In fact I had an issue at the time of the new wallet (2.9.2) not connecting. I wrote here (last entry) https://github.com/spesmilo/electrum/issues/2726
I cannot now remember what I did to the old version, whether I deleted it and re-installed it... when I had a connection problem for instance.
Anyhow, I '' .....restored from seed, and it contains two master private keys. Therefore, two-factor authentication is disabled. ''
Perhaps this did something to the old version? I have tried, just a few days ago to use Time Machine, to go back to the old version as it was before I installed the newer one. But still have the problem.
With both versions of the wallet, when I load the transaction I wish to sign this is how it looks:
Transaction ID ...unknown
Status.... partially signed (3/6)
Amount received.....xxx mBTC
Size.....822 bytes
Fee ...unknown
Inputs....3
[Box] three inputs infront of the Linux address
Outputs...(1)
Address highlight of the recipient followed by amount xxx
Copy QR Save xSign (..is not available) xBroadcast (..is not available) Close
Restoring your Mac wallet from word seed should have recreated an identical wallet on the Mac... that would have identical xpub/xpriv to the original wallet.
When you say you "upgraded your mac wallet", what exactly did you upgrade and how? Did you install a newer version of Electrum? Or did you install a completely different wallet app?
When you say you "upgraded your mac wallet", what exactly did you upgrade and how? Did you install a newer version of Electrum? Or did you install a completely different wallet app?
I upgraded my Mac wallet and seem to have a new Bitcoin address and private key. Although I used my word seen to restore the old wallet, the old address and private key is not there.
To restore your original multisig wallet, you have to restore it by putting in the xpub (master public keys) of all the co-signers. If you don't, the seed that you used will be considered as a normal address.Thank you for your reply. I am not sure this will help, since I did not store the Master Public keys, for the Mac wallet used to co-sign the Linux wallet. Just the word seed
Jump to: