The older (non-HD) Bitcoin Core wallet.dat's would maintain a keypool of around 100 private keys/addresses. Nowadays, the default keypool size is 1000... so it could be worse!

And yes, they are all addresses that are generated from keys in your wallet.dat file.

As PawGo suggested, the best method to ensure you don't miss anything... is to simply export all] the private keys from your wallet.dat and then import them into another wallet. That way the wallet will be able to find all your coins for you and you won't accidentally miss one.

Note that you will need to get the private keys from your wallet.dat (the "sec" field in the pywallet output is the WIF format private key, "hexsec" and "secret" are hex format)... just importing addresses will mean that you can see the coins, but you can't spend them.

I don't see how some users are more equal than others? It's not like people running the latest version magically get priority for their transactions or lower fees simply because they are on a specific version of the client. The network consensus is still the network consensus... and any changes that have been made so far have been "backwards compatible".

So, if you want to run your old version, run your old version. No one is forcing you to change. You have the choice. However, like all choices, they come with consequences... in this case, running an old version means you get an "annoying" (but harmless) warning message show up. It doesn't affect the usability or functionality of your client in anyway... or your ability to "help" with maintaining the decentralisation of the network.

There are plenty of alternatives to simply upgrading to the lastest version of the software you're already running. You could even choose, as ETFbitcoin suggested, to run a completely different implementation... or you could even modify your current one to your liking by altering the code to remove the message and recompiling.

Thankfully...

Can you imagine what would happen to the mempool, network load and fees if someone created a Bitcoin version of "CrypoKitties"

That address hasn't been "Active" (ie. spent coins) since 2011. It was most likely a deposit address on one of the old exchanges like Mt. Gox or something. Mt. Gox started in July 2010 too... which would line up with when you say you sent the bitcoin to the "investor"

That is expected as the addresses you exported are the one from your wallet. However, if you were to import those private keys into another wallet or use a utility like bitaddress.org, you will find that the private keys do not match the addresses you have exported.

This is because the addresses in your 2FA wallet are "p2sh" (you can see in your first screen shot). P2SH = Pay to Script Hash. In this instance, the "script" being used is a multisig script that requires a minimum of 2 out of 3 private keys to be able to sign... as that is effectively what an Electrum 2fa wallet is... a 2-of-3 MultiSig.

Without the other keys (either from your seed and/or TrustedCoin), you will not be able to sign the transaction to spend your coins.


Best of luck with TrustedCoin, hopefully they can help!

Well, in any case, if OP has managed to get as far as "decrypting" the wallet backup file using openssl... then they can very easily load their wallet/keys into a BIP39 compatible wallet that allows you to specify the derivation path (such as Electrum). If you simply open the "decrypted" file in a text editor, you should see "org.bitcoin.production" (as you say you are recovering from a PROTOBUF wallet)... and then shortly after that, you should see 12 plain english words... this is your 12 word seed.

Here is an example of a decrypted wallet backup:



If you load that seed into Electrum... ("New/Restore -> Standard Wallet -> I already have a Seed -> Enter seed, click options -> select the BIP39 seed option) and then on the derivation path screen select "legacy" and then set the derivation path to: m/0' ^[1] then it will load up all your old legacy addresses.



 







[1] NOTE: this derivation path is slightly different to the one used by ian coleman's tool below because of the way Electrum works

---

---

Alternatively, you can put the seed into iancoleman's BIP39 mnemonic code convertor... click the "BIP32" tab, and then select the "MultiBit HD" option from the "Client" dropdown box (This will automatically set the derivation path to m/0'/0 for you). Then it will show all your legacy addresses/private keys at the bottom:


All your keys displayed below:

Glad you got there in the end... unfortunately, the way that GPG works and displays the results of checking digital signatures can be a bit confusing for new users. Especially when you see a big "WARNING" about a key not being certified with a trusted signature etc.

Also, good on you for taking the time to verify the signatures for Electrum, it is a very important step to prevent loss of your coins!

You don't seem to be understanding what people are telling you.

You were scammed! You are not going to get any money or any bitcoins. You sent $56 to a scammer. They tricked you into sending them money. They were never going to give you any bitcoins, ever!

Wait what??!? It only recovers SegWit addresses and does not also check the legacy addresses generated from the backed up keys for transaction history etc??!?

That is ridiculous!

