arXiv:2003.03052cs.CR
We present "Gasper," a proof-of-stake-based consensus protocol, which is an idealized version of the proposed Ethereum 2.0 beacon chain. The protocol combines Casper FFG, a finality tool, with LMD GHOST, a fork-choice rule. We prove safety, plausible liveness, and probabilistic liveness under different sets of assumptions.
Linked by 4 identifiable commenters in 7 comments across 7 threads, from Feb 2021 to Aug 2022.
If you really want to dig in, here are the key papers on the PoS algorithm: https://arxiv.org/abs/1710.09437 https://arxiv.org/abs/2003.03052 To learn about the sharding plan and various other stuff in the roadmap, this is a great technical overview…
If you want more details you can always read the Gasper paper[1], the spec[2], or client code. It is complex to somebody not familiar with consensus and blockchain execution, but you might say that about any modern engineering. PoW is undoubtedly simpler but also exponentially…
> if over 1/3 of the staked coins are malicious So now you've escalated the attack to be a 33% staker, which I don't think you'd mentioned before. I'll note that 33% of stake is likely to cost more than 50% of mining hardware, and certainly would at the high levels of staking…
It's a relevant answer to your personal attack "I don't think you've studied how the attack would work." My job is literally implementing proof-of-stake securely. Also when I work and implement an algorithm, I provide references and sources, which my PR is. > The coordinated…
Here are the two papers on Casper: Casper the Friendly Finality Gadget: https://arxiv.org/abs/1710.09437 Combining GHOST and Casper: https://arxiv.org/abs/2003.03052 A very simple summary is that it's a fairly traditional consensus protocol, in which if anyone breaks the rules…
Shard execution isn't necessary for migrating to proof-of-stake. The PoS migration just links a single EVM to the beacon chain; that's enough to remove PoW, i.e. the main concern in this discussion about GPUs. Around the same time is the migration to data sharding, which…
Connected through shared HN threads, not inferred similarity or a recommendation.
Do you have any explanations of proof of stake? I've tried to read https://ethereum.org/en/developers/docs/consensus-mechanisms... and https://arxiv.org/pdf/2003.03052.pdf but I feel they're intentionally obfuscated. I understand proof of work very well. I tried reading the…
Jasper_View on HNParent context