Update docs v1 dv

docs/docs/intro.md

@@ -7,5 +7,4 @@ sidebar_position: 1
 
 ![Commit Boost Logo](/img/logo.jpg)
 
-Commit-Boost is a new Ethereum validator sidecar focused on standardizing the last mile of communication between validators and third-party protocols. It is fully compatible with [MEV-Boost](https://github.com/flashbots/mev-boost) and can also act as a validator platform to enable optional safe commitments. It's being developed in Rust from scratch, with the goal of widening the range of different proposer commitments protocols, and open the design space around them.
-
+Due to the risks developing for Ethereum, core development, and its validators set, a group of teams / individuals are working on developing a public good called Commit-Boost. Commit-Boost is an open-source public good that is fully compatible with [MEV-Boost](https://github.com/flashbots/mev-boost), but acts as a light-weight validator platform to safely make commitments. Specifically, Commit-Boost is a new Ethereum validator sidecar focused on standardizing the last mile of communication between validators and third-party protocols. It's being developed in Rust from scratch, and has been designed with safety and modularity at its core, with the goal of not limiting the market downstream including stakeholders, flows, proposer commitments, enforcement mechanisms, etc.

docs/docs/overview.md

@@ -5,14 +5,20 @@ sidebar_position: 2
 # Overview
 
 ## Background
-- Proposer commitments have been an important part of Ethereum’s history and continue to be a powerful unlock for Ethereum validators
-- Today, more than 90% of Ethereum validators make a wholesale commitment by outsourcing block production to external third parties via [MEV-Boost](https://github.com/flashbots/mev-boost)
-- By outsourcing completely block production, validators lose autonomy over the block. Allowing validators to make more granular commitments unlocks a significant design space and opportunity for validators and Ethereum at large
-- There is already great interest in the use cases enabled by granular proposer commitments, for example preconfirmations and inclusion lists
-- This interest and the proliferation of different commitment protocols carries an inherent risk of fragmentation and cross-protocol compatibility issues
+- Proposer commitments have been an important part of Ethereum’s history. Today, we already see the power of commitments where over  90% of validators give up their autonomy and make a wholesale commitment that outsources block building to a sophisticated actor called a block builder 
+- However, most are starting to agree on a common denominator: in the future, beacon proposers will face a broader set of options of what they may “commit" to–be it inclusions lists or preconfs or other types of commitments such as long-dated blockspace futures–compared to just an external or local payload they see today
+- A recent post from Barnabe captures this well; during block construction, the validator “…creates the specs, or the template, by which the resulting block must be created, and the builders engaged by the proposer are tasked with delivering the block according to its specifications”
+- While this all seems great, the challenge is that many teams building commitments are creating new sidecars driving fragmentation and risks for Ethereum
+- For Ethereum, there are going to be significant challenges and increased risks during upgrades if there are a handful of sidecars validators are running 
+- For validators, these risks potentially take us to a world where proposers will need to make decisions on which teams to “bet on” and which sidecars they will need to run to participate in what those teams are offering
+- For homestakers, this is difficult and they likely will be unable to participate in more than one of these commitments
+- For sophisticated actors, this increases the attack vector and operational complexity as more and more sidecars are required to be run
+- Another side effect of this is validators are somewhat locked into using a specific sidecar due to limited operational capacity and the switching costs of running a different sidecar (i.e., vendor lock-in). The higher the switching costs, the more embedded network effects could become if these sidecars only support certain downstream actors / proposer commitment protocols 
+- This also could create a dynamic where core out-of-protocol infrastructure supporting Ethereum which should be a public good, starts being used for monetization, distribution, or other purposes
 - Commit-Boost aims to standardize how proposer commitment protocols communicate with the proposer, by providing a unified interface implemented in a single validator sidecar with the goal of reducing fragmentations
 
 ## Goals
+- Unify behind a software / standard to reduce fragmentation risks for Ethereum and its validators, while ensuring open innovation downstream from the proposer can flourish
 - Create a neutral, open-source, public good for the safe development and distribution of proposer commitments protocols
 - Provide a well-tested, reliable validator sidecar with support for advanced observability and telemetry
 
@@ -26,4 +32,4 @@ sidebar_position: 2
 ### For developers
 - A modular platform to develop and distribute proposer commitments protocols
 - A single API to interact with validators
-- Support for hard-forks and new protocol requirements
+- Support for hard-forks and new protocol requirements