If you click the blue "Mostra il registro di controllo" (show the audit log) link in your 2nd screen shot... you will see the "raw" output of the GPG log.

Here you will see that there are definitely "good signatures" ("buona firma")... something like this:

Yeah... I was equally confused by the whole "they converted my BTC to SEK and then transfered the BTC the next morning"... That seems very very odd, so I'm not sure we're getting the complete picture of exactly what happened there, but it isn't really of great importance as it would appear that the OPs Electrum wallet was compromised and the BTC is gone.

Another "seed stored digitally" scenario

I concur. The whole "request payment" feature and the expiry time stuff really needs some sort of rework. The number of "HALP!!!!111!! MY PAYMENT EXPIRES IN 1 HOUR"-type threads we get from people that generally contain statements like "I just installed Electrum and have never used it before" would indicate that it is indeed quite confusing for new users who are attempting to receive their first Bitcoin payments.

The question remains tho... how should it be changed to make it less confusing whilst maintaining the same functionality?

I would have thought that having it unpowered for extended periods of time might be tempting "bit rot" in a flash memory based device. This article, although it is specifically talking about SSDs, suggests exactly that: https://www.techadvisor.com/how-to/storage/bit-rot-slow-death-of-hard-drives-ssds-3796137/

Although your message implies you may have plugged it in occasionally?

This is quite a common concern for a lot of people who don't understand the sheer vastness of the "keyspace" being generated by this "fixed and known" list.

People will quite happily secure their online banking or whatever with a 10-12 character password... if you use UPPERCASE + lowercase + numbers... that's 26+26+10 = 62 possible characters... then we can throw in the 33 ASCII printable "symbol" characters like ~!@#$%^&*()_+ etc... and all up it would be 62+33 = 95 characters in your "fixed and known list".

So, a 12 character password using this list would be: 95 * 95 * 95 * 95 * 95 * 95 * 95 * 95 * 95 * 95 * 95 * 95 = 540360087662636962890625 possibilities.

The 2048 word list that Electrum uses means that your "alphabet" has 2048 characters... so that means your 12 word seed is effectively a "12 character password where the alphabet has 2048 characters" in it. Giving up this many different seeds: 2048 * 2048 * 2048 * 2048 * 2048 * 2048 * 2048 * 2048 * 2048 * 2048 * 2048 * 2048 = 5444517870735015415413993718908291383296 possibilities...

monospaced to illustrate the difference in length of the 2 numbers.

If you're not worried about someone hacking your 12 character password, you don't need to be worried about someone hacking your 12 word seed.

If your Bitcoin Core is fully synced and unpruned... and Armory is communicating with it OK (showing as 'Online' and the number of blocks is ~710227), then everything is running properly. So, if you then restored your Armory wallet using the backup you have... and it's "Empty", then you may have the wrong backup.

Do you see any transaction history in Armory at all? Or is it completely blank?

This honestly sounds like it could be a "large number of UTXOs" issue. The Nano S is notoriously problematic if you're trying to sign a transaction that includes a large number of inputs. It'll take a long time for the transaction signing to complete and/or time out etc.

I would be interested to know if the OP's transaction was like this.

Unfortunately, that isn't the correct log file... would need to see the contents of armorylog.txt (and/or dbLog.txt) to try and trouble shoot your "offline" errors.

No. Only if you run into any issues attempting to use the older versions... But you should find they'll still enable you to send/receive just fine.

Also, all three apps you have are essentially "Bitcoin" based... so Bitcoin is the "big" one... it is 40kb. The other "bitcoin-based" apps like Bitcoin Cash, Bitcoin Gold, Litecoin, Dogecoin etc are all 2kb. So, if all your apps were bitcoin based, then theoretically, you could run like 40 apps


Not really... unless someone were to say, it's Version 2.0.0:


Not that it really makes any difference... you need to connect to your laptop to use it/update the apps anyway... so I'm not sure why you care? If it is there to update when you open Ledger Live and connect your device... then click "update".  It really isn't as difficult as you seem to think it is

Ouch... Cobo Vault wasn't that old was it?

Launched in Nov 2018 apparently... so less than 3 years and they "killed it", by rebranding to another company and basically releasing the same thing, but incompatible??!?

What a clusterfuck.

It's probably the secret 5G transmitter that is sending all your private keys to Bill Gates so he can fund the NWO

/s


Seriously tho, that seems like pretty poor battery life... that's somewhat unfortunate for a $200 device.