@vitalik.eth: We should revisit beacon/execution client separation

Submit
vitalik.eth@vitalik.eth

We should be open to revisiting whole beacon/execution client separation thing. Running two daemons and getting them to talk to each other is far more difficult than running one daemon. Our goal is to make the self-sovereign way of using ethereum have good UX. In many cases that means running your own node. The current approach to running your own node adds needless complexity. Short-term, maybe we want some more standardized basic wrapper that lets you install dockers of any client and make them talk to each other easily? Also good that @ethnimbus unified node https://github.com/status-im/nimbus-eth1… exists. Longer term, we should be open to revisiting the whole architecture once @leanethereum lean consensus is more mature.

farcaster.xyz

@vitalik.eth: We should revisit beacon/execution client separation

submitted bymisha13,1837mo
1
Read original article
AI summary of the linked article

Vitalik Buterin argues that Ethereum should be open to revisiting the separation of beacon and execution clients, because running two daemons that must talk to each other is much harder than running one. He says the goal is good user experience for self-sovereign use of Ethereum, which in many cases means running your own node, and that the current setup adds needless complexity. In the short term he suggests a more standardized wrapper for running any clients in Docker and connecting them easily, and he welcomes the unified node in status-im's nimbus-eth1 pull request 3646. Over the longer term he proposes revisiting the whole architecture once lean consensus is more mature.

1 comment
avatar
mishaSubmitter· 7 months ago
Top stories that week →