Blockchair recently received it
So did Blockcypher
Blockchain.com is showing "original" date of mid Feb

For the record it is in the mempool of my local node...


It's possible the wallet is rebroadcasting the transaction whenever you open Mycelium on your device. It seems your transaction was recently rebroadcast (within the last 12 hours). This means that some nodes might retain your transaction for 14 days from today.

If you want it to cancel out and for it to stop being rebroadcast... you may need to wipe the data for Mycelium (make sure you have a working backup first!!!), and then leave it closed for at least 2 weeks... If your transaction is not confirmed in the meantime, after your transaction disappears from all the major blockexplorers, you should be able to open Mycelium and restore your wallet from the 12 word recovery phrase.

The transaction should have "dropped" and you should see all the funds available in your wallet.

Not exactly an "ideal" solution, but if you can't or don't want to CPFP, then it's about all you can do to try and stop your transaction from being rebroadcast by the wallet, as there is no "abandon transaction"-type functionality in Mycelium.

What is the exact form of the address from Blue wallet that you are attempting to send to?

Mycelium supports all the standard Bitcoin address types - Legacy ("1"-type), P2SH ("3"-type) and bech32 ("bc1"-type) addresses...

I do knot that Bluewallet also supports using Lightning Network... so, I suspect you might be attempting to send to a "Lightning" wallet from BlueWallet... Mycelium is not compatible with the Lightning network at this time.

The only other thing I could suggest is exporting all the "unused" keys from Armory... and importing them into Electrum to see if it finds something that Armory is not... but I would say that the chances of that yielding different results are relatively low

Note that it is possible you may have been using one of the "Armory Specific" P2SH-P2PK addresses... and if you try and import those keys into another wallet, it won't create the same address as this address type is unique to Armory as far as I'm aware. Regardless, Armory should have found the transaction history for any of these types of addresses.

To check if that is the case, you'd need to look at the addresses generated in Armory (not the private keys), then check those addresses on a block explorer to see if they show any history/balance etc.

The ending slayed me!
Bwhahaha...


