I could give this a start, just as I've been thinking about a FAQ for "I sent my coins to the wrong chain", but there are too many permutations to make a complete list:

• dozens of different wallets
• many chains (Bitcoin, Bitcoin Cash, Bitcoin Gold, BitCore and probably many more in the future

This easily gives more than a hundred combinations already, which is too much to cover in one thread.

In general I prefer to move the most trusted and most valuable coins first:
1. Bitcoin (wait for confirmations before continuing to step 2!)
2. Bitcoin Cash
3. Bitcoin Gold
4. BitCore (not a fork but an airdrop to existing Bitcoin addresses)
5. Whatever they fork next week

And of course take safety precautions:
1. Be paranoid
2. Don't install untrusted software on any computer you'll use again after that
3. Tripple-check to be sure the address you're sending to is on the correct chain

I've recently installed Coinomi on my phone. Although I haven't tested it yet, it seems to be one wallet that can handle all forks until now. This might be an easy solution to split coins.

Exodus: How can I view my private keys?
Bitcoin Core: How do I import a private key into Bitcoin-Qt?

Check required fees on btc.com before making a transaction. Don't just look at the value at top, look at the bars on the bottom of the page too. If you have small inputs and you're not in a hurry, you can set a fee much lower. Don't use the high fee to be in the next block if it's not needed.

I must say though, if you can't search these answers on your own, Bitcoin Core, and importing/exporting private keys in general, might not be the best solution for you.

Critic here, please sit down


Let me quote your FAQ:
First, it's not true that non-HD wallets stick to using a single address. My Bitcoin Core wallet for example is non-HD but uses many different addresses.
Second, you say you "try to implement the best existing solutions", but you implementation goes directly against Satoshi Nakamoto's whitepaper:
This means your current implementation is worst practice instead of best practice.

Your website mentions "Featuring client side private key storage", as if that's something unique and special. It's not, in fact, it shouldn't even be necessary to mention this. This implies you think it's something special, instead of basic wallet privacy and security.

Let me first tell you I'm very paranoid to installing any Bitcoin related software. If I do, it has to be highly established and must have a flawless track record.
Installing any software basically allows that software to do anything I can't check, and when you're offering closed source software without any existing method of earning, it will be very difficult to trust your intentions are 100% good.
It can be that you mean well, but I can't be sure, and I don't give random strangers the benefit of the doubt when it comes to my Bitcoin private keys.

You can't gain trust now by something you say you'll do in the future.
No, we won't meet. I like my privacy.

Signing messages is an integral part of Bitcoin. It is needed.
What do you mean when you say "we work directly with blockchain"? What makes it worth mentioning this?

Please read through all the details again, for instance, payments are in Bitcoin, not Ethereum.

How to Join Youtube Campaign
Reply in the following format:


Links
Remember to use these links:
[1] Telegram Chat: https://bitlogic.cc/tlgrm/
[2] BitcoinTalk: https://bitlogic.cc/we/

The main problem I see here is trust: I have to trust you only show addresses that are based on my master public key, and don't sneak in your own address once in a while.

I get the privacy aspect, but if I'd have a website would donate-button, I would choose to be transparant about donated amounts.

I haven't heard of Square before, but it could be a good solution.
I'm fine with Bitcoin being a store of wealth, as long as I can also use it for small payments. And for small payments, I don't mind using a centralized trusted service provider, as long as it is widely accepted.

If for example Electrum and some other wallets would implement a "small expenses trusted payment processor", I would happily deposit $100 at a time to make many small payments over the months. Think of it as a Lighting Network, but without the trustless aspect.
If I receive many payments, I would move some of it back on-chain, if I make many payments I deposit more funds.
I trust Paypal with much more than $100! Ideally there should be competition, but if Paypal and others start doing the same, we'll end up with different incompatible services that needs something like Shapeshift for transfers between them.

In general I don't really care about how small payments and high fees are fixed, as long as something is done to enable it again.

You could have left the password empty, that's what I did.

Click Wallet > Password > enter "Current Password" > leave New Password empty > click OK.

Alternative: just create a new wallet, restore your old seed, and start over from there. Obviously, don't delete your old wallet yet, just to be sure.

I've never used RBF, but I have used double spend. What I did was simply erase the transaction from my Bitcoin Core, and make a new transaction.

As a receiving party, you should never rely on this. As long as a transaction is not confirmed, there is no guarantee it will go true. Satoshi recommends to even wait for 6 confirmations.

It's actually quite simple, it just took me a while because rescanning my wallet to dump the transaction was slow. With the proper setup for this, a scammer could easily do it.

How did you end up in this situation "a couple times"? If it's accidental, you should be more thorough. If it's malicious, well, you shouldn't

Did you mean two Bitcions instead of "but coins"?

Kraken processes MtGox claims. I wouldn't be surprised if your eBay seller used the codes by himself after you didn't claim them. If not, and if you still manage to get your claim processed, you're looking at the value of those 2 Bitcoins when MtGox filed for bankruptcy, not the current value.

There's a vacancy for a Lead Software Engineer for Bitcoin Casino.

DarkStar_, I'd like to change my payment address, so I can safely split Bitcoin Gold (and BitCore).

My old address: 1Paydays4YWcXghQjwPPQH4mk7y4mGFV14 (Balance: ).
My new address: 166666666LyMNrkpwwNCdUPzvDTh2tNDLu (Balance: ).

Signed message from old address (verify!) and staked address (verify!).
Thanks!

Correct. I have the same setup, and it's annoying to have to do it again.
I already missed several opportunities to sell Bitcoin Cash at a high price, because it's still "locked" and I want to transfer the Bitcoins to a new wallet before touching the forks.

There's now 4 things (that I know of):
1. Bitcoin ($7200)
2. Bitcoin Cash ($1240)
3. Bitcoin Gold ($160)
4. BitCore ($13; it's $26 per coin, but half a coin got airdropped per Bitcoin)

I plan to extract them in this  same order, then store them all in their own wallets again.

This thread is relevant again: after upgrading, Bitcoin Core no longer allows me to symlink the wallet.dat file. I have never before encountered any application that threats a symlink different than a real file, this is supposed to be handled on the file system level.

Having my wallet on a different location worked fine for as long as I've been using Bitcoin Core, and that way it's easier to include it in my backups.
My obvious question: is there any method to still have a wallet outside the data directory? I can't make a hard link, as it's a different physical disk.

Edit: I found a solution, see here.

I don't use either one of those, but Coinbase is not an wallet. It's an exchange, which means they'll be the one who have to deal with small inputs instead of you.

I prefer using a wallet that allows me to choose exactly which inputs to choose. That way I can for instance prevent getting small change, which is what happened to the addresses you showed earlier.
Example: 899c98c646df9605b7ad6501636a5bd968ae2b04707e8645afb0768626d2e39d:
You had 0.04501152, paid 0.044253 + 0.00043531 fee, and got 0.00032321 change.
If possible, you could have paid a fraction more, and used the input completely, without change.

As an alternative, try to spend small change once in a while too, when fees are low. Think of it this way: if you pay with banknotes only, you'll collect many heavy coins in your pocket. It's annoying to spend them all at once, so you do it during your normal shopping.

This is exactly what I expected. You have many very low amounts, that gives a big transaction (in bytes), and requires a high fee.

At current fees, you can forget about it (sorry!).
Try sending your entire balance to 1 address of your own when https://btc.com/stats/unconfirmed-tx recommends 40 Satoshs/byte (or less). This sometimes happens on Sundays.

In the future, try to prevent collecing very small inputs, they're not worth the fee they require to send them.

Since you already did it, it's too late to use an offline computer. Now all you have to do is import the private key in your Bitcoin Cash wallet. I assume you have one already, if not, you'll have to download one first.
Since you've been exporting private keys and (worse!) using your recovery phrase on an online computer, you should now consider your Ledger Nano-S wallet compromised! I'm not familiar with the device, but I would recommend to first safe your coins and then restart everything with a new recovery phrase.
But, since you ignored my previous security precautions, there are several ways to mess up here! You have to be careful, paranoid and think about what you're doing before doing it to keep your coins safe.

Enough warnings, I don't want to be responsible for helping someone who ignores security warnings, that's just waiting for a disaster.

You can use https://iancoleman.io/bip39/ to get your private key from the recovery phrase.
But: Take security precautions!
1. Move the Bitcoins from that address to a safe address first.
2. Make sure you do this on an offline computer, a Linux live CD is best.
3. Be paranoid when doing this, many people lost their coins due to mistakes they made trying to split their forked coins.

Can you share the address on which you hold these funds?
My guess is you have several small inputs, that means the fee required to send them is very high. Basically, at current fees, any input under 0.001BTC can't be spend, as it would entirely be taken by fees.

If the small inputs are indeed what causes your problem, you'll have to wait until fees are much lower to send them. Unfortunately, Bitcoin has come to this point where fees are this high. You have to compete with a growning number of other users.

When I try to register for the airdrop, I get this error:

I've had this before in the past, back then it was a server side problem with certain adresses if I recall correctly. I'm signing from an uncompressed address.

Another question:
I've had a hard time installing the wallet before, there were always dependencies missing on Linux. Is there a recommended Linux distribution to make the install work out of the box?

It depends: before HD-wallets, Bitcoin Core used a keypool, which by default stored 100 addresses. Any backup you made, should have the same 100 addresses. When you ran out of addresses, new addresses would be created, but your backup wouldn't know them.
If you deleted your wallet and restored an older backup, it might not have all your private keys. In that case it's impossible to restore.
Did you receive payments to 100+ addresses before this transfer?

Bitcoin Core doesn't have a "seed".