It was a bunch of different bugs We're trying to figure out the architecture over on this other thread - https://news.ycombinator.com/item?id=38954516 https://

It was a bunch of different bugs We're trying to figure out the architecture over on this other thread - https://news.ycombinator.com/item?id=38954516 https://news.ycombinator.com/item?id=38954516 But basically it was based on a sortof replicated XML database that sent text files back and forth, so the basics of synchronisation and consensus were just not covered properly. e.g. if someone kept pressing a key when the screen was frozen, duplicate transactions got created. Or if they turned their machine off earlier than 5pm, end-of-day processes did not get run properly. Or if their node was trying to synchronise with the central node a bit later than normal and the central node was doing a 'reindexing' operation, their messages got lost. Lots of edge case synronisation bugs basically. edit: also here's a good computerphile video about the bugs https://www.youtube.com/watch?v=hBJm9ZYqL10 https://www.youtube.com/watch?v=hBJm9ZYqL10