I love the way people think "outside the box" (if you'll pardon the pun ) like this:
That's genius!

Indeed... It's possible that the "old" keys are buried in amongst the "bc1" keys etc... without an address for reference it is a little bit difficult to suggest a search term though.

If there are no keys showing a legacy address, then it's possible that this wallet.dat is actually not the wallet.dat that your friend thinks it is. For instance, depending on how your friend setup and ran Bitcoin Core, it may have created a completely new (empty) wallet.dat on first startup and populated the keypool etc... and your friend has simply mixed up the newly created .dat with their old .dat file.

The other thing that concerns me is that it has an xpriv (Master Private Key)... which means it is an "HD" wallet built from a seed... from memory, Bitcoin Core does not automatically convert a "non-HD" wallet into an "HD" wallet... you need to explicitly use the -upgradewallet command or the upgradewallet RPC command in 0.21.0.

With regards to using Electrum to recover your wallet. You will need to click the "Options" button on the seed entry screen, then select the "BIP39 Seed" option. After that, you should see the text "BIP39 (checksum: ok)" appear next to the "Options" button and the "next" button should be activated.

If you don't see "BIP39 (checksum: ok)" and you see something like "BIP39 (checksum: failed)", then one or more of your 12 words has been entered incorrectly.

This wallet already appears to have been loaded into Bitcoin Core previously... in Mid-December 2020... and it has "refilled" the keypool with a bunch of new private keys/addresses. The 0014 privkeys and "3" addresses are the P2SH versions of the private keys.

What exactly has your "friend" done with this wallet.dat before they gave it to you? How was it "recovered" to start with?

Can confirm... I just fired up the Raspberry Pi 4 that I got a few days ago... using Ubuntu Server 20.04.2 LTS 64 Bit for the RPi... you want:


NOTE: Clicking "ARM Linux" on the Bitcoin Core download page defaults to downloading the 32bit download!!?!... So, you need to click "64 bit" to get the aarch64 version (or right click it to copy the URL for the 64 bit download)

Just FYI, I contacted the OP on Discord and managed to walk them through the steps required to use the "bump fee" functionality to increase the transaction fee.

Notes:

- Transaction was RBF
- Transaction was 1 input, 2 output... size was 223 bytes
- Fee used was 1 sat/vbyte (was actually 0.00000223 BTC, NOT 0.0000233 BTC:P)
- After bump fee, increased to 20 sat/vbyte (which immediately got swamped due to no blocks being found for over an hour )
- However, replacement transaction is now confirmed
- OP decided against moving the rest of the coins from Electrum until fees are a bit lower

If you were able to load the wallet in Bitcoin Core and run dumpwallet then all you need are the privkeys starting with "5" or "L" or "K". You can import all of those into an Electrum wallet (https://electrum.org/#download - Read the HOWTO verify guide here: https://bitcointalk.org/index.php?topic=5240594.msg54223763#msg54223763)


As I said, it seems that you're having issues with PyWallet due to the updates... you'd either need to switch back to Python2.7 and my old version of PyWallet... or wait for JackJack to get a less "unstable" version of the new Python3 compatible Pywallet up and running.

But it's not necessary if the wallet.dat opens in Bitcoin Core... you'd just be dumping the same info... so I'd just forget about PyWallet for now.

Focus on importing those private keys into another wallet, and check to see if any transaction history is found (and hopefully a positive balance! )

Those are simply a list of labels/names etc that PyWallet has stored in the wallet file for those particular addresses so that you know they were "recovered"... and are not newly generated etc. I think the original idea was that you could just use the whole recovered wallet.dat with Bitcoin Core and continue using it as "normal" and Bitcoin Core would be able to generate new keys and add them into the wallet file etc.

However, with the advent of HD wallets, that is probably not recommended.

My advice is to not use the bitcoin.com app... It is very misleading and it will most likely result in you buying Bitcoin Cash (aka BCH) and NOT Bitcoin (aka BTC)... The app tries to make out that BCH is the "real" Bitcoin

To buy bitcoins using bank transfers etc, you'll need to find an Exchange in your location that supports bank transfers. Where in the world are you located? The US?

Excellent... seems like we are getting somewhere. If you find addresses with coins, you will need to use the --passphrase option to generate the same output, but with the private keys listed... the command would be:


And change the YOUR_PASSPHRASE_HERE part as appropriate... this time the file created will be called: C:\Users\Catherine\Downloads\pywallet_output_with_privatekeys.txt

And the format should look the same, but you should see a field called "sec"... this will be the private key in "WIF" format (it will start with a "5", "K" or "L")... that can be used to import the private key(s) into another wallet.

Bitcoin Core is an HD wallet... it uses new addresses for each "receive" and whenever it generates change from a send transaction etc.

Most modern wallets are like this.

If you get really desperate... you can just use something like Ian Coleman's website... https://iancoleman.io/bip39/

First, move all other coins from your KeepKey to new wallets. Then input your 12/24 word seed from KeepKey into the BIP39 mnemonic code converter... change the "coin" to DOGE... export all your private keys and then import them into another Dogecoin wallet (like Dogecoin Core or MultiDoge or something like that)

Then you should consider that seed as compromised... either throw away the Keepkey and get another hardware wallet like Trezor, Ledger, Coldcard etc... or reinitialise the KeepKey with a new seed and then move your funds back.

Sounds like your wallet was "double encrypted" from the very beginning with a 2nd password

There is another option to test... which would be this:
https://github.com/blockchain/my-wallet-backup-decryption-tool

You can setup that tool on your local PC and try and decrypt the wallet.aes.json file just using your main password. See if that works... if it doesn't, then it is almost 100% guaranteed that your wallet has the 2nd password set and you'll need to try bruteforce it with btcrecover.

It is specifically for Bitcoin Core GUI... so if you have multiple wallet files open, they are stored in settings.json, so when you restart, it will automatically re-open the ones you had open when the application was closed.

And if you close a wallet in the GUI, it will be removed from the settings.json, so if you restart, it won't be automatically re-opened.

Also, you can still use -wallet option on commandline or wallet= option in bitcoin.conf

Ok... try this:

That will dump all the output from the script into a file: C:\Users\Catherine\Downloads\pywallet_output.txt

You'll be able to open that with a text editor. It'll make it easier to view/read and search. At the very top of the file, does it say "The wallet is encrypted but no passphrase is used"? You should also see some records below it that have names like: "addr", "compressed", "encrypted_privkey", "pubkey" etc

Was it one of the simple "single page" backups?

Do you have a record of the funding transaction? ie. the receive address etc?

Awesome... that helps a lot...

Try this:

See if that does anything... if you still get the "ERROR:root:Couldn't open wallet.dat/main" error, then it would appear that either the wallet filename is wrong... or the recovered wallet.dat is corrupted. You could try one of the other recovered wallet.dat's... just chance the filename as appropriate... although the fact they say "partial_recovery" in the name is not encouraging