Where Is My Bailout Ethereum? PART II (The Replay)

In the first part of this story I talked about how my Ethereum wallet was drained of almost all of it's ether. 

If not, read it here: https://steemit.com/ethereum/@scottcal/where-is-my-bailout-ethereum

I am delighted to announce I DID get my ethereum back!!! This is how I got my coins were return and what I understand about ETH vs ETC.

I received an email early on Wednesday morning when I woke up. It was from Bittrex!!! The first email said they may be able to help me get my lost ether. The next email almost made me fall out of bed. It stated they had credited my Ethereum for the full amount lost. YES!!!! I WAS JUMPING FOR JOY! 

Btw nice baby goat or lamb picture Ryan ;p

As stated in the first post I take full responsibility for not doing the research and taking the proper precautions to ensure the safe transit of both chain's coins. I had all but given up and I guess Bittrex would have had kept my Ethereum had I not asked for it back. I want to be clear Bittrex policy states " Note that due to the current replay attacks occurring against both chains and potential of future cross chain attacks, Bittrex WILL NOT be crediting you if you deposit ETC to an ETH deposit address or vice versa under any circumstance" I very happy that they took pity on me that day.

Now on to the "Replay Attack". After doing some research and thinking into this, I've realized that these are not replay attacks at all. In truth they are the result of a poorly planned hard fork. Hey I love Ethereum and all it stands for, but the planning on this was pretty one sided and short sighted. (Yes, I see the irony in this being that I almost lost my coins due to not putting in the work and planning and research.)

Here is what I mean... the so called "replay attacks" are actually two block chains using the same network. There really isn't any difference between the ETH network nodes and the ETC network nodes for the most part. The transaction are basically the same too. That's why you can mine with the same miner and sync each with the same wallet. So this is why we are getting all these replays. Each coin created before the hard fork actually exists in both chains. If you move the same coin (the coin had to have existed before the hard fork) from wallet 0x2.... to 0x3.... on the ETH network, the transaction will in most cases move the same coin from wallet 0x2.... to 0x3.... on the ETC network. Of course the coins need to be in the same wallet on each chain for this to occur. This won't happen if the coin is on 0x2.... on ETC and ox7.... on ETH. 

No one predicted that ETC would live on as long as it has or at least no one planned for it. Each side is simply telling the other that they should be the one to hard fork and fix the issue. Personally  I think this a huge vulnerability for Ethereum and should be seriously considered and considered carefully. I'm leaning on the side of "we should fix this and move on". For those of you in the other camp "Do nothing", do we really want this hanging over our heads? Not to mention what, about all extra processing the Ethereum network is doing to support ETC? Is it possible that something much worse could happen with all of these transaction from both chains colliding like this (I can't think of any issues right now, but do we want to be wishing later that we did something when the unexpected happens)? I'd love to hear your thoughts on this.