> and assumes that 1/3+ must be "bad"? // That's not an assumption, that's just a result of the facts of the consensus algorithm. It says that a fork won't happen if +1/3 *aren't* bad. You've completely misunderstood even the most basic logical statement about BFT/Tendermint.
By "cheating" I mean Bitcoin doesn't _really_ give you the C in CAP - consistency. But it's close.
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
PoW breaks down and loses "pseudo-consistency" in the case of a 51% attack. Just like Tendermint does at +1/3. (the sacrifice of 1/2 -> 1/3 is for safety in asynchrony)
-
“Breakdown” is accurate for PoS but not accurate for PoW. 51% attack in PoW only causes partial degradation (“graceful”). Ledger history is still next to impossible to rewrite & double-spending is possible but costly to pull off. I discussed this in my articles. Good night.
End of conversation
New conversation -
-
-
You can pretty easily configure PoS so that it mimics Bitcoin’s particular safety/liveness/economic cost tradeoffs. But it would be pretty silly to
-
You could punish forks only based on their depths (so longer forks are more expensive, like they are in PoW)
-
And the reason it would be silly is that you have the ability to punish maximally for any fork, no matter how long, which like, why wouldn't you?
-
Argh Sunny get on board with partial slashing, mechanism design has so much more depth to offer than just “off with her head” for everything!
-
Off-topic for the thread, but "Off with her head" gives your mechanism the greatest protection from external pressures
-
Not necessarily! Just like punishing every crime with capital punishment would probably increase rather than decrease crime
-
Check out partial slashing. (Best explanation I can find online starts on page 161 of
@karl_dot_tech's BPASE presentation: https://cyber.stanford.edu/sites/default/files/ethereum_proof_of_stake_casper_ffg_2017_chronicles.pdf …) - 4 more replies
New conversation -
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.

