It now seems that the original transaction actually "won" and was confirmed... and the RBF (second) transaction with the "higher" fee ended up being invalid.

Essentially, 2 miners... 2 transactions...

Miner 1 Block 666833: Original Transaction
Miner 2 Block 666833: RBF Transaction

Miner 1's chain then becomes longest, as more miners add blocks on top of Miner 1's Block 666833.... it "wins" so Miner 2's block 666833 becomes "stale". This means that the Original Transaction is now "confirmed"... and the RBF Transaction is now invalid in the "stale" block.

What you "see" as "confirmed" and/or "invalid" when the 2 miners both broadcast competing block 666833's would depend on what "chain" your wallet (or wallet provider) was taking it's data from (ie. which Nodes it happened to be receiving data from). You may never have seen the RBF transaction if you were getting Miner 1 chain data... However, if you were getting Miner 2 chain data, you'd suddenly see a "re-org" when the other chain became longest and the last block on Miner 2 chain got rolled back.

It also goes against the one of the core (if you'll excuse the pun) tenets of Bitcoin: "Don't Trust, Verify"

I know you're just trying to help, but the entire purpose of running a "Full Node" is knowing that you have downloaded and verified every single block. "Bootstrapping" with just blocks is bad enough, taking someone else's chainstate is basically removing all of the verification from the process and going to "Don't Verify, Trust".

To anyone contemplating using this download... If you don't have the time and resources to fully sync a full node the "proper way"™, then perhaps you should be asking yourself why you're even running a full node?

Brainflayer should have output something like this:


The "passphrase" should be the bit at the end... in my example, "abc123"


Once you have the "passphrase", you can just use one of the "brainwallet" apps like: https://brainwalletx.github.io/#generator or https://www.bitaddress.org/ (NOTE: download the source/zip linked at the bottom of page and run offline)

Put your passphrase in and it should generate the private keys etc for you. For BrainWalletX, you need to click the "toggle key" button to see the private key and you might need to change between "uncompressed" and "compressed" to see the correct address:

Note that using dumpprivkey (and/or dumpwallet) command will not "interrupt" your sync... that will quite happily continue in the background.

It will also save you a lot of time/bandwidth.

Correct... Electrum only seems to allow you to "paste" private key "text" in... you can't physically type it in... I've always found that a little bit "odd"... but possibly related to security issues around trusting 3rd-party keyboards?

There is already this tool (forked from Ian Coleman's BIP39 tool): https://github.com/FarCanary/ElectrumSeedTester

Takes an Electrum seed, converts to BIP32 and outputs all your addresses/private keys from various derivation paths etc.


And while it doesn't currently support importing Electrum seeds, Sparrow wallet will import Electrum wallet files.

One important thing you seem to be missing is that "Child Pays For Parent" can only be executed by a wallet that has received one of the outputs from the unconfirmed transaction.

So for:

Case 1:

Only WalletB can execute the CPFP... as it is the only wallet with a "child"


Case 2:

Either WalletA or WalletB (or Both) can attempt to execute CPFP... as they both have "children" from the transaction.

Hopefully... but yes, you must ensure that the "prune block storage" option is UNchecked... Armory cannot function with a "Pruned" node... it needs the full blockchain available to scan all the blocks.

Is the "building databases" progressing? You might want to check the dbLog.txt file and make sure that it is actually logging the "parsed block file #xxxx" lines... if it's not, then it might be "stuck". When it gets to "scanning transactions" in Armory GUI, then you should see a bunch of lines in dbLog.txt like: "scanned from block #xxxxxx to #yyyyyy".

And yes, both of these processes can take quite a while to complete.

Public Key? Or your address converted back into Hash160 form?


When you ran brainflayer... and it popped out a result... the "passphrase" should have been on the end of the line of output... like this example where I found that "abc123" was the passphrase used:


The 40 char hex at the start of the line should be the "RIPEMD-160(SHA-256(public key))" (aka HASH160) that you derived from your address (convert Base58check address back to Hex) and put into the example.hex file before you ran hex2blf


Anyway, simply put that "passphrase" into a brainwallet generator like: https://www.bitaddress.org/ (use the "Wallet Details" tab)
or, if your passphrase is too short to be recognised using BitAddress (like my example) try: https://brainwalletx.github.io/#generator (click "Toggle Key" to see private key in WIF format)

NOTE: don't run these tools "online"... you should download them and run them "offline"... both have links to github and/or .zip files at the bottom of the page!

This gives:



(You may need to check both the "uncompressed" and "compressed" options to see the correct address)

That's not really an issue... as long as you have your 24 words, you'll be able to recover whatever coins are being managed by your Ledger device. All the keys necessary are able to be restored from your 24 words, so regardless of whether or not your laptop/PC or Ledger device are functioning, you can recover.


As bob123 is theorising... It sounds like your Ledger device is not being recognised by Windows correctly.

When you connect the device and then unlock it with your PIN, do you get the the USB device connected "bing bong" sound? If not, then there is either an issue with the USB cable you are using (no data, only power?)... or there is some sort of issue with the USB device driver install.

If you've tried a different cable (that you know allows you to transfer data and isn't just a power cable from a phone charger etc), you may need to go into Windows Device Manager and see if you can see a device with a little yellow triangle and ! mark. Right click on the device and then "uninstall device". Then disconnect your Ledger, and then reconnect it and unlock it with your PIN again.

See if it then gives the "bing bong" sound and shows up in Device Manager as "Nano S" under "Universal Serial Bus devices":


If it does, then you should be able to see the device in Ledger Live... open Ledger Live and away you go.
   

That is basically a "screen saver" on the device... it'll scroll along after an "Auto-lock timeout" (which you can adjust on the device in "Settings -> Security -> Auto-lock").

It's most likely just a syncing issue with Mycelium... their servers are notoriously bad for this. There are reports every few weeks from users complaining that their wallet balance isn't correct etc... 48 hours later they are like "OK, it's finally working".

Try going to the "Transactions" tab for the account your bitcoins are supposed to be on... then click the "3 dot" menu in the top right corner... then select "Reload Account".

That will hopefully force a resync and show your correct balance etc. If not, you might just need to wait another 12+ hours... but don't worry, your coins are not "lost"... they will show up eventually.

Any luck? Did you figure out exactly what it was that was causing 3.3.8 to keep opening? Was it the icon pointing at the wrong executable?

Are you 100% sure that those addresses were actually from your Ledger device? What makes you believe this to be the case? Were they labelled that way in Coinbase? or are you relying on memory?


What exactly did you do in Electrum? Did you use your 24 words or did you create a standard wallet with the "use a hardware device" option? And what "derivations" did you use?

If you let us know exactly what you've already tried, we won't waste time suggesting things you've already attempted.

At this point... it's time to ask... do you want to continue using Armory or are you just wanting to "rescue" funds?

If you just want the funds out... you'd be better of exporting your private keys and then importing them into a lightweight wallet of your choice (I would recommend Electrum). You can follow the guide here to get private keys: https://bitcointalk.org/index.php?topic=4746784.msg43255691#msg43255691


If you want to continue using Armory, then we can work on getting it up and running... I personally have had it running on an Ubuntu 18.04 instance... but my daily driver is on Windows 10.

It's not really an issue if you're simply updating the application itself without moving the blocks, migrating to a new PC and/or you still have a decent amount of storage space available.

I just did this just now (upgraded to 0.21.0) and had no issues with it whatsoever... it didn't "auto prune" my blocks or change any of the settings.

I have noticed however, that if I run the -choosedatadir option and set it to use the current location of my bitcoin datadir, because the current diskspace free is less than the current blockchain size (ie. 350+gigs), it auto-enables the pruning option:


Even though it doesn't need to actually download anything, because the blocks are already there...

So, I assume for anyone that copies the datadir first and then runs Bitcoin Core... it will do the same thing, unless there is >350gigs free space etc.


If I untick pruning, it then "warns" about the disk free space in red:

Yes.

Rescan makes Bitcoin Core go back through all the blocks and hunt for transactions that relate to your wallet... logically, if you no longer have those blocks stored on the disk, then you can't "rescan" them without redownloading.

Your options are:

1. Disabled "Pruning", resync and store all the 350+Gigs on your disk.
- This will mean that should you need to rescan in the future, you've already got the blockchain stored so it doesn't need to be downloaded again... however it means you need to permanently store the full blockchain.

or

2. Leave "Pruning" enabled,  and simply "reindex" your node.
- This will still need to redownload the full 350+Gigs of blockchain, so each block can be scanned for transaction relating to your wallet... but it will discard the blocks after they've been verified/scanned (after the pruning size limit is reached) and you'll only need to store up to the "prune limit" worth of the most recent blocks. So, you don't need as much storage space, however if you need to "rescan" again in the future, you'll need to redownload the full blockchain again.


TLDR; which is more important to you? Only needing to download the blocks once and being able to rescan at will... or not using up large amounts of storage space but having to redownload the full blockchain if you ever need to rescan/reindex again?

Did you make sure that "Discard blocks after verification" was "unchecked" when using -choosedatadir? And also that in Bitcoin Core GUI in "Settings -> Options -> Main" menu, that the "Prune block storage" is also unchecked?

Sounds like the 3.3.8 is a "portable" version or possibly the "Standalone" version of Electrum.

If you've already run the Windows Installer (several times by the sounds of it), then Electrum 4.0.9 should now be installed in "C:\Program Files (x86)\Electrum", so you can easily check and confirm if it is there.

When you right click the icon on the desktop that you're using to start Electrum, and select "properties", what is the "Target" that is displayed? It should say:
Like this:


If it says something else, what exactly does it say?

Brainflayer is pretty much the "standard" when it comes to brainwallet "cracking"... there are loads of tutorials on google/blogs/youtube etc that show it in action.

You feed it a list of potential passphrases (wordlists, phrase lists, book quotes, song lyrics etc), it then generates the "brainwallet+address" and compares with a bloom filter of addresses you're interested in...

So now they seem to believe that this was an instance of RBF, where the lower fee (ie. the original) transaction won!!?!

Not normally what you'd consider "likely" to happen, but certainly not "impossible". #funAndGames