Olivia
Online
Developeruche
@developeruche
ZK, Rust, Blockchain. 🧘♂️
space
Joined August 2020
399 Following
781 Followers
551 Posts
Pinned Tweet
🚀 Big news for #Ethereum! Just wrapped phase-one research + PoC showing how Rust smart contracts (or any lang targeting RISC-V ISA) can run on a RISCV variant of the EVM! 🦀💻
🔍 Research: https://t.co/dMr5VhUWtL
💻 Rust PoC code: https://t.co/QFKx3Bybnp
Read the thread for a quick dive or check the links for full details! 🧵👇 #Blockchain #Rust #RISC_V
Over the past few weeks we have re-audited every cryptographic dependency Hyperbridge relies on.
This has led to the discovery of even more critical vulnerabilities in our code, third-party libraries and even Polkadot itself.
All have been responsibly disclosed and patched. We’ll be publishing a detailed write-up on shortly on all our findings.
The root cause of the original incident was a missing single line of code that permitted proof forgery.
The vulnerable code in question dates to early Polytope Labs days and predates our current review & testing standards, which is why the re-audit was warranted and why it’s ongoing.
Alongside this, we’re launching a bug bounty which will help us work with whitehats on the continued security of the protocol.
I mapped out projects from Cohort 5 & 6 what’s been explored and where there’s still room to contribute.
Read here: https://t.co/jh2rRnCJ5m
EPF7 applications are open. Deadline is May 13.
If you want to work on core Ethereum protocol — client development, testing, specs, research — this is the program for you.
Who to follow
Web3bridge™ Africa 
@Web3Bridge
Exploring cohort based model to train web3 developers in Africa. [email protected] https://t.co/xmXUppu3Cj Telegram: https://t.co/j2zcYJkgar
Web3 Lady (oluchi.eth)
@koderHolic
Principal Engineer - DeFi @WioBank| Founder @web3ladies | ex: @binance @cryptocom @nestcoin @liquality_io
Ebunayo.eth 🇳🇬
@Ebunayo08
Ethereum ecosystem builder, grooming developers @Web3Bridge| exploring construction & business @bloceducare 🦇🔊 host @web3LagosCon|@kernel0x
Introducing https://t.co/hCcz4pQCxZ,
A tool that allows you compute anything.
Think of how programming languages work. You are not restricted to a certain type of program rather you are given the building blocks to build whatever you want.
That's the goal for https://t.co/hCcz4pQCxZ. A turing-complete math platform that gives you the building blocks to calculate, experiment and build deep computational flows.
This is the first of many demos. Try it out and join me on this journey as I build the best math and computation platform.
Introducing strawmap, a strawman roadmap by EF Protocol.
Believe in something. Believe in an Ethereum strawmap.
Who is this for?
The document, available at strawmap[.]org, is intended for advanced readers. It is a dense and technical resource primarily for researchers, developers, and participants in Ethereum governance. Visit ethereum[.]org/roadmap for more introductory material. Accessible explainers unpacking the strawmap will follow soon™.
What is the strawmap?
The strawmap is an invitation to view L1 protocol upgrades through a holistic lens. By placing proposals on a single visual it provides a unified perspective on Ethereum L1 ambitions. The time horizon spans years, extending beyond the immediate focus of All Core Devs (ACD) and forkcast[.]org which typically cover only the next couple of forks.
What are some of the highlights?
The strawmap features five simple north stars, presented as black boxes on the right:
→ fast L1: fast UX, via short slots and finality in seconds
→ gigagas L1: 1 gigagas/sec (10K TPS), via zkEVMs and real-time proving
→ teragas L2: 1 gigabyte/sec (10M TPS), via data availability sampling
→ post quantum L1: durable cryptography, via hash-based schemes
→ private L1: first-class privacy, via shielded ETH transfers
What is the origin story?
The strawman roadmap originated as a discussion starter at an EF workshop in Jan 2026, partly motivated by a desire to integrate lean Ethereum with shorter-term initiatives. Upgrade dependencies and fork constraints became particularly effective at surfacing valuable discussion topics. The strawman is now shared publicly in a spirit of proactive transparency and accelerationism.
Why the "strawmap" name?
"Strawmap" is a portmanteau of "strawman" and "roadmap". The strawman qualifier is deliberate for two reasons:
1. It acknowledges the limits of drafting a roadmap in a highly decentralized ecosystem. An "official" roadmap reflecting all Ethereum stakeholders is effectively impossible. Rough consensus is fundamentally an emergent, continuous, and inherent uncertain process.
2. It underscores the document's status as a work-in-progress. Although it originated within the EF Protocol cluster, there are competing views held among its 100 members, not to mention a rich diversity of non-EFer views.
The strawmap is not a prediction. It is an accelerationist coordination tool, sketching one reasonably coherent path among millions of possible outcomes.
What is the strawmap time frame?
The strawmap focuses on forks extending through the end of the decade. It outlines seven forks by 2029 based on a rough cadence of one fork every six months. While grounded in current expectations, these timelines should be treated with healthy skepticism. The current draft assumes human-first development. AI-driven development and formal verification could significantly compress schedules.
What do the letters on top represent?
The strawmap is organized as a timeline, with forks progressing from left to right. Consensus layer forks follow a star-based naming scheme with incrementing first letters: Altair, Bellatrix, Capella, Deneb, Electra, Fulu, etc. Upcoming forks such as Glamsterdam and Hegotá have finalized names. Other forks, like I* and J*, have placeholder names (with I* pronounced "I star").
What do the colors and arrows represent?
Upgrades are grouped into three color-coded horizontal layers: consensus (CL), data (DL), execution (EL). Dark boxes denote headliners (see below), grey boxes indicate offchain upgrades, and black boxes represent north stars. An explanatory legend appears at the bottom.
Within each layer, upgrades are further organized by theme and sub-theme. Arrows signal hard technical dependencies or natural upgrade progressions. Underlined text in boxes links to relevant EIPs and write-ups.
What are headliners?
Headliners are particularly prominent and ambitious upgrades. To maintain a fast fork cadence, the modern ACD process limits itself to one consensus and one execution headliner per fork. For example, in Glamsterdam, these headliners are ePBS and BALs, respectively.
(L* is an exceptional fork, displaying two headliners tied to the bigger lean consensus fork. Lean consensus landing in L* would be a fateful coincidence.)
Will the strawmap evolve?
Yes, the strawmap is a living and malleable document. It will evolve alongside community feedback, R&D advancements, and governance. Expect at least quarterly updates, with the latest revision date noted on the document.
Can I share feedback?
Yes, feedback is actively encouraged. The EF Protocol strawmap is maintained by the EF Architecture team: @adietrichs, @barnabemonnot, @fradamt, @drakefjustin. Each has open DMs and can be reached at first.name@ethereum[.]org. General inquiries can be sent to strawmap@ethereum[.]org.
![drakefjustin's tweet photo. Introducing strawmap, a strawman roadmap by EF Protocol.
Believe in something. Believe in an Ethereum strawmap.
Who is this for?
The document, available at strawmap[.]org, is intended for advanced readers. It is a dense and technical resource primarily for researchers, developers, and participants in Ethereum governance. Visit ethereum[.]org/roadmap for more introductory material. Accessible explainers unpacking the strawmap will follow soon™.
What is the strawmap?
The strawmap is an invitation to view L1 protocol upgrades through a holistic lens. By placing proposals on a single visual it provides a unified perspective on Ethereum L1 ambitions. The time horizon spans years, extending beyond the immediate focus of All Core Devs (ACD) and forkcast[.]org which typically cover only the next couple of forks.
What are some of the highlights?
The strawmap features five simple north stars, presented as black boxes on the right:
→ fast L1: fast UX, via short slots and finality in seconds
→ gigagas L1: 1 gigagas/sec (10K TPS), via zkEVMs and real-time proving
→ teragas L2: 1 gigabyte/sec (10M TPS), via data availability sampling
→ post quantum L1: durable cryptography, via hash-based schemes
→ private L1: first-class privacy, via shielded ETH transfers
What is the origin story?
The strawman roadmap originated as a discussion starter at an EF workshop in Jan 2026, partly motivated by a desire to integrate lean Ethereum with shorter-term initiatives. Upgrade dependencies and fork constraints became particularly effective at surfacing valuable discussion topics. The strawman is now shared publicly in a spirit of proactive transparency and accelerationism.
Why the "strawmap" name?
"Strawmap" is a portmanteau of "strawman" and "roadmap". The strawman qualifier is deliberate for two reasons:
1. It acknowledges the limits of drafting a roadmap in a highly decentralized ecosystem. An "official" roadmap reflecting all Ethereum stakeholders is effectively impossible. Rough consensus is fundamentally an emergent, continuous, and inherent uncertain process.
2. It underscores the document's status as a work-in-progress. Although it originated within the EF Protocol cluster, there are competing views held among its 100 members, not to mention a rich diversity of non-EFer views.
The strawmap is not a prediction. It is an accelerationist coordination tool, sketching one reasonably coherent path among millions of possible outcomes.
What is the strawmap time frame?
The strawmap focuses on forks extending through the end of the decade. It outlines seven forks by 2029 based on a rough cadence of one fork every six months. While grounded in current expectations, these timelines should be treated with healthy skepticism. The current draft assumes human-first development. AI-driven development and formal verification could significantly compress schedules.
What do the letters on top represent?
The strawmap is organized as a timeline, with forks progressing from left to right. Consensus layer forks follow a star-based naming scheme with incrementing first letters: Altair, Bellatrix, Capella, Deneb, Electra, Fulu, etc. Upcoming forks such as Glamsterdam and Hegotá have finalized names. Other forks, like I* and J*, have placeholder names (with I* pronounced "I star").
What do the colors and arrows represent?
Upgrades are grouped into three color-coded horizontal layers: consensus (CL), data (DL), execution (EL). Dark boxes denote headliners (see below), grey boxes indicate offchain upgrades, and black boxes represent north stars. An explanatory legend appears at the bottom.
Within each layer, upgrades are further organized by theme and sub-theme. Arrows signal hard technical dependencies or natural upgrade progressions. Underlined text in boxes links to relevant EIPs and write-ups.
What are headliners?
Headliners are particularly prominent and ambitious upgrades. To maintain a fast fork cadence, the modern ACD process limits itself to one consensus and one execution headliner per fork. For example, in Glamsterdam, these headliners are ePBS and BALs, respectively.
(L* is an exceptional fork, displaying two headliners tied to the bigger lean consensus fork. Lean consensus landing in L* would be a fateful coincidence.)
Will the strawmap evolve?
Yes, the strawmap is a living and malleable document. It will evolve alongside community feedback, R&D advancements, and governance. Expect at least quarterly updates, with the latest revision date noted on the document.
Can I share feedback?
Yes, feedback is actively encouraged. The EF Protocol strawmap is maintained by the EF Architecture team: @adietrichs, @barnabemonnot, @fradamt, @drakefjustin. Each has open DMs and can be reached at first.name@ethereum[.]org. General inquiries can be sent to strawmap@ethereum[.]org.](https://pbs.twimg.com/media/HCBwqPeWoAAC5Kj.jpg)
We promised it and we delivered it: realtime proving with @ziskvm!
💻 24x5090 GPUs
⏱️ 6.56s avg per proof
⚡️99.74% under 12s
🚀 9.7s avg time-to-proof
🥇86.36% under 12s
The future of proving is happening right now
@eth_proofs
The roundtable discussion format of the Whitepaper Reading Club is great
@WPReadingClub
@archiexzzz GitHub link please 🫣
Today, we are having a retreat for the alumni in celebrating @Web3Bridge 6th anniversary. We presently have @m_a_y_o_w_a talking about Pathways to continuous growth as a developer.
You can join the livestream here
https://t.co/fxjAdzW0lU
1/ New post: Jolt now proves RISC-V programs with 64-bit registers (RV64IMAC), at speeds exceeding those we previously reported for 32-bit.
1.5M cycles/sec on a 32-core CPU, 500k cycles/sec on a MacBook.
Here’s why this matters 🧵
I finished my STARK prover.
Is it production-ready? Definitely not. But is it educational? Absolutely!
The goal was to write it from scratch, with zero dependencies. Took only ~20 months, a lot of frustration, and many moments of feeling very stupid. How can it be so difficult?
Do check out my article describing the journey and the repository itself!
Repository: https://t.co/JOMVAmzqXm
Article: https://t.co/tp1sOQgMFe
Ethereum Foundation Protocol will host a Reddit AMA on Aug 29 at 2pm UTC
questions can be submitted now :)
https://t.co/lBPmKQVO0i
Thrilled to announce that @only1franchesco and I won the @PolyhedraZK Explore Expander zkML track!
We developed a compiler that translates ML models compiled to ONNX into Expander circuits, enabling model inference to be proven and verified using the Expander backend
@5dayoldburrito Technically, Yes.
Still exploring the surfaces, but this could imply a modification of the zkVM's exec trace structure to adopt this.... [not 100% on this yet]
How did @ziskvm achieve a mind-blowing 1.5 GHz RISC-V trace generation—10× faster than any other zkVM? 🤯
They smashed the sequential bottleneck holding back real-time ZK proofs. I deconstructed their genius two-part strategy in my latest blog post.
A must-read for anyone in verifiable computation. 🧵👇
https://t.co/fJK8sORlb4
big thanks to @jbaylina and @kevaundray for making this happen
Most Popular Users
Elon Musk
@elonmusk
240.3M followers
Barack Obama
@barackobama
119.2M followers
Donald J. Trump
@realdonaldtrump
111.6M followers
Cristiano Ronaldo
@cristiano
109.6M followers
Narendra Modi
@narendramodi
106.9M followers
Rihanna
@rihanna
97.4M followers
NASA
@nasa
92.1M followers
Justin Bieber
@justinbieber
90.7M followers
KATY PERRY
@katyperry
87.2M followers
Taylor Swift
@taylorswift13
81M followers
Lady Gaga
@ladygaga
72.6M followers
Kim Kardashian
@kimkardashian
69.6M followers
Virat Kohli
@imvkohli
69.1M followers
YouTube
@youtube
68.6M followers
Bill Gates
@billgates
63.6M followers
The Ellen Show
@theellenshow
62.5M followers
CNN
@cnn
61.9M followers
Neymar Jr
@neymarjr
61.8M followers
X
@x
60.9M followers
Selena Gomez
@selenagomez
60.3M followers