1/ CVE-2018-17144 happens and you see a bunch of PoW & Core haters coming out of the woodwork. But they still fail at basic logical reasoning.https://twitter.com/killerstorm/status/1043243532423753729 …
-
-
4/ You can simultaneously believe in (a) & (b). There’s no contradiction here. Engineering is both about the minimization of catastrophic failures, AND still expect a reasonable rate of failures.
Show this thread -
5/ Such is the unfortunate nature of software. Software abstractions are great but often times they are constrained by human’s inability to reason with absolute precision & comprehensiveness, unlike a machine.
Show this thread -
6/ Human intellect is analog, while “perfect" software requires digital precision. I learned this lesson the hard way from 10+ years of writing software. I've seen many amazing & super intelligent programmers, I've seen no programmers that don't make (serious) mistakes.
Show this thread -
7/ CVE-2018-17144 is evidence that shit will hit the fans *despite how good of a dev team you have*. I can bet hands-down that for every serious bug Bitcoin Core has, there are numerous equally serious bugs in your centralized and/or PoS shitcoins.
Show this thread -
8/ PoS problems are apparent to many without even writing a single line of code
That is another job of good engineers: to point out errors way before shit gets implemented.
Engineers who correctly conclude PoS is inferior will potentially save you millions down the line.Show this thread -
9/ CVE-2018-17144 also reaffirms my belief that the Bitcoin protocol should ossify quickly. We *might* not even get to integrate Privacy, but that’s the price we have to pay if we want to not jeopardize this soon-to-be trillion-dollar foundation. The stake is already too high.
Show this thread
End of conversation
New conversation -
-
-
And not all mistakes are created equal...
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
