It changes automatically, after the current receiving address receives some coins and is marked as "used"... have a look on the "addresses" tab (you may need to use "View -> Show Addresses" to see this tab in v2.9.3)... you will see "Receive" addresses, and those marked as "used". The default address on the receive tab should be the first unused address (the first one with a "Tx" value of 0)

You might like to setup a copy of Electrum on the TestNet and use a TestNet faucet to get some coins to a couple of TestNet wallets and have a practice sending coins around to see how the addresses change etc.

To run on testnet, you just start Electrum using the --testnet commandline



Some try to use new addresses... but for regular payments, this can often be difficult/impossible to setup... having said that, in general, if you're always receiving coins from one particular address... and those payments are always going to the same address, it isn't really much different from getting one payment. People can still see that coins went from SenderAddressA to ReceiverAddressB regardless of if that happened once or 10 times.

The "privacy" issues with address reuse really stem from getting or sending to multiple different addresses repeatedly... ie. putting an address on your Bitcointalk profile... that is one address, and multiple people can send to it... now all these addresses are linked up... and you've "publicly" linked that address to yourself...

So, something like SenderAddressA, SenderAddressB, SenderAddressC ... SenderAddressZ all send to your bitcointalkProfileAddress.

or... you do something like:

yourAddressA -> someGuyOne
yourAddressA -> someOtherGuy
yourAddressA -> randomPerson321
yourAddressA -> yetAnotherBitcoinAddress

you have now effectively created "links" between all of these addresses...



Depends on your definition of private. Some people care... others don't... and the real problem is that regardless of how "safe" you are and follow best practices like only using an address once etc... if you ever receive or send to someone who doesn't care and re-uses addresses etc... it can ruin your privacy by association.

If you're serious about remaining anonymous, then BTC probably isn't the best crypto currency... you'd be better off with something properly anonymous with on-chain mixing like Monero.

It would appear that chipmixer.io is currently offline/down... http://downforeveryoneorjustme.com/chipmixer.io

Hopefully it is back to normal soon

Have you checked how much free space you have on your computer? Specifically on your C: Drive

Bitcoin Core requires a LOT of hard drive space for the blockchain (currently 150Gigs+)... and (from your logfile) looked like you had some issues getting it all to fit (a few readAndWrite errors etc)... It is possible (although, I would think a little unlikely) that your drive is full again and Electrum is unable to create the wallet and that is why it just closes during wallet creation. I say unlikely because the Electrum wallet filesize is actually pretty small.

As Phoenix asked, does it also close if you just create a wallet using "Create a new seed"?

Also, which version did you download from: https://electrum.org/#download ?

Standalone? The filename is: electrum-2.9.3.exe
Installer? The filename is: electrum-2.9.3-setup.exe
Portable? The filename is: electrum-2.9.3-portable.exe

Good to know your 1.6BTC is "safe"... Now if you could solve the mystery of the 5 BTC...

but yeah, leaving sizeable balances on exchanges is not recommended. I would definitely get your Trezor up and running as soon as you can if I were you!

To get "merged"... UTXOs need to be included in an "on chain" transaction... this will obviously require a transaction fee. It is technically possible to use a fee of zero, but the chances of that transaction being mined will be relatively low.

The best option, in my experience, is to use a manually set fee of 10+ sats/byte and then use the ViaBTC TX accelerator to push the transaction through. For a transaction with 20 inputs, the size will be around 3K bytes, so at that fee rate, the fee will only be ~30K sats

Basically... it simply comes down to exporting either your private keys or your seed mnemonic (12/24 word backup) and then "importing" these into a compatible BCC wallet.

Some wallets are easier than others, as they make it super easy to export your keys/seed mnemonic and/or they have a "BCC Clone" like Electrum->ElectronCash or Bitcoin Core->BitcoinABC where you can actually just use your existing wallet file to get access to your BCC.

Others are a little more complex... and you need to find out what "Derivation Path" they use in combination with the seed mnemonic for the wallet addresses, so you can input that into ElectronCash (or the BIP39 Mnemonic Code Converter) and it regenerates the correct addresses.

