Proposal: Migrate Stargaze, Its Applications, and Collections to the Cosmos Hub

On behalf of the Govmos team and the PRO Delegators validator, we believe that using community pool funding to support a project migration sets a dangerous precedent. The Cosmos Hub previously experimented with a grant DAO, and history has shown that this approach led to poor outcomes and misaligned incentives. Now that the Cosmos roadmap has evolved significantly, it is crucial that the Hub is not perceived as a piggy bank for public chains seeking financial support. To be clear, this position is not directed against Stargaze specifically, a project we respect and hope to see thrive within the Cosmos ecosystem. However, the principle remains firm: using the Hub’s financial resources to fund a migration is not acceptable.

From a strategic perspective, we recognize that Stargaze’s potential migration to the Hub is a logical step. Like many public chains in Cosmos, it faces the challenge of sustaining operations with a low-revenue model. While its services undoubtedly fall within the realm of public goods, this creates long-term financial alignment issues that hinder economic sustainability. Therefore, migrating to a chain with stronger fundamentals makes sense, yet expecting that chain to cover the cost of migration does not.

To be perfectly clear, this position extends to any project seeking community pool funding for Hub integration. With CosmWasm now permissionless, all teams are free to deploy, migrate, and evolve independently inside Cosmos Hub. The community pool should not serve as an incentive mechanism for this process, and we will firmly oppose any proposal that moves in that direction.


Thank you for reading,
Govmos.
pro-delegators-sign

3 Likes