This proposal is a revised version of the Cosmos Hub forum post Re-routing PoL deployments through Hydro, which was preceded by the following Cosmos Hub forum posts:
Prior community discussions surfaced a preference to reroute existing PoL deployments into Hydro before exporting additional funds from the Cosmos Hub community pool. Consequently, this on-chain proposal is not a community spend proposal but a signaling proposal that requests members of the different multi-sigs involved in the existing PoL deployments to transfer fund custody to the Hydro committee.
Additional changes resulting from community discussion are as follows:
This signaling proposal indicates the Cosmos Hub community’s intent to re-route all existing liquidity exports to Hydro. This includes the PoL deployments previously approved by governance and any new PoL deployment approved by governance prior to the official launch of Hydro, unless explicitly stated otherwise by a team requesting a new PoL deployment or for maintaining an existing deployment.
This liquidity is essential for many projects, and brutal claw-backs may trigger several issues in Cosmos DeFi (significant slippage, liquidations, problems with borrowing & minting caps, etc.). We suggest the following framework:
The least disruptive process may vary slightly based on how PoL exports are managed. For example, the Osmosis PoL from Prop 858 is managed by a DAO on Osmosis. If this proposal passes, the existing custodians can simply transfer control of the DAO to the Hydro committee. The Informal Systems Cosmos Hub team and the Hydro committee will work with each custodian to transfer the liquidity to Hydro while minimizing position disruptions.
Hydro will launch with a single ATOM bucket and accept LSTs (instead of ATOM) upon the return of the existing liquidity deployments. This market-based approach organically establishes LST buckets based on demand, eliminating the need for the Hub to convert ATOMs into liquid-staking tokens with insufficient demand.
This solution comes with risks. For instance, an LS protocol may put up a very attractive bid to convert a large part of the ATOM into their LST and initiate a large LST bucket without actual market demand. For that reason:
While the above initially requires more active management from the Hydro committee, it is the best way to let the market decide the appropriate size of any LST buckets during the Hydro launch phase.
Note that we do expect Hydro to start new buckets for other tokens in the near future.
LSM shares introduce technical complexity because each tokenization event creates a distinct share denomination, making them non-fungible. Over time, slashing events may make each share denomination worth less than the underlying ATOMs. This necessitates querying the Hub via Interchain Query (ICQ) to determine the weights between LSM shares and handle potentially fluctuating ratios. The Informal team has now prioritized LSM integration and anticipates that this change will cause a few weeks’ delay.
The following committee members have agreed to work unpaid for the first few months as Hydro establishes itself. Afterward, we will develop a compensation model based on the committee’s performance (measured by auction profitability and liquidity export effectiveness) and seek community approval through a separate proposal.
Note that we expect the Hydro committee to have to add/remove members as members' availability changes over time.
Yes: You signal your support for the transfer of custody of Cosmos Hub community pool PoL deployments to the Hydro committee as outlined in this prop to run a competitive bidding process as per the mechanics described in the Hydro litepaper and subsequent community disucssions and revisions on the Cosmos Hub forum
No: You do not signal your support for the transfer of custody of the Cosmos Hub community pool PoL deployments to the Hydro committee
No with Veto: You indicate that this proposal either (1) is deemed to be spam, i.e., irrelevant to Cosmos Hub, (2) disproportionately infringes on minority interests, or (3) violates or encourages violation of the rules of engagement as currently set out by Cosmos Hub
Abstain: You wish to contribute to the quorum, but you decline to vote either for or against