---
# System prepended metadata

title: Weeks Six and Seven EPF6
tags: [EPF]

---

---
title: Weeks Six and Seven EPF6
tags: [EPF]
---


# An Insight Into the Implementation 

Since the [last update](https://hackmd.io/@0xEllie/HJGqDw9Iee), I've spent more of my time inspecting and debugging Besu's code base to meet the needs of the proposal. Fortunately, I've got feedback on my proposal [here](https://github.com/eth-protocol-fellows/cohort-six/pull/188), which I saw as a lantern to light the path. I needed to first see what this software looks like from the outside. How an amateur user is going to run an Ephemery node, and what is missing in terms of functionality and such. Thus, I ran the Ephemery testnet with Besu and Teku and got my lessons from it. The second step was to get inside the implementation to get an intuition on the path for development and, based on that, plan a roadmap. In the third phase, I rewrote the proposal and finally got it merged. I spent time on the codebase of Besu again and also wrote a tutorial on running Ephemery with Besu and Teku. 

Overall, I believe that writing the project proposal gave me the opportunity to have an insight into the tasks before I begin working on them. It allowed me to better understand the specifics of the steps that lie ahead on my journey. It also gives me a better measurement to evaluate my work afterwards. Without it, I would've jumped into the implementation phase right away. So it would typically be like other enterprise projects I've worked on in the past, with a lot of pressure on me, no time to prepare for implementation, and a lot of stress. However, I appreciate my past; it shaped who I am today. 

[Link to running Ephemery tutorial](https://hackmd.io/@0xEllie/SJdF71Kvxx)

[Link to my final proposal](https://github.com/eth-protocol-fellows/cohort-six/blob/master/projects/Ephemery-Besu-Implementation.md)