[Prop#986] [Passed] Funding Hydro development & integrations in 2025

I urge a veto of this proposal because:

  • If hydro is continued, we build further dependencies on the LSM, which was authored by the north Korean military who were contracted by iqlusion and funded by ICF via iqlusion. When contacted by by the FBI, Zaki Manian, CEO of iqlusion chose not to inform ICF or the wider community, and chose to allow the majority of the code fo ship in an unaltered form while claiming that it had been fully rebuilt. LSM is fine. North Korean military being funded by us isn’t fine. Shipping north Korean military code isn’t fine. Audits aren’t enough. It just needs to go, because the LSM poses a cosmos hub death risk from a reputational and security angle.

  • I think hydro will have a negative impact on the price of atom. For similar reasons, osmosis moved primary liquidity away from the osmo token. Having primary liquidity in atom will drive the price of atom down anytime anybody wants to exit one of the many hydro driven projects. This was the very clear finding of the Osmosis community.

  • Willful violation of the 2-week review period by a team that has enforced it in the past. Rules for thy but not for me. Wait like you told everyone else to wait.

  • Hydro doesn’t even run on the Hub and therefore should not be funded by the Hub

  • Hydro is built using a smart contract framework that is being deprecated

  • I believe that the hub needs a clean break with the past. I think that hydro will undermine the success and vitality of the cosmos hub by removing control of the roadmap from Skip. For example, hydro prevents the removal of the LSM, which should be a high priority.

  • The committee based structure is anathema to decentralization.

If LSM is exploited I don’t see the hub being able to regain user trust. Ever. And the users would be right not to trust.

7 Likes