Honestly, I've never seen a bitcoin wallet that uses the .pfx format... I'm not entirely sure that the OP even has a bitcoin private key. They seem to think they exported it from a mywallet.pfx file to .pem.

But in all the research I have done, I've only found reference to bitcoin and .pfx in a "presentation" here: https://github.com/Dreammaster13/blockchain-for-devs-book/blob/master/content/part-1-blockchain-networks-concepts/wallets/wallet-apis-and-libraries/wallets-apis-and-libraries.md#other-wallet-formats

Where it is mentioned as an "other" type of wallet/keystore


Do you have a wallet.dat or a .pfx file? and what makes you think that the .pfx is a wallet file?

Yes... The i7 isn't bad... the 8gigs isn't ideal (like my setup), but it will definitely be the 5400rpm causing the largest bottleneck for you at the moment. A 7200rpm HDD is pretty slow, and a 5400 will be even worse

bc_key doesn't work with "encrypted" wallet.dat files...


A standard "wallet.dat" (from Bitcoin Core) is not in a format that openssl can read/understand. A wallet.dat is a BerkeleyDB binary file... and if the wallet.dat has a password  on it, then the private key data will be encrypted.

If you have a wallet.dat, the best way to recover data from it is by opening a copy of the wallet.dat with a fully synced Bitcoin Core... attempting to open it with other utilities may damage the file or just not work.

It you have the "3 gears" and it says unconfirmed... and you have the "green dot" in the bottom right corner, then the transaction is "broadcast", but most likely still "unconfirmed". The recipient might have a "receive" transaction showing in whatever wallet they are using, but the transaction is not "complete".

If you right click on the transaction showing as unconfirmed, then select "Copy -> Transaction ID"... and then search for that TransactionID on one or more of the following blockexplorers, what do you see? Does it say the transaction is confirmed or unconfirmed?

https://www.blockchain.com/
https://btc.com/
https://blockchair.com/bitcoin/
https://live.blockcypher.com/btc/
https://blockstream.info/


And I'm a little confused by your description of what you've attempted to do and what has actually happened...

How many transactions have you attempted to send since you updated? And how many do you see in your transaction history?

I agree... stick with Win10. I wouldn't even bother attempting to do anything with the old Windows 7 Laptop. It's only really going to cause more issues


Correct. You just use "Standard Wallet -> I already have a seed" during the wallet creation process. Then input your 12 word seed and Bob is your mother's brother! NOTE: you won't see any transaction history (as the wallet is "offline"), but you will be able to see the addresses and confirm they're the same.

So, download and verify Electrum from: https://electrum.org/#download  You can follow abdussamad's very useful guide on how to verify your Electrum download using Windows here: https://bitcoinelectrum.com/how-to-verify-your-electrum-download/

Once you have it installed on the airgapped machine, and the wallet restored using your 12 word seed, you can just goto "Wallet -> Info" and get your "Master Public Key" (aka XPUB) from the window there and then use that xpub on the online Win10 machine to create the "watching-only" wallet (Standard Wallet -> "Use a Master Key" option during wallet setup)

Then you'll be able to see the full wallet history on the online machine... and you can create a transaction (click "Export -> to File" when prompted) and save the ".psbt" (partially signed bitcoin transaction) file... copy the .psbt file to USB to transfer to the "offline" machine, open the .psbt file on the "offline" machine using "Tools -> Load Transaction -> From File"...

Then sign it... "export -> To file" and this time it will be saving a ".txn" (completed transaction) file... copy that .txn to USB, transfer back to "online" machine... open in Electrum using (Tools -> Load Transaction -> From File)... double check everything looks good and "Broadcast"!

It seems that you may not understand the "workflow" in Electrum for creating/sending transactions... and are clicking things that are not doing what you think they are. There are some slightly "confusing" parts of the Electrum UI/UX and it may not be obvious to new users.

For instance, on the "Send" tab, when you click "Pay"... it doesn't necessarily immediately send funds. You need to select the fee using the fee slider (or inspect the transaction details using "Advanced"), then enter a password (if required)... before clicking "Send".

However, if you use the "Advanced Preview", you need to click "Finalize", then "Sign" (enter password if required), then click "Broadcast".

---

If you click "save" on the "Send" tab, then it just adds an "Outgoing payment" and marks it as "unpaid" (you need to right click and select "Pay" to actually get this signed/broadcast etc)

However, if you use the "save" on the "Advanced Preview"... it saves a local copy of your transaction in your "History"... shows an "unconfirmed" amount being sent, but it is only on your PC. Nothing is sent, nothing is "broadcast" to the network:

---

