# EPF5 Week-11: Project adjustments
## Week overview
- [X] Completed the draft Lighthouse metrics.
- [X] Integrated the dashboard into EthPandaOps Grafana.
- [X] Had a productive discussion with Parithosh about my project, incorporating his recommendations.
- [X] Initiated work on Teku metrics.
- [X] Contributed the draft table containing PeerDAS metrics to the forked beacon-metrics repository.
- [X] Distributed the Lighthouse dashboard among other teams as an exemple.
- [X] Began collaborating with Hangleang on developing Grandine metrics.
This week started with talking to Parithosh about my project. We decided to make some changes. Also, I continued working on the dashboards. I finished the Lighthouse metrics draft and moved on to other clients.
### Project changes
During our recent call, Parithosh provided valuable feedback regarding the current phase of the PeerDAS project. He indicated that focusing on the API might not be as beneficial at this point due to the frequent changes in specifications. Instead, what would prove more useful to the DevOps team is standardizing metrics across all clients. By calculating average values for these metrics and compiling them into a comprehensive summary dashboard, we can facilitate more effective testing and monitoring of PeerDAS by both the DevOps and CL teams.
### Lighthouse metrics
This week, I received feedback from Jimmy that my dashboard was helpful in monitoring node bandwidth. Additionally, João provided assistance with libp2p metrics, enabling me to complete the draft metrics for Lighthouse and push my updates. Now, I am awaiting the team's review.
### EthPandaOps Grafana
I've set up my folder within EthPandaOps Grafana in preparation for creating future dashboards. I've imported the Lighthouse dashboard, though it requires some adjustments. However, I'll need to wait for the launch of devnet-2 to access the necessary metrics for further refinement.
### Beacon metrics
Following our discussions with Parithosh, I initiated the creation of the PeerDAS metrics table in the Beacon Metrics forked repository. It is now pending review by Jimmy. Once approved, I plan to share it with the CL teams.
### Grandine collaboration
I participated in the Grandine call sharing my updates. As a result, we decided to collaborate with Hangleang on developing PeerDS metrics. I've already begun by creating an initial overview of the DAS branch for metrics, identifying several key indicators. I intend to continue refining these metrics to progress further with the development of the Grandine dashboard.
## Weekly EPF Activity
- [EPF5 Standup]()
- [EPF5 Office Hours](https://youtu.be/K1HELi5iy9E)
AMA with Lightclient
- [PeerDAS Breakout Room #6](https://github.com/ethereum/pm/issues/1136)
Clients updates
[Spec without peer sampling #3870](https://github.com/ethereum/consensus-specs/pull/3870)
[PeerDASwithout peer sampling](https://hackmd.io/@fradamt/no-peer-sampling)
- [Grandine Call]()
- [ACDC #140]( https://www.youtube.com/live/hSNJ6vURfmE
)
[Github issue #1129](https://github.com/ethereum/pm/issues/1129)
Devnet-2: blockers, issues. Devnet-3. EIP-7251. Execution requests. PeerDAS.
## TODO
- [ ] Get Lighthouse review and implement any necessary corrections.
- [ ] Proceed with the development of Teku and Grandine metrics.
- [ ] Begin exploring Prysm metrics.
- [ ] Retrieve metric values from the Lighthouse dashboard.
- [ ] Build the EthPandaOps Grafana dashboard upon the launch of devnet-2.
## Links
[EIP-7742: Uncouple blob count between CL and EL](https://eips.ethereum.org/EIPS/eip-7742)
[Consensus specs: Alpha-5 release](https://github.com/ethereum/consensus-specs/releases/tag/v1.5.0-alpha.5)
[EIP.directory by Radek](https://eip.directory/)
[My Lighthouse PR](https://github.com/sigp/lighthouse/pull/6248)
[PeerDAS metrics table](https://github.com/KatyaRyazantseva/beacon-metrics/blob/master/metrics.md#peerdas-metrics)