lol
Keccak is SHA3..
which will totally kill off ASICs of todays current design.. and would cause the system to take weeks to solve one block because the difficulty is soo high, by the time that 2016 blocks are solved (years) to then downgrade difficulty, would be too late... ASIC producers would have created a SHA3 asic chip. and the chinese manufacturers would dominate again..
all because it costs them $200 to make the asic but sell it to others for $2000, meaning for every unit a competitor buys.. the competitor is literally handing the chinese manufacturer multiple units for free.
it solves nothing short term or long term..
instead:
the only way to solve centralization, without delaying blocks for months by changing the algorithm, without just making it a stopgap to repeat again next year and without risking security by allowing single user to be more powerful than super computer power...
is to ignore a solved block provided by the same known pool if it solves more than 3 blocks an hour.
infact implementing a rule to ignore a pool for atleast 6 blocks means there will be atleast 6 pools on equal footing
EG
00:05:00am bl400000 -BTCC.com
00:15:00am bl400001 -BTCC.com (ignored)00:15:02am bl400001 -Iceland.com
00:25:00am bl400002 -BTCC.com (ignored)00:25:02am bl400002 -iceland.com (ignored)00:15:04am bl400001 -canada.com
00:35:00am bl400003 -BTCC.com (ignored)00:35:02am bl400003 -iceland.com (ignored)00:35:04am bl400003 -canada.com (ignored)00:35:06am bl400003 -Emerica.com
00:45:00am bl400004 -BTCC.com (ignored)00:45:02am bl400004 -iceland.com (ignored)00:45:04am bl400004 -canada.com (ignored)00:45:06am bl400004 -Emerica.com (ignored)00:45:08am bl400004 -England.com
00:55:00am bl400005 -BTCC.com (ignored)00:55:02am bl400005 -iceland.com (ignored)00:55:04am bl400005 -canada.com (ignored)00:55:06am bl400005 -Emerica.com (ignored)00:55:08am bl400005 -England.com (ignored)00:55:10am bl400005 -france.com
01:05:00am bl400006 -BTCC.com
01:15:00am bl400007 -BTCC.com (ignored)01:15:02am bl400007 -Iceland.com
blah blah blah you get the idea.
i personally dont like this idea as it messes with consensus and can be abused to not relay certain miners block based on emotion rather than security strength of the solution. but atleast its easier to implement than luke jr's version which is just a short stop gap, with lots of immediate negative repercussions and by the time it settles down the stopgap is over and dominance begins again