Yeah... without knowing the default derivation path, it will be quite difficult to determine if it is BIP39 as you'll just be taking shots in the dark...

Having said that... the BitcoinJ docs actually say they are BIP39: https://bitcoinj.github.io/working-with-the-wallet#seeds-and-mnemonic-codes

They also indicate that it uses the "Default" path specified in BIP32... "bitcoinj uses the default recommended tree structure from BIP 32.", which, according to the BIP32 standard is:


So, if you import to Electrum... try the derivation path of m/0' (NOTE: you'll need Electrum v2.9.0 or higher)

Ok, if you look at addresses tab in Electron Cash (wallet - show addresses), do you see that address? If not then the wallet has not been created with either the correct seed or is not using the correct derivation path.

To get your b.info wallet BCH, you need to:

"File -> New\Restore -> standard wallet -> I already have a seed -> Options -> BIP39 seed"

Then enter your 12 words from b.info and, when prompted, use derivation path: m/44'/0'/0'/0 (it should default to this)

You're not moving BTC to "split" your coins... The fork and replay protection had already effectively done that.

You're moving your BTC to protect your BTC from theft should whatever BCH wallet you choose to use turn out to be "bad" and it steals your wallet/seed/private keys...

If you move your BTC to a completely new wallet... Even if ElectronCash then sends your old seed/private keys to the hacker, your BTC is safe as it is in a different seed/private key.

Sending to an exchange will do the same thing, but if you send it back to your old Electrum wallet, you're putting it back on the old seed!

The idea of using a 2nd machine or a VM or live distro CD/USB further increases the security by preventing your BCH wallet from being able to steal your wallet file for new wallet, as it would effectively be on a "separate" device

Yes... If you import these keys into a BCH wallet, you will have access to the amount of BCH equal to the amount of BTC that was stored on those keys when the fork happened

- Make sure ElectronCash is connected to a BCH server
- Close ElectronCash
- Go into the ElectronCash data directory (C:\users\YOURUSER\AppData\Roaming\ElectronCash) and delete the "blockchain_headers" file
- Restart ElectronCash

That'll get rid of all the old BTC data it will have copied from your Electrum install and refresh all the transactions etc

If you're concerned about the 0.09, don't be, that's just the change coming back to your wallet... It isn't being sent to anyone else

Was it entirely necessary to quote most of the OP to ask a simple question?

You can also Google "escrow"... And see that escrow is usually defined as: ”An escrow is a financial arrangement where a third party holds and regulates payment of the funds required for two parties involved in a given transaction."

In our scenario, Darkstar is escrow, the participants and ChipMixer are the two parties involved in a transaction.

Essentially, what this means is ChipMixer put funds into the campaign address... Darkstar has access to this, so you can see the funds are available and that the campaign is solvent and has enough funds to pay the participants. Even if ChipMixer disappears tomorrow, Darkstar will still have the funds to pay everyone out.

At the same time ChipMixer trusts Darkstar to check that the participants are holding up their end of the deal (post quality, post count etc)

What he has posted is simply a "signed message" proving that he has access to and controls the campaign address...

Yes... handing over your wallet.dat to a stranger via an anonymous "decrepted" chat service... "very save"

also, you kind of missed the part where the OP already posted all their wallet.dats:

so you ignored the previous advice to use Bitcoin Core? or you did and it didn't work immediately so you switched back to classic?



and you still haven't updated your Armory to the latest release and are running an earlier beta?

The use of a second computer and 2nd Electrum wallet is a security measure to protect your BTC. It isn't strictly required, but is recommended. The idea is that by moving your BTC to a new wallet with new seed/private keys, if the BCH wallet turns out to be "Bad" and it steals your seed or keys, then only your BCH is at risk as your BTC has already been moved. The use of a second computer is also an extra step to protect your wallet file from being stolen.

The same thing can be achieved using VMs or live distro bootable USBs/CDs etc... as mentioned, it's not necessary, just a good idea

And yes, by seed they mean the 12 words

As long as you had BTC on those private keys when the fork happened, they will have BCH on them now (assuming you haven't moved the BCH). It makes no difference what you've done with the BTC since the fork occurred as the chains are separate. BTC transactions do not affect BCH... and BCH transactions do not affect BTC.

You shouldn't blame Electrum for the ElectronCash issues... ElectronCash was forked from Electrum by relatively unknown Devs... the issues with it are their's... not ThomasV's

It has already been noted... You restore using the 2FA seed in ElectronCash but "DISABLE" 2FA when prompted:


That will put 2 master private keys in your ElectronCash wallet and you'll be able to create and sign the transactions as required

You need to upgrade. It only works on Electrum v2.9.0 and higher as that is when the custom derivation path functionality was added... current version is v2.9.3.

If you haven't wiped/reinstalled your Operating System... and all you did was uninstall Litecoin Core, there is a VERY good chance that your litecoin core wallet.dat is still on your harddrive in the Litecoin Core datadir.

By default, on windows, this should be something like C:\Users\YOURUSER\AppData\Roaming\Litecoin (note: if you can't see AppData, you need to show hidden files)

If you have the wallet.dat file, you can simply back it up somewhere safe just in case, then reinstall Litecoin Core (you don't need to sync the blockchain)... once Litecoin Core is reinstalled and has opened up your wallet you can use dumpprivkey command to get your private keys again

Range for sale is from 0.05 MB/MBB to 0.019 MB/MBB

Bot has the following stats:

There is no reason you can't keep doing it... so if you want to go through all the hassle and waste time and potentially get your coins stuck in unconfirmed transactions by messing about with low fee transactions and bitcoin accelerators to try and save your dust... Then go for it.

No... that's not how it works... Example:

FaucetUser gets the following payments from various faucets to his address 1bitcoinAddr:

0.00010000
0.00015000
0.00012345
0.00022000
0.00020000

So in total they have 0.00079345 btc... and it is all in one address, but it is spread across 5 inputs... now say they want to transfer 0.0005 to someone... most wallets will use something like this:

0.00022000
0.00020000
0.00012345

ie. only using enough Inputs to cover the amount transferred (+ fee)... now lets say they had 5x bitcoin addresses and got those same inputs:

1bitcoinAddr1 - 0.00010000
1bitcoinAddr2 - 0.00015000
1bitcoinAddr3 - 0.00012345
1bitcoinAddr4 - 0.00022000
1bitcoinAddr5 - 0.00020000

If they try to sen 0.005, the wallet will still use 3 inputs to make it up...

1bitcoinAddr3 - 0.00012345
1bitcoinAddr4 - 0.00022000
1bitcoinAddr5 - 0.00020000

So, it doesn't matter if those 5 inputs are all in one address... or spread across multiple addresses... they'll still need to use those 3 inputs to make 0.0005... and the transaction will be the same size.


TLDR; just don't accept small amounts of BTC

The general way seems to be something like this:

1. Fork code from "SomeCoin"
2. Find/Replace "SomeCoin" with "YourCoin"
3. Conduct ICO while you premine coins
4. Dump pre-mined YourCoins for Max Profit

ALL bitcoin wallets will do this... it is just the way bitcoin works. Either stop collecting such small amounts, or live with the fact that you're going to end up with large transactions.

The only way to stop this is to not receive small amounts.