---
# System prepended metadata

title: Update 4 - week 3

---

# Update 4 - Week 3: Navigating New Paths and Shifting Focus

## Encounter with Kev?

In my previous update, I was eagerly anticipating a meeting with Kev. However, I must admit that this endeavor has not borne fruit thus far. The anticipated meetup did not exactly materialize. I have discussed the issues with Josh, and new suggestions have surfaced regarding potential mentors. While I'm awaiting the contact details of these suggested mentors, I'm gearing up to initiate contact and explore these alternative avenues.


## Exploring Nim

During this interlude, I've dived into the world of Nim, a programming language that blends the familiar syntax of Python with the potential for low-level manipulations. The experience has been thoroughly engaging, allowing me to grasp various concepts with relative ease. Nim's unique amalgamation of features has indeed made for a stimulating learning experience.


## Observations from Fellow Fellows and the Nimbus Niche

I took the time to read the development updates shared by my fellow participants. An interesting trend caught my attention: a considerable number of participants who are either aligned with Nim or are collaborating on projects proposed by Zahary of the Nimbus team seem to be gravitating towards the Verkle tree. It's intriguing to note that there appears to be less focus on the extended features projects of Nimbus_eth2. This observation has sparked an idea that might guide my future direction.


## The Allure of Nimbus Team's Openness and Hospitality

Notably, I've discerned that the Nimbus team possesses a commendable openness and a welcoming atmosphere. This observation serves as a testament to the conducive environment they've fostered from the updates I have seen of fellows.


## Project Pivot: Evaluating the Viability of My Initial Proposal

Reflecting on my initial project proposal centered around enhancing bip32 keys. This project was sparked by Paul Miller's critique of the current design, and while the implications extend to Ethereum's bip32 usage, I find myself questioning its suitability for the Ethereum Protocol Fellowship. It's prudent to consider whether this proposal aligns seamlessly with Ethereum's roadmap and whether it has been acknowledged as a pressing concern within the Ethereum ecosystem. This evaluation underscores the crucial need for mentors' review, as their expertise could provide clarity on the project's scope within the program.


## Taking Charge: Navigating the Path Forward

While awaiting potential mentor contacts, I recognize the urgency of my situation. The time has come to embark on a swift yet thorough immersion into Nimbus_eth2. The pressing need for a change in project direction necessitates rapid adaptation, and I'm committed to bridging the gap in my knowledge swiftly.

In conclusion, this period has been one of introspection, adaptability, and a renewed sense of purpose. I remain steadfast in my commitment to contributing meaningfully to the Ethereum ecosystem, and I eagerly anticipate the guidance and insights that the upcoming weeks will undoubtedly bring.