From 52caba6eae98169549b78b3e5f5219f79c0db740 Mon Sep 17 00:00:00 2001 From: Paul Hauner Date: Tue, 18 Jan 2022 11:28:08 +1100 Subject: [PATCH] Add section about backwards compat --- sync/optimistic.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/sync/optimistic.md b/sync/optimistic.md index 88dc28444..d794269a2 100644 --- a/sync/optimistic.md +++ b/sync/optimistic.md @@ -9,6 +9,13 @@ of the chain, it may be desirable for a consensus engine to import beacon blocks without verifying the execution payloads. This partial sync is called an *optimistic sync*. +Optimistic sync is designed to be opt-in and backwards compatible (i.e., +non-optimistic nodes can tolerate optimistic nodes on the network and vice +versa). Optimistic sync is not a fundamental requirement for consensus nodes. +Rather, it's a stop-gap measure to allow execution nodes to sync via +established methods until future Ethereum roadmap items are implemented (e.g., +statelessness). + ## Constants |Name|Value|Unit