Discover and read the best of Twitter Threads about #microlecture
Most recents (2)
I always thought the word "bug" was too diminutive. "Flaw" is often more appropriate. I don't understand someone trying to draw a distinction between bug and typo.
Typos happen in text.
Problems that affect execution are "bugs."
Any divergence from a specification are "flaws."
Not all bugs are flaws. Some unexpected behaviors do not affect user expectations.
Problems that affect execution are "bugs."
Any divergence from a specification are "flaws."
Not all bugs are flaws. Some unexpected behaviors do not affect user expectations.
If I expect to get my money back, and I don't, that's a flaw. It violates their contract with me, the user. It's severe.
If there's some weird unanticipated behavior, it's a bug.
If an error message has a misspelling, that's a typo.
If there's some weird unanticipated behavior, it's a bug.
If an error message has a misspelling, that's a typo.
Ok, there is a terribly wrong framework emerging around consensus protocols. People think that PoW and PoS are consensus protocols, and that they are the only two consensus protocols out there.
This is false. Let me explain.
This is false. Let me explain.
Proof-of-Work and Proof-of-Stake are **sybil control mechanisms**. PoS doesn't achieve consensus by itself. It has to be coupled with a protocol, such as PBFT, or Ben-Or, or Tendermint/Cosmos, or Avalanche, to make decisions.
PoW, by itself, isn't a consensus mechanism. In BTC/BCH, it works with the heaviest/"longest" chain selection rule to achieve consensus. PoW by itself can be used to thwart spam, as originally proposed by Dwork&Naor. PoW doesn't get you agreement, it gets you rate limiting.
