During the last 2 weeks of the 5th EPF cohort, my work was focused on a design validation document (pseudocode), with a Python project and pytests attached, in order to prove the beacon-chain accounting model I proposed for the eODS feature.
As I mentioned in the Accounting section of eODS design notes, beacon chain accounting already exists under the current protocol, in the form of beacon chain operations, or beacon state mutators, e.g. process_deposit, increase_balance, etc.
Since Accounting is an important part of eODS model, it proved useful to group these functions in a virtual group based on functionality (i.e. accounting) rather than beacon-chain specification appartenance. This document is a study I made on beacon chain accounting under the current Ethereum protocol.
This is the document: Beacon chain accounting - eODS feature
I plan to fix the remaining tests and functions (marked as BROKEN), so that all minimal eODS functionalities in terms of delegators and delegated validators are met, during next 4 weeks and refactor where appropriate, in order to have this Python implementation as close to the logic of beacon-chain specs as possible.