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

Which doesn't work for Electrum 2FA wallets... as they are MultiSig.

Coinomi is ONLY useful if the address you have the coins in starts with a "1"... if your address starts with a "3" (either 2FA or MultiSig)... you CANNOT use Coinomi at this time (I believe they said they were working on MultiSig solutions? )

ALSO, 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

Sure... whatever you say


There is no loop that I can see, but excessive use of resetseed() and resetstats() which no doubt requires a bit of extra reading and writing... Also, as Seuntjie has pointed out, having 8 bots making 5+ bets second is going to require a LOT of reading/writing to disk... that's 40 entries/second being made to disk...

If your hardware isn't up to, run less bots.

There are a couple of possible causes:

1. You have non BIP39 words written down in your 24 words.
2. You have BIP39 words, but in the wrong order.
3. You have the wrong BIP39 words.
4. The firmware is bad.

#1 is easy enough to check... do as bob123 suggested and make sure all your words are in the BIP39 wordlist

I've seen cases of #2 caused by someone filling the recovery sheet in the wrong order... it is two columns of 12 numbers, (ie. 1-12 and 13-24 going DOWN then across) like this:

1    13
2    14
3    15
4    16
5    17
6    18
7    19
8    20
9    21
10  22
11  23
12  24

... but some people write their seed as 12 rows of 2 (ie. going ACROSS then down) on the recovery sheet...

1    2
3    4
5    6
7    8
9    10
11  12
13  14
15  16
17  18
19  20
21  22
23  24

but the recovery sheet is still numbered in columns going down... so when they are asked to type it in, they get the words in the wrong order!!

#3 is pretty common, as there are a LOT of very similar words in the word list... kid, kind, kit, kite, then, them etc. It can be VERY easy to get these mixed up. gurnec's seed recovery can help with this: https://github.com/gurnec/btcrecover/blob/master/docs/Seedrecover_Quick_Start_Guide.md

#4 would be relatively rare... one would assume Ledger would do quite thorough testing before releasing a new firmware to prevent this sort of thing from happening. Although, given that your update didn't go well... it is possible the firmware is corrupted in some way. Maybe try and redo the firmware update so that you can be sure there are no issues.

Probably because a. your profit is not reaching a level relative to the balance where the calculations result in a negative value very often (in combination with the long losing streaks required looking at the script)... and b. it'll stop whenever it occurs, so instead of seeing a series of negative bets (which would occur if the bot kept running), you see 1.

Chances are this is the same thing... an altcoin wallet. Don't check the address on the altcoin chain... check the transactionID.


It isn't a bug... if you're running a wallet file from a different blockchain (most likely forked from bitcoin so compatible at a technical level), these transactions you see are actually stored locally in the wallet, but obviously, not on the BTC blockchain... so Bitcoin Core marks them as unconfirmed.


The blockchain doesn't need correcting.

Guessing you didn't see the thread titled: [TUTORIAL] How to extract Bitcoin Gold from a 2fa Electrum Wallet [STEP BY STEP]

and before you ask... no, there isn't really an easier way to get it out... unless you want to pay someone to do it for you.

It's entirely possible that you received 3 transactions that either did not confirm, or were double spent, or were in orphaned blocks... If I had to guess, I'd guess possibly orphaned blocks as the likely culprit... SopaXTs idea about it being an altcoin possibly has merit as well.

Anyway, that address (1Jxn...) has ZERO transaction history... so you're effectively chasing ghosts. The transactions no longer exist and I seriously doubt you'll be able to locate them... most likely because the inputs have since been spent in other transactions.

As always, the blockchain has the final say... if that TXID does not exist on the blockchain, then it doesn't exist.

Do you see the address you sent coins to when you open the wallet.dat on your PC?  If so, is that version of Bitcoin Core fully synced? It may not show your coins unless you have downloaded the full blockchain (150+ gigs), assuming you sent the coins to the wallet recently.

"Help -> Debug window -> console"

Then type: listaddressgroupings

and press enter. See if you can see the address you sent coins to.


