Try   HackMD

eODS design rationale development

I settled on a design rationale detail, regarding enshrining Delegators.

Related to building the beacon-chain Delegators registry, I'm going for adding the new class Delegator container in the beacon-chain specs and NOT alter existing containers with new fields (as previously intended), in order to introduce as few breaking changes as possible.

This reflected in the Project Proposal, and in the:

Project presentation slides - for EPF day at ETHCC week

This is the presentation I used at EPF day in Brussels

Week 5 planning

  • Meet permissionless staking pool representative at ETHCC
  • Further look into phase0 deposit-contract and depositcontract.sol and staking-deposit-cli to accommodate Delegations
Last changed by 
 
DanGoron
0
54

Read more

Towards enshrining Delegation in Ethereum protocol

Delegation—the process of assigning staking power or governance authority to a third party—is fundamental in many blockchain ecosystems.Ethereum, however, lacks native delegation support at the protocol level, relying instead on contract-based staking services.While these services have been effective in attracting capital, they introduce centralization risks and governance challenges.

May 8, 2025
Post EPF regular update no.1

regarding the eODS project

Jan 20, 2025
eODS (enshrined Operator-Delegator Separation) design notes

This document contains the design notes for eODS (enshrined Operator-Delegator Separation) specification.

Jan 15, 2025
Final Dev Update - eODS (enshrined Operator Delegator Separation) specification

Abstract: Unbundling the Validator role between Operator and Delegator.

Dec 20, 2024
Read more from DanGoron
Published on HackMD