the EF Protocol Support team has been dissolved 🖖

I was getting questions about recent EF layoffs and my situation so I should share something public as well. I am still part of EF, continuing my work and figuring out what's most needed in the future. However, all of my team, Protocol Support, that I have been part for 5+ years, has been dissolved. And we lost some really great people during this. @joshdavislight is personally the biggest loss for me, although I hope our two ring circus will continue. He came to Ethereum inspired by his friend @pipermerriam and we met to work on a project. Two of us with widely different backgrounds, pretty random match but we found out we have a lot in common, that's why we are here. Starting around 4 years ago, we built EPF together, running cohorts regularly since. It became machine that brings dozens of new core developers, we made friends with so many talented people all over the world. I'm grateful we could do this in tandem with Josh. @wolovim here is the man himself behind Forkcast and the final leader of the team. He stepped up to this role when his original team got dissolved to immediately build a tool that became core to all core development coordination. One of the biggest improvements we saw in years with major step in public and devs being able to follow the process. Huge respect for his skills and dedication, really glad you kept us all together till the end. @dionysuzx Joined him only couple months ago to take Forkcast to next level. One of those people who just showed up in community, you see their motivation and contributions so you just want to work with them! He was able to step up and do great things really fast. I am sure his potential finds even better opportunities in the future. @Butta_eth Who also joined recently but did incredible work in the time. He is the guy who knows everyone and gets stuff done, iykwim👀Managing inputs from the ecosystem, he helped to push core r&d and only in couple of months he ramped up maxEB adoption across the whole network. This was the last iteration of Protocol Support, the team with catch-all name started by @JosefJ_ , pushing whole Ethereum forward for years lead by @TimBeiko and finally being transformed to accelerate core development by @nixorokish. It's been a wild ride to see it all the way from humble beginning, through peak and all the way to the bitter end. RIP @EFprotocol Respect to all quiet builders out there working without fancy loud handles and keeping everything running. Posledný nech zhasne

unfortunately, i was among those laid off from the @ethereumfndn in the last round. over 8+ years, it was a hell of a ride and a genuine joy to work with all my colleagues across three teams (mist browser, python tooling, protocol support) while at the EF; their blend of humility and ambition will continue to inspire my approach to work. immensely grateful to have landed with the protocol support team last year, to whom i pitched my little side project, Forkcast. it felt like a real spark from the start, but Forkcast has grown into something i'm deeply proud of: a tool that is relied on by Ethereum's stewards to understand and react to their complex world. i wake up and go to bed thinking about the nuanced social challenges that Forkcast attempts to tame. the work is meaningful and demands the wide range of technical and non-technical skills i've developed over a 12-year software career. its difficult to imagine stepping away. fortunately, i don't have to just yet. starting with the next three months, i'll be an independent contributor to Forkcast and the ethereum/pm repo, with support from the EF. during that period, i'll also explore what comes next for me, possibly including spinning out Forkcast. the platform makes good sense to me as an independent observer of Ethereum core development and i'd like to hear from individuals and orgs in the ecosystem that want to support that work. gratitude to those that have already reached out to start conversations. DMs open if you want to chat about the future of Forkcast or ways we might work together.

watch Forkcast from the @EFprotocol team steadily become the canonical resource for information on @ethereum upgrades over time can you spot the peaks from the Fusaka fork being announced and then going live?

💯 forkcast is goated for tracking progress

Gotta say that I love how the glamsterdam EIP updates are packaged in a digestible way for different stakeholders. forkcast.org/upgrade/glamste… Kudos @ethereumfndn 7708 is one of those almost invisible things but a big UX unlock for @safe users.

Shoutout to @EFprotocol, forkcast has been great to follow Glamsterdam EIPs closely

Very happy to share that I’ve been accepted into Cohort 7 of the @ethereum Protocol Fellowship, run by the @ethereumfndn's Protocol Support team. I first came across Eth back in late 2017. At the time it was just something I found very interesting. A neutral, permissionless system that anyone could use or build on, not owned by any company, state, or institution. In 2018 I really fell down the rabbit hole when DeFi started kicking off. I found the idea of an open, composable financial layer that anyone could build on top of really compelling. It felt like a completely new design space. From there, Eth became my entry point into more complex topics like mechanism design, protocol economics, credible neutrality, and the challenge of coordinating large groups of people around shared infrastructure. Over time this really shaped what I chose to study, what I chose to work on, and the kinds of problems I spend my time thinking about. Most of my work so far has been at the app layer. The fellowship is a great opportunity to move closer to the bare metal. I'm looking forward to working on the protocol itself and learning from the people who are shaping what Eth becomes next. I’m still narrowing down the exact project I will be working on, but currently looking into a Reth-based prototype around partial statefulness/state expiry, with broader interests in block production, censorship resistance, FOCIL, ePBS, and block-level access lists. More broadly, I’m excited by this next phase of Eth protocol development: scaling, privacy, censorship resistance, credible neutrality, and the renewed focus on the values captured by CROPS. Finally, a huge thank you to @C1aranMurray for introducing me to Eth back in 2017, to @post_polar_ for encouraging me to go for this, and to @joshdavislight and @TMIYChao for giving me the opportunity to take part! Excited for the months ahead, and determined to contribute something meaningful to the protocol.

🔥 chefs are already cooking on top of frame transactions (eip-8141), a native AA proposal for the hegota upgrade trouble keeping up? forkcast now displays dependent eips (including those not yet merged):

EPF7 applications are open!