Then you need to consider the "safety" of your BTC... It is considered "safe practice" to move your BTC from the exisiting keys/wallet before exporting/importing BCC clients so that only your BCC is at risk should the keys/seed be compromised. Having said that, as far as I'm aware, there have been no issues of people suffering loss when using "official" BCC clients downloaded from the "official" repositories on malware free computers...

Did you try reading the BIP32 and BIP44 specification which spells it all out??

Try reading this: https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki#path-levels

Did you use "dumpprivkey" or "dumpwallet" to export your private keys?

if you used "dumpprivkey" and specified your addresses individually, did you remember to include all your change addresses?

I'd recommend either using "listaddressgroupings" on your original wallet to identify all the addresses (receive AND change) with UTXOs that you need to use with "dumpprivkey"... OR use "dumpwallet" on your original wallet and get ALL the privkeys... with coins and empty

Then try importing those privkeys again

It attempts to dump all the private keys it can detect (including false positives) from your wallet.dat... it isn't a magic bullet that will magically resurrect a corrupt or damaged wallet.dat and should only be used as a last resort and only on a copy of the file.

Apparently, there have been instances in the past where salvagewallet has actually corrupted a valid wallet file...

Sorry... this doesn't verify...

I think you've not posted your message properly... it should be like this one, without all the <>'s:

-----BEGIN BITCOIN SIGNED MESSAGE-----
S_Natural bitcointalk 2017/09/05
-----BEGIN SIGNATURE-----
176rVybXv6T7X4RaY6iyBQt1MBwVrpTc5B
IHpDE3QbiOf05k+FVIutzeoVG2HeG6YRYT/rZSt3adgoAZdt8OUkfV7pG6MEcx/dwmn5jkmiy1ftjhjYtDigl+w=
-----END BITCOIN SIGNED MESSAGE-----

You cannot do this.

If I am understanding what you want... you want to be able to do something like this:
- YourAddressABC = No History = 0 BTC
- YourNewAddress123 = No Hisotry = 0 BTC

- RandomGuy sends 0.25btc to YourAddressABC
- YourAddressABC = 1 transaction = 0.25 BTC
- YourNewAddressABC = No History = 0 BTC

Now, you wan to take the 0.25btc and send "from" YourNewAddress123 to someOtherGuy... so "someOtherGuy" cannot see your transaction history and coin totals etc, correct?

Well, unfortunately, this is impossible... the 0.25btc is controlled by YourAddressABC, you cannot send "from" YourNewAddress123... it has no coins. You cannot move control of coins from one address to another address without creating an on-chain transaction, which is then visible to anyone who looks at the blockchain, and that will create a trail that can be followed.

This is why people invented Bitcoin Mixers



To receive BTC to an address that has no history, you just simply generate a new address... most HD wallets do this automatically... older non-HD wallets, you needed to manage it yourself... generate a new address, give that new address to recipient.

Electrum should pick the first "unused" address in your address pool when you click on the "receive" tab... you should also be able to click the "new" button to move to the next new address.

No.

OP explicitly stated that he moved his Bitcoin data directory because his laptop only had a 128Gig SSD and he didn't have room for the blockchain, so shifted everything to F: drive and into a folder called F:\Bitcoin Core.

If you're getting the "Purple" text in Armory, it sounds like it isn't able to connect to your Bitcoin Core using RPC properly. Did you try setting up a bitcoin.conf file in your Bitcoin Core datadir and adding in the following lines:
Personally, I'd recommend shutting Bitcoin Core down and letting Armory run it in the background... it just doesn't seem to work for me if I open Bitcoin Core and then start Armory.

You don't put your seed into a Trezor server if you need to restore it... and your recovery seed uses the "standard" BIP39/BIP44 configuration... so if Trezor goes out of business or your lose it, you can restore to a compatible wallet or another hardware wallet...

Have a read of these two: https://doc.satoshilabs.com/trezor-user/emergency.html and https://doc.satoshilabs.com/trezor-apps/index.html#recovering-funds-without-trezor-device

