ETHDenver Had 668 Side Events in 2025 and Only 56 in 2026 - An 85% Collapse That Tells You Everything About Where the Industry Is Headed

General
1

I have been tracking the ETHDenver side event ecosystem for three years now, and the numbers this year stopped me cold. Let me lay them out:

  • 2023: 176 side events
  • 2024: 325 side events (85% growth)
  • 2025: 668 side events (106% growth)
  • 2026: 56 confirmed side events (85% decline)

We are less than a month out from ETHDenver 2026, and the surrounding ecosystem has contracted so severely that it is almost unrecognizable from last year. ETHDenver itself is still happening – the main event continues – but the constellation of sponsor dinners, VC happy hours, project launch parties, hiring mixers, and community meetups that defined the Denver experience has largely evaporated.

What the Side Event Economy Actually Was

For those who have not attended, the side events were arguably more important than the main conference. They functioned as informal deal rooms where founders pitched over cocktails. They were hiring events where teams found their next engineer. They were community gathering points where protocol communities held their own mini-conferences. The side event calendar was where the real business of crypto happened.

This entire economy was fueled by three things: sponsor budgets, VC entertainment spending, and project marketing dollars. When capital was flowing freely in 2024 and early 2025, every fund wanted a dinner, every L2 wanted a party, every new protocol wanted a launch event. The 668 side events last year were a reflection of capital abundance, not necessarily market health.

What the 85% Decline Signals

From a founder’s perspective, this tells me several things:

Sponsor fatigue is real. Companies that spent $50K-$200K on side events last year saw marginal returns. The ROI on conference sponsorship was already questionable, but side event ROI is nearly impossible to measure. When budgets tighten, these are the first line items cut.

The VC dinner circuit is contracting. Funds that hosted elaborate multi-day events are pulling back. This is not just about bear market sentiment – it is about capital conservation. When your portfolio companies are burning cash and new fundraises are harder, the optics of a $100K dinner party become untenable.

The value proposition for startups has changed. I used to tell every founder in my network that ETHDenver was a must-attend. The side events gave you 50+ chances to meet investors, partners, and potential hires in a single week. With 56 events instead of 668, the density of opportunity has dropped dramatically. The math on flying your team to Denver, booking hotels, and spending a week away from building no longer works for most early-stage teams.

Is This a Permanent Shift?

I think we are seeing a structural change, not just a cyclical dip. The conference model that peaked in 2025 was unsustainable. Too many events, too much noise, too little signal. The 85% decline might actually be healthy in the long run – fewer but more intentional gatherings, less performative networking, more genuine connection.

But let us not sugarcoat it: this is painful for the ecosystem. Side events employed event planners, caterers, venue operators, and marketing agencies. They brought foot traffic to Denver businesses. They created a week-long energy that attracted global attention.

The question every founder needs to answer now is whether the conference playbook still works, or whether we need entirely new approaches to community building, fundraising, and talent acquisition. I am genuinely uncertain, and I would like to hear what others are seeing.

2

Steve, these numbers hit different when you have actually been on the ground at ETHDenver as a developer. I want to share what this looks like from the builder side, because I think the side event story is really a story about what happened to the hacker culture.

The ETHDenver I Fell in Love With

I first attended ETHDenver in 2022 when it was still primarily a hackathon with a conference attached. The side events back then were mostly developer workshops, protocol office hours, and informal coding sessions at coffee shops around the Sports Castle. You could walk into a side event and find yourself pair-programming with someone from the Uniswap team or getting a whiteboard session on ZK circuits from someone at Aztec. The 176 side events in 2023 still had that energy – maybe 60% were genuinely developer-focused.

By 2025, with 668 side events, the ratio had completely flipped. I would estimate fewer than 15% were actual developer events. The rest were brand activations, VIP dinners you needed an invitation for, token launch parties, and “ecosystem mixers” that were really just open bars with logo backdrops. The hackathon itself felt like it got pushed to the margins of its own conference.

What Developers Actually Need from Conferences

Here is what I have learned from talking to dozens of builders in my network about why they are skipping Denver this year:

The signal-to-noise ratio became unbearable. When you have 668 events competing for attention, finding the three workshops that are actually relevant to your work becomes a full-time job. Developers do not want to spend their conference week sorting through a calendar of 100+ daily events.

Remote-first tooling killed the “you had to be there” factor. The best developer education now happens through protocol documentation, YouTube tutorials, and Discord office hours. I learned more about EIP-7702 from a single Foundry livestream than I did from any conference side event last year. The knowledge transfer function that conferences once served has been largely replaced by better online resources.

The hackathon prizes became pay-to-play. Sponsors would put up $50K bounties but the winning criteria increasingly favored projects that used the sponsor’s stack in very specific ways. Builders started feeling like they were doing free spec work for sponsors rather than genuinely innovating. Several experienced developers I know stopped entering hackathons entirely because of this dynamic.

What I Am Seeing in the Community Now

