Quote from: dogeberet on June 18, 2014, 02:02:44 AM

Quote from: defaced on June 14, 2014, 11:55:41 AM

Quote from: xfr on June 14, 2014, 07:36:33 AM

Quote from: MarKusRomanus on June 14, 2014, 06:22:42 AM

I also believe you made a bad chain the official fork.
Our pool is back online with this , uh, "official" blockchain.

lost alot

Same here, several pools have switched over but one can still compare https://altexplorer.net/chain/Franko and https://coinplorer.com/FRK to see that the bad fork that was made official still has 2x lower diff. What a low move....

The reason I chose the shorter chain was because all of the main nodes including cryptsy and coins-e and the two main block explorers were stuck at block 785863 and reporting that specific block as being invalid. Whoever made the invalid block probably did so on an old wallet before the kgw timewarp fix. Some of the pools accepted it while most of the wallets didnt. By the time I released the fix to get cryptsy syncing again the chain autocorrected and orphaned the longer chain anyways. Why did it do that? Because only a few of the clients were actually accepting it.

So what was the right answer? Allow an invalid block by putting in an "ignore block 785864 it may be invalid but who cares" or orphan a days worth of work to make sure the block chain syncs fine and does so by staying true to the parameters we all agree on.

Altexplorer.net was on the wrong chain, it may be longer, there were a couple pools on the longer chain but it was still an invalid chain, if you dont believe me, set up 2 nodes on a private network with the other chain.. have the one node already have the wrong chain but start the second node from scratch and you will see it doesnt sync past 785863 then check the log and you will see why.

FRK was stuck for 37 hours before anyone noticed, cryptsy needed a fix asap or risk being delisted. So again, what would you have done? I'm sorry some people lost work, I dont have any money to compensate, wish I did but the only option we have is to move forward. We need to do whatever it takes to stay moving forward even if it means to step back a couple steps and correct a problem.

Well, I have been a FRK coin supporter up to now, but if this technically is possible, in my opinion - it deserves to be delisted and go the way of the dodo bird.

How can this sort of thing be expected to get wide acceptance and be treated like a currency when it can go on for 37 hours before anyone notices - and pools can run for days longer with no errors wasting days and days of work.

There have to be innovations to make these blockchains healing and self-correcting or the whole alt coin experiment is just going to be a failure. But we also have to accept failures and move on - which is what we should do with lots of the first round of alt coins, and I am done with this one.

Thing about it is the network IS self healing its just that a multipool using an old client didnt have the timewarp fix and created an invalid block that everyone on the new client refused. Before I even implemented my fix the network already orphaned the longer chain and started the healing process of banning the bad nodes because the legitimate pools mining on the new client started finding blocks that werent being considered stale. Thats the beauty of the bitcoin protocol. Its amazingly elastic.