Ethereum’s core development machine may not keep its current pace for long, according to VanEpps, a former Ethereum Foundation contributor.
VanEpps warned The Block that Ethereum could face a “core development funding crisis” within 3-9 months after the Cryptography Incentive Program (CIP) expires. The warning is simple. If the funding gap opens, core work does not pause politely. It slows, gets harder to schedule, and starts competing with other budget needs.
Why CIP matters
The core issue is not that Ethereum needs “innovation” on a calendar. It needs ongoing engineering support. Bug fixing, protocol maintenance, and coordination across clients and teams are the kind of work that tends to run on sustained funding.
VanEpps frames that sustained support as dependent on CIP until it expires. Once CIP is gone, the runway shortens. The Block reports that risk timing is measured in months, not years.
The nine-month window
The Block’s reporting gives a range, “3-9 months,” after CIP expired. That spread matters because it implies uncertainty in either renewal timing or replacement funding. A narrow window is a management problem. A wide window is a planning problem.
In practical terms, any gap can show up as fewer staffed reviews, slower follow-through on fixes, and reduced bandwidth for coordination work that keeps upgrades from turning into operational surprises.
Funding gaps hit execution, not headlines
Funding warnings sound abstract until you map them to how Ethereum ships changes. Core development is coordination-heavy. It spans multiple client teams and contributors who need time to test, implement, and validate. When funding dries up, the bottleneck usually lands where verification lives, not where ideas originate.
VanEpps’ concern, as relayed by The Block, is about continuity. That’s the uncomfortable part. Even if Ethereum’s roadmap still exists, the people and process that turn it into running software rely on money.
What to watch next
The Block’s account points to one immediate checkpoint: what happens after CIP expires. If replacement mechanisms do not arrive in time, the desk expects the “crisis” to show up as coordination friction and reduced capacity for core maintenance.
For readers tracking protocol health, the question becomes less “what upgrade is next” and more “who funds the work that makes upgrades safe and deployable.” VanEpps’ warning shifts attention from ambition to infrastructure reality.
Note: This article is based only on the limited provided source text, which states VanEpps’ warning and the CIP timing. It does not include further details on the size of any shortfall or specific funding proposals.