What people need to realise is that if a hard fork occurs... you are NOT going to lose your coins if you have access to your private keys.

If you have your private keys, you can import them into "LeftForkWallet"™ and get access to the "LeftForkCoins"™... and/or put them in the "RightForkWallet"™ and get access to the "RightForkCoins"™.

The only people who should be nervous are people who have their coins stored in Online Services like gambling sites, exchanges and a number of web wallets like Xapo and Coinbase etc where you do NOT have access to the private keys or the seed/mnemonic used to restore the wallet. In those instances, your coins are effectively just a number in a database  somewhere... the service holds the keys and will end up deciding which fork to follow... left, right or both... and how they want to give you those coins... or not give you

as I posted in another thread:

If the seed was created in Electrum, then you shouldn't use the BIP39 option when restoring your account.

If you end up with a zero balance when restoring, then you either have the wrong seed... or your addresses containing coins are beyond the "gap-limit". By default, Electrum will stop looking once it finds 20 unused addresses. If you goto the console and try:


It will generate the next 50 addresses in your wallet... It might be worth trying that to see if you find anything.

Just to confirm, with the seed you are using, you are not finding ANY history right? There are no transactions showing? If that is the case, I'd probably guess that your seed is wrong.

Well, that is the minimum reward, assuming you make 20 "constructive" posts per week. You can make more if you make more (constructive) posts. Up to the limit of 0.0075 btc (0.00015 x 50 maximum).

Best not to think of it in terms of $$$... the price could boost or dump... but 0.0075 btc will still be 0.0075 btc

Based on the fees being discussed, particularly the usage of the term "unloading" fee, it would appear to be some sort of "Virtual" Credit/Debit card service...

Cryptopay has very similar charges:

Which lines up nicely with the "1.99% Paypayl + 1% unloading +$0.10" fee that is discussed... not sure about the conversion and/or mining fee... but it also looks like the "redacted" part at the the top might say "the card"

Not sure that this IS Cryptopay... but I'd say that it is definitely a virtual card service of some description...

That bit looks like the actual failure point... quite why that hash check is failing will most likely require the full debug logs... seems like it might mean the OP has a corrupt block?

The only "non-standard" thing I can see from these Lykke transactions, is that they seem to be using the signature hash "ALL|ANYONECANPAY"... as opposed to the default "ALL"...

Whether this is just coincidental... or is causing the issue, I honestly couldn't say.




The only payments from a MultiSig that I have in Electrum wallets all seem to use just the default signature hash "ALL"... for instance:

You should be able to test for the so-called "clipboard virus" fairly easily... just copy a bitcoin address like this random one: 1Nr14VQZuYDVC1TmHUszDBdBhi39gAn4Cp

Try and paste it into a text editor or your webbrowser or whatever... and also try and paste it into coinbase like you are going to purchase coins just in case it is a coinbase specific hack as some chrome extension malware is known to target only bitcoin exchange websites... if it pastes a different address, then it is very likely your computer is infected.

If it ISN'T changing the address, then maybe you're not infected. When you were looking for your "previous" addresses... did you click "used" and see a warning dialog? If not, then you may not have actually seen ALL your addresses

First goto "Settings -> Security"... then click the "Manage" link under "My Bitcoin Wallet":



Then scroll all the way down until you see the "Used Addresses" section, click the "Show" link:



You'll get a warning popup... click "OK":



Now ALL your used addresses will show up:



If "1JqosveT62rZiPKDMZ49AjdqKRjMizSj8F" is NOT in this list... then you've somehow pasted in someone elses bitcoin address to Coinbase...

As for removal if your computer IS infected... maybe give malwarebytes a shot?

