We didn’t see this coming. But maybe we should have.
In late 2017, at DevCon3 in Tokyo, I remember the electric buzz around new ideas—continuous token streaming was one of them. Sablier Labs, founded by Paul Berg, emerged as the pioneer. By 2023, its contracts had been used by over 345,000 Ethereum addresses. DAOs used it for vesting. Projects used it for airdrops. It was simple, reliable, and quiet. Then, on a Tuesday that felt too ordinary, Paul Berg announced: Sablier Labs would cease active product development and enter maintenance mode until June 2028.
Maintenance mode. In crypto, those two words often sound like a soft landing. The contracts keep running. Users can still stream tokens. The website stays up. But beneath this veneer of stability lies a creeping threat. When a project stops development, it doesn’t become safe—it becomes a time bomb. The code doesn’t change, but the environment does. New vulnerabilities are discovered. Ethereum upgrades like EIPs can alter behavior. No one is watching. No one is patching. And the 345,000 addresses that trusted Sablier? They are now custodians of their own risk.
The Context: What Sablier Was and What It Became
Sablier pioneered the concept of token streaming—sending tokens continuously over time rather than in lump sums. Imagine a salary paid per second, or a vesting schedule that unlocks every block. It was a beautiful primitive, and it fit perfectly into the DAO ecosystem where project contributors needed predictable, on-chain compensation. The protocol was minimal: a set of immutable smart contracts deployed on Ethereum. No admin keys to steal funds. No governance to bribe. It was trustless by design.
But trustlessness doesn’t mean maintenance-free. The contracts were built for a specific Ethereum state. As the EVM evolves, as new attack vectors emerge (like reentrancy variants or cross-contract exploits), the original code becomes brittle. The team that built it is now on standby. No new audits. No bug bounties. No one to call if something breaks. The announcement was clear: “The team will pivot to other opportunities.”
The Core: What Maintenance Mode Really Means
Let’s dissect the risks, using my own experience from the 2022 bear market refinements. When I audited the smart contracts of failed DeFi protocols, I found that most collapses were not due to technical bugs at launch, but due to incentive misalignments and lack of maintenance. Sablier is different—it has no incentives to manipulate. But it has code that can fail.
1. Smart Contract Time Bomb
The biggest risk is undiscovered vulnerabilities. Every smart contract has a bug somewhere—it’s just a matter of time and use. Sablier’s contracts were audited, but audits are point-in-time checks. Since the team stops all development, they won’t fix any future exploit. Imagine a vulnerability that allows an attacker to drain all streams from a contract. In an active protocol, a responsible team would pause, upgrade, or compensate users. In Sablier’s maintenance mode, the team is gone. The funds would be lost forever.
2. Ecosystem Decay
Sablier was integrated by over 345,000 addresses, but that number includes many one-time users. The real active users are DAOs with long-term vesting plans. These DAOs now face a choice: either keep using Sablier and hope nothing breaks, or migrate to an active competitor like Superfluid. Migration costs gas and time. But staying is a gamble. I’ve seen DAOs that procrastinated on similar decisions—they often regret it when a minor exploit forces an emergency shutdown.
3. Market and Token Value
If Sablier has a governance token—the article did not confirm—the token’s value would collapse. Even without a token, the brand loses all future value. No one will build new integrations. No one will list it as a recommended tool. The market labels it a “zombie protocol.” And zombies attract only scavengers.
4. User Experience Breakdown
The front end and developer tools will degrade over time. Wallets update, browsers change, APIs sunset. Users trying to interact with Sablier’s interface may encounter errors, confusing them into mistakes. Without support, even simple actions like withdrawing a stream become dangerous. I recommend every Sablier user learn how to call the contracts directly via Etherscan. But that’s a high bar for the average DAO contributor.
The Contrarian: Why “Immutable” Is Not “Safe”
Some will argue that Sablier’s contracts are immutable and trustless, so maintenance mode shouldn’t matter. That’s a naive view. Immutability is a feature only if the code is provably safe for all time. It is not. The Ethereum network itself changes. For example, the upcoming EOF (EVM Object Format) proposal could change how contracts are deployed and executed. While unlikely to break existing contracts, it’s not impossible. More importantly, new attack techniques—like the recent “read-only reentrancy”—can make previously safe contracts exploitable. Without active monitoring and response, a protocol that stops evolving is a protocol that eventually breaks.
We didn’t build crypto to watch our favorite platforms go dormant. We built it for resilience, for continuous improvement, for the ability to adapt. Sablier’s choice to enter maintenance mode contradicts the very ethos of decentralized innovation. It signals surrender. And surrender in a bear market is often followed by a slow death.
The Takeaway: What You Should Do Now
If you are using Sablier for any active or pending stream, withdraw your funds. If you have a vesting schedule that lasts months or years, migrate it to Superfluid or even a simple escrow contract. Don’t wait for the protocol to prove it’s broken. By then, it will be too late.
For the industry, Sablier’s maintenance mode is a warning. As the bull market euphoria fades, we will see more protocols become zombies. The lesson is simple: a protocol without a living team is a protocol without a future. Trust the code, yes. But also trust the people who keep the code alive.
What will you build on top of an abandoned layer?