As for "bump fee", that should generate a completely new transaction (different TransactionID etc)... and the original transaction should be removed.

So what exactly do you see in the "Transaction History" for your wallet? Do you see the test transaction you sent with a green tick?

You'd be better off seeking assistance on a phone-centric forum like XDA Developers: https://forum.xda-developers.com/

They have a Galaxy S9+ specific section here: https://forum.xda-developers.com/c/samsung-galaxy-s9.7530/

I would recommend that you tell them you specifically need to recover certain "App Data" and not just pictures/videos etc. A lot of the popular "data recovery" apps focus only on retrieving your texts/pics/vids etc and recovering actual application data can be a bit trickier and require more work that installing some type of "AndroidPhoneDoctorDataRecoveryExtractor2020" type app.

Ok... I think I can see why you have two different copies of the blockchain.

In Armory settings, you have "Let Armory run Bitcoin Core/bitcoind in the background" checked don't you? If my assumption is correct, what is happening is that the "bitcoind" that you see in your task manager (grouped under the Armory process) is being spawned by Armory and is using "-datadir=E:\Bitcoin".

However, when you run BitcoinQT manually, it appears to be using "E:\Bitcoin\btc". You can confirm this by running BitcoinQT (without Armory) and in the "Window -> Information" menu, you will see "datadir" and "blockdir"... what are these set to? If my hunch is correct, is will say "E:\Bitcoin\btc" and "E:\Bitcoin\btc\blocks".

If that turns out to be true, we can reconfigure either Bitcoin Core (or Armory) so that both are pointing to the same data folder... then you'll be able to remove one of those folders and reclaim some "wasted" storage space

No, you can't... and I admire your desire to "get it right" without rushing into things


I forgot to ask... what CPU do you have? and are you storing the Bitcoin Core data on an HDD or SDD and is it internal or external?

I know you're just making a joke... but I have Edge (built on Chromium I believe) running pretty much constantly with at least 5 tabs (including Gmail), more often 10+ tabs... and a Bitcoin Core full node, Electrum + Local Electrum Server in an Ubuntu WSL instance, Steam, Discord, BNet Launcher and a bunch of other stuff running... all on my 8 year old i5 with 8 Gigs of RAM

And I don't have any issues running Armory.

Doing a "normal" startup:



After a "rebuild and rescan databases":


RAM usage was below 700megs during the entire "Building Databases" phase. Took ~50mins. Transaction scanning still going Like I said... it's "a bit slow"


It's not taking up ludicrous amounts of RAM, because I simply don't have that amount of RAM in my system. I'm sure if I was running 16 or 32 gigs, then it would take as much as it could get it's hands on. Applications using large amounts of "free" RAM isn't necessarily a "bad thing"™... if nothing else needs to use it

Try using the getaddressinfo command:

Right near the top of the output you should see "ismine". If that is "true" then the private keys that the address is derived from is in your wallet.dat.



NOTE: If you have multiple wallet.dat's "open" in Bitcoin Core, make sure you have set the correct wallet selected in the dropdown menu in the console window

Not as far as I can see... there are no "import" options within the wallet app. When you first setup the wallet, your options are to create a new wallet (gives new HD based wallet with 12 word seed mnemonic)... or you can restore your wallet from a 12 word seed mnemonic (or a coinbase backup stored on google drive??!? )

You don't need to do anything complicated like coin control and selecting UTXOs or Addresses if you don't care about linking all of your UTXOs together.

To consolidate, simply goto the "Send" tab in Electrum, Enter the address from your wallet that you want to consolidate all of the coins to, then click the "max" button... then click "Pay" and sign/broadcast the transaction. All of your UTXOs will be consolidated into one.


I'm not sure what you mean by a "single output point"... do you mean a single address that all coins are sent to? Or a single "UTXO" that is created whenever you spend coins and get change?

Every time you receive coins, it creates a new UTXO... even if they're all in the same "address", they are all separate and unique UTXOs. The only way to maintain a single UTXO is to spend "everything", every single time you create a transaction, and receive the change back as a single UTXO. However, as soon as you receive any more coins, you're going to have multiple UTXOs again until you create another transaction that consolidates everything again.

You can do the same thing in Electrum, but it's somewhat "manual". We can simply (ab)use the "pay2many" functionally... on the "Send" tab, you simply enter the external address you are wanting to send coins to and the amount to send to that address... and then you create an entry on the 2nd line with the address from your wallet you want all the "change" to go to (as a single UTXO), and then you use ! as the payment amount, like this:


