Somewhat confusingly... the links on the "download" page still link to version v3.0.3 downloads!!?!

For the record, the v3.0.5 downloads are here: https://download.electrum.org/3.0.5/

Seems, like my chrome is "broken", or my ISP is caching stuff again to be "helpful"... *sigh*...

Because Electrum "2FA" wallets do not use SegWit... they are simply a type of MultiSignature (aka "MultiSig") wallet... that utilises the services of TrustedCoin's Google Authenticator system to provide Two Factor Authentication security for your wallet.

Just because *some* "3"-type addresses are SegWit... does not mean ALL "3"-type addresses are SegWit addresses... It is impossible to tell what type of address a "3"-type address is, unless you know it's redeemscript.



Already fix what? Are you asking about the "bug" that was recently discovered? If so, go start a thread of your own instead of hijacking a completely unrelated thread

But to answer your question, the bug is an issue with the application... NOT the wallet file or format. If you upgrade to the latest version and have a wallet password set, your wallet is relatively safe.

I was just explaining my setup... so people could understand how I have everything configured...

- When I installed Bitcoin Core using the Windows installer, it installed the application itself to "C:\Program Files\Bitcoin"... ie. this is where bitcoin-qt.exe is
- When I ran it the first time, it asked where I wanted the block data stored... I keep it on a different disk... in E:\Bitcoin... ie. this is where my wallet.dat and "blocks" folder are

Inside the E:\Bitcoin folder... I use "bitcoin.conf" file, so I don't have to run bitcoin-qt.exe with arguments like -server=1 or -walletrbf=1... it is specified in the bitcoin.conf file (this is just a text file... and the FULL contents of that file, when opened in a text editor are:


This setup works for ME... I have no idea if it will work for anyone else... but I tried for days to get Bitcoin Core and Armory talking to each other (with the Bitcoin Core GUI running)... and all I ever got was the "Purple" 'connected' (that doesn't update new blocks)... or the "Node Offline" status...

The video was created using the older v2.9.3 version of Electrum. However, the import options were (silently) changed in the latest v3.x version of Electrum. As such, the options specified in the video only allow import of "Master" private keys (aka "xprv's") in the latest versions of Electrum... you cannot import single "WIF" format keys (the ones you get from MultiBit Classic) that start with "5", "L" or "K"

for v2.9.3, to import WIF keys you use: "Standard Wallet" -> "Use Public or Private Keys"
for v3.x, to import WIF keys you use: "Import Bitcoin Address or private keys"

Was it Freewallet? If so, try submitting a ticket to their support here: https://freewallet.freshdesk.com/support/tickets/new

They also appear to have a "chat" facility in their mobile apps.

Otherwise, what wallet were you receiving the funds to?

So not an "obvious" scam address like some of the "clipboard" viruses, or you were the first victim.

Quite... it would indeed appear that it is a deliberate modification to the QR Code. I have previously seen other users on here claim that they've "scanned QR Codes" but somehow the address they sent to was the wrong one. Perhaps this QR Code modification is a less used, more subtle and better disguised scam?

In any case, it would appear that maybe the "blind trust" that people seem to have in QR Codes (myself included) is somewhat misplaced. Indeed a valuable lesson for everyone, unfortunately, at your expense.

No. You wouldn't necessarily get a different private key (the HW wallets use this fact for claiming "fork" coins, see belwo)  So, in actuality, some of the coins CAN have the same private key... private keys are generally just very large numbers. We might be used to looking at them in slightly different forms like:
BTC: KzQdYqDHhCKNkjdr5kSCP5WJURbEq22BKa3kaVLVh6K9mD4iszXB
ETH: 0x82145ea7c90faa066109fafbfdec363adc30cf8827549daab096fd5f43d9057b
XRP: 61c2967ecd1fdc5e4c9070d9884e40b7084acc32cb9b1f85e0e40972db99b043

etc... but at the end of the day... they all convert back into numbers.

If you go here: https://iancoleman.io/bip39/ and generate a random seed... Click the "BIP44" tab... and then change the "Coin" value at the top, you can get a firsthand demonstration of how a hardware wallet is able to generate all the different keys/addresses for the different coins.

You'll notice that the "Derivation Path" changes... specifically... the "coin" value:

BTC: m/44'/0'/0'/0/0
EHT: m/44'/60'/0'/0/0
XRP: m/44'/144'/0'/0/0

This enables the wallet to generate different private keys/addresses for each coin... it is also what allows the hardware wallets to easily "claim" coins from Bitcoin forks... by simply using the BTC derivation path, but for a "BCH" or "BTG" wallet, they can generate the SAME private keys/addresses and get access to the forked coins!

To demonstrate... note down the private key/address for BTC:

Example seed: execute blouse test blast average detail polar slide measure warm little man
BTC:
Address Path: m/44'/0'/0'/0/0
Address: 1Yn6AeqnE2eJT23VzB1yHpbytcXNCveoK
Pubkey: 03db0ff63c62d27f9f0e0547661c4692a3dd4ee098145056fc2da9df3a25d288c1
Privkey: KzQdYqDHhCKNkjdr5kSCP5WJURbEq22BKa3kaVLVh6K9mD4iszXB

Now, click BCH... but click BIP32 tab, and set Client to "custom" and Derivation Path to m/44'/0'/0'/0 (this is simulating a hardware wallet "claiming" fork coins):

Address Path: m/44'/0'/0'/0/0
Address: 1Yn6AeqnE2eJT23VzB1yHpbytcXNCveoK
Pubkey: 03db0ff63c62d27f9f0e0547661c4692a3dd4ee098145056fc2da9df3a25d288c1
Privkey: KzQdYqDHhCKNkjdr5kSCP5WJURbEq22BKa3kaVLVh6K9mD4iszXB


IDENTICAL! Now set the coin to "ETH" (still with BIP32, custom client and m/44'/0'/0'/0 derivation path):

Address Path: m/44'/0'/0'/0/0
Address: 0x16924278d8897F1dCAD81717F517A1F3c3b633f6
Pubkey: 0x03db0ff63c62d27f9f0e0547661c4692a3dd4ee098145056fc2da9df3a25d288c1
Privkey: 0x5f2140e2517fa4f496f40b46c8d6b07c39d2e912dd951ba00f6b0642401a6c47

Notice the pubkey... it's the same "big number"!!?! And if we put the BTC "WIF" privkey into https://www.bitaddress.org (click "wallet details")... we can see that:

The privkey is the SAME as the ETH privkey!!?! #funWithCrypto


They don't store anything, anywhere... that recovery seed is the start point for ALL the wallets for ALL the coins... they simply use different derivation paths to get the private keys/addresses for the different coins.

The original transaction (coinsquare to b.info) is still unconfirmed... so the 2nd transaction (b.info to coinsquare) cannot confirm until the first one does...

I'm not sure why you sent it back? All you've managed to do is spend 0.0013+ BTC in transaction fees across two transactions...

Bitpay recently tried to introduce a minimum $100.00 amount to orders processed through them... at least, they tried for eGifter.com... then seemed to backtrack on that a day or two later (I assume because of a massive backlash from customers and vendors)...

You need to talk to your Vendor and find out where your Bitcoins are... they're either with the Payment Processor (most likely scenario) or the payment processor forwarded the payment to the Vendor less likely, as apparently the Payment Processor "rejected" the transaction... which isn't actually possible by the way, you can't stop bitcoins coming into your address

If the seed was originally from Bread Wallet... and you restored it to Bread Wallet, there should be no reason why it didn't show your balance... the only thing I can think of is that either:

a. The wallet had NOT synced properly (Last time I checked Bread wallet, it took quite a while to sync newly restored wallets)
b. The seed you have written down is NOT the seed for the wallet that had your BTC
c. The developer changed the way the app works since you created your seed (not likely)

Also, if you are going to import your Breadwallet seed into Electrum, you need to know that Breadwallet does NOT use the default BIP44 "derivation path"... when prompted during wallet creation in Electrum... do NOT use m/44'/0'/0'... instead, change it to m/0'

NOTE that the ' (apostrophe) at the end is VERY important... m/0'

Then it sounds like you've created a MultiSig... or a Two-Factor Authentication (2FA) wallet...

In the title bar, what does it say in [ ]'s after the wallet name? Does it say [2fa] or does it say something like [2of3]?

NOTE: Neither of these wallet types is "SegWit"

Are you running on Windows 10? I had all sorts of weird issues getting Armory and Bitcoin Core to run together... the ONLY solution I found that worked for me is documented here: https://bitcointalk.org/index.php?topic=2200306.msg22126330#msg22126330

For whatever reason, for MY setup, having the GUI open and trying to run Armory results in "Node Offline" (but correct number of blocks)

If I have the GUI shutdown, let Armory run bitcoind (with the bitcoin.conf settings that I have)... it all works fine??!?

It depends... I work shifts... so my "online" time is an always changing window



NOTE: Deleting/Uninstalling the program won't remove the wallet files (safety feature to prevent accidental wallet file loss  You'll need to manually track down the wallet file and delete it (http://docs.electrum.org/en/latest/faq.html#where-is-my-wallet-file-located)


Also, as for the ludicrously large numbers (1250 "BTC" and 499 "BTC")... Electrum, by default, shows wallet values as "milliBitcoins" or mBTC... you should try using "Tools -> Preferences -> Appearance" and change the units to BTC (unless you happen to like mBTC... which I absolutely HATE )... note that after you change to BTC, to set the number of "zeros after the decimal point" to the full "8", you need to close the preferences window, and then re-open it.



Thanks guys... just trying to help out fellow BCTalkers

ps. LoyceV was on the money with the answers

In theory, no more than any other vulnerability/virus/malware... if the system with the private keys/seed is running on an offline system, then the opportunity for "leaks" is pretty minimal... there ARE still attack vectors (compromised USB key etc), so it would probably be prudent to update.

Additionally, the "vulnerable" Electrum on your online computer, could still leak "private" data like your addresses/wallet info etc. (as opposed to "sensitive" data like the private keys/seed)

As mentioned (several times), the only way you will be able to transfer those coins is if you have the private key...

Where/how did you get the address 1Dv23Ci4ys7VF8UsmJi2EM6Utvmq5jhp9c?

In short... yes, if they moved their coins to the 2FA wallet AFTER the fork, then their old, original "Standard" seed would allow them to get the private key. Note that with a Standard Electrum wallet, you don't even need to use the seed+BIP39 tool, you can just goto the "Addresses" tab ("View -> Show Addresses"), right click on the address you are interested in and select "Private Key"


You don't "convert" to 2FA as such... you generate a completely new wallet with a completely new seed... and then send all your coins to the new 2FA wallet... so yes, you are correct, the 2FA wallet will indeed have a new seed mnemonic and entirely new sets of key pairs.

Two things spring to mind on this...

1. Malware on iOS (while not unheard of) is relatively rare
2. The iOS settings/instructions for Mycelium Gear (website payment processor) actually generates different addresses to the iOS wallet itself (derivation path issue)

I'm wondering if the QR Code generator in Mycelium iOS is having the same issue? Perhaps it is generating an address from the right xpub, but using the wrong derivation path? Or was it obviously a "scam address" with a lot of transactions in/out?

You seem to be a bit confused regarding wallet names

1) For BTC, you want Electrum... I'd recommend v3.0.3... available here: https://electrum.org/#download
2) For BCH, you want ElectronCash... I'd recommend v3.1... available here: https://electroncash.org/#download
3) For BTG, the only real wallet I can recommend is BitcoinGold Core... available here: https://bitcoingold.org/downloads/ (NOTE: requires FULL blockchain download)