The whole idea of a hardware wallet, is that the seed should only exist within the wallet itself, or written on your recovery sheet... it should never be stored digitally. So aside, from the recovery sheet, the device is "truly independent of outside factors" as you put it.

Note: I wasn't suggesting that you should take the space out... I was merely asking if that works or not. I apologise if I caused any confusion.

In Bitcoin Core, have a look at "Help -> debug window -> Information" and see what is listed as the "datadir":


Armory needs to have the Bitcoin home dir set to the same value.

So, if you tried with F:\Bitcoin Core and it didn't work... try using "F:\Bitcoin Core"... or 'F:\Bitcoin Core'

I would guess your chances of finding a MultiSig vanity address would be less that hitting a national lottery...

For a normal vanity, you just need to find one private key that converts to your desired vanity address... and even that can take days/months depending on the complexity of the desired vanity address.

For a MultiSig, you need to find at least 2 private keys (for a 2of2 setup... basically you need M private keys in an N-oF-M MultiSig setup)... that when combined will generate a redeem script that when hashed will convert to the desired vanity address.

The chances of being able to do this are somewhere between slim and none... Good luck!

They were two transactions that were inbound to your Xapo wallet that never got confirmed... and were then dropped from the mempool before they were mined into a block/confirmed.

Your Xapo wallet is "incorrect" and showing transactions that do not exist anymore. You should contact Xapo support and tell them. I don't believe there is any way to "refresh" your Xapo wallet from the user end, so I think that only Xapo can fix this.

Also, those payments should have been returned to the original sending wallet. You should contact the sender and tell them to resend.

Someone with access to the private key for 13QSnhZrKYpHkbxuKiXaEwqVFgsSfB7Gi9 has sent the 5 BTC from that address (combined it with 516 other inputs (!!?! ) and sent it to 18yhZFwZcHGVKStRfVWBV5dXJ6Yb1MdHdx.

Do you recognise ANY of the other INPUT addresses in this transaction: https://blockchain.info/tx/c2ac656069e9719aa906aab4a8ba8dc5805ddca75b7cc3c6c3afb897216a6cab

Are any of them (apart from the 13QSnhZrKYpHkbxuKiXaEwqVFgsSfB7Gi9 one) yours? Did you try and combine all your BTC or send them to an exchange or other online service or sweep them into a different wallet?

If you're 100% sure that you didn't send those coins anywhere, then the only other explanation is that they have been stolen.


That is most likely a "change" address from your wallet. You can read about "change" here: https://en.bitcoin.it/wiki/Change and here: https://en.bitcoin.it/wiki/Coin_analogy

I'm guessing you missed the part where you need to have Bitcoin Core downloaded, installed and fully synced to be able to use Armory "properly"...

Armory requires the Bitcoin Core blocks to be able to read/scan to see the incoming transactions that affect your Armory bitcoin addresses... and it utilises the Bitcoin Core subsystem to send outgoing transactions.

NOTE: your BTC is not lost, it will be in your Armory address (assuming you entered the correct address when withdrawing from the exchange)... it just won't show until Bitcoin Core is fully synced... and Armory has scanned the Bitcoin Core blocks.

Does it not give you the option to select where to install it on Linux? On Windows you can select the install directory during the install process... so that it does not overwrite the application.

Also, it allows you to select a "data directory" on first setup... or you can specify it on the commandline (or in bitcoin.conf)... so that the blockchain is not overwritten.

Hmmmm seems that the address it ended up in: 12cgpFdJViXbwHbhrA3TuW1EGnL25Zqc3P belongs to Poloniex... so someone has sent those coins to the deposit address: 1Dfat2qDcdAh9Tjgux59U7jHzKwHt8LHbW at Polo, and Polo have then consolidated it all...

I'm really hoping it was the OP moving his coins... they sat around for nearly an hour or so before being sent to Polo, so it doesn't seem like an automated bot...

OP, did you create a brand new Electrum wallet? If so, and you didn't send the coins to that 1Dfat2 address, then as Abdussamad has suggested, it is highly likely your machine is totally compromised