Cosmos Hub Proposal: #986

[v2] Funding Hydro development & integrations in 2025

Status:
Passed
Yes53.3%

Turnout:58.82%

Quorum:40.00%

Yes: 53.3%

74,010,324 ATOM

No: 3%

4,131,969 ATOM

No With Veto: 0%

49,205 ATOM

Abstain: 43.7%

60,614,965 ATOM

Voting Period

  -  

Proposer

cosmos1tvqum6psu8waphaatuau2gxpaay4z7zlntmhkv

Deposit End

Submit Time

Description

Note

This proposal supersedes Prop #984, which doesn't include the requested amount of ATOM and won’t transfer any funds when executed (see the transaction hash of the proposal creation here).

Therefore, we recommend to cast a Yes vote on Prop #984 (which won't execute anyway), as well as this proposal.

Introduction

In November 2023, the Cosmos Hub funded Informal Systems for 2024. The Informal Hub team eliminated the Hub’s technical debt and shipped two products:

Through this process, it became obvious that the Hub needed consolidated leadership to realize its full potential and Informal recruited one of the best teams in the Interchain to take up the product ownership role. Although Informal’s Hub 2024 mandate officially ends on 31-Dec, with the recent success of the first pilot rounds, the Skip team asked the Hydro team to keep developing the product in 2025.

Since the Informal Hub team is under budget in Q4 2024 (see the breakdown in the Funding & reporting section - the Informal Hub team was also under budget in Q1 & Q2 2024 and returned these funds to the community pool), this proposal requests community approval to fund Hydro product development and some Hydro-focused grants for the first two quarters of 2025 by giving Informal a green light to re-assign the excess Q4 2024 budget to Hydro and approving the transfer of an additional 180,000 ATOM from the community pool.

In addition, since we believe that Hydro could be partly self-funded in the second half of 2025, we’re requesting community approval to send Hydro’s PoL profits to an account collectively owned by Hydro’s voters but placed under the control of the Cosmos Hub community (see the Hydro Treasury section for details).

Hydro Roadmap

The Hydro litepaper was published in late May-2024 and the inaugural pilot round started on 6-Nov. To date, 10 projects have submitted bids and 8 third-party teams have also expressed interest in building DeFi apps on top of Hydro. The round 1 cap was reached within 24 hours and the round 2 cap in less than 4 minutes.

In the last couple of months, the Hydro team has also worked on several major updates:

The custom deployment duration and custom export floor are critical for making Hydro more widely useful to larger projects. However, Hydro is still far from a finished product.

The goal is to make Hydro a fully permissionless, automated, risk-minimizing & profit-maximizing system for efficient treasury management on a public blockchain. Hydro should be able to operate like Aave, Compound, or Curve: risk parameter approvals via governance votes, allocations via the auction system, and automatic deployments.

Over the first 6 months of 2025, the Hydro team plans to work on the following features:

FeatureDescription
Third-party integrationsVote optimizers, automated hedging contracts, insurance premium or escrow contracts can be built on top of Hydro to enable new cases
Valence integrationThe Hub retains ownership of Hydro’s liquidity, making the committee less of a bottleneck and increasing the overall security & efficiency of the system.
Token integrationsHydro can be used for the deployment of new tokens ( NTRN, TIA, stables etc.), and projects can submit atomic bids to get both sides of an LP pair
Rev-sharing & penalitiesVoters get a portion of the PoL yield. A portion of the users' locked capital gets slashed when they vote for a project that underperforms.
Hydro governanceHydro users can vote on governance proposals to define all of the protocol parameters and elect or remove committee members
Staking interfaceHydro users can stake, delegate, re-delegate, claim, swap and compound rewards directly from the Hydro interface
“Just-in-time” liquidityHydro provides insurance against liquidity crunches by ensuring that buckets can be deployed quickly to stabilize a position or market.

Note that this is a working backlog that will be re-prioritized based on market signals and community feedback.

Budget

Product development

The Informal Hub team in 2024 consisted of 14 people, split between Forge, Hydro and Hub maintenance. For 2025, we believe it is possible to achieve our Hydro objectives with a reduced team of 6 Full-Time Equivalent staff: 1 Project Lead, 1 Technical Lead, 1 Product Lead, 2 Developers & 1 Growth Lead. We will use the same per-head total rate averages of $325K per year, which includes approximately $225K in salary (and relevant overhead such as employer taxes and benefits) and a standard margin to pay for operational expenses like legal, HR, finance as well as some profit buffer for the company. Like last year, these rates are aligned with the mid-point of market software development rates ($110-$220/hour)

The entire overhead margin will be paid out in ATOMs for alignment purposes. In addition, our proposal will not include any performance bonus (Informal & Hypha 2024 proposal did). See the FAQ section for more details on these decisions.

Hydro grants

To become a fully permissionless & automated protocol, Hydro requires several DeFi & security integrations. While Hydro's core team itself could develop all the necessary features over time, a better option to achieve this goal as fast and cost-efficiently as possible is to enable other third-party teams to build products on top of Hydro.

CategoryBudget
Vote optimizersVote aggregators are smart contract applications that abstract the complexities of voting away from users, give them the benefits of long-term locking, provide them with a tradable liquid derivative, compete for maximal returns, etc.
Delta-neutral deploymentsAutomated strategies are required to avoid exposing the Hub deployments to impermanent loss. Hydro’s bidders can implement a delta-neutral strategy with a real-time adjustment mechanism via smart contracts, insurance, or over-collateralization
Permissionless deploymentsThe Hub retains direct ownership of the liquidity, progressively reducing the need for the Hydro committee to manually deploy funds, enabling shorter and more competitive rounds, and increasing the system's overall security.
SecurityThird-party audits for the features developed by the Hydro product team. Security monitoring, threat detection system, and bug-bounty program for finding and reporting vulnerabilities on PoL venues.

Over the past couple of weeks, the Hydro team has been helping several Cosmos projects submit well-scoped grant proposals to the AADAO so their applications can be processed before the end of the program. However, new teams / existing grantees are likely to step forward with other ideas during the coming months, and the Hydro team may also try to outsource “nice-to-have” features and support work (relaying, infrastructure, community) to external partners. For that reason, the proposal includes a $350,000 budget to manage an ecosystem fund that will support the initiatives listed in the table below (each item is a rough estimate and the final distribution may look significantly different). All outgoing transactions will be managed on-chain via DAO DAO and labeled for transparency.

InitiativeBudgetAmount
Hydro committee~$90/h for six members for 6 months, 5-10h per member per month (adjusted up or down based on individual time commitment)$40,000
Vote optimizers~$30,000 for smart contract development or audits for two separate teams (adjusted up or down based on a statement of work)$60,000
Automated hedging~$30,000 for the smart contract development or audits (adjusted up or down based on a statement of work)$30,000
Insurance premiums~$30,000 for the smart contract development or audits (adjusted up or down based on a statement of work)$30,000
Valence integration~ $50,000 for a first integration of Valence into Hydro (adjusted up or down based on the exact scope)$50,000
Data services~ $20,000 for the tracking of PoL deployments & rewards (adjusted up or down based on development & indexing costs)$20,000
Security audits~ $25,000 per audit & 1 per quarter from a reputable firm (adjusted up or down based on the exact scope)$50,000
Bug bounties~ $10,000 per bug submission for up to five security issues during a six-month period$50,000
Miscellaneous~ $20,000 for IBC relaying, security monitoring, infrastructure costs, software licenses and other miscellaneous expenses$20,000

Note that the Hydro team submitted a $350,000 grant application to the AADAO, which was downsized to $75,000. The amount has been discounted from the ask (see Funding section below).

Hydro treasury

The rewards generated by the Hub’s PoL deployments are currently in the custody of the Hydro committee. The Hydro product team is planning to build out a governance module and equip it with the ability to hold and manage funds.

The purpose of the Hydro treasury is two-fold:

The Hydro treasury transforms Hydro into a self-funded project and may eliminate the need for more community pool requests to the Hub community pool. The treasury would remain under the control of the Cosmos Hub via two mechanisms to be built into Hydro governance:

If this proposal passes, the Hydro product team will transfer pre-Hydro and pilot rounds PoL rewards to a new public DAO on DAO DAO and start building the Hydro governance module and treasury. The DAO will initially be controlled by the product team and ownership will be transferred to Hydro’s governance as soon as it is technically possible.

Funding & reporting

Proposal request

In its 2024 funding proposal, the Informal Hub team planned for a total team of 14 full-time equivalents (FTE) per quarter:

The excess budget represented by 4 FTE in Q4 is $225,714 USDC and 10,214.29 ATOM. We suggest assigning this funding to cover Hydro product development in the first half of 2025. Assuming 1 ATOM is worth $6.5 (and rounding conversion numbers), the breakdown is the following:

Budget lineIn USDIn ATOM
Hydro Team$975,000150,000
Hydro Grants$350,00055,000
Reassigned 2024 funding$-290,000-45,000
Temporary 20% buffer$207,00031,000
AADAO grant$-75,000-11,000
Total$1,167,000180,000

The funding request amount includes a 20% buffer to hedge against ATOM price movement (both for the reassigned Q4 2024 funding and the new 2025 funding):

Sequence of events

Funding will be distributed on the following schedule:

DateAction
On 24-JanThe total ask (including buffer) of 180,000 ATOMs is transferred from the community pool to the Hydro Team DAO
On 25-JanThe Hydro Team converts the relevant number of ATOM into 975,000 * 70% + 275,000 - 290,000 = 667,500 USDC and sends 275,000 USDC to the Hydro Grants DAO
Before 24-JunThe Hydro Team and Hydro Grants DAOs send all excess USDC & ATOM funds (including buffer) to the Hydro Treasury

A new separate entity will receive the distributed funds. This new company (name & domicile to be determined) will be created specifically for Hydro product development. As a company, Informal Systems will be focusing on engineering services, security audits and public good development for devcos and foundations with clear service agreements.

Undistributed funds can be clawed back via a proposal submitted by any community member (the tooling introduced by Prop 972 could be used). Assuming funds are not clawed back before, all excess budget shall be sent to the Hydro Treasury at the end of the mandate.

Reporting

A quarterly progress report will be shared on the Cosmos Hub forum by the Hydro development team, using the same format as the reporting done by the Informal Hub team (see Q1 2024, Q2 2024, Q3 2024, Q4 2024).

Governance votes

Yes: You approve the allocation of Informal Systems excess Q4 budget and an additional 180,000 ATOM from the community pool towards Hydro product development and integrations, and you approve the transfer of Hydro’s PoL rewards to the Hydro Treasury.

No: You do not approve the suggested budget allocation and / or the transfer of Hydro’s PoL rewards to the Hydro Treasury.

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.