Bleutrade HTML5 Volume: 32,915,617.37178000
Actually Bleutrade volume is well over a billion in the past 48 hours due to the dumping of coins into what are normally crazy low priced orders that would normally never be filled. Two low priced orders traded over a half billion coins.
For the record I am
NOT saying anyone is dumping the Cryptsy wallets. I would like to see the wallets to confirm they are corrupt. I am simply trying to understand why we have had this massive meltdown and huge dumping.
There was clearly something going on the past 48 hours and now we have confirmation of that: A 51% ATTACK.NEWS from Bluetrade: "NOTICE: [HTML5] Wallet maintenance. A 51% attack was successful at Html5coin and transactions were erased. Due to this vulnerability Html5coin will be removed soon."The exchange has confirmed the coin is under attack, and they are going to delete the coin. This means there really is nowhere to trade and we are finished. The only other trading pair on Yobit is BTC and that is little volume. What a total shame. I have put years into this coin, and have had hash on it continually for the past two years to keep it moving when it was mostly abandoned.
There has been massive hash showing up here and there and in the past few days in the order of 100MH (today it's gone). For the first time in a long time my Solo servers where offline late Sunday night to early Wednesday morning. I was away and could not restore them. A good time for someone to attack where there was no opposition.
Very disheartening to see this happening, this was my favorite, and the one I dedicated my servers to keeping my alive. This seems to be the end of the line for X15 coins, the end of an era. I am not aware of any other viable X15 coins.
hmmm.... i have a node running and my debug shows a LOT of 1 to 3 block reorganizations done by the chain. which. isnt bad. but its not a good sign. and recently there were 2 larger reorgs of 36 blocks and 25 blocks. bleutrade is probably referencing one of those two reorgs as lost transactions. there probably is some editing that needs to be done to the code. but this is mostly due to a lack of hashing power on POWs part
edit: there is also some evidence of a second or possibly third fork in the chain. it mostly looks like the network might be segmented
