HackMD
Dev Update Week 5 (robzajac)
Update
Last week:
- Finished writing the light client project proposal. Submitted to EPF repo and presented in office hours.
- Added feedback around testing light client APIs with Hive and exploring different incentivization solutions e.g. Vipnode, POKT Network, and any designs used in the Portal Network
- Sent proposal to mentors and started discussion with teku team about caching light client data in the implementations of
GetLightClientBootstrapandGetLightClientUpdatesByRange- By default teku runs in "prune" mode which doesn't store any finalized
BeaconStateto save disk space. Only the latest state may be available. But the light client APIs may request information derived from the state (sync committee and sync committee branch) from as far as 5 months ago. It would be quite expensive for nodes to store 5 months of finalized states, so instead we propose caching light client data for the duration of the light client period (same retention period as blocks) - To avoid adding the extra computational and storage requirements to all nodes, light client APIs will run behind a flag
- Updated teku tracking in issue
- By default teku runs in "prune" mode which doesn't store any finalized
- Continued reading the Eth2 book for more information on construction of the consensus layer
- Needed to understand the structure of
BeaconStateto inform implementation of the light client data cache in teku
- Needed to understand the structure of
- Began implementation of
GetLightClientBootsrapin teku
Goals this week:
- PR
GetLightClientBootstrap - Continue design & begin implementation of light client data cache
- Reach out to past researchers in light client incentivization, such as zsolt from geth
