When you sweep, Electrum just treats this as though it were creating a 'normal' transaction from the wallet. Simplified process goes something like:

- Find all the UTXO's on the blockchain that are controlled by the private keys being swept and use them all as inputs... giving you a "TotalIn" amount of BTC

- Set the entered receive address as the output target address.

- It then uses whatever fee setup you have configured to set the fee for the transaction. In your case, you had Dynamic Fees enabled, so it would have received a notification from the Electrum Server Network regarding the current fee rate required (in BTC/kB) and then calculated the total fee based on that fee rate and your generated transaction size. It would then subtract that fee from the "TotalIn" amount to create "TotalOut" amount.

- "TotalOut" amount assigned to output target address.

- Transaction gets signed by the private keys to prove ownership.

- Transaction gets broadcast.

- Bitcoins arrive in new address

Which isn't an HD wallet.

Like I said, you cannot import private keys into an HD wallet... if you create a wallet file in Electrum that isn't built from a seed... then that isn't an HD wallet. It is just a keystore of essentially "random" private keys.

These two things are essentially mutually exclusive... you cannot import private keys into an HD wallet. The whole point of an HD wallet is that all the addresses in it are derived from the seed.

This is theoretically possible... but because the wallet would have to start generating addresses from the seed to try and match the desired "vanity" tag, the search space becomes limited and the time required to find a matching addresses would be increased. Most likely rendering the entire process very lengthy and uneconomic.

Given that a vanity tags longer than 6 characters take hours/days of searching to find... and then you restrict the search to a specific sequence of addresses being generated... you're going to be crunching addresses for quite a while trying to find what you want.

Do the files that you found in MultiBit > Multibit data > Wallet-Backup contain text that look something like this:

And do the "Asian writing" ones look something like this:

Currently, it crashes if I try to add a new wallet... From what I can gather, it is a "SegFault" of some description, but because it is running "native" code via kivy, I can't see the exact cause of the problem... the error message is a bit obscure

Previously, I had it go into some crash loop where it would just instacrash on app startup... the only way around that was to clear the app data/cache, and then restore my wallet...

ok, so in wallet-unenc-backup... do you see a file titled something similar to:

multibit-20170602232432.wallet.cipher

it might be called untitled-20170602232432.wallet.cipher or untitled-20170602232432.wallet? I need to know the exact file name, so I can be sure you have the right file.

This sort of bullshit is the reason I have auto update switched off...

Going to have to go create an Android dev environment now so I can download the source and hack the ads out... I just wish Electrum was a bit more stable on my device, otherwise I'd switch in a heartbeat...

I love the "we gotta pay for stuff" excuse... wtf happened to all the money from the crowdsale?

Included In Blocks 470049 ( 2017-06-06 13:45:48 + 18,106 minutes )

Looks like the AntPool acceleration worked

as mocacinno has already suggested, stop collecting tiny dust payments. If you are collecting from mining or faucets or whatever... try and set a minimum payout/withdraw amount of 0.01.

It will be because you have several inputs making up your total balance... each input will add 148 bytes to your transaction size when you want to spend coins...

