There are a number of "fork claiming" scripts around... like these:

https://github.com/forkdrop/forkdrop_suite
https://github.com/ymgve/bitcoin_fork_claimer

There is also websites like: http://www.findmycoins.ninja/

DISCLAIMER: I do NOT endorse any of these scripts/sites and have not tested/vetted them for any bugs/security issues.

Additionally, you'll find that most, if not all, "modern" wallets default to compressed... I can't think of any that default to using uncompressed addresses.

Go with o_e_l_e_o's suggestion... using offline computer and live OSes etc...

- Download Electrum and verify the digital signature.
- Create your own 256 bits of entropy using a coin flip (or dice etc) and put it into an offline version of Ian Coleman's mnemonic generator.
- Create the wallet in Electrum and crosscheck the addresses generated with those from Ian Coleman
- Make sure the words generated are NEVER stored digitally or online etc.
- Use Electrum "normally" and it will end up generating new addresses as required (or use the gap limit hack to pregenerate more if required)


As someone mentioned earlier... there comes a point where you need to trust someone... either software devs or hardware manufacturers etc. and it's a fine line between healthy paranoia and craziness

If you have lost your 12/24 seed mnemonic words, and you no longer have access to the wallet that was generated from those words, then your coins are effectively lost forever


What "card" are you talking about?

Are you actually able to provide some screenshots of the Wallet screens/tabs?

It isn't very clear from your description what is actually happening with your app and/or any transactions you make have received/made.

To really throw a spanner in the works... it is actually technically possible to have zero fee transactions (and historically there have been a few).

However, these days, the vast majority of nodes will refuse to accept and/or relay transactions with fee rates below a certain threshold... the so-called "min relay fee" (which is customisable). But, if you're friendly with a miner/mining pool, it is possible for them to take your zero fee transaction and put it in a block and everything will validate just fine. It just isn't practical for the general public

Just to clarify (for the users who just skip to the end and don't read the whole thread and for the sake of keeping the terminology somewhat correct)... by "Change addresses"... the OP appears to actually mean "a new address every time you want to deposit"... as opposed to actual change addresses which are used for receiving change outputs from a bitcoin transaction.

This one most likely would not have worked for the OP as their transaction only had an 8 sat/byte fee... ViaBTC require a minimum of 10 to be able to use the free accelerator.


about 99.9% sure that the AntPool one no longer works... which is a shame... it was relatively reliable "back in the day"

It was something of a secret and then someone plastered it all over these boards/reddit etc and it basically became useless


In any case, it seems the OPs transaction got confirmed by BTC.com... I wonder if they ponied up the massive fees that BTC.com charge for acceleration?

I would concur that it is most likely a "permissions" error of some description... Caused by either an antivirus/antimalware app preventing writing to the system drive... or Windows Security settings doing the same.

Two questions:

1. Are you running the installer as Administrator? ie. right click -> "Run as administrator"?
2. If you already have Bitcoin Core on the PC, did you shutdown Bitcoin Core before attempting to install/update?

It has certainly been an interesting end to the season... just happy to finally get to see the captain do "The Hendo Shuffle"™ and raise the PL trophy! Just hope it doesn't take another 30 years for the next one!

And there is still a bit to play for in terms of the minor places... A three-way at the top between ManU, Chelsea and Leicester for the Champions League/Europa spots... and Villa and Watford desperately trying to avoid relegation. Personally, I'm more interested in the relegation battle, because I just don't care about ManU, Chelsea and Leicester

On paper, Watford have the harder game against Arsenal... but West Ham should prove difficult for Villa... in the end I think Watford will end up going down.


Predictions:
- ManU to beat Leicester
- Chelsea to beat Wolves.
- Watford lose to Arsenal
- Villa draw with the hammers

I would not say that it was a "puzzle" as such, in that it wasn't publicly listed as a challenge or anything like that... it seems they were just experimenting with P2SH scripts and discovered someone had been sending dust to the address generated from the "1=1" script address...

It might have been useful for readers if they had actually shown the step by step guide to how they constructed the transaction, rather than "here is the finished transaction, feel free to decode it yourself"

Still, it's nice to see theory being used in practice

Note that running Bitcoin Core with it storing it's data on external drives has the added risk of an accidental drive disconnection resulting in data corruption in the block files, wallet.dat or both.

Additionally, external drives are generally a lot slower than internal drives due to limitations of the interfaces used for this ie. USB... that may impact on your initial blockchain syncing time (which involves a lot of disk I/O)... but is probably not so much of an issue in day to day usage.

Note that Bitcoin Core does not provide seed phrases... the backup methodology for Bitcoin Core is to simply make (multiple) secure backups of your wallet.dat.


Just to make a small clarification... a deterministic wallet, uses a "master private key" derived from a seed, and then multiple child private keys are derived from that master (and then the addresses the for child keys are derived from that)... so the wallet still contains multiple private keys just like a non-deterministic wallet.

The difference, is that you can regenerate ALL the derived private keys in a deterministic manner by starting from the seed... with a non-deterministic wallet, the private keys are just randomly generated.

Your problem is that you're possibly not comparing apples to apples...

As the others have tried to explain, it's not the amount of BTC you're trying to send... Or the address you're sending to...

It's the actual data size of the transaction you are creating... Measured in bytes... And the thing that has the largest effect on the data size, is the number of inputs (and to a smaller extent, the number of outputs being generated).

Because of the way Bitcoin is received and "stored" when you are using Desktop/Mobile wallets, this can sometimes result in transactions that you generate from these wallets having larger data sizes than when using centralised services like Coinbase... As these services can use various tricks to minimise transaction sizes (like batching transactions etc)

The trade off is that you have full control over these desktop/mobile wallets (unlike centralised custodial wallet services like Coinbase) and don't need to worry about KYC etc.

Also, don't just accept whatever fee rate a wallet tells you that you need to use... They're "best guess" algorithms... and the Bitcoin network can be quite volatile. Read the various threads and learn how to determine what a "good fee rate" is based on the network conditions at the time you are sending your transactions.

Electrum, by default, connects to public servers which will not be affected by your Bitcoin Core node. So, whether or not your Bitcoin Core was synced should not make any difference... unless you are connecting your Electrum to your own private Electrum Server (like ElectrumX, electrs or Electrum Personal Server) which is connected to your Bitcoin Core node.

Are you running a private Electrum Server?

Basically, if the private keys in Electrum are the same as the ones in Bitcoin Core and have been imported as the appropriate script type so that the addresses holding coins in Bitcoin Core are the ones being displayed in Electrum... Then everything should work.


It does... The command is dumpwallet

It will allow you to dump ALL the private keys contained in the wallet.dat (including ones in the keypool which are not displayed in the "receiving addresses" list)


That's not how it works... The two wallets, while containing the same keys/addresses, still operate independently of each other.

For instance, it's possible to export a single key out of Bitcoin Core and put that into Electrum, but still have other keys in Bitcoin Core that aren't in Electrum... And vice versa, you could have keys in Electrum that are not in Bitcoin Core.

However, for any private key/address pairs that are in both wallets you should see all the same transactions for those addresses (assuming both wallets are properly synced and up to date).

Quoted for truth... a lot of people jumped on the Bitcoin hype train when it was exploding through $10K the first time as they seemed to believe there was "Easy Money"™ to be made, but had zero understanding of how it all worked...

And then we saw the increase in "stuck transaction" and "omg I just paid $100 in fees, wtf??!?" type threads... along with the stories of "seed/private key entered into fake website", "scam wallets downloaded" etc etc.

Cryptocurrency can be an unforgiving place if you don't take the time to read and learn.

Which wallet.dat are you talking about? Wallet files for Electrum? or actual wallet.dat files for Core?

I'm still very confused as to what the actual issue was here... because now you're talking about "hidden" master/private keys?

Can you just answer one thing for me... when you imported your "5 keys"... how many addresses were showing in the Electrum "Addresses" tab?

And this is why "address re-use" is a "Bad Idea"™ if you value your and other peoples privacy.

If you only ever use an address once, and give anyone who asks for one a completely new and previously unused address, then this kind of tracking becomes more difficult, as it is harder to ascertain what address belongs to whom.

Be aware that Exodus does not provide any way to specify or set the transaction fees you want to use... You are completely at the mercy of the Exodus fee calculating algorithm.

Anecdotally, this algorithm is not great and will generally result in fees that are higher than they probably should be. Having said that, I don't recall reading any instances where it set fees too low, resulting in a stuck transaction.

Looks like whomever sent that transaction was attempting to make a point... Possibly to the hackers.

Did you read the "addresses"?

The message appears to be:
"Just read all transaction outputs as text, you take risk when use Bitcoin for your Twitter game. Bitcoin is traceable. Why not Monero?"

Technically yes... But it was ~0.00000666 for each one... And 0.00001337 (aka "leet") to the hackers address

As already stated, you can have multiple inputs or outputs.