The proposal to shorten Cosmos Hub’s governance voting periods, from 14 to 7 days for standard votes and from 7 to 3 days for expedited ones. is a practical step toward making the governance effective and agile. At GATA HUB, we support this change. We’ve seen the community handle shorter timelines successfully in the past, and we believe these adjustments can improve decision-making without compromising participation, so long as communication remains strong. Shorter voting periods mean quicker reactions to important issues, which is essential as the ecosystem grows. That said, it’ll be important to monitor the impact over time and adjust if needed. Overall, it’s a smart move that balances efficiency with the reality of how active this community already is.
Heavily support this - this will let us do upgrades faster and better!
Can we get rid of the “abstain” voting nonsense while we’re at it? I don’t see the benefit of people showing up to say “no opinion”. Either lower required quorum or make vals actually vote.
Can we get rid of the “abstain” voting nonsense while we’re at it?
That is well beyond the scope of this proposal, but everyone is welcome to make their own proposals (signal or otherwise) to request changes to governance.
Yeah, I’m not getting into the whole process again for no validators to participate in the discussion and then vote no. Concur it’s outside of scope, wanted to put the idea on magmar’s radar, sorry for the poor wording.
Seen sir - abstain has caused much pain
Can’t we create something dynamic based on the quorum ?
Not without changes to the gov module, which is beyond the scope of this proposal. That would be a longer term solution and it’s on the list of things my team and the ICL team is looking into.
Yeah, 100% supportive of this prop. The manual upgrades are painful and this is really going to save time for the validators, ICL & Hypha. They’re also just taking away time for our team to be able to ship, so it’s really going to help us move faster.
If it turns out props are not meeting quorum, we can always revert back. But Osmosis has been doing this for a while now and there are no major problems there, even though there’s a large validator overlap.
Feeling the urgency to put this to a vote so that (if it passes), we will be able to use expedited proposals for patches in June. I’ve moved this into [LAST CALL] and intend to put it on-chain tomorrow.
I’ve added the details of the experiment into the prop text. In essence:
- This is a trial for up to 6 months
- If a better longterm solution arises in 6 months, Hypha will put up a prop to revert the params and work to make sure it hits quorum
- If >10% of reasonable proposals fail to hit quorum in 6 months, Hypha will put up a prop to revert the params and work to make sure it hits quorum
- Hypha is not responsible for passing the reversion proposal, just for putting it up and getting it to quorum
This is incredibly important for enabling the Hub to benefit from rapidly increasing Cosmos development pace and future developer platform we want to build on top of the hub.
Since we’ve become responsible for hub and broader stack development, we’ve been focused on rapidly accelerating product development everywhere. In 3 months, we’ve shipped:
- A new version of IBC with a connection to Ethereum
- A new version of the Cosmos SDK
- A massively improved version of EVMOS’s EVM
- A new liquid staking module that doesn’t require forking the SDK
We’ve also triaged a ton of security issues across the stack and the hub, and we’re really just getting started. With all of this development (espeically the emergency development), we’re constantly bottlenecked on hub upgrade times.
As a result, the Hypha team has had to coordinate multiple unusual non-gov upgrades to patch issues or get the latest and greatest in time for product releases
If we’re going to make the Hub great, we need to be able to move faster as a community and this proposal takes us in that direction
We’re in voting: Mintscan
This closes on May 23rd. Please cast your vote!
Vote YES easily. Great proposal to make Cosmos more agile and faster in decision-making
Hi, how you will make it dynamic? Like some props only or…?