1/ Thinking about things in terms of worst-case-scenarios is not normal, even for trained specialists. Most projects in the crypto space spend the majority of their time analyzing the best-case & average-case, and zero time on the worst-case.
-
Show this thread
-
2/ It’s pretty scary that 6 months after I wrote about worst-case scenarios (in the context of PoW vs. PoS), Bitcoin has a consensus-critical, inflationary bug. If Bitcoin Core can fuck up, then 100% guaranteed other projects can fuck up. A lot more.https://medium.com/@hugonguyen/proof-of-stake-the-wrong-engineering-mindset-15e641ab65a2 …
1 reply 1 retweet 5 likesShow this thread -
3/ CVE-2018-17144 is not evidence of Bitcoin Core’s lack of excellence - although I’m sure things can be improved in the code documentation / test coverage areas. It is evidence that shit will hit the fan despite having an excellent team.
1 reply 1 retweet 5 likesShow this thread -
4/ Worst-case-scenarios thinking is an absolute must, *especially* because software (and the human mind) is highly fallible.
1 reply 0 retweets 1 likeShow this thread
5/ I wrote this article explaining the underlying cause behind CVE-2018-17144. But this is just *one* reason among many on why bugs are an inevitability in software. The world of software is highly imperfect. It is a lot more arts than science.https://medium.com/@hugonguyen/code-reusability-vs-accidental-commonness-89e2b2b007cd …
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.