There is no "lightweight" wallet that I know of for BTG that I would consider "trust worthy"... there certainly isn't an "Electrum" fork like ElectronCash etc.. There is the option of using Coinomi (requires Android, although, theoretically, you could install the BlueStacks Android Emulator on Windows and use Coinomi there).

For 1) and 2)... I *HIGHLY* recommend that you check the digital signatures for the downloaded wallet installers BEFORE running/using them... there are a LOT of fake websites that look IDENTICAL to Electrum and ElectronCash websites and it is VERY easy to download a fake wallet that will steal your coins.



As for the actual process, it would be fairly easy... simply import your MultiBit HD seed into Electrum, move your BTC to a new wallet... then import your MultiBit HD seed into Electron Cash... move the BCH to a new BCH wallet... finally, you would need to either import your seed into Coinomi to get BTG... or use https://iancoleman.io/bip39/ along with MultiBitHD seed to get the private keys to import into BTG Core.

HitBTC have basically screwed everyone involved in those 3 transactions (and no doubt in the following transaction) by doing a PayToMany with such a low fee (no doubt collecting a nice amount of fixed withdrawal fees from all the users while they were at it)... and then using unconfirmed UTXO's as inputs to subsequent transactions.

Your chances of being able to accelerate this are fairly minimal. The original transaction is 10K, the next one is 6K and the one with your withdrawal is 2.8K... the CPFP required to get those transactions pushed through will be HUGE.

You'll just have to keep trying with ViaBTC and work on this one first: d3652ae16e696c140d53ae3a080f8744ec23e7ce8077f1461f62cff8e7ad1257

Once that is accelerated AND confirmed, then move onto the 2nd one... and then your one.

Theoretically, it should be possible to modify the seed_recovery tool to generate SegWit addresses to test against... the algorithm for creation of P2SH-P2WPKH addresses is fairly straight forward (https://bitcoincore.org/en/segwit_wallet_dev/#creation-of-p2sh-p2wpkh-address)