Just for the record... it appears that blockchain.info is using the "BIP44" Derivation Path (m/44'/0'/0'/0) to generate addresses... I just created an account... chucked the 12 word seed into the BIP39 Mnemonic page (https://iancoleman.github.io/bip39/) and the addresses match up when you leave the Derivation Path as "BIP44".

The good news is that this means you should be able to put this seed straight into a number of other clients like Mycelium to be able to recover your wallet. Even Electrum will let you "restore" this seed if you select "Options -> BIP39 Seed" when doing the seed input.

The most frustrating part about all this is that it would probably take less than 5 minutes to recover all of the coins... no password on a MultiBit Classic wallet means that with a simple python script, all the private keys can be dumped directly from one of the wallet files in the "wallet-unenc-backup" directory

However, I get the feeling that installing Python and using a command line based Python script is going to be way beyond the technical ability of the OP, given their obvious struggle with some computing basics like working Explorer and copy/paste. 

So, I have been experimenting with "pyinstaller" and "Tkinter" to create a standalone Python version of my script that extracts pubkeys and privkeys from MultiBit Classic .wallet files. I have even created a GUI for the script, so the user doesn't need to know or use the commandline... you just extract all the files from the .zip and run the .exe from Windows Explorer:



Then you use the dialog to select your wallet file (maybe copy your .wallet to the same directory as the script first):



Enter a password if the wallet has one (if you don't have a password, you won't be prompted):



If there was a password, you'll probably have to wait a little bit for the decryption process to complete:



Then it should dump out the Addresses and matching PrivKeys (it even autodetects if using compressed or uncompressed keys and outputs the appropriate PrivKey):



Credits: Christopher Gurnee (gurnec) and his BitcoinJ Seed Extractor... It should be fairly obvious that I've borrowed quite heavily from his script

The source code for the script (which can also be run from the commandline if required) is here: https://github.com/HardCorePawn/extract_mbc_keys
The zip package is here: https://github.com/HardCorePawn/extract_mbc_keys/raw/master/extract_mbc_keys.zip

---------------------------
Checksum information
---------------------------
Name: extract_mbc_keys.zip
Size: 7642347 bytes (7 MB)

CRC32: 6F21AE1E
CRC64: 8DD1D7666DCFA36A
SHA256: 938424AB82973B6D8C6B9E8E0FBA46EB52D72B290D526C0C7B3E1CEABFD02004
SHA1: D925BA360A87DF864CD719B98E42C0AD92715502
BLAKE2sp: 5912D39405FE05623465280F247BDCE568935042D9D149B9C62E7F734131EA59
MD5: 7d7edf7d7c0bceb300aef7628a004cd9
---------------------------

NOTES:

• Yes, I know distributing .exe's is not best practice... but if you read this thread from the start, you'll understand why I have chosen this solution.
• The source script is included in the github repository, so it can be peer reviewed and/or you can "compile" it yourself using pyinstaller.
• This package will ONLY work on Windows... it's just the way pyinstaller works... it was "compiled" on Windows, so it runs on Windows. If you want to compile it for Linux and/or MacOSX feel free... the source is there and pyinstaller apparently runs on Linux/MacOSX.

Close... more correctly it is X number of "unused" addresses, before it stops looking for coins. This means that an address that might be empty now but did at some time contain coins would still be counted, so the gap limit count would be reset and Electrum would continue searching.

So, the "danger" here with the "red" addresses... is that should you choose or need to restore your wallet for any reason, it will not automatically find the addresses in red... until you have used addresses in the gap which forces Electrum to then look X more addresses along the derivation path.

What is confusing is that it seems to occasionally marking them as red and sometimes not? is that correct? If so, it would seem that you must be hitting a malfunctioning server that is lagging... and not detecting a transaction in an earlier address, so it makes it seem like those addresses are beyond the gap limit... when in fact, due to this "missing" transaction, they are within the gap limit.

Yeah... same with 148 bytes for compressed address (or 180 bytes for uncompressed addresses)... generally it is 1 byte here or there for each component... so unless you have more than 10 inputs, the difference in calculated size should be less than 10 bytes.

Given the OP doesn't really seem to understand how bitcoin transaction sizes and fees are calculated... or that it is purely the number of Inputs used and Outputs created and NOT the number of "addresses" used, I didn't want to get overly complicated

You can take a look at my guide for getting the addresses and keys that you need to sign messages from 2FA accounts here: https://bitcointalk.org/index.php?topic=1989369.msg19853098#msg19853098

Please do take note of the security warnings... exposing your xprvs should not done lightly and proper precautions should be taken.

So you're saying that you shutdown, restarted and then it was OK?

If so, it could be that the "random" Electrum server you are connecting to when it comes up with red addresses is having some issues and is not fully synced. It will have nothing to do with "chains being forked" or anything like that.

Click the green light and check which server you are connected to when it isn't working properly... also check the number of blocks... the current block height is 473795, so if it isn't showing at least this number, then the server is having problems:

The addresses in red indicate that they are beyond the so-called "Gap Limit" of your wallet.

Is your Electrum wallet an HD "seeded" wallet... or was it an old style keystore that just generates random private/public keypairs?

Is the dot in the bottom right corner of the Electrum window green or red or do you see two blue arrows?


Green is connected and synced
Red indicates network problems
Blue arrows indicate syncing in progress

No offense, but why would you be running an online shop from your phone?

Honestly, I don't really see the issue with going into your bitcoin wallet app... and clicking "receive" and then "sharing" the address to another app via the builtin Android "share" functionality or using the clipboard and copy/pasting it wherever you need it to be input. I'm fairly sure that pretty much all Android wallets support this feature already.

I still don't quite understand why someone would need to be retrieving so many new addresses from within another app that it would be too much hassle to just manually copy/paste from the wallet app?

OP... are you attempting to use your phone as a POS (Point of Sale) device or something? If so, then perhaps there is a niche market opportunity here for someone to develop a phone based POS system that accepts bitcoin payments?

Ok... so as Muhammed has suggested, we will start at the beginning and step our way through the process to try and find where the issue is

So, first up... we'll check that your redeem script was created correctly. First of all, you should have found the correct "3" address in Electrum. You say it is now in your "used" section. So you would right click it and select "Public Keys":



That would then give you the popup window that shows the three public keys for your "3" address like this:


Note: they are most likely NOT in the correct order for generating your redeem script! They need to be in "lexicographic" order... this means you order them based on numbers AND characters... starting from the characters on the left.


In my case this results in them being in this order:

02e61b5030d21d2a520e19a22ce7180310d79c48f377a586d926fe38ff6f7df534
02e796ea85ac10b9c12a9b812982844b4b31c71c8a754b74c5213f9b0f7b6f456d
03341434abf31791a735e02ccc2cad2c1ddda85686545639b6f039c2317cd89125


You should have entered something similar to the following in the Electrum Console:


So using my public keys... I entered this:


Note that the "3" address here is the same as the "3" address that I got the public keys for. If this "3" address is NOT the same, then you have the public keys in the wrong order!


Now we put the redeem script into the Verify section at coinb.in:


Again, note that the "3" address here is the same as the "3" address from Electrum. If this "3" address is NOT the same, then your redeem script is wrong!

If your "3" address is the same as "3" address in Electrum, then everything is OK. Next we'll generate the xprv's to find the private keys for the three "1" addresses that match our redeem script public keys.

Sounds like you have a Stop condition set in the "Advanced" settings section. These settings are still "active" when in "Programmer" mode... so switch back to Advanced and make sure you dont have any stop conditions set that are causing it to stop (most likely a "stop if balance > xxx" etc)

Chances are that one of your block files is corrupted. Can you post your debug.log? (Preferably paste it to pastebin.com and provide a link)...

Alternatively, try shutting down Bitcoin Core and then running it with the -rescan option to force it to resync... note: this make take a while depending on your internet connection and/or PC hardware

blockchain.info web wallet is an HD wallet... like most HD wallets, after an address has been "used".. it will automatically generate a new address to help prevent address re-use. Do you have a record in your transaction history in blockchain.info of this "Aw9" address?

If you click on "Transactions" in the menu on the left... do you not see the "Aw9" address there?

That address received a payment and then sent the coins within the last day or so... if you didn't do this, then there is a chance you have the "clipboard malware" that scans your clipboard for bitcoin addresses and when you "paste" them, it automatically replaces with the hackers bitcoin address.

The address you have given currently has a balance of 0 BTC: https://blockchain.info/address/19PfFbgDZVmDQ7DkFAQfcDG4QVfuiimAw9

Can you provide TXIDs and BTC amounts?

Privacy isn't your concern... with 4 people living in a small room, you have none. Security is your problem!

If you don't feel that you can trust your roomates:

1. Secure your OS... in this case, maybe Windows isn't your best option, perhaps Linux is a better option. In either case, a strong password is your first layer of defense.
2. Secure your wallet... at the very least a strong wallet password... or perhaps an encrypted partition to store the wallet on
3. Secure your laptop... perhaps a lockable container of some description... may not stop complete theft of the container itself, but it might deter any opportunistic types