Re:Kraken Goes Down for 40 Hours, Drawing Mt. Gox Comparisons
by verroq on Saturday January 13, 2018 @04:48AM
(#16138946)
They could have left the legacy system running before switching irreversibly to the new bugged system. That way they can rollback the change.
[ Parent
| on HN ]
Re:Kraken Goes Down for 40 Hours, Drawing Mt. Gox Comparisons
by evgen on Saturday January 13, 2018 @05:09AM
(#16138984)
Unless the bug being fixed was some sort of critical security failure that enabled people to game the exchange or manipulate balances. I am guessing this is more of a screw-up by amateurs than a 'take it all down until this hole is patched' situation, but there is a slim possibility that keeping it up was a bigger risk than the reputation hit of extended downtime.
Re:Kraken Goes Down for 40 Hours, Drawing Mt. Gox Comparisons
by hrpnk on Saturday January 13, 2018 @05:25AM
(#16139023)
Looks like these are announced improvements to the Exchange engine. Really look forward to a post-mortem on this issue.
Curious if they had issues with database migrations or such, that required recovery from backup in case of errors. Plus, for sure there were bugs in the code itself.
Re:Kraken Goes Down for 40 Hours, Drawing Mt. Gox Comparisons
by bufferoverflow on Saturday January 13, 2018 @05:50AM
(#16139068)
No, they couldn't. It's a large trading platform. Any serious bug can lead to the theft of tens of millions of dollars worth of cryptocurrencies.