Why is no one talking about all the malicious QRcode generators? They come up as top results in major search engines. Most are scams. WTF

I can't make sense of the IRS requirements.

If I trade BTC for ALT and ALT only has value in BTC (ie. a net zero transaction), what do I owe tax on?

And if I trade that ALT back to BTC I owe tax AGAIN on the same thing I already paid tax for. 

This applies to all coin forks but since there have been so many Bitcoin forks lately it's the most appropriate to demonstrate the issue.

So everyone hopefully knows you should move your original BTC to a new wallet after a fork and before importing your old wallet in to one of these forks. This prevents the forked client from stealing your original BTC.

However, if several forks happen between the time you move your original BTC then you're in a tough spot because although you can still protect your original BTC, there is no way to protect all the other forks from stealing coins from each other.

Consider this situation:
1. You have BTC in your BTC client wallet "A".
2. Bitcoin Alpha fork happens. You're like "whatever" and don't do anything.
3. Bitcoin Beta and Charlie fork happen at the same time. Meh...
4. Bitcoin Delta happens.
5. OK, maybe it's time to claim these forked coins.
6. You move your original BTC from wallet "A" to a new wallet "B". It's safe.
7. Now in order to get some Alpha, Beta, Charlie, and/or Delta coins you have to import your wallet or private key from old wallet "A". There is no other way to do it. This means all the forks have to use the same wallet/private key(s) from old wallet "A".  See the problem? All with the same private key, now any of the forks can access the coins of any other fork until you move the coins on those forks.

So you would want to use/import the forks in the order that you trust them (from most trusted to least trusted) but it's a gamble. Once you have coins on a new fork you want to move them to a new wallet on the fork. This will protect them from the other forks.

The only way to protect against this would be to move your original BTC in between each fork (or not use the forks at all). However, that can be expensive in fees and in the case of a Beta/Charlie simultaneous fork it would be impossible (this happened with BitcoinX and SuperBitcoin).

To be clear again, this only applies in the situation where you have multiple forks happening in between the movement of your original BTC.

Reposting here because BITMAIN deleted my support thread (nice, guys... real nice)

I have an S3 that was offline for about 4 months. I started it up a few days ago and it was running fine for a few days until last night it stopped running at full speed. All ASIC's except one were listed as x's. This is not usual and has happened before and is usually fixed with a power cycle so I powered it off. Then when I powered it back on, now it will not start any ASIC's at all. The web interface works, network is working, etc. In the web interface there is nothing listed under ASIC's (literally nothing, it's just blank).

Both the green and red status lights are flashing in unison about once per second.

I run all stock clocks/voltages etc, no modifications. I have tried a full reset but that did not fix it. Tried multiple power supplies and no change.

Update:
After some fiddling I found that one of the ASIC cards is not working (there are two of these boards in the S3). If I only connect the working one then that hashes at half speed to a full S3. If I connect the other one either by itself or with the other working board then it will not hash at all.

So it seems that one of the hash-boards is bad for some reason. Any ideas how to affect a repair? I'm not sure what would make the entire set of ASIC's go bad so I'm guessing it's a component on the board... Or are they like Christmas tree lights and if one ASIC goes bad, they all go bad? What is the PIC looking for when it talks to the hash-board?

Nothing looks burned or broken on the nonfunctional board. I'd like to repair it if possible.

Edit:
For those wondering. This was my original support post (now deleted? WTF): https://forum.bitmain.com/bbs/topics/1961
And the cache is here (at least for now, until bitmain requests a takedown... again, WTF... What's with these guys?)