In this example, we're sending 0.1 BTC to "addressYouAreSendingCoinsTo"... and our wallet address "yourAddressForChangeUTXO" is going to receive the leftover balance (- transaction fee) as a single UTXO. After we send the transaction, we'll only have one UTXO in the wallet.

If you don't have the 12 word recovery phrase, then your only option is to remember what your encrypt password was.

Depending on the .aes file, you might be able to extract a hash from the file and use something like hashcat to bruteforce it, but you'd need to have some idea of what the password you used was (password length, types of characters/numbers/symbols used, random chars or words? etc)


Failing that, I found this link for the "bitcoin.com wallet", which was a fork of CoPay... they say that the wallet backups were encrypted using SJCL... and that you can use the online demo to try and decode it using your "password".


Obviously, the usual caveats of using "online" pages with sensitive data like passwords/keys/wallet files etc apply You should be able to save the page and run it offline.

Please don't perpetuate the "myth" that these rebroadcasting services do anything to speed up confirmation time. They literally don't do anything useful.

All of them are just ad-revenue generators... or outright "scams" looking for donations from users who don't know any better.

That format is incorrect. You've got an extra "{" in the middle... and some extra stuff on the end... it should just be:
Obviously, you fill in the "master_private_key" and the "wallet_password" with the info you have from your original wallet.



NotATether mentioned a couple of posts back that they wrote the wrong command... they should hopefully go back and edit the original post... the correct command is just:

You need the private keys to be able to "claim" the fork coins... essentially, you need some way to  get those private keys into a forkcoin wallet application.

The options are:

- If there is a compatible [forkcoin wallet], simply use the old wallet file from your Bitcoin wallet and open it with [forkcoin wallet]
or
- Export the private keys from Bitcoin Core, then import them into [forkcoin wallet]
or
- If you have a wallet that supports 12/24 word seeds, you can recreate your wallet in [forkcoin wallet] by restoring a wallet using your 12/24 word seed

---

---

You currently have a Bitcoin Core wallet.dat. This does not support 12/24 word seeds, so that option is not available. Instead you can:

NOTE: you should do the following after you have created a new_wallet.dat in Bitcoin Core and moved all your BTC to new_wallet.dat!

Option 1. Install BitcoinABC & BitcoinSV "node" software (like Bitcoin Core, but built for BCH/BSV).

- You will need to download and sync each blockchain for each fork that you want to claim. This will require significant on disk storage space and time.
- Then, using BitcoinABC/BitcoinSV node software, open your (now empty) old wallet.dat and let it rescan
- It will find any/all BCH/BSV that is controlled by the private keys in your old wallet.dat
- Do what you want with the BCH/BSV that you find (send to another wallet, sell on an exchange etc)


Option 2. Install "lightweight" SPV wallets compatible with the forkcoins and import private keys.

- As per LoyceV's message, your options are things like:

• Electron Cash for BCH - https://electroncash.org/
• Coinomi (should do BCH/BSV) - https://www.coinomi.com/en/
• ElectrumSV for BSV - https://electrumsv.io/
• Electrum ABC for BCH-A - https://www.bitcoinabc.org/electrum/

Next, you need to export your private keys from the old wallet.dat. You can do this very easily using the dumpwallet command on the Bitcoin Core console. This will generate a text file that contains ALL your private keys.

Once you have successfully exported your private keys, you then need to import them into the lightweight BCH/BSV wallet that you installed. How you actually achieve this depends on the wallet you're using. Most have a menu option that allow you to "import", or in the case of the Electrum "clones" (ElectronCash + ElectrumABC), when you create the wallet, there is a "Import Addresses or Private keys" option.

You can't use 2FA with BCH/Electron Cash.
You can only use 2FA with BTC/Electrum.

What are you wanting to continue using? BCH or BTC or Both?

Unfortunately, that is correct.

Fortunately, the network is quite quiet at the moment... transactions with just 5+ sats/byte fees are getting next block confirmation etc. So, you're not having to pay "outrageous" fees right at this point in time

You could... but the issue is that you still need to download the forkcoin blockchain if you want to use the old wallet.dat with the forkcoin wallet... (and in the case of BCH or BCHA or BCHN or whatever the hell it's called these days), that is quite a significant amount of data (not quite as big as Bitcoin Core, but it's still a couple of hundred gigs ).

If you create a "new_wallet.dat" in Bitcoin Core, then move all your BTC from your old wallet.dat to an address in "new_wallet.dat"... then you could simply use the dumpwallet or dumpprivkey on the old wallet.dat file to get the private keys you need.

You can then use any of the wallets that LoyceV listed above to import those keys and get the fork coins.

The important part is to move all your BTC to a completely new wallet.dat first... and then start messing about with claiming forkcoins.