---
title: Weeks Sixteen and Seventeen EPF6
tags: [EPF]
---

# Second-guessing my Last PR along with Tests

Since the last update, I've been working on two major things. First, working on the last PR. I haven't heard from Justin, probably because the team is busy these days. Devconnect is close, and deadlines are close as well. However, I reviewed my last PR. The last PR was about resolving Justin's feedback; I gave it a second guess and moved some of `initialProcess()` steps out of the Ephemery cycle.

The rationale and details of it are in the description.

[Link to my review PR](https://github.com/hyperledger/besu/pull/9210/commits/1ae2f079a9f8a1dc9bb37ce34687f0e1b352e52a)

[Link to description of the review PR](https://github.com/hyperledger/besu/pull/9210#issuecomment-3417685791)

The second thing I spent much time on was the test for Ephemery. I've provided a screenshot of logs before and after two cycles of Ephemery in the PR description. The screenshots show that after each cycle, peer discovery is going to refresh. Tests are also going to substantiate the proof and provide robust proofs for peers' refreshing task. That being said, these tests are going to prove:

- At every update ephemery peers will start over.
- When ephemery stops, peer discovery will stop.
- At every cycle, the database directory will be changed to a new one.

[Link to the tests PR](https://github.com/hyperledger/besu/pull/9210/commits/a83d59e0e9ac2f78352718d1fb42d819ad73b6b9)

[Link to description of the tests PR](https://github.com/hyperledger/besu/pull/9210#issuecomment-3417692516)

Screenshots of tests that shows the peering restarts after each Ephemery reset:


(The discovery agent starts over and peers with different nodes after each cycle)

### Where were we?

Based on my roadmap in my proposal, I should be working on the genesis file task, but I want to be finished with ephemery implementation. So I might want to start working on ***Weeks 20 and 21: research on how to enable the Besu client itself to become a bootnode*** and skip the tasks for Weeks 18 and 19.

>Weeks 14 and 15
>- Research on the 'reset peers' task.
>- Implement the task.

I finished This👆🏻 task, tests and screenshots prove it.
>Weeks 16 and 17
>- Plan and implement to enable the bootnode command to read from a file or URL.
>- Implement the task.
>- Write related tests.

This👆🏻 issue already has been merged and closed by someone else

>Weeks 18 and 19
>- Start working on an idea to parse the genesis file in a more general way so that it is in compliance with other client genesis.
>- Implement the task.
>- Write related tests.
>
>Weeks 20 and 21
>- research on how to enable the Besu client itself to become a bootnode.
>
>- Implement the task.
>- Write related tests.

This 👆🏻 task I'm going to work on next