Something strange happens when an industry that spent three years promising to rewrite the rules of human coordination suddenly starts cutting payrolls. The headlines write themselves with almost mechanical predictability. "Web3 winter." "The bubble bursts." "Crypto is dead — again." I have been reading those headlines for the better part of a decade now, and I have learned to treat them the way experienced sailors treat a barometer: the needle matters less than the direction of the change, and the direction of the change matters less than what you actually do with the information.
The latest reading on the Web3 employment barometer is unmistakable. After a period that can only be described as overheated — a period when protocols were handing out six-figure salaries to fresh graduates with a GitHub account and two Solidity tutorials under their belts, when marketing budgets exceeded the GDP of small Pacific nations, when the phrase "talent war" appeared in every industry newsletter with the solemnity of a weather warning — the industry has entered what reporters are now calling a "layoff wave." The word "wave" is doing a lot of work in that sentence. It suggests a single, unified event, a natural disaster sweeping across the ecosystem with the impartiality of a tsunami. The reality is messier, more human, and far more instructive. Waves do not fire people. Companies do. Managers do. Treasuries run dry, and human beings make decisions about other human beings' livelihoods.
This is not my first employment cycle in Web3. I have been watching the hiring and firing patterns of this industry since 2017, when I was a 29-year-old data scientist applying Python simulations to whitepapers that promised decentralized world computers, bank-less banking, and the transformation of global finance within a single token launch. Back then, the employment market for crypto talent was a peculiar blend of frenzy and amateurism. Projects were raising hundreds of millions of dollars in initial coin offerings and then attempting to hire entire organizations in a matter of weeks, a timeline that would be absurd in any mature industry but was treated as perfectly normal in a sector that had decided it was exempt from the laws of organizational development.
I remember auditing the tokenomics of three major ICOs in the months leading up to the EOS and Bancor launches. My conclusion — published in a blog post titled "The Math Doesn't Lie" — was that the growth assumptions embedded in their token models were not just optimistic but mathematically impossible. The post went viral by the standards of the time, fifty thousand views, which in 2017 was like winning the internet and then being asked to give a keynote about it. But the more interesting signal, the one that has stayed with me across the years, was in the responses. Hiring managers from those very projects reached out to me, not to debate my math — most of them had not actually read the math — but to ask if I knew any developers who could build what their whitepapers promised. There was a fundamental disconnect between the employment market and the technical reality. Teams were being hired to build things that could not be built, at valuations that assumed they would be, with payroll obligations that required the entire edifice to work perfectly from day one.
The pattern repeated, with variations, through DeFi Summer in 2020. I was in Berlin for the ETHGlobal hackathon when the compounding euphoria of yield farming reached its peak. I spontaneously joined a team to build a narrative-tracking bot for liquidity mining rewards — a project that was technically crude but conceptually ahead of its time, designed to capture the sentiment flows behind the capital flows. The seed funding we attracted, fifty thousand dollars from three angel investors, was less a vote of confidence in our code and more a wager on the narrative itself. That is the thing about crypto hiring, and about crypto capital more broadly: it is procyclical. When liquidity flows, humans follow. When the narrative turns, the first thing to contract is the headcount. It is never the last. But it is always the first.
The 2022 crash taught me the first real lesson about employment lags. Watching my portfolio drop seventy percent was painful, a visceral education in the difference between intellectual conviction and financial exposure. But what I found while working on my "Rebuilding from Ashes" series, which involved interviewing fifteen founders who pivoted their companies during the downturn, was more educational than the portfolio damage. The founders who survived that bear market were not the ones with the best technology — I say this with the full weight of my data science background — they were the ones who had built lean teams from the start, or who moved decisively when the capital environment shifted. The ones who failed were the ones who had treated the boom as permanent. They had hired for peak conditions, built org charts that assumed infinite growth, and then discovered, tragically too late, that payroll is a fixed cost in a variable-revenue world.
Now, in 2026, we are seeing the same dynamics play out at industry scale, accelerated by the macro environment and the gravitational pull of artificial intelligence. The layoff wave is not news about any single project. It is news about the entire substrate of the industry. And in some ways, that makes it more important than any individual company's staffing announcement.
Here is what I want to challenge in the conventional reading of this moment. Most commentators will tell you that a wave of layoffs is evidence that Web3 has failed, or at least that its growth narrative has been falsified. That interpretation, rooted in the familiar "bubble burst" framing, is seductive. It provides a clean moral arc: hubris, excess, collapse, redemption. It maps neatly onto the media cycle. But it misses the more interesting technical reality.
Layoffs in Web3 are a lagging indicator, not a leading one. They are the echo of a prior shock — typically a funding contraction or a token price correction — that arrives at the payroll with a delay of six to twelve months. The reason is straightforward and deeply human. Cuts to engineering teams require difficult conversations, legal reviews, severance planning, and something approaching actual courage from leadership. No founder wants to be the one who lets go of the team that shipped the roadmap. No project wants to admit, publicly, that its growth assumptions were wrong. So the timeline stretches. First, hiring freezes that are announced quietly and not at all. Then, surgical reductions in discretionary spending. Then, the marketing cuts, which are easier because marketing is understood as auxiliary. And only then, when the treasury outlook has become undeniably grim, do the engineering and product layoffs arrive.
This means that the current wave of layoffs is not a measure of the present state of Web3. It is a measure of where the industry was six to twelve months ago. The lag creates an information asymmetry that can be exploited by careful analysts — and I mean "exploited" in the most professional sense. If you understand that layoffs reflect the past rather than the present, you can evaluate which of today's signals will become tomorrow's headlines, and position your analysis accordingly.
Let me break down what the layoff ledger is actually telling us across the dimensions I track professionally.
The Technical Dimension: Who Actually Got Cut?
The first question any technical analyst should ask about a layoff wave is not "how many people lost their jobs" but "which functions were cut." The distinction between core protocol engineering and peripheral roles is the difference between a scaling-down and a technical retrenchment. It is the difference between a project that will survive the winter and a project that is already dead but has not yet stopped moving.
Based on the patterns I observed in 2022 and the signals emerging in the current cycle, the cuts are predominantly concentrated in the peripheral categories. Growth teams that were hired to chase user acquisition during the boom. Marketing departments that were building brand awareness at a time when brand awareness was cheap to purchase with inflated treasuries. Community managers who were maintaining the emotional temperature of Discord servers that had gone quiet. These roles, genuinely valuable during expansion, become targets during contraction precisely because they are categorized as non-essential. It is a brutal logic, but it is a logic. When a project must reduce its burn rate by forty percent, it does not start by cutting its protocol engineers. It starts by cutting the functions that produce announcements rather than code.
The core cryptography researchers, the protocol engineers who understand consensus mechanisms at a level measurable in graduate-level mathematics courses, the distributed systems architects who can reason about adversarial network conditions as easily as they reason about API design — these roles are more expensive to replace and more difficult to source. When a project cuts its core engineering team, that is a signal of existential distress. It is the technical equivalent of selling the load-bearing walls to pay the mortgage. When a project cuts only its peripheral functions, that is a signal of strategic repositioning — often painful, but not necessarily fatal.
My intermediate confidence assessment, based on the current information available, is that the aggregate layoff wave is a mix of both categories. Some projects are genuinely in distress, reducing headcount across the board to extend their runway, hoping that a rescue round arrives before the treasury hits zero. Others are using the market correction as an opportunity to restructure, shedding the bloat of the boom era while retaining their technical core. The challenge for any analyst — and I say this from direct experience auditing project health across multiple cycles — is distinguishing between the two categories when the public announcements all use the same euphemistic language. "Streamlining operations." "Focusing on core priorities." "Aligning our resources with our strategic vision." I have read hundreds of these announcements. The language is almost always identical. The reality underneath is almost always different.
The distinction matters enormously for evaluating the industry's technical future. If the layoff wave is primarily peripheral, the long-term impact on innovation is minimal — arguably even positive, because it forces projects to operate leaner and to prioritize technical deliverables over narrative theater. If the wave has reached core engineering teams, we should expect a measurable slowdown in protocol development over the next two to four quarters. That slowdown will show up in the data trails that I monitor: GitHub commit frequency, EIP proposal activity, conference submission quality, the velocity of testnet deployments. My historical analysis of the 2022 cycle suggests that core engineering cuts took approximately two quarters to manifest in measurable development slowdowns, and approximately four quarters for the effects to reach end users through slower feature releases and postponed roadmap items. If the current cycle follows a similar timeline, the development consequences of the current layoff wave will be visible by the middle of the next year.
The Treasury Dimension: How Payroll Pressure Reshapes Tokenomics
Every layoff is a treasury decision wearing a human mask. Projects do not reduce headcount because they woke up one morning with philosophical objections to their existing team structure. They do it because their cash runway, or their token price, or their projected revenue, no longer supports the existing payroll. The human story is real, and I do not want to minimize it, but the analytical story is about the treasury.
This is where employment and tokenomics intersect in ways that most coverage ignores. In my audit work — the same work I have been doing since those 2017 whitepapers — I have developed a heuristic for evaluating the sustainability of token models. The question I always start with is not "what price will this token reach?" but "what is the relationship between the project's spending obligations and its treasury inflows?" A token can have the most elegant tokenomics on paper and still be worthless if the spending obligations consume the treasury faster than the inflows replenish it. Conversely, a token with a simple, even crude model can sustain itself if the treasury is managed with discipline.
In a bull market, this relationship becomes dangerously ambiguous. Projects fund their operations through token emissions, selling newly minted tokens into the market to cover operating expenses. As long as the token price appreciates or remains stable, this creates a seemingly virtuous cycle: token sales fund development, development produces announcements, announcements attract users, users increase demand, demand raises the price, and the price enables more token sales. Every one of these steps feels real in the moment. Each contributes its own evidence to the narrative. But the cycle is only sustainable as long as the token price remains at a level where the emissions yield sufficient funding.
The layoff wave represents the moment this cycle breaks. When the token price falls below the threshold where emissions can fund operations, the project faces an impossible choice. It can reduce emissions, which will upset token holders who expect yields and who may sell in response, further depressing the price. It can accept dilution, which technically keeps the treasury funded but sends a signal of desperation to the market. Or it can cut expenses — and the largest expense for most Web3 projects, after the compensation of the founding team, is the payroll.
This is why, when I see a wave of layoffs, I immediately start monitoring treasury behavior rather than price action. The projects that survive with their technical integrity intact are the ones with sufficient cash reserves to fund their core teams through the contraction. The projects that fail are the ones that relied on token price appreciation to fund their operations, discovering too late that payroll does not wait for sentiment to recover.
There is a secondary effect worth noting, and it connects directly to my analysis of tokenomics sustainability. The current layoff wave may include modifications to token unlock schedules and incentive structures. Projects under budget pressure face a tempting set of shortcuts: accelerating team token unlocks as a substitute for cash severance, reducing liquidity mining rewards to preserve treasury, cutting staking yields to reduce emissions. Each of these moves is rational in the short term. Each produces measurable declines in network activity in the medium term. The analyst who monitors emissions schedules and incentive programs during the current contraction will have an information advantage when the market returns to expansion.
And there is a deeper point, one that I want to make carefully because it connects to a broader critique I have developed over multiple cycles. The token models most vulnerable to the current contraction are the ones that were never rooted in sustainable economics in the first place. The RWA narrative — real-world assets tokenized on-chain — has been a three-year storytelling exercise that has produced more press releases than verifiable volume. I have audited the tokenomics of RWA protocols, and the fundamental question is always the same: who is paying for the privilege of using a public blockchain to represent an asset that already functions perfectly well in the traditional financial system? The answer, in most cases, is nobody. Traditional institutions do not need your public chain. They have custody, clearing, settlement, and legal finality. They do not need tokenization to achieve these functions. When the layoff wave arrives at RWA projects — and it will, because the narrative funding those projects was never grounded in economic fundamentals — the cuts will expose what was always true: the storytelling was the product, and the storytelling was not sustainable.
The Market Dimension: Layoffs as Sentiment Architecture
Let me be candid about the emotional reality here. When a headline announces that Web3 is shedding thousands of jobs, the immediate market response is rarely rational. It is visceral. The news triggers a cascade of associations: failing companies, dead projects, worthless tokens, wrecked portfolios. This emotional response is itself a market signal, a data point that belongs in any serious analysis of the industry's trajectory.
I have spent years studying the narrative mechanics of this industry — it is literally my job as Editor-in-Chief, but it also reflects a genuine intellectual obsession with the intersection where the code meets the chaotic human heart. I have come to understand that sentiment operates on a lag that mirrors the employment cycle. The market sells first on the news that created the layoffs — the funding crunch, the regulatory uncertainty, the price correction. It then sells again, with less force, on the layoff headlines themselves. This second selloff is what traders call the "echo." It is a response to the headline, not to the underlying reality. It is the market reacting to its own fear rather than to any new information.
The danger of the echo is that it creates a self-fulfilling narrative. The layoff headlines produce fear. The fear produces selling. The selling produces treasury contractions. The treasury contractions force more layoffs. And the cycle continues until some exogenous factor breaks the spiral. Understanding this dynamic allows me to position my analysis against it. When the market is reacting to layoff headlines, I look for the divergence between the stated narrative and the underlying signals. Is the layoff wave actually concentrated in the weakest projects — the ones that were never technically viable, the ones whose product never achieved product-market fit? Or is it indiscriminately affecting sound projects alongside failed ones? The answer to that question determines whether the market's reaction is an opportunity or a warning.
The current information points, as I noted, are limited. We know that Web3 was overheated. We know that it is entering a layoff wave. What we do not yet know is the distribution of the cuts. Are they concentrated in the speculative excesses of the past cycle? Are they spreading to the infrastructure that will support the next one? The resolution of that question is what will determine whether the layoff wave is a healthy correction or a structural decline.
My intermediate-confidence assessment is that the current wave, like the one in 2022, is primarily concentrated in the speculative excesses. The projects that are cutting deepest are the ones that raised the most money at the highest valuations during the boom — the ones that hired for peak conditions and now find themselves operating in an environment where those conditions no longer apply. The sound projects, the ones that kept their treasuries disciplined and their teams lean, are more likely to be making surgical cuts rather than wholesale eliminations.
The result is an information paradox. The layoff headlines are real, and the human suffering behind them is real, but the market's interpretation of the headlines is systematically biased toward the dramatic. The protagonists of the boom era are the casualties of the bust era, and their stories are more visible than the quiet competence of the teams that managed their treasuries well. Those who can read past the headline, into the distribution behind it, will find opportunities that the consensus narrative hides.
The Ecosystem Dimension: Where Does the Talent Go?
The single most important question about the Web3 layoff wave is not what happens to the companies that remain. It is what happens to the people who leave. Talent, more than capital, more than regulatory clarity, more than any single protocol or application, is the industry's most fundamental resource. The distribution of that talent after the layoffs will determine the shape of the next cycle.
In 2022, I interviewed fifteen founders who pivoted their projects during the downturn. The pattern that emerged from those interviews was consistent and instructive. The most successful pivots were not technical pivots. They were narrative pivots. The founders who survived were the ones who recognized early that the market's attention had shifted, and who repositioned their human capital accordingly. Some moved from consumer applications to infrastructure. Some moved from speculative DeFi to regulatory-compliant asset management. Some moved out of crypto entirely. The ones who thrived — and I want to emphasize this because it contradicts the romantic image of the founder who refuses to pivot — were the ones who treated their team as a precious resource to be redeployed rather than a commitment to be defended.
The current wave is different in one crucial respect. The developers leaving Web3 are walking into the strongest labor market for artificial intelligence talent in history. The large language model companies, the autonomous agent startups, the infrastructure providers building the compute layer for machine intelligence — they are all hiring, and they are all looking at Web3's displaced developers with real interest. The pay is competitive. The work is technically interesting. The narrative is fresh.
This creates a new dynamic in the talent flow. In 2022, displaced developers mostly stayed within the broader crypto ecosystem, moving from one project to another, because there was nowhere else to go that matched their skill sets. In 2026, there is a genuine risk of talent flight out of Web3 and into AI. The skills that made a great protocol engineer — the ability to reason about distributed systems, the understanding of cryptographic primitives, the comfort with adversarial environments — are directly transferable to AI infrastructure.
But there is a counter-signal, and it is one of the most exciting developments I have observed in the industry. The intersection of AI and crypto is becoming one of the most technically fertile spaces in the entire technology landscape. The concept of autonomous economies — AI agents that transact with each other using crypto wallets, that negotiate with each other, that build their own capital allocation strategies, that participate in markets without human supervision — requires exactly the talent that Web3 has been cultivating for years. Every AI researcher building on blockchain rails, every crypto developer applying their knowledge to agent frameworks, is evidence that the two industries are converging rather than competing. Those developers are rewriting the ledger of their own careers, one story at a time.
My work on the "Autonomous Economies" special report, which involved interviewing thirty AI researchers and crypto economists, revealed something that genuinely surprised me. The most interesting projects at the intersection are not being built by either community alone. They are being built by people who have one foot in each world — the distributed systems understanding of Web3 married to the probabilistic reasoning of AI. The layoff wave, in this reading, is less a migration out of crypto and more a redistribution within a broader technological landscape. The talent that Web3 is shedding may not return to the same project structures, but it will remain within reach of the ecosystem's core thesis: that code can coordinate human and machine behavior in trust-minimized ways.
There is also the Layer2 story, which I cannot ignore because it has become central to my critique of the industry's growth habits. We now have dozens of Layer2 solutions, each with its own token, its own ecosystem fund, its own cohort of hired developers. The mathematics of the situation are simple: dozens of Layer2s serving the same small user base does not equal scaling. It equals slicing already-scarce liquidity into fragments. The layoff wave will be brutal for the Layer2s that cannot demonstrate real usage, and that brutality is warranted. The industry raised billions of dollars to build infrastructure for a user base that was already being fragmented across attention, liquidity, and value. The correction was not a question of whether. It was a question of when.
The Narrative Dimension: When "Overheated" Becomes a Four-Letter Word
The word "overheated" is doing a lot of work in the current narrative. It suggests that Web3's growth was not organic but feverish, not sustainable but pathological. The implication is that the decline is not simply a cyclical adjustment but a correction of an imbalance — a returning of the industry's temperature to a healthy baseline.
There is truth in this framing. The 2021 through 2023 cycle was genuinely overheated. I was there. I covered the Beeple Christology auction in 2021, investigating the intersection of art, identity, and blockchain ownership while prices made a mockery of all traditional valuation frameworks. I wrote my deep-dive article "Who Owns the Soul of Crypto Art?" at a moment when the moral and financial questions around NFTs were both intensifying. I watched ten thousand Punks sell for increasingly insane prices while the cultural conversation around ownership and provenance struggled to keep pace. I interviewed five NFT artists in a single weekend, trying to capture the multi-perspective reality of a phenomenon that the financial press was treating as a monolith. And I published my analysis while knowing that the male-dominated trading communities would dismiss much of it as "soft" cultural commentary.
That era was overheated in every sense. The capital inflows were unprecedented. The hiring was frenzied. The narrative promises exceeded technical delivery by an order of magnitude. And I documented all of it, not to celebrate the excess but because the excess itself revealed something deep about human psychology — about our willingness to participate in narratives that feel good rather than narratives that are true.
The current layoff wave is the inevitable correction of that overheating. In metabolic terms, the industry is burning off the fat it accumulated during the feast. This is painful, but it is not pathological. It is the restoration of balance.
But here is where I depart from the consensus interpretation. The layoffs are not evidence that Web3 failed. They are evidence that Web3 is joining the ranks of industries that experience economic cycles. They are evidence that the industry has, in the most unglamorous sense, become normal.
The technology sector has always operated in this rhythm. The dot-com crash of 2000 eliminated the speculative excesses while leaving the underlying internet infrastructure intact. The 2008 financial crisis reset the financial industry's relationship with risk in ways that continue to shape regulation and institutional behavior. The 2022 crash, and the current contraction, are performing the same function for Web3. The projects that survive will be the ones that provide actual utility, that generate actual revenue, that solve actual problems. The ones that were — let me be honest — the human equivalent of a token with good stickers and no use case will not survive. And that is not a tragedy. It is a correction.
Now let me offer the counterintuitive framing that I think will define the post-layoff narrative, because I believe it is both true and useful.
The layoff wave is not the industry's failure. It is the industry's most honest audit — a public accounting, enforced by the unforgiving pressures of the labor market, of which projects had real substance and which were running on narrative fumes.
In the boom era, every project could hire. Capital was flowing, positions were open, salaries were generous. A project with a whitepaper, a Discord server, and a charismatic founder could assemble a team of fifty people and project an image of operational substance that had no connection to operational reality. The employment market was the great enabler of fiction. It allowed vapor to look solid.
The layoff wave reverses that dynamic. When capital stops flowing, projects are forced to make impossible decisions about which people to keep and which to let go. Those decisions expose the project's actual priorities. If the core engineering team is retained while the marketing team is cut, that tells you the project's leadership believes the technology will carry them through. If the core engineers are cut while the marketing team survives, that tells you the project's leadership is more focused on narrative preservation than technical delivery. If the entire team is cut, that tells you the project is finished no matter what the official statements say.
This is why the layoff wave is, paradoxically, a valuable information source. Every layoff announcement is a public disclosure of project health — far more honest than the carefully curated metrics projects publish in their quarterly reports, far more revealing than the vanity metrics of Twitter followers or Discord memberships. The careful analyst reads the announcements, the leaked memos, the whispered rumors about which teams were retained and which were eliminated, and builds a map of the industry's actual priorities.
There is an even deeper contrarian point. The overheated hiring that preceded the layoff wave was, in retrospect, largely wasteful. The industry spent enormous sums on projects that never delivered, on teams that never shipped, on communities that never formed, on narratives that evaporated under contact with reality. The layoff wave, by eliminating the waste, is clearing the ground for the next cycle. The projects that remain, the talent that remains, the capital that remains — these are the building blocks for the next wave of innovation.
I have seen this pattern before. The "Rebuilding from Ashes" series I published during the 2022 crash interviewed founders who pivoted during the downturn. Many of them described the layoffs and restructuring as the best thing that happened to their projects. They were forced to focus. They were forced to identify what actually mattered. They were forced to build with constraints, and the constraints made the resulting products better. It is a counterintuitive lesson, but it is one that recurs across every industry, every cycle: abundance produces waste, and scarcity produces discipline.
The same dynamic will play out on an industry scale. The Web3 that emerges from this layoff wave will be smaller, more focused, more technical. It will have less marketing and more substance. It will be less interested in narrative and more interested in delivery. And the people who survive in it — the ones who kept their technical integrity through the contraction — will be the core of the next expansion.
The contrarian angle is not that layoffs are pleasant. They are not. They represent real human costs: lost income, disrupted careers, broken teams, scattered communities. I do not minimize that, and anyone who has worked in this industry through multiple cycles has felt those costs personally. But the contrarian angle is that layoffs, as an industry-wide event, are the mechanism by which Web3 metabolizes its own excesses. They are the system achieving equilibrium through the only available channel.
The question is not whether the layoff wave will end. It will. Markets always clear. The question is what kind of Web3 emerges from it — and that depends on where the talent went, which projects retained their core teams, and which narratives survive contact with reality.
There is a dimension of the layoff wave that the headlines tend to obscure: geography. The distribution of layoffs across jurisdictions is itself a signal about where the industry's future will be built, and I want to spend a moment on it because it is frequently overlooked.
Based on my conversations with founders and my analysis of the global regulatory landscape, the contraction is not uniform. Projects with substantial exposure to the United States and the European Union face the most severe compliance overhead — and thus the most pressure to reduce headcount when capital tightens. The cost of regulatory compliance is a fixed cost, one that does not scale down with the token price. It requires legal counsel, financial reporting infrastructure, jurisdictional analysis, and a team to manage ongoing obligations. When revenues contract, these fixed costs become proportionally heavier, and the pressure on the rest of the budget — including payroll — intensifies.
Conversely, jurisdictions with clearer regulatory frameworks, or with more permissive attitudes toward digital assets, may find themselves as relative beneficiaries of the talent redistribution. The developers who leave the high-compliance jurisdictions, either by choice or by layoff, face a decision: remain in Web3 in a different jurisdiction, or exit to AI. The jurisdictions that offer clearer rules, more favorable tax treatment, and more institutional acceptance are likely to attract the displaced talent.
I do not want to overstate this point — my confidence in the specific geographic distribution of the current layoff wave is low, because the available information does not provide the necessary resolution. But the direction of the effect is clear from the 2022 cycle, where I observed a measurable shift in the geographic concentration of Web3 startups. The current wave will likely amplify that shift.
If I were to distill all of this analysis into a practical framework for readers — and I know that many of you are here for exactly that, for the actionable insight buried in the narrative — it would be this.
First, stop treating layoff headlines as market signals. They are lagging indicators, echoes of decisions made six to twelve months ago. The market has already priced in the underlying reality by the time the headlines arrive. If you respond to the headlines, you are responding to yesterday's news, and yesterday's news has already moved the price.
Second, start tracking the signals that will define the next cycle. Watch the treasury consumption rates of the projects you care about — you can see them on-chain if you know where to look. Watch the open-source contribution velocity of the core teams. Watch where the displaced developers land. Watch the new project announcements from the teams that have sufficient capital to hire through the contraction. These signals, not the headlines, will tell you which projects are building for the long term.
Third, pay attention to the most counterintuitive signal of all: the quality of the next generation of projects. The projects that start during the layoff wave are, by definition, being built by people who are choosing to build in a difficult environment. They are not chasing easy money, because there is no easy money. They are pursuing a technical or economic thesis that they believe in deeply enough to accept the risk. Those are the projects that have historically produced the most significant innovations.
I have a favorite observation from the 2022 cycle that I return to whenever the industry becomes doom-heavy. The projects that were built during the 2017-2018 bear market — the ones that ignored the FUD, managed their treasuries, and focused on technical delivery — were disproportionately represented among the winners of the 2020-2021 expansion. The same pattern is likely to hold for whatever is built during the current contraction. The seeds of the next bull market are being planted right now, in the soil of the layoff wave, by the people who choose to build when building is hard.
So where does this leave us?
The layoff wave is real. It is painful. It represents genuine hardship for the individuals and teams affected. I do not offer the long-term perspective to minimize that hardship but to contextualize it, to give it a shape that is more useful than despair.
The story of Web3 has never been a straight line. It has been a series of booms and busts, of narratives created and deconstructed, of promises made and then evaluated against delivery. The layoff wave is the latest chapter in that story. It is the industry's most honest audit, the mechanism by which excess is metabolized and the ground is cleared for the next cycle. The projects that survive will be the ones with technical substance, disciplined treasuries, and narratives that can survive contact with reality. The talent that remains will be the talent that builds. The capital that remains will be the capital that deploys.
Where the code meets the chaotic human heart, there has always been friction. That friction is the heat we now call an overheated industry. But heat dissipates. Friction resolves into equilibrium. And the technologies that emerge from this contraction — the autonomous economies, the AI-blockchain convergence, the institutional adoption that follows regulatory clarity — will be built on the foundations that survive the current correction.
The code will persist, rewritten, refined, and re-architected by the people who choose to stay. The ledger is being rewritten, one story at a time. The question I leave you with is not whether Web3 will survive. It is whether you are positioned to build what comes next. The layoffs are not an obituary. They are an opening.
