Guys, do not bother with FUD by BitcoinEXpress. He is old member of this forum and he perfectly knows how cryptocoins work which means he
knows stuff he posted here is not all true. There can not be hard-fork if nodes on network use the same version! What happened (again) is 1GH
pool, people who were behind 51% attack on Bter, attempted and successfuly completed another 51% attack but this time revealing the origin
of it e.g. made it obvious it is they who are doing shits. Basically, what happened is large blockchain reorganization. At some point 1GH stopped
mining on legit blockchain, went off the network and used combined hashpower of miners (yes, you retards still mining there) to create second
version of blockchain which, due to them having way over 51% of total hashpower, became longer than legit blockchain (more work done). In the
meantime they made some transactions on legit blockchain, most likely sent MAX to exchanges to dump them, and once they dumped those coins
they withdrew BTC from exchanges and connected back to network. Since their node has version of blockchain longer (more work done) than all
other nodes, 1GH's version of blockchain started propagating through Maxcoin network, overwritting blocks and thus transactions that happened
on legit blockchain since 1GH went off network (that means transaction which moved 1GH's coins to exchange never happened and that means
exchange lost BTC). Due to size of new version of blockchain (in megabytes) and generaly very bussy MAX network (30 seconds blocktime is still
an overkill), what happened is that slower nodes switched to 1GH's version of blockchain with very noticable delay. Not everyone use super fast
Internet connection so 1GH's version of blockchain could not propagate to all nodes in a second! To put things for you into perspective, on Bitcoin
network which uses 10 minutes block time (much less traffic than with Maxcoin) it is observed that it can take up to 40 seconds for data to reach
all nodes. Now imagine Maxcoin where network activity is high by default due to 30 seconds block time then add megabytes more in an instant! Of
course, some nodes will almost halt, especially nodes run on slow computers. But after a while all nodes will have the same version of blockchain,
in this case 1GH's version. To sum it up, what happened is perfectly normal considering that Maxcoin uses 30 seconds block time. There is no need
for dev to add checkpoints. What is needed is that idiots still mining at 1GH move to some other pools.
TLDR - BitcoinEXpress wants to negatively affect MAX price or he is pissed off cause blocks he mined ended up orphaned by blocks mined by 1GH.
There were two forks and 1GH was aware of it. 1GH was DDoS'd for a while till they pulled back below 50% for a while to allow the chain to merge. The Maxcointicker and Rocketpool both went off line for about two hours.
Bullshit, you cannot merge the chain back in time. Besides, none of the pools shows the chain of orphans that a 'wrong' fork would become.
It is not called merging but overwritting. Unless there are checkpoints added at certain block heights, attacker can overwrite all blocks down to but
excluding genesis block. In other words, if there are no checkpoints, genesis block is the only block hard-coded in wallet and thus permanent for
that version of wallet. All other blocks can be overwritten and that is the reason why any decent cryptocoin dev occassionaly adds checkpoints. As
for the no orphans shown at other pools, since 1 GH has massive hashrate once they went off network other pools mined not so many blocks. Some
pools mined maybe a block or two. If those blocks are later labeled as orphans no one would notice something very unusual. Given that orphans are
not so uncommon with 30 second block times, you would not notice a long serie of orphans (long reorg) anywhere except in wallet's debug.log file.
"He's currently DDoS'ing pools! And likes to impersonate Asian women!" by Simran
"I call for death penalty" by Satoshi
