Since my advice to use those other wallets... Electrum has been upgraded to accept BIP39 compatible mnemonics with any derivation path.

It is very quick and easy to use, and MultiBit even released a video demonstrating how to take a MBHD seed and put it into Electrum: https://www.youtube.com/watch?v=E-KcY6KUVnY

Hard to say exactly without seeing the transaction details... but there is no rule that says a node must propagate any given transaction. It's possible that if the fee was too low, nodes won't propagate it (hence why it doesn't show on all explorers).

What block explorers have you looked on? Try all of these:
https://blockchain.info/
https://blockexplorer.com/
https://live.blockcypher.com/btc/
https://www.blocktrail.com/BTC
https://btc.com/

If it doesn't show on any of them... try rebroadcasting your raw transaction here:
https://pool.viabtc.com/tools/BTC/broadcast/
https://btc.com/tools/tx/publish
https://live.blockcypher.com/btc/pushtx/
https://coinb.in/#broadcast

See if you get any error messages

I believe Exodus makes use of BIP39 seed mnemonics doesn't it? ie. 12 or 24 word backup phrase... I was never able to test, because it won't let you make a backup until you actually have some coins in your wallet, which is just illogical... I want to be able to make sure the backup works BEFORE i commit coins

Anyway, you should be able to take the seed phrase from Exodus and import it into Electrum... Just create a new wallet, then use "Standard Wallet" -> "I already have a Seed" -> Click the options button, select "BIP39 Seed" -> Enter your words -> Use the default "Derivation Path" when prompted (should be: m/44'/0'/0')

You should see all your transaction history, addresses and coins from Exodus.

There are plenty of Bitcoin Payment APIs... try searching Google.

Woocommerce seems to be a popular one... and there are bitcoin plugins for it.
Mycelium GEAR is one that allows you to integrate bitcoin payments directly to your own wallet... without a 3rd-party, not sure if it supports handing the digital download thing tho...
You could also try using "Selly" etc.

This has NOTHING to do with MultiSig.

This feature (of creating a new address for each transaction) is not even unique to HD (Hierarchically Deterministic) wallets, as some older non-HD wallets also did the same thing... It is simply a means to try and prevent address re-use and increase privacy and, to a lesser extent, security. Every time an address is "used", ie. it has received some coin, the wallet will automagically generate a new receive address.

MultiSig relates to the number of signatures required to sign a transaction for it to be valid... hence "Multiple Signature" aka "MultiSig".

A couple of things to check...

Firstly, is your total balance made up of a LARGE number of UTXO's? If you click "View -> Show Coins", and the select the "Coins" tab... do you see 10+ items listed? If so, the reason your full balance is not spendable is probably due to an increased transaction size from all the UTXO's being used pushing up the fees (as they are calculated on a "per kilobyte" in Electrum. If you have a large number of UTXOs showing on your Coins tab, you have likely received a LOT of "dust" sized transactions (cloud mining? faucet collecting?). More inputs = more bytes = more fees.

If you want to get closer to the total balance, you would need to disable dynamic fees and/or enable "edit fees manually" in the settings (Tools -> Preferences -> Fees). NOTE: Doing this may result in setting fees that are too low for current network conditions which may result in longer confirmation times, BE CAREFUL!:




Also, check that whether you have "spend only confirmed coins" ticked (Tools -> Preferences -> Transactions):

The original thread regarding the bootstrap download is here: https://bitcointalk.org/index.php?topic=145386.0 It hasn't been updated since August 2014. There is a reason they stopped making/updating the "bootstrap.dat" torrent and offering it for download... since v0.10 optimisations have made it slower to use than just letting Core sync naturally.


And of course, there were more optimisations in v0.15(.0.1) to make it even faster: https://bitcoin.org/en/release/v0.15.0.1#performance-improvements

Ok, just making sure you hadn't used the "25th" word pass phrase to create a hidden wallet or anything

So when you say you see 0 balance... do you see any transaction history? or is it all blank?

Bitcoin ABC has most likely "corrupted" your bitcoin datadir (ie. blocks and chainstate folders etC) by filling it full of Bitcoin Cash data... as the devs were idiots and just configured it to use the same default data paths as Bitcoin Core

Your only real solution at this point is to configure Bitcoin ABC to use a different datadir (start with -datadir="Some/other/path" commandline argument) so that it uses it's own directory for BCH blocks... then backup your wallet.dat's and remove everything from the original datadir and then re-sync your bitcoin client.

Yes, but do make sure that you read ALL of the fine print carefully... 2FA is provided using TrustedCoin's API... and using 2FA has a "per transaction" fee charged by TrustedCoin, which I believe has to be prepaid now.

Current charges as of 16/10/2017:



More info on TrustedCoins website here: https://api.trustedcoin.com/#/electrum-help

I wrote my own: https://github.com/HardCorePawn/multibit_recovery

Feel free to try them out if you like... they're basically just edited versions of gurnec's "decrypt_bitcoinj_seed" scripts. If you're using MultiBit Classic and a .wallet file, you're probably wanting to use: https://github.com/HardCorePawn/multibit_recovery#decrypt_multibit_classic_walletkeyspy

good luck, let me know if you need any help.

That defeats the purpose of the blockchain.

The value of the blockchain is that it is immutable and can be verified from the beginning to the end as each block references the previous block. By simply downloading all of the data, you are skipping the block validation which could potentially open yourself up to issues if the data is "bad".

Additionally, it means you need to fully trust the source of the data... which also goes against the whole "Trustless" system that Bitcoin is designed for.

Finally, given the recent updates, it is also faster and more efficient to simply sync the full blockchain using the Bitcoin Core client than it is to use a "bootstrap" anyway...

It is a pointless test... prior performance is no indication of future performance.

There are too many variables at play to say that an X fee will confirm in Y blocks/minutes/days etc. We've all seen the way that the number of transactions suddenly spikes at random times. If you send using 1 sat/bye fee when mempool is empty, it'll likely get confirmed next block. If you send it when there are 30,000 unconfirmed transactions all paying 100+ sats/byte, your 1 sat/byte transaction would like not get confirmed for days.

At the end of the day, if you want to cheap out on fees, regardless of how busy the network is... use a fee of at least 10 sats/byte and use the "free" transaction accelerators like ViaBTC or confirmTx etc... works for me

Did you use a passphrase at all for your wallet originally? Or did you just set it against the default PIN? or did you set a passphrase+alternate PIN?

It would be quite difficult to pick your own set of 24 words... Given that not every combination of words actually generates a "valid" phrase.

Have a play with https://iancoleman.github.io/bip39/ generate a random 24 word phrase... and try changing the words around... or replace words with other BIP39 words... you'll get an idea for how "difficult" it is to actually make a valid phrase.

The whole idea of the words was not to make it easier to memorise as such, but to represent the seed in such a way that it reduces transcription errors and also provides a small amount of error checking.

No worries... glad to help where I can... my address for future reference is: 16qkTAUmtCdBYfXXKKGKqD8pAYtL1T5pqV

As for the links, they're all github... and all found under the btcrecover repo: https://github.com/gurnec/btcrecover

As for a total solution, you're basically down to creating a "token" file for btcrecover... and then setting it going and hoping for the best... was your password likely to be long and complicated? or relatively simple? At the end of the day... that, and the "quality" of your token file is likely to determine the chances of wallet recovery.

Ahhhh OK... I understand now... you have the "Show History Rates" box ticked on the "Tools -> Preferences -> Fiat" window don't you?

This does exactly what it says... it shows the "Historical" rate for each individual transaction... ie. what that amount of bitcoin was worth when it was sent! The fiat value for the overall balance, shows you what the total value of your wallet balance is worth NOW.


If you had a 1 BTC transaction from Dec 2011, you'd see it was worth like $2... even though the total balance today would show $5800+

Yes, your wallet knows that those coins are "confirmed and spendable" at the date the wallet is synced up to... but how does your wallet know that those coins have not already been spent between the time it is synced to, until the current block?

Have you tried using "getrawtransaction TRANSACTIONID" and then copy paste the HEX output into "sendrawtransaction HEX" in "Help -> Debug Window -> Console" ?

It might just need a rebroadcast... or you may see the error that is stopping it from being accepted by the network.

So if I am understanding correctly... you have an old Electrum wallet file from when Electrum used to allow storing "non Seed" private keys in the same wallet file as "seeded" private keys... You have the seed but you can't remember the password to this file, so you can recover the coins contained in the "seeded" addresses, but not the imported addresses?

As unamis76 has stated, your best option is probably btcrecover. If you are having issues getting btcrecover working, it might also be possible for you to use the "extract" scripts that btcrecover offers (https://github.com/gurnec/btcrecover/blob/master/docs/Extract_Scripts.md#usage-for-electrum), so that other users can attempt to find your password for you WITHOUT needing a copy of your wallet file. In essence they get a short snippet of the wallet file, that will enable btcrecover to test passwords for correctness but contains no useful wallet info.

To use the extract script, you just need to have Python 2.7 installed... https://github.com/gurnec/btcrecover/blob/master/docs/INSTALL.md#python-27

download the appropriate Electrum extract script:

Electrum 1.x: https://github.com/gurnec/btcrecover/raw/master/extract-scripts/extract-electrum-halfseed.py
Electrum 2.x: https://github.com/gurnec/btcrecover/raw/master/extract-scripts/extract-electrum2-partmpk.py

Usage of the script is decscribed here: https://github.com/gurnec/btcrecover/blob/master/docs/Extract_Scripts.md#usage-for-electrum

After you have the extract, you would be able to provide anyone attempting to crack it, hints on what the password is likely to be, they could create a token file... and start using btcrecover to try and crack it.

Alternatively, for the amounts you're talking about, you might want to contact Dave at Wallet Recover Services (https://walletrecoveryservices.com/)... he seems to have a fairly solid reputation for be legit: https://bitcointalk.org/index.php?topic=240779.0

It sounds like you've accidentally switched onto the BCC chain in the Ledger wallet...

Do you see something like this?



If so... click on "Settings":




Then select "Blockchains":




Then select "Bitcoin" (note: if asked, select "Legacy"):




You should then see that you're connected to the "Bitcoin" chain and your BTC wallet should show up: