Why I Believe Proposal 1029 Is Not Right for the Hub
I’m writing to share my perspective one more time on the Osmosis merger proposal and to explain why we believe it is not right for the Hub.
We’ve published a detailed response on the forums, and I wrote a follow-up response to that post. I’m writing again because this is a critical matter.
To be clear about something broader: We agree completely with the underlying logic. For ATOM to thrive, we need to bring new enterprise blockchains and financial institutions into Cosmos, but we also need the Hub to play a central role in servicing those users. Cosmos Labs and the community need to take more proactive steps to creating a strong Hub. We do believe this means introducing a DEX and incentivizing liquidity, continuing to expand IBC to public and private networks with routing through the Hub, potentially introducing an EVM, and partnering with more institutional-facing defi protocols. We’ve stated this in the past, and we are taking steps to obtain resources that will enable us to do that while continuing to advance our enterprise roadmap.
Unfortunately, the fact remains that I don’t personally view the proposal as right for the Hub for reasons related to the finances, incentives, and product.
Finances
Financially, what the ATOM community gains (or does not gain) under this proposal is substantially outweighed by what we lose and destroy. Specifically:
What the ATOM community gains
- Hard assets (roughly $4m in USDC, ETH, BTC), which will be placed under the control of the maintenance team at OGP and used to pay for their salaries and market-making operations. The composition of this team is not a part of the proposal, nor is a budget for their operations provided. The proposal positions these assets as Cosmos Hub treasury assets while simultaneously double-spending them on maintenance team salaries. As revenues continue to decline, these assets will be drained over time by operational costs, and Osmosis will eventually become a financial liability. All these assets do is delay that outcome.
What we lose
- The cost. At roughly 11 million ATOM, this would consume the entirety of the Community Pool’s ATOM. This is the largest single expenditure in the Hub’s history, for a declining asset with a limited team, no locked liquidity, no growth plan, and no downside protection. Under the most recent annualized revenue projections of $730,000 (see: Datalenses), the payback period is 20+ years before accounting for migration losses, maintenance costs, and continued decline.
What we destroy
- Liquidity. ATOM will own the venue where Osmosis liquidity lives, but we are fragmenting it between two separate venues: one on the Hub and one on Osmosis. Market makers, major LPs, and retail users all have to independently decide to migrate their capital to the Hub deployment. None of that is guaranteed or even incentivized in the proposal. Without spending more ATOM to incentivize the migration, the result is likely fragmented liquidity, meaning worse trade execution for users, lower profits for LPs and the Hub, and a worse overall trading experience than what Osmosis has today. In sum, we might actually accidentally destroy a lot of the value of the Osmosis DEX by acquiring it and trying to migrate the liquidity piecemeal.
What we can’t save
- Osmosis Revenues. We know from our own experience how hard it is to take an asset that is shrinking and turn it around. Osmosis usage, liquidity, and revenue have been declining consistently for a long time. Looking at the last 3 months, Osmosis’s annualized revenue is less than $730,000 (Source: Datalenses), and continues to decline month over month (Annualizing March revenue yields $500k). This proposal does not present a thesis for how the merger reverses that trend. It doesn’t even try. It just makes the decline the Hub’s problem and accelerates the decline by fragmenting liquidity across two chains.
Team and Incentives
Liquidation Risk. We expect a significant amount of ATOM to be immediately sold on the open market, given the lack of lockup or vest. Most of the team is moving on to new projects. They are not interested in continuing to work on Osmosis when they have higher ownership shares. Why would they hold their ATOM after their ownership in the DEX is significantly diluted? The same could be said for the other Osmosis token holders. The Hub would be funding its own sell pressure at a time when it can least afford it.
Limited human capital. The vast majority of the Osmosis team is leaving the project post-migration or has already left, including the founders. We are paying $15m+ dollars and getting very limited continuity from the team that made the product work. In particular, we’re only aware of 2 engineers and several community/ops team members who plan to stick around full or part-time. We will need to use the assets the community pool acquires to build a new team that can actually continue to innovate and expand the DEX.
Continuity risk. The team supposedly staying to help with the liquidity migration and ongoing maintenance has no financial incentive that we’re aware of to do so. Their new ATOM is liquid as soon as the technical migration is completed. This is extremely unusual in an acquisition. A portion of the proceeds is typically set aside to pay out retention over several years, rather than making it fully liquid on day 1. The result is that we are “hoping” that the team members Osmosis claims will be involved for the migration and beyond, actually will be, rather than having any kind of guarantee or incentive-aligned system.
Product
Tech debt. Osmosis is five years old. In the time since it launched, the DEX landscape has moved decisively toward orderbooks, intents and standardized EVM-based implementations. That is what institutional and enterprise counterparties expect to interact with, and what is required to be competitive over the next five years. Osmosis’s architecture does not meet those requirements, and modernizing it is a major undertaking that is not scoped, staffed, or funded in this proposal.
Growth and PMF. We don’t have a growth plan for the DEX that is compelling in the short-term (We wish we did but that’s the truth), and neither does the Osmosis team. ). That’s why many are leaving (I don’t criticize them for it, but that’s the truth).Osmosis in structural decline. How is moving to the Hub going to change Osmosis’s prospects for the better? Especially when you consider the team dissolution and liquidation fragmentation, it feels impossible to me. Even many of the people supporting the proposal admit that there isn’t a compelling path to value accrual at a scale that can payback the acquisition given the product.
The Best Reason to Vote Yes
I think the best reason to vote yes is that the Osmosis team has done incredible work for the Cosmos ecosystem over the years. At an emotional or “karmic” level, they are “owed” an outcome in some sense. Osmosis’s DEX was one of the single best cross-chain products built in Cosmos or with IBC. It is one of the only DEXes that consistently works well with Skip:Go, and we’re deeply dependent on it. More than that, Dev and the engineering team have contributed numerous critical technical upgrades to the Cosmos stack over the years, including ABCI++, tokenfactory, and various improvements to Tendermint performance. Sunny advocated for many builders to choose Cosmos, leading to Akash, Zenith (Urbit’s Cosmos chain), and Babylon.
Personally, I consider Sunny and Dev friends, and I have a deep respect for them as people and builders (efforts to frame this proposal as a personal referendum on Mag and me aside). They helped us ship ProtoRev to Osmosis when Skip was just getting started, and helped us level up on the core stack. They grew Osmosis and grew Cosmos too.
Without Sunny and Dev, there is no doubt that Cosmos would be smaller and less successful than it is today. I think that is the single best reason to vote for this proposal. This is why I actually feel physically uncomfortable opposing the proposal at some level. If anyone is “owed” something, it’s them and their community. (I would put Keplr and Mintscan in a similar bucket)
But, the reality is – and the reason I oppose it – is that that’s not a rational argument about ATOM and what’s best for ATOM tokenholders. It’s not a sensible use of the community pool, which is dedicated to supporting ATOM, not paying developers their “dues”. It’s an emotional argument about karma, and we have to go deeper and analyze from the perspective of ATOM tokenholders. When I do that personally, I don’t see that the deal makes sense in terms of finances, team/incentives, or product.
Conclusion
We will still be here, as we have been. The ICF has committed to not selling ATOM. We have concrete steps in motion to invest in the Hub and the ecosystem around it. Some of these involve commercial processes with other parties, and we have to be responsible about timing before sharing more. What we can say is that these are not ideas on a whiteboard. We are excited to share them and to collaborate with the community on building a Hub that is genuinely worth rallying around.
In the meantime, we urge you to vote no. The goal is right, but the deal is not.
Barry