Proposal #922
Passed on 12 Apr 2025 with 77.3% of the votes for yes.
Yes
77.3%
100.0% without abstain
Veto
0.0%
of votes cast
Ended
12 Apr 2025
Asked
37.0K
MNTA
77.31%
of votes cast
22.66%
of votes cast
0.02%
of votes cast
0.01%
of votes cast
This proposal seeks to unwind the MNTA/OSMO liquidity position established through [Hidden link], return the MNTA tokens held in the Osmosis Community Pool and Supercharged pool LP position to the MantaDAO multisig, and receive all OSMO deployed to Kujira by Manta DAO in return.
This aligns with both MantaDAO's [Hidden link] and Osmosis' broader move away from OSMO pairings with smaller, non-correlated assets as outlined in [Hidden link].
In 2023, the Osmosis and Manta DAO communities collaborated on a $50k OSMO <> $50k MNTA token swap ([Hidden link]) aimed at deepening cross-ecosystem liquidity and cooperation. Each side deployed matched liquidity to their respective DEXs — Osmosis and Kujira’s FIN — creating protocol-owned liquidity (POL) in both ecosystems.
Since then, Manta DAO has initiated a strategic migration to Rujira, and recently passed [Hidden link], which mandates unwinding all active token swap deals, including MNTA/OSMO, to repatriate assets and simplify token management pre-launch.
Concurrently, Osmosis has adopted a new treasury strategy centered around OSMO decoupling ([Hidden link]), which calls for the dissolution of liquidity pairings between OSMO and lower-cap, non-correlated assets. These are being phased out in favor of stablecoins and high-cap assets with deeper and more efficient trading routes.
This liquidity deployment initially deployed 312,290 OSMO and, if both MNTA/OSMO pools were to be dissolved, would only receiving ~108k back. The pool has historically generated around $3500 in taker fees resulting in a net loss.
Some of this loss could be recouped through the sale of excess MNTA above the 1:1 value ratio, however this would incur high slippage.
Manta Ops have agreed to liquidate their stOSMO/OSMO holdings to bring the ratio of assets closer without resulting in high slippage.
This should result in the recovery of approximately 134k OSMO from the original 312k deployment.
Forum Post: [Hidden link]