at the moment, recommended fees are over 350 sats/byte... and getting close to 400 sats/byte (https://bitcoinfees.21.co/ and https://btc.com/stats/unconfirmed-tx)

148 bytes * 350 sats/byte = 51,800 sats (0.00051800 btc) fee PER INPUT. which at current rates is almost USD$1.50 per input... (Then you have 34 bytes PER OUTPUT + a fixed 10 bytes per transaction...)

If you have 5 inputs in your wallet... that is currently going to cost you ~USD$7.50 to use them all in a transaction (ie. spending all your coin), because Jaxx doesn't let you specify your fees, it sets them for quick confirmations by setting them at the recommended levels.

HD doesn't stand for hardware... it stands for "Heirachical Deterministic": https://en.bitcoin.it/wiki/Deterministic_wallet#Type_2_hierarchical_deterministic_wallet

Basically, you have a seed which acts as a starting point and ALL your wallet addresses are generated from this starting point in a known, repeatable way... so should your computer be completely destroyed, you simply load up Electrum on a new PC, "restore" -> "I have a seed" -> put in your seed words and the wallet will recreate exactly the same addresses and thus rebuild your wallet from the data already in the blockchain

What did you open with Notepad? which file exactly... what is the name?

If you are sure you know the password for your wallet file... there is a very good chance that we can recover your bitcoins.  You want to look for files that have names like (NOTE: the numbers will be different!):

multbit.wallet
multibit-20170602232432.key
multibit-20170602232432.wallet
multibit-20170602232432.wallet.cipher

You may need to look in "key-backup", "wallet-backup" and "wallet-unenc-backup" directories...

Triple posting effectively the same stuff over and over isn't going to get you any help...

https://bot.seuntjie.com/programmermode.aspx
https://steemit.com/dicebot/@seuntjie/dicebot-programmer-mode-tutorial-1-1-variables

Did you read the programmer mode tutorials that Seuntjie linked to? He clearly put a lot of effort into making them...


chance = 90.4 -- sets chance to 90.4%
bethigh = true -- sets to roll High/Over


chance = 94 -- sets chance to 94%
bethigh = false -- sets to roll Low/Under

Honestly, looking at your script, it is fairly obvious that you have zero (or close to zero) programming knowledge and lack the understanding of the basic fundamentals to be able to make this work. I highly recommend that you at least work through the tutorials that Seuntjie put together to at least build up some knowledge of the very basics and learn how the bot actually processes the script. There is a nifty flow chart that explains the "flow" of the bot and how it processes the script.

I'm happy to provide tips on how to add certain features to a script... little code snippets... but if you want a script generated from scratch... I'm happy to offer my services for a fee...

If you want to send mining output to a wallet... make sure you set the withdraw limit to be high. Otherwise you will end up like all these other people complaining about having to spend $10 on fees to send $40. Getting lots of small payments results in increased transaction size when you go to send and then you get slammed with massive fees.

Not sure what constitutes small amounts for ETH, but for BTC you want to set your withdraw to like 0.01

Great news... glad we could be of service... thanks for the tip!

Given there are 2048 words in the list of valid seed words... and 12 words in a seed... the number of combinations is "very large"

You will find the next button "appears" whenever you put any valid seed in... but there are literally millions of millions of millions of valid seeds, good luck "cracking" that...

As addresses are based from the seed, it is highly likely that it let you put in the seed without custom words but the generated bitcoin addresses and private keys would have been different.

I don't quite understand what you mean by "logon" using your seed? You are supposed to use your seed once when setting up the wallet, then you add a password (and optionally encrypt the file with your password)... when you want to open the wallet and/or send transactions, the app should ask for your password... but you certainly don't need your seed.

I would think that Electrum-LTC probably does!

That is just plain wrong. The entire point of HD wallets like Electrum is that the entire thing can be restored using only the 12 word seed. So, if OP's "PASSPHRASE" is 12 words... and he was using Electrum a simple wallet restore is possible.

It all depends what wallet was being used tho.

Find your seed using: https://github.com/gurnec/decrypt_bitcoinj_seed

Then import the seed to "Breadwallet" (iOS/Android) or "Simple Bitcoin Wallet" (Android).

If you can't use BreadWallet or SBW... then my python scripts will help get private keys from MBHD wallet: https://github.com/HardCorePawn/multibit_recovery

Or you can do it manually... create offline copy of https://iancoleman.github.io/bip39/, put in your seed, set Derivation Path to BIP32, set client = MultiBit HD, get addresses/keys. then set client = custom and bip32 derivation path = m/0'/1 and get change addresses/keys.

Import keys into another wallet like Electrum

Did you even look at any of the other threads? A few even state in the thread title "Password does not unlock the wallet"

Here is a small selection:
https://bitcointalk.org/index.php?topic=1901987.0
https://bitcointalk.org/index.php?topic=1733063.0
https://bitcointalk.org/index.php?topic=1944436.0
https://bitcointalk.org/index.php?topic=1938280.0
https://bitcointalk.org/index.php?topic=1936405.0

Transaction has been accelerated...  As noted here: https://bitcointalk.org/index.php?topic=1943939.msg19384052#msg19384052