[Proposal #985][VOTING] Fund testnets and mainnet ops by Hypha in 2025

Skip has announced their acquisition by the ICF and the formation of a new entity: Interchain Inc . Under Interchain Inc., all aspects of the core stack will be brought together for in-house work, including the technical development and stewardship of the Cosmos Hub. This is an exciting time for the Hub – strengthening its position as the gateway to the interchain under new leadership. Our work remains focused on supporting the Hub with our well-established testnet program and coordination experience. We’ve waited to post our 2025 funding proposal until this news became public, so the community has access to the full context of how Hypha and the Hub team at Interchain Inc. will be able to work together. Our plan is to put this prop on-chain at the start of the new year to allow time for feedback and so as not to interrupt the holidays. This means there will likely be a 2-3 week period in January 2025 where Hypha’s mandate and funding has ended. During this time, we intend to continue the work we’ve planned (e.g., ensuring the successful v22 upgrade) with the outgoing Hub team at Informal and the incoming team at Interchain Inc. We will also continue coordinating the…

Excerpt (1193 of 19886 characters). Read the whole post on the forum ↗

You guys do a great job and it’s critical we have a high quality coordinated testing environment if the Hub’s going to progress like we expect. Easy yes.

Thanks for the early support

(Which reminds me that I almost forgot one of the most important things I gotta say here!!)

Throughout this first year of working wholly funded by the Hub, we have benefited from the support, guidance, and feedback from countless other builders and thoughtful interchain friends and colleagues.

Thank you to everyone we’ve worked with this year, but especially:

• Our technical colleagues at Informal – Jehan, Marius, Matija, and Philip
• The ICS integration experts at CryptoCrew - Clemens and Paul
• Our 2024 oversight committee – Aidan, Avril, Polkachu, Jim, Shane, and James

And of course, the incredible validators who put in hard work both on mainnet and testnet: Paul at Everstake, James at Lavender Five, Ghazni at Stakecito, Bosco at Silk Nodes, Nikita at Citadel One, Sergey at Quokka Stake, Thomas at High Stakes, Kevin at Oni, and many more.

Hypha has asked me to comment on this proposal, and I’m happy to do so.

In my opinion, Hypha has done excellent work keeping the testnet program and ICS alive. As Interchain Inc. scales into its Hub maintainership, we are going to need immediate infrastructural help in many forms, and from my discussions, Hypha has won the trust of the validator community on that front.

As Interchain Inc. has ended the “team of teams” model, and opted to in-house all core development, Hypha is a perfect example of an external party that provides value for the Cosmos ecosystem for fair prices and with high quality (yet is not core development). I would love to work with them further this year, at a minimum until Interchain develops the devops resources to take over their work ourselves.

This is an easy Yes - Hypha’s work stewarding our testnet has been spectacular, and Hypha’s involvement in valset coordination is also why Hub’s mainnet has effectively been disruption-free, despite numerous upgrades over the past 2 years.

The change to oversight and reporting structure makes sense, and I’m also glad to see the lower budget overall.

It’ll be interesting to see the changes to the Testnet Incentives Program vis-a-vis ICF Delegations Program, and I’m hoping this won’t delay the TIP due to start in Jan’25. That program btw, for those who don’t know, has been great at ensuring validator participation in testing new upgrades of the Hub. I’m honoured that renewing TIP was one of the last grants I was involved in at AADAO.

–

@lexa At the time of the gov prop, could you readjust the USDC<>ATOM ask? Among other assets, AADAO will return USDC to the CP in the next week or so, so maybe you could take more USDC? I don’t have the figure to hand, but the DAO should publicly communicate the amounts soon

The AADAO-funded portion of TIP (which is approved for Jan - Jun 2025) will be unaffected by our work with the ICF on their delegations program. Our 10th period has just wrapped up and was a great pilot for the points-model we pitched to AADAO; I think we’ll hit the ground running in January.

If our overall Hub testnet mandate doesn’t get approved for the rest of 2025, we’ll have to work with the team at Interchain Inc., to very rapidly figure out what happens to the testnets and the incentives program. I hope it’ll persist regardless of who is running it.

Yes, we can adjust all the numbers just before it goes on-chain. More USDC makes sense, agreed. Probably should refresh the ATOM spot price too.

Seems like a no-brainer - Hypha did an outstanding job in managing incentivised testnet, ISLE and everything was extra smooth, so a big thank you for that an an obvious YES from us.

Wholeheartedly support this.

The testnet events have been instrumental in getting to properly understand the PSS mechanisms and ensure smooth operations on the mainnet.
We absolutely need these to continue for the upcoming novelties that are brought to the Hub.

The incentivization is a (very) nice plus, but tbh I’d participate to the testnet Wednesdays even without it simply because they’re extremely useful.

On behalf of the PRO Delegators’ validator team, we fully support this proposal. Hypha’s continued stewardship of the Cosmos Hub testnets and mainnet operations has proven invaluable over the years. Their dedication to validator education, smooth upgrade coordination, and robust testing processes aligns with the long-term success and security of the Hub.

The clear accountability measures and transparency commitments outlined further solidify trust in their work. This proposal ensures critical continuity during the transition to Interchain Inc. and supports the Hub’s evolving ecosystem.

We encourage the community to approve this funding for 2025.
Govmos.

I’m obviously hugely supportive of Hypha, who have a track record of doing a great job and have always been incredible to work with.

I fully support this prop.

lets reduce the gov time. do faster !

Appreciate the hardcore support, Guinch!

I don’t really want to be dragging validators to their voting keys over the holidays and it’s not urgent since we’re fine to keep working for a few weeks while it’s in voting in January. As we all know by now, the holiday season is for emergency upgrades, not governance

I strongly support hypha, recognising their impressive track record, and consistent excellence.

Its a yes from me

I also support Hypha ! Would vote YES

Happy New Year, everyone!

Proposal is now in last call, with intentions to put it on-chain on January 09, 2025.

Some administrative details I’ve added:

• The community pool still has roughly 200k USDC available as no major returns have been processed. We will keep our estimate at 200k USDC.
• The intended recipient wallet is Hypha’s existing Available Fee Cap wallet from our 2024 funding proposal. Prior to the end of voting period, we will ensure all of our 2024 funding wallet are empty and ready for 2025 finances. Currently, we haven’t yet withdrawn our Dec 2024 invoice or processed our final returns.

Please voice any final feedback

Like literally the only “official” party-inclined team we support. Even though we always viewed Hypha as part of the foundation (we know, we know… the stigmas) and part of “that side”. Hypha has not only been the closest thing to any proper dev feedback we have to the foundation, but one of the few teams to try and take things with an angle in mind (at least that has been my personal experience). A Big, strange yes from Citizen Web3

This proposal from the Hypha team is truly a remarkable initiative that demonstrates a deep commitment to the development of the Cosmos Hub ecosystem. It not only addresses critical aspects such as testnet coordination, mainnet support, and the development of new features but also offers a transparent approach to fund allocation and reporting. Here’s why this proposal deserves attention and support: Strategic Integration: With the introduction of the new Interchain Inc. structure, this proposal ensures a smooth transition and the continuation of work on key projects. The plans to maintain testnet stability and support mainnet updates are crucial for the ecosystem’s success. Community Support: The proposal includes transparent reporting mechanisms, such as quarterly reports and a mechanism for fund recall if needed by the community. This builds trust and confidence in the work of the Hypha team. Professionalism and Expertise: The Hypha team has demonstrated a high level of efficiency in previous years, successfully supporting testnets, implementing major updates, and minimizing risks. This proposal continues that tradition and guarantees stability. We are excited to…

Excerpt (1191 of 1341 characters). Read the whole post on the forum ↗

Hypha has done an excellent job in co-coordinating the TIP program. Would love to see them continue their work in 2025

YES from Everstake here. We fully support this proposal, as Hypha has consistently demonstrated exceptional stewardship of the Cosmos Hub testnets, devnet, and mainnet operations. Their assistance to validators during chain upgrades and their robust testing efforts have been invaluable to the Hub’s security and success. The clear accountability measures and transparency outlined further reinforce trust in their work. We hope the community shares our perspective, and that Hypha’s funding for 2025 will be approved by the majority of votes.

Absolutely support this proposal. Hypha is unquestionably professional, dedicated, and competent in running testnets for the Cosmos Hub.

Easy yes vote.

We’re in voting! Thanks for your support, everyone Some final logistics about the on-chain prop: • We did a final adjustment to the ATOM estimates: $6.5 USD ATOM price for a total ask of 200k USDC and 86,538.46 ATOM (which includes the 25% returnable buffer). • In block explorer UI, ATOM is denominated in whole ATOM (not `uatom`) but the IBC-wrapped USDC is denominated in `uusdc`. Expect to see 200,000,000,000 `uusdc` on our prop, which is 200,000 USDC • The IPFS pin of the full text and forum comments does not include this comment. We did several rounds of testing on this proposal because (we think) this is the first time a community spend proposal is requesting two different denoms from the community pool. Here is the public result of a final successful pre-flight check we did this morning. • Proposal 218 on the `provider` testnet proposed funding wallet `cosmos1ax7krw2ymq8upaxwce7df3xpalpp0jddm29fws` with 1,000 ibc/04FF59 and 1.5 ATOM. • This wallet was empty prior to being funded by the proposal. • After passing, the wallet now contains 1,000 ibc/04FF59 and 1.5 ATOM. In private tests, we also found an unexpected detail – the ordering of the denoms…

Excerpt (1196 of 1398 characters). Read the whole post on the forum ↗

Hypha has been great, cosmosrescue supports this proposal and voted YES

Voted yes with my personal ATOM.

Does the cosmos Hub replicated security test net resemble mainnet in any way shape or form?

No it doesn’t

The @cosmoshub replicated security testnet run by @HyphaCoop is worse than useless.

The reason that it is worse than useless is that well people might want to test various scenarios. But if you try to test those various scenarios, they will pass on testnet but fail in the real world, thereby failing at the simple purpose of being a test Network worth testing on.

It’s impossible to overstate the danger that this adds.

And yes, I am saying the changes were made to hide P2P storms.

We can disagree on this but it’s easy to verify what I am saying, so I hope that you check, and learn that the supermajority thing was changed while testing was occuring, that hypha was informed that their changes masked dangerous scenarios in real ways, and that nothing has changed for two years and that funding was given to fix this, but no fix occured.

All relevant conversations are in the hub’s testnet validator channel, unless they’ve been deleted.