The BitWallet support people told me that the Derivation Path is user customisable... so you can pick whatever you want... but that the default was the m/i’/0/k one. However, I'm not sure if they ALWAYS used this default, to be honest, I got the impression that the people answering my email queries were not very "technical"



Sort of... as an SPV wallet, it uses "Bloom Filters" to lookup transactions in an indexed database maintained by a node. This is a LOT faster than having to scan block by block like Armory does... but potentially gives up some privacy as you're passing those addresses to an external node.

Yeah, it all depends on your choice of apps... I believe the Fido "U2F" app is one of the larger ones. Depending on the specific combination, you'll get 4-6 apps on there before you need to uninstall one to (re)install another.

Note that uninstalling an app does NOT delete your wallet or coins etc... you can simply reinstall the app and that specific coins wallet will be fully accessible again with the same addresses/transactions/coins etc

You would need to find Android litecoin and ETH wallets that work with hardware wallets... or at least allow you to import "xpubs". Then you could simply import the "xpub" (master PUBLIC key) for your Ledger wallet and create a "watching only" wallet on your mobile device.

I know the (newer?) LTC version of an xpub is the "ltub"... but I can't seem to find any explorers or wallets that allow importing them  I'm not terribly familiar with ETH, I've used it about twice... so can't really comment on that one.

Maybe try asking the Electrum-LTC folks if they'll consider creating an Android version?

In BitcoinGold Core, look at the following menu: "Help -> Debug Window -> Information"

There is an entry labelled "Datadir":


That is the location of your BitcoinGold Core data directory and should contain the blocks folder and wallet.dat etc.

You could possibly create an offline copy of https://coinb.in/#newTransaction

While offline, you could create and sign the transaction that sends from your old paper wallet, to the new paper wallet... and then just go online with just the "signed transaction" hex and broadcast it using an online transaction broadcast service (see: https://en.bitcoin.it/wiki/Transaction_broadcasting) via Tor or a VPN or something??

NOTE: I've not tried broadcasting transactions using Tor, so I'm only guessing if that is actually possible.

The simplest explanation is that you need to recreate the Bitcoin address, but on the Litecoin network (ie. using the same private keys as the Bitcoin address).

The only way to do this, is by using private keys. So you need to export private keys for the Bitcoin address that you sent the LTC to, and then import these private keys into a Litecoin wallet. This should (in theory) recreate the address on Litecoin, and show you the LTC that you sent.

It can be complicated depending on the type of Bitcoin address that you sent to... If it was a "SegWit" address, it isn't too difficult as they only have one private key. If it was a "MultiSig" address, that complicates matters as they have multiple private keys.

rescan or zapwallettxes?

Zapwallettxes is GUARANTEED to remove the transaction from your wallet... because it removes ALL the locally stored transactions and then rescans the blockchain.

remember to backup wallet.dat FIRST

NOTE: if you are in "pruned" mode, the rescan will need to download all 150gigs of blockchain

This is why I said "make a backup of the wallet.dat"

-zapwallettxes just removes ALL the locally stored transactions in your wallet.dat file (if you have a backup, then you can always put it back if something doesn't go right). It should then "rescan" the blockchain and find all the confirmed transactions and your balance should be updated accordingly.

NOTE: if you are running in "pruned" mode... rescan will redownload all 150+ gigs.

Restart Bitcoin Core using the -rescan command.

It will force the wallet to rescan the blockchain looking for transactions that apply to your wallet addresses. If the "dead" transaction still persists... consider using -zapwallettxes to remove it.

NOTE: you should make a backup of your wallet.dat before you attempt this.

The issue is that a "3" address is a P2SH address... so it may have multiple private keys if it is a MultiSig (and not a SegWit address)... Which will make importing it all into Electrum a bit difficult...

It seems some of your inputs have already been spent... I attempted to broadcast this transaction and got: "Missing inputs (code -25)" Because those inputs are now "missing" (ie. confirmed in other transactions), this transaction is no longer valid. I would suggest the following:

- Make sure Bitcoin Core is fully synced.
- Shutdown Bitcoin Core.
- Make a backup of the wallet.dat
- Start Bitcoin Core using -zapwallettxes command

It should remove ALL transactions from your wallet, then rescan the blockchain for "confirmed" transactions that relate to your wallet addresses. Once it has finished, you should see all your "confirmed" coins... and this "impossible" transaction should no longer appear.

You can then shut down Bitcoin Core and restart normally (ie. WITHOUT the -zapwallettxes command).

That address has received 0.00051802 BTC in transaction: 4b66df42662cf840d8853b8133b3700b8480547840a8b1580097cc81193d3704

The transaction was confirmed in block: 498629 ( 2017-12-10 21:49:15 + 27 minutes ) This time is UTC, so it was confirmed approximate 2.5 days ago.

The coins should be available in your wallet.

It is not only possible... but it is quite common.

Previously, Litecoin generated "3" addresses... there was a fork that changed to the newer "m" addresses to try and prevent this issue... but they still needed to retain the ability to send to "3" addresses for backwards compatibility.

Fortunately, there IS a solution: https://www.reddit.com/r/devbitcoin/comments/7f4m39/accidental_ltc_to_btc_address_on_ledger_nano_s/?st=jasludh0&sh=213007dc

PM me if you need any help.

Just to clarify... The "Bump Fee" option (aka. "Replace-by-Fee")... can ONLY use coins from outputs which are generated in the transaction you are trying to increase the fees on. (This applies to ALL wallets that allow RBF)

Your first transaction had outputs of:
16hUPiK8Q7ZXYAqUZdoDsqVkq249jkyXmR - (Spent) 0.01073038 BTC
14WoZyqvowrn3rFTxLdVNNSdTyH2mXphjP - (Spent) 0.0051 BTC

I'm assuming you were sending 0.0051 BTC... and 0.01073038 BTC was the "change". Under normal circumstances, you could have elected to use some of this 0.01073038 BTC to bump the fee (NOTE: you can't use any other coins from your wallet, even if you had 100 BTC in your wallet... you're limited to the coins from the transaction output)

However, as you had already "spent" the change of 0.01073038 BTC from your first transaction by creating and broadcasting the 2nd transaction... you had nothing left to bump the fee as those coins were spent (even if not confirmed)

You MIGHT have been able to bump the fee on the 2nd transaction assuming you had not spent whichever one of these outputs was your "change" from the 2nd transaction:
1GXDWPUzbZYHYc3HUT39V4ydysRmPXXncB - (Spent) 0.0091 BTC
1B56iMVo5oejJq4Z5adE5eW3HWLcdYF5Nx - (Spent) 0.00155019 BTC

All of those addresses are empty... and have been since 2012... what exactly are you trying to achieve?

As for the "read only" addresses... it sounds like you imported some "public addresses" (ie. NO private key) creating "watching only" addresses... so you could see transactions/balances, but unable to spend.

Bitcoin Core will only import "WIF" private keys ie. the individual private keys that start with "5", "K" or "L"... you can't import a master private key (aka "xprv").

So, if you use the Mnemonic Code Convertor you have to copy all the private keys from the bottom of the page. You'll need to figure out exactly which addresses actually have coins and import those (Don't forget your change addresses!!)

If you have a LOT of private keys to import, your best option is probably to just send all the coins from b.info to Bitcoin Core using a standard transaction.

I think he was specifically referring to the user who said that backing up addresses/private keys was a good idea. The issue being that you could get into the situation where you are missing certain addresses/private keys...

Having the seed means you will be covered no matter what. Of course, having BOTH the seed and addresses/private keys is probably "safer"... but really unnecessary. In summary, in my opinion:

Addresses/private keys only = Potentially dangerous
Seed only = Perfectly Adequate
Seed+Addr/Priv keys = Overkill

I believe the newer versions of "non-HD" wallets will actually run a keypool of 1000

Anyway, advantages of HD include only ever needing to take one backup... you do actually get the "master private key" if you dumpwallet, so theoretically, you could write that down and store it offline and then be able to recover your entire wallet by importing that into a compatible wallet.

However, in the limited testing that I did, with the "seed changes on password change" system... if you change the password (or set one)... the OLD master private key is not stored... only the addresses

Also, I guess having an HD wallet would make it easier to use your wallet from multiple locations and not need to worry about it generating different addresses? (assuming you don't change the encryption password! ) It probably makes creating "watching only" wallets easier too...

Whether or not you consider any of these advantageous is really dependent on your particular use cases.

This website appears to be a SCAM... being spammed by a bunch of newbies... the official site is www.coinomi.com and they have ONLY (officially) released a wallet for Android

This website appears to be a SCAM... being spammed by a bunch of newbies... the official site is www.coinomi.com and they have ONLY (officially) released a wallet for Android