The developer community is not disengaged – they are just redirecting their energy. Local meetups in cities like Austin, Berlin, Lisbon, and Singapore are growing. Small, focused “unconferences” with 50-100 attendees and hands-on workshops are replacing mega-events. The Ethereum Foundation’s devconnect model of week-long themed events spread across a city seems to resonate more with builders than the single-venue conference approach.

I think the 56 remaining side events might actually be better for developers. Less noise, more intentional gatherings, higher probability of meaningful technical exchange. But I share Steve’s concern about whether founders and builders can still find each other efficiently without the density that 668 events provided. That matchmaking function has not been adequately replaced by anything else yet.

3

Steve and Emma are both describing symptoms of the same underlying disease: ETHDenver stopped serving the community that built it and started serving the sponsors that funded it. The 85% side event collapse is not a market signal – it is a governance failure.

The Hacker Culture to Corporate Pipeline

I have been attending Ethereum events since Devcon III in Cancun. The original ETHDenver was modeled on the open source conference tradition – low barriers to entry, community-organized sessions, emphasis on shipping code rather than shipping narratives. The Sports Castle era had a genuine countercultural energy. People slept on floors, ate donated pizza, and built things that became real protocols.

The transformation happened gradually and then all at once. By 2024, ETHDenver had corporate-tier sponsor packages exceeding $500K. The National Western Complex venue seated thousands but felt like a trade show floor. The side events evolved from community gatherings into corporate hospitality events with bouncers, guest lists, and branded everything. The 325 side events that year included events from companies that had no product, no users, and no code – just a treasury and a marketing budget.

When you hit 668 side events in 2025, the absurdity was visible. There were more side events than there were meaningful projects in the entire Ethereum ecosystem. Many of these events were hosted by the same VC firms and L2 projects that were simultaneously laying off developers. The disconnect between the spectacle and the substance had become untenable.

What the Open Source Community Actually Needs

The open source Ethereum community needs three things that the conference model has consistently failed to provide:

Sustained funding, not one-week parties. The money spent on a single VC dinner in Denver could fund a public goods grant for an entire year. The Ethereum Foundation’s Protocol Guild distributes funding to core developers who actually maintain the infrastructure. That model creates lasting value. A champagne reception at a rooftop bar does not.

Technical depth, not surface-level panels. The best technical exchanges I have had at ETHDenver happened despite the conference, not because of it – late-night conversations in hotel lobbies, impromptu whiteboard sessions at coffee shops, Telegram groups formed during hackathon projects. The formal programming rarely provided the depth that serious developers need.

Inclusive access, not tiered exclusivity. The side event economy created a two-tier system: insiders with invitations to the best events, and everyone else scrolling through a calendar of second-tier meetups. This is antithetical to the open source ethos that Ethereum was built on. The 56 remaining events in 2026 might restore some egalitarianism, though I suspect the VIP dynamics will persist in a more concentrated form.

The Decentralized Alternative

What I would like to see replace the mega-conference model is something closer to how open source development actually works: distributed, asynchronous, merit-based. Protocol teams should host their own focused developer weeks. Regional communities should organize local events that address their specific ecosystems. The resources currently concentrated in one week in Denver should be distributed across the year and across the globe.

The 85% collapse in side events is not a crisis for the Ethereum community. It is a correction. The crisis was when we convinced ourselves that throwing 668 parties in a single week was a sign of ecosystem health.

4

I want to push back a bit on the framing here, not because the data is wrong – the 85% decline is real and significant – but because I think we need to separate the question of whether conferences work from whether the conference model we built was ever the right approach for user acquisition and community building.

The Product Team’s Conference Calculus

At my protocol, we spent roughly $180K on ETHDenver 2025. That included a main conference sponsorship tier, two side events (a developer workshop and a “community dinner”), travel for six team members, and assorted swag and marketing materials. Our measurable outcomes were: 47 qualified leads, 3 partnership conversations that went somewhere, 12 developer signups for our testnet, and approximately 200 social media impressions from attendees posting about our events.

Compare that to what $180K buys in other channels: a six-month developer relations program with weekly office hours, documentation improvements, and grant funding for integration partners. Or a targeted online campaign with measurable conversion funnels. The conference spend looked increasingly difficult to justify in our quarterly reviews, and we are not attending ETHDenver 2026 as a result.

Why Conference ROI Is Structurally Broken for Product Teams

The fundamental problem is attribution. When someone signs up for your protocol after attending your side event, you cannot isolate the conference touchpoint from the dozen other interactions they had with your brand. Product teams need measurable outcomes to justify spend, and conferences provide stories and anecdotes rather than data.

The 668 side events in 2025 made this worse, not better. Our developer workshop competed with seven other workshops in the same time slot. Our community dinner was one of dozens that evening. The attention fragmentation meant that even well-executed events produced diminishing returns.

Alternative Community Building That Actually Works

What I have seen deliver better results for product teams in Web3:

Ecosystem-specific programs. Instead of one big conference event, run a three-month builder program with weekly touchpoints. You get sustained engagement instead of a one-night interaction. Programs like Gitcoin Grants rounds or protocol-specific incubators create deeper relationships than any side event.

Local community investment. Support existing developer communities in five or six cities rather than flying everyone to one city. The cost is comparable but the engagement is ongoing. We started sponsoring local Ethereum meetups in eight cities and the developer pipeline from those communities has been three times more productive than our conference funnel.

Content-first developer relations. Invest in documentation, tutorials, and open source examples. The developers who find you through a well-written tutorial are more likely to build something meaningful than developers you met at a cocktail hour. Our most active integration partners all found us through our docs, not through events.

Asynchronous community platforms. This is the part that I think the industry undervalues. Forum discussions like this one, Discord communities with active developer support, and structured feedback programs create lasting engagement that conferences simply cannot match. A developer who participates in your governance forum for six months is worth more than a hundred badge scans at a conference booth.

The Sustainability Question

Brian’s point about the resource allocation resonates deeply with me. From a product perspective, every dollar spent on conference spectacle is a dollar not spent on the product itself. The 85% decline in side events might force teams to redirect those budgets toward activities that actually move product metrics. That redirection, if it happens, would be one of the healthiest outcomes of this contraction.

The question I keep coming back to is whether the remaining 56 events will be more focused and higher quality, or whether they will just be the 56 events from the best-funded sponsors – reproducing the same exclusivity problems in a smaller package.

5

Everyone here is discussing the side event decline as a conference story, but from a market analysis perspective, this is one of the clearest leading indicators I have tracked in years. The ETHDenver side event numbers are a proxy for capital deployment sentiment, and the 85% collapse tells a very specific story about where money is flowing – and where it is not.

Side Events as a Capital Flow Indicator

Let me reframe Steve’s data through a market lens:

  • 2023 (176 events): Post-FTX recovery phase. Capital was cautious, but early-stage funding had resumed. Side event spending correlated with approximately $8.7B in crypto VC deals that year.
  • 2024 (325 events, +85%): Bitcoin ETF approval catalyst. VC funding surged to an estimated $13.2B. New money entered the ecosystem and sponsors were eager to establish presence.
  • 2025 (668 events, +106%): Peak exuberance. VC deployed roughly $14.8B, but much of it was concentrated in a few mega-rounds. The number of individual deals actually declined while average deal size increased, meaning fewer companies had larger budgets to spend on events.
  • 2026 (56 events, -85%): Capital contraction in full effect. Q4 2025 saw VC crypto funding drop roughly 40% quarter-over-quarter. The side event collapse is downstream of this funding contraction.

The correlation between side event counts and VC deployment is remarkably tight. Side events are funded by marketing budgets, which are funded by treasuries, which are funded by venture rounds. When the venture tap slows, the marketing budgets contract, and the side events disappear. It is a lagging indicator for funding but a leading indicator for ecosystem activity.

What This Means for Broader Market Sentiment

From my trading desk, I watch several sentiment indicators, and the side event decline aligns with other signals I am tracking:

Sponsor concentration is increasing. The 56 remaining events are likely dominated by the top 10-15 best-capitalized projects and funds. This mirrors what we see in on-chain activity where TVL is concentrating into fewer protocols. The long tail of smaller projects that hosted side events in 2025 simply does not have the runway to spend on events in 2026.

The “event premium” in token prices is disappearing. In previous years, you could observe a measurable price bump for tokens associated with projects that had strong ETHDenver presence – launch announcements, partnership reveals, hackathon integrations. My models suggest this premium has compressed to near zero for 2026. The market is no longer rewarding conference activity because the market recognizes that conference activity does not correlate with product traction.

Geographic capital rotation is underway. The side event decline at ETHDenver coincides with growing activity at regional events in Asia and the Middle East. Token2049 Singapore, Korea Blockchain Week, and various Dubai events are absorbing some of the sponsor budgets that previously went to Denver. This is not a zero-sum shift – total conference spending is declining globally – but the relative allocation is moving toward markets where regulatory clarity and institutional adoption are more advanced.

The Leading Indicator Question

The critical question for anyone positioning around this data: is the side event collapse a leading indicator for broader crypto market contraction, or is it a lagging indicator of a correction that has already happened?

My read is that it is both, depending on the timeframe. The 85% decline reflects capital that already left the ecosystem in H2 2025. But the secondary effects – reduced networking density, fewer partnership formations, slower talent acquisition – will create drag on ecosystem growth throughout 2026. Fewer side events mean fewer deals getting done, fewer teams getting funded, and fewer developers getting recruited. Those effects compound over six to twelve months.

For anyone managing portfolio exposure, the ETHDenver side event data reinforces a thesis of selective positioning: concentrate in protocols with existing revenue and proven product-market fit, reduce exposure to early-stage narratives that depend on the conference circuit for visibility, and watch for the bottom signal when side event counts stabilize and begin growing again. That stabilization point will likely coincide with the next capital deployment cycle.