At close to twice the price of the current Trezor (and more than twice a Nano S), I can't say I'm overly enthusiastic about it... Wooo a colour touchscreen

I don't see myself updating from the current one to be honest.

Which website did you buy the coins from? Did you have an account on there? Or was it simply a "enter your address + credit card details and click buy" type of thing?

If you have an account there, the coins should still be available there, as technically they have not moved. If they're not showing, then you'll need to contact the support for the site you used and ask them for assistance.

Also, do you have some sort of transaction history available on the site? If so, maybe double check the transaction IDs for your coin purchases and make sure they're the same as what the wallet is showing. It's possible that the transaction information you see in the wallet might be incorrect due to it actually being from another network.

Good to hear you managed to get it all sorted mate! With current BTC prices, 0.77 BTC is a considerable amount of money!

Did you just "import" your private keys? Or did you "sweep" them into a full Electrum wallet that has "12 word recovery seed"?

Just wanting to make sure you understand the difference and especially the fact that if you imported them, you need to make sure you have a backup of the Electrum wallet file and/or the private keys themselves!

If you created an Electrum wallet with a 12 word seed, you just need to make sure you have those 12 words written down and stored safely offline!

The first thing you should do is send all your coins to 1HCPsAddress for safe keeping!

But seriously, given that MultiBit Classic is really old and outdated, sending your coins from MBC is actually a bit difficult. It's fee system is really "broken" and only allows for a max fee of around 50 sats/byte... Which in today's Bitcoin network can often mean slow confirmation times and stuck transactions.

What you can do, however, is export your private keys from MBC and then import (or "sweep", see below) them into another wallet like Electrum. Electrum is also a light weight SPV wallet like MultiBit was (no need to download the full blockchain), is actively maintained and has a good group of knowledgeable users here who can assist with any issues.

You can get Electrum here: https://electrum.org/#download

You can find a good, easy to follow video tutorial (created by MultiBit) on how to export your keys and import into Electrum here: https://youtu.be/LaijbTcxsv8

---

On the slightly more technical and involved front, personally, I would recommend creating a "seeded" HD wallet in Electrum ("standard wallet -> create a new seed") before you start. Then, once you have that setup, you should export your keys and then "sweep" the contents of the MBC private keys into your new Electrum wallet.

That way your coins are actually moved into new addresses with new "more secure "private keys (ie. They haven't been potentially exposed during export like your MBC ones now have) and your coins will now be protected with the 12 word seed mnemonic, making recovery a LOT more simple!

To sweep, you simply open the Electrum wallet and select "Wallet -> Private keys -> sweep" and follow the directions.

If you need any more advice or help, just ask

Looks like Vertcoin (VTC) also uses "3" for MultiSig addresses... Did you send to a "3" address? If so... Maybe you could recover your coins by recreating your BTC multiSig wallet in a VTC wallet (like Vertcoin Electrum)...

Theoretically, it should work.

I did a quick test and a MultiSig wallet from BTC Electrum generates the same addresses in VTC Electrum.

Next time, be more careful

The UTXO set is constantly changing... And not necessarily just getting bigger.

There are always people consolidating (on purpose like what you've suggested and accidentally when their wallets use up several smaller UTXOs to create 1 output) and there are always people "splitting" (change and pay-to-many). It's just part of the way Bitcoin works.

I used to occasionally consolidate as you've suggested... but it's just as easy to simply put in a 10sats/byte fee on any given transaction and then use the various transaction accelerators to avoid the "low fee long wait".

No. That's not how it works at all... The two values are completely independent. Look at what happened with BTC and BCC... The value of BCC plummeted from initial trading and in recent days even went up without affecting BTC value at all

For the record, the TXID for the OP is supposedly this: f53850b8050cc30416802426b8ac4959f55728db7b6ad8d34c8ddca46013d7ea

However this transaction is not valid on BTC or LTC networks... Furthermore, the screenshot suggests that transaction was on 9th September... And had 0 confirmations

I suspect that the transaction never confirmed and was eventually dropped by all networks.

OP, unless you can provide the addresses matching this transaction, there isn't much more anyone can do to assist. It looks like the transaction was never confirmed... You'll probably need to use the "zapwallettxes" option to remove the Phantom transaction from your wallet

Any reason you're not using a block explorer API like block cypher? https://www.blockcypher.com/dev/bitcoin/

But I guess the Electrum commands you're after are:
getaddressbalance('1bitcoinAddress')
getaddresshistory('1bitcoinAddress')

NOTE: Those are the console commands... When trying to use from the command line, you may not need the ()'s or the ' characters

You'll have to provide either the BTC address you sent to, or the transactionID of the transaction that sent the Bitcoins from localbitcoins to your Electrum wallet.

Without at least one of those, no one will be able to assist in a meaningful way.

Yes, you are correct.

The original 12 words you got from Electrum are not needed (unless you transferred the coins into an address in the Electrum default wallet).

If you simply created a new wallet in Electrum using the MultiBit words, you can continue to use that, and will just need to make sure you you have a backup of the MultiBit words.

Are you sure you're on the "real" MyEtherWallet website? I've heard that there are a number of fake MEW sites designed to steal wallets.

It isn't "HardForks" in general that are the problem. It is the lack of replay protection. None of this would be necessary if replay protection is implemented... But from what I gather, the 2X is deliberately NOT implementing replay protection in an effort to become the "majority" chain without wallet software and service providers needing to update anything.

I predict a large number of "technically unaware" Bitcoin users losing a lot of coins following this fork...

No worries... If you get desperate, let us know what address you want to send to (and desired fee rate) and pretty much anyone can create an unsigned raw transaction for you.

You'd just need to put it in the "verify" section to confirm it's sending the correct amount(s) to the correct address(es), sign it and broadcast it.

Coinb.in is actually pretty straightforward...

The other option is to download the Electrum 3.x source code from GitHub and run that... See if it reads the transaction correctly. I'm surprised that 2.x is struggling with the witness tx, as you can create a watching only wallet for your 1Hefr address and it shows the transaction just fine... So I'm not sure why it can't read it when you have the spending wallet??!?

Honestly, the "double slider" seems like an unnecessary complication... What's wrong with having the 4 "presets" + one labelled "custom"... Clicking the button to cycle through the presets automatically populates a text box with the "dynamic" fee... "Custom" makes the text box editable and the user can manually edit the fee rate in sats/byte...

It's such a simple feature and one the people have been requesting for ages... So, naturally, they completely ignored everyone and put in the fancy double slider, that offers some "coarse grained" control over the fee

I know that MultiBit was using BitcoinJ... Maybe make some copies of your .wallet files and see if you can open them with MultiBit Classic (https://multibit.org/release-info/classic/v0.5.19.html)... Not sure if you can open "random" wallet files with MultiBit HD (https://multibit.org/releases/multibit-hd/multibit-hd-0.5.1/)

NOTE: both versions of MultiBit are outdated and are no longer maintained and don't come with any official support.

Hopefully, the BitcoinJ "wallet file" format should be relatively consistent across applications, as the apps use BitcoinJ functions and "ProtoBuf" to read/write the wallet files.

Also, assuming you have the encryption password, it's possible you may be able to dump the private keys out of the .wallet file or the .key file using my Python scripts (https://github.com/HardCorePawn/multibit_recovery). No guarantees though, MacWallet may have used different encryption settings

Again, I think you've very confused about how MultiSig works and you're attempting to recover the wrong keys for what you're trying to achieve. All you need at this point is a wallet containing the "missing" MultiSig key, so you can sign transactions from your Linux wallet.

So, I'll try and breakdown what *my* understanding of the situation is:

- You have a MultiSig wallet on your Linux machine, that has coins in it, that you want to spend.

- LinuxWallet contains Linux private key + a public key from MacWallet as "co-signer"

- MacWallet is actually a 2FA wallet. It has x1 privateKey (stored in wallet file), x2 privateKey (normally "hidden", but accessible with seed) and x3 private key (held by TrustedCoin)

- Based on your description of the "co-signer" pubkeys in LinuxWallet, it would appear that the MacWallet pubkey it is using is the one that matches the "x1" private key from your 2FA MacWallet (NOTE: Without seeing the full pubkey, it is impossible to know if this is true, please double check the full pub key and make sure it is completely identical to the one reported in Linux wallet)

- if these assumptions are indeed correct, to be able to spend from your Linux wallet, you would need to extract the "x1" privkey from MacWallet (simply change the password, and leave the "new password" boxes empty, you can then open the wallet in a text editor to view the xprv)

- once you have the x1 xprv, create a "standard" wallet using just that xpriv. ("New/restore -> call it 'signingWallet' -> standard wallet -> use public or private keys", paste in the x1 xprv).

- you should now have the original LinuxWallet MultiSig and a new "standard" wallet on Mac that is using the x1 xprv.

- From here, you simply create a (partially signed) transaction on Linux, transfer it to the newly created 'signingWallet', sign it and then broadcast it.

- using LinuxWallet, create the transaction as desired (ie. Address, amount, fee etc). Click "sign" and put in wallet password (if any). You'll get the "preview" window pop up with options to Copy, Save, "send to cosigner" etc. Click "Save" and save the unsigned.txn file to USB.

- using 'signingWallet' on Mac goto: "Tools -> Load Transaction -> from file"... select the unsigned.txn file from the USB... you'll get the "preview" window open up. Verify it's all correct (fyi, it's normal for it to say "transaction unrelated to your wallet"), click sign, put in wallet password (if any) and then click broadcast.

Job done!

Personally, I'd recommend that once you have confirmed that the signing wallet is all working, that if you want to continue using a MultiSig setup, that you seriously consider creating a new pair of wallets, so you can easily recover using seeds... Rather than having to mess about with xprvs etc.

By looking at the decoded "raw" transaction, you can see references to "witnesses" for certain inputs/outputs.

I wouldn't have thought this would be an issue, as your address is obviously NOT a SegWit address (it can't be as it starts with a "1")... But perhaps Electrum 2.x is just not able to parse the transaction and that is why you see balance=0??

If you need to move those coins in a hurry... You could always try creating a transaction manually using something like coinb.in (https://coinb.in/#newTransaction)

As a test, I put your "1Hefr" address in, it found the 0.5 BTC input... I was able to put in the same BTC address as output address, an output value of 0.49995000 (creates a fee 0.00005000 which should be about 25sats/byte) and then created the raw transaction...

Theoretically, you could then verify it, sign it and broadcast it using coinb.in as well...

Things you would have to be careful of include making sure you calculate the fee and output value correctly, so the transaction gets confirmed. Double checking that your output address is correct. Also, you'd want to do the "signing" part (when you put in your private key) using an "offline copy" of the coinb.in website (save as, or get it from the GitHub linked at the bottom of the site).

Does your address begin with a "1" or a "3"?

If it begins with a "3" (ie. You have an Electrum MultiSig or a 2FA wallet)... Your addresses are "P2SH" - "Pay to Script Hash"...

There is no way to sign a message with a P2SH address they don't necessarily have a private key... And in the case of MultiSig have multiple private keys associated with them.

You can only sign a message using P2PKH (Pay to pubkey hash) addresses... They start with a "1"... And only have 1 private key associated with them

You only get "x2/" if you restore your wallet and then "Disable" 2fa so that it puts both xprvs into your wallet...

If you restore and "keep" the 2FA then you only get one xprv...

To be honest, I still think you're trying to retrieve the wrong keys... All these two xprvs will let you do is spend from your 2FA wallet without needing TrustedCoin.

But you're trying to spend from an unrelated MultiSig from your Linux wallet.