Your transaction will confirm once the backlog clears a bit more. You just need to be patient. I would expect to wait around 24 hours or so.

You need to double-check everything you're looking at and make sure you're really sending to Bitcoin Cash on poloniex and not normal Bitcoin. AFAIK since Bitcoin Cash doesn't support Segwit, you won't be able to send to that address, unless it's some other type of P2SH address.

The large backlog of transactions has recently started to clear. You'll need to just be patient for a bit while it clears.

Well, Electrum is just the wallet. They can't help you not send to Bitcoin Cash addresses, because they're identical, and I'm fairly certain Kraken, like all other exchanges includes a big warning when depositing BCH or BTC that other currencies are not supported. It's on you to read the instructions and warnings presented to you, and it's not on them to clean up your mess. Take responsibility.

If you're only given the option to watch the wallet and not to send funds out, you've probably only used the Bitcoin address. Bitcoin address can't be used to send the BTC in them without their corresponding private keys. It appears that you can export your private keys from Strongcoin by either using the paper wallet mechanism or for each account you can supply the password and decrypt your private key in the browser.. Once you have the private key for your account you should be able to import it into Electrum.

If Kraken is advising you to resort to double spending then they probably won't recover your BTC (or at least won't try to) if the transaction confirms. Here are the steps you should follow to create a double spending transaction back to yourself.

1. Go to https://coinb.in/#newTransaction
2. Open Electrum. You will need to export the private key for the Bitcoin address the money was sent from, which in your case is a single address. Do not share this with anybody, as it will compromise the security of your entire wallet. To do this, click on Wallet on the toolbar, then go to Wallet > Private Keys > Export. Look for the private key (the one on the right column) corresponding to the address you used (1B9G9SzFKrtEin7XBo1Yss4pQtXvSYunUG).
3. On coinb.in, where it says "Address, WIF key or Redeem Script:", paste that key and click "Load".
4. Here's the tricky part that I can't give you exact steps for because I don't have a wallet to test this with. Once you click load, you're going to want to create a transaction with the following:
Inputs: You want to use the single input that you used in the transaction, which was of size 0.17876 BTC and from address 1B9G9SzFKrtEin7XBo1Yss4pQtXvSYunUG.
Outputs: You want to send the money back to yourself so that the new transaction you're creating confirms and not the other one sent to Kraken. This means the output you add should be back to yourself. You can re-use the address you sent from or use a different receiving address, but this one should be coming back to you.
Fee: I believe that the fee on this page is calculated like it is in Bitcoin, meaning that the fee is whatever is left over from the amounts you've sent to all your outputs (Just your address in this case). You'll want it to be  significantly higher than the original transaction, if I were you I would choose something about 50% higher than your original transaction, about 0.0015. Your new transaction will be slightly smaller in size so your fee/byte should be more than 50% higher.

Once you've done all this (Entered your private key, selected the correct inputs, created a new output back to yourself with a sufficiently higher fee), you should have a raw transaction which is a bunch of hex characters (0-9 and a-f). Take this and copy it, then go to the verify page on the same site (it's on the navbar up top) and paste it in. It will show you where the money is coming from, where it's going to and what the fee is, double check all of this.

Finally, if it all checks out, click on the "broadcast" link on the top. This is where you actually submit your transaction to the network. Take that same hex you copied earlier and click submit. You should then be able to see it on the network and on blockchain explorers.

Remember, never give out your private key to anybody here. Good luck.

If the transaction isn't on the network, it's not because of the congestion but because LBC hasn't sent it yet. I would double check your LBC account page and make sure that you actually withdrew the coins from there. If you did, and it shows but there's just no transaction ID, I would just wait 24 hours for the congestion to die down and see if they're just waiting to send it when fees are significantly lower. So unfortunately, your best option right now is probably just patience.

There's nothing inherently dangerous with these sites, but they can take forever to accumulate enough money to actually send to your wallet, and when you do, you'll lose a lot to fees, and you'll have a very small input in your wallet to spend which will only increase your future transaction fees spending out. They're an alright time waster but you won't really ever get any meaningful amount of money.

I agree with you that scalability is a complex problem, but I don't think that miners picking what's most profitable for them is the problem. In a world with limited block space being completely filled, fees provide what I think is a necessary amount of money to pay for your space in that block. People might disagree with that viewpoint and that's okay, but I also think that fees are way to high for people to be using Bitcoin normally right now.

I do believe we need to focus on our other upcoming scalability solutions such as LN and Schnorr signatures so that we can fit more transactions in a block before we think about raising the block size.

You can watch https://fork.lol to see when Bitcoin is more profitable to mine than BCH, which will let you know when the miners will move back over, and https://core.jochen-hoenicke.de/queue/#24h to see the current status of the mempool by fee size.

Because scaling Bitcoin is harder than changing a 1 MB block cap to 8 MB. We have already added Segwit, which was great. With future improvements, we will add Schnorr signatures and Lightning Network to Bitcoin. This is important because these improvements focus on fitting more transactions into a block instead of just making the blocks bigger. The bigger we make blocks, the larger the blockchain becomes, and the harder it gets for people to run full nodes. And when less people run full nodes that means less people are verifying their own transactions the way Bitcoin was designed to be used, trustlessly.

They can call their forked coin "Bitcoin" if they want but it's not going to catch on. It's fundamentally different than Bitcoin and all these people want is control.

How in the world did Segwit "break" Bitcoin? It raises the amount of transactions that can fit in a block and fixes transaction malleability

Your fee is high, but the network is more congested than normal. You'll just have to be patient and wait it out, probably about another 24-48 hours.

The Bitcoin network has a very large backlog right now. There's nothing you can do but be patient. I would expect to wait about 2 days for it to confirm at the moment.

Okay, I'm fairly certain it would be impossible for you to send LTC to a Bitcoin address because the address shouldn't validate. So you say you sent it to a 2 of 3 electrum Litecoin wallet? Shouldn't you have 3 keys for it then? If you've lost your keys to the wallet, it's impossible for you to recover your coins. Could you link us to the transaction or try pro provide more information?

It's called a change address. You can learn more here: https://en.bitcoin.it/wiki/Change

I highly suggest trying to learn more about how Bitcoin works, because it will help you from freaking out/making small mistakes.

If you're looking to invest your money, I'd stop looking for ICOs. They've become a cesspool of people with barely an idea and no working product just looking to make a few quick bucks then run with the money. It's disgusting.

So many people don't understand what an ICO is (or at least what it was/was supposed to be). An ICO is an Initial Coin Offering. That means you need to offer a coin. That already cuts out half of the people running "ICOs". Secondly, the whole idea is that this coin is supposed to actually do something. Usually, these coins were ERC20 tokens on the Ethereum network. Usually the coins had some sort of value, e.g. Etheroll, which has tokens that allow you to claim some of the house's profit with your tokens. Their ICO allowed them to make the bankroll for the game, and their coins served a purpose. Now, people will create cookie-cutter coins that have no value other than they sell them for 30 cents each in their ICO.

If you really, really need money for something, build something useful first. Don't just tell people "hey I need money for this fantastic idea" and expect people to fund you (although that's happening at an alarming rate). Build something, a prototype at least, then say "hey, look at this thing I built, I have an idea and a prototype that has potential but I need a little boost". That's when you should run an ICO, if ever.

Or, you could stop trying to trick the newbies in here into making bad, uninformed trades. While BCH raises the blocksize and allows more transactions to fit in blocks, many people agree that it's best to use the new technology available to us (Scnorr signatures, LN) to fit more transactions in the space we have before we resort to increasing the block size.