You can always dump the private keys from the wallet and then import the private keys into a lightweight wallet like Electrum (https://electrum.org/#download)

And this is precisely the reason that Electrum does NOT let you import private keys into a seeded wallet...

You have restored an HD wallet, but your 12 word recovery phrase, was only backing up the wallet address with no/little funds... It would appear that the address WITH the funds was an imported private key that is not able to be recreated by the recovery seed.

There is one thing you should try before giving up tho... try using an OFFLINE copy of: https://iancoleman.io/bip39/

Put your 12 word seed in, click the BIP44 tab and then have a look through the generated addresses looking for one that matches the address with 0.28 BTC. I would probably not bother looking any further than the first 100.

If you don't find them there, change the "External/Internal" value to 1... so the Derivation Path should read as m/44'/0'/0'/1 and see if you can find the address there... again probably not worth looking past 100.


If that doesn't work, you'll probably need to contact b.info support and ask them for assistance.

You didn't read what I wrote did you? "Good" users will then check https://bitcoinfees.earn.com/ and https://btc.com/stats/unconfirmed-tx to get an idea of how busy the network is and what sort of fees are required to get their transaction confirmed in a reasonable amount of time"

You're more than welcome to try zero fees... then watch your transaction get rejected for not meeting the minimum relay fee... and/or stuck for multiple days not confirming because you chose a fee that was too low.



"WHAAT? you mean I have to *work* for my #freeMoney??!? #OUTRAGEOUS!!?!" Sooooo much work downloading a couple of applications and installing them...



You could try Exodus (HUGE default fees which you can't change)... Jaxx (buggy as hell)... Coinomi (Possibly mobile only, don't think the desktop version is released yet)


And I'd like my wallet balance to to say 1000 BTC... I'm guessing both of us are going to be disappointed this week

NOTE: before you start... make copies of the wallet files and work on the copies!

Maybe download the most recent MBC (https://multibit.org/releases/multibit-classic/multibit-classic-0.5.19/) and see if you can open the wallet... try doing "Export Private Keys" (DO NOT set an export password), then open the text file and see how many keys you get... if you just get one, you're probably screwed, as in that case, the receiving address you see is the only one in the wallet... and you say that doesn't have your BTC.

However, if you get several private keys, trying importing them into Electrum (https://electrum.org/#download) and see what you get.

Unless you have a good grasp of commandline scripts, Python, AES-256 encryption, Google Protobufs etc... you're asking for trouble

Which just proves that Armory is looking in the wrong place for your Bitcoin blocks folder... for some reason your --satoshi-datadir command is not working properly. Do you have something setup in armoryQt.conf in C:\Users\xxx\AppData\Roaming\Armory?



They don't actually affect things... it's just a quirk of using languages "designed" for Linux (which uses /) on Windows (which uses \)



No... it means that it got shutdown (most likely you closed Armory?)... so it was just tidying up some connections/processes before shutdown.

That's like saying your letterbox is faulty because someone sent you a parcel with insufficient postage and the Post Office delayed it.

You do realise that the RECEIVING wallet has absolutely NO control over the fees right? If the transaction was sent with a low fee, blame the sender... they're the one who set the transaction up and set it with a low fee. As a receiver, the ONLY recourse you have is to attempt a "Child Pays For Parent".

This is NOT an issue with Electrum.

Sounds like you've set up a 2FA wallet... and ignored all the warnings and information about how you have to PAY for the 2FA service: https://api.trustedcoin.com/#/electrum-help

Your choices are either click the little blue shield in the bottom right corner and select the cheapest option available (if you want to retain 2FA functionality)... OR you can simply restore your wallet from Seed... and select "Disable" when prompted if you want to "keep or disable" the 2FA functionality.

This will put 2 of the 3 private keys in your wallet, and you'll be able to send transactions without using TrustedCoin (ie. NO 2FA)... but you won't have to prepay for the 2FA functionality.

Did you read the links? specifically the Coin Analogy one? https://en.bitcoin.it/wiki/Coin_analogy

When you receive bitcoins in multiple transactions, they don't all merge into one balance, like they would with a bank account. They remain as separate pieces. For instance, say you received:

0.1 BTC
1.0 BTC
0.7 BTC

You now have THREE coins, totalling a value of 1.8 BTC. If you now decide you want to send out 0.012, your wallet will generally (but not always) use the smallest coin it can, that covers the total to send + transaction fee.

So, your wallet picks up the 0.1 BTC coin, and uses that... breaks off a 0.012 piece and a small bit for a fee (0.000853)... and then puts the rest (0.087147 BTC) back in your wallet as change.

You now have:

0.087147 BTC
1.0 BTC
0.7 BTC

If you now wanted to send 0.1... your wallet would mostly likely use the 0.7 BTC coin etc etc...

So, in answer to your question:
At some point, you would have received a transaction that sent 0.1 BTC to your address (or wallet)... so you have a coin worth 0.1 BTC sitting in your wallet, which your wallet decided to use to send out the 0.012.

Electrum does NOT store BIP39 seeds in the wallet files it creates when you restore from a BIP39 seed (like the one from MultiBit HD)... instead, it ONLY stores the Master Private Key (aka "xprv") in the wallet file.

The downside is that you are unable to "view" your seed using the menu option. You will need to retain your offline copy of the seed.

If this bothers you, do as instructed above and create a "native" Electrum seed using: File -> New\Restore -> Standard Wallet -> Create a new seed

Jerry... I admire your thirst for knowledge... but how about you actually go visit the Ledger support site and read ALL the articles they have there: https://ledger.zendesk.com/hc/en-us

Almost ALL of your queries about the Ledger are likely to be answered there.

For instance, the supported coins one links to the ERC20 token list: https://ledger.zendesk.com/hc/en-us/articles/115005439585

It's probably a quirk with the way it handles BCH... Because a lot of people got BCH from the fork, they had to setup a method where you could see BCH on m/44'/0'/0' instead of the actual derivation path for BCH of m/44'/145'/0' .... so I'd assume it's because you selected "Bitcoin Cash" -> "Main"... this effectively shows your BTC account, but listed as BCH. You'll probably notice all your transactions are identical to your BTC ones.


It's all a bit confusing, but was setup so you could easily get the BCH stored on the BTC addresses. I believe the correct one for the "BCH" specific account is "Bitcoin Cash" -> "Split"