Our great sponsors
-
annotated-spec
Vitalik's annotated eth2 spec. Not intended to be "the" annotated spec; other documents like Ben Edgington's https://benjaminion.xyz/eth2-annotated-spec/ also exist. This one is intended to focus more on design rationale.
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
Even a relatively light reading of the Annotated Spec[1] for Eth2 and/or the Eth Org's Proof of Stake FAQs[2] suggests the designers (and independent implementer-teams who gave feedback to designers... lather, rinse, repeat) understand it's important to consider the overall system "outside of the comfort zone".
[1] https://github.com/ethereum/annotated-spec/blob/master/phase...
[2] https://eth.wiki/en/concepts/proof-of-stake-faqs
> You can literally validate the entire chain with a simple python script.
I challenge you to present a "simple python script" that implements the exact same consensus rules that bitcoin core does. Bitcoin is not all that simple and there's a nontrivial amount of complexity in bitcoin script [1].
> The chain is validated in its entirety upon first sync. 100% from genesis to tip.
The default behaviour is to skip signature verification for all signatures before some relatively recent block [2].
[1] https://github.com/bitcoin/bitcoin/blob/master/src/script/in...