On May 26, the Stargaze Core Team posted a proposal titled “Preparation for Stargaze Chain Sunset.” It names a target date, June 15, 2026, and asks the community one question: do you support signalling the intent to sunset the Stargaze chain and proceeding with the governance sequence that would carry it out? A yes supports the direction and the timeline. A no rejects them.
The proposal is careful about what it is. It is a signalling proposal, which means it is non-binding and enacts nothing. It has its own section listing what it does not do: it does not reduce the validator set, does not trigger a snapshot, does not convert STARS, does not enact any upgrade. Every one of those actions is left to separate binding proposals brought on-chain later. This first vote exists only to establish agreement on the direction before any of the work begins. That restraint is the reason the proposal is worth writing about.
Most chains do not get to choose how they end. They drift. Validators shut down their nodes, the forum goes quiet, and one day the network is gone without anyone having voted on it. Stargaze is doing the opposite. It is treating its own wind-down as a governance event and running it in the open.
What is actually happening
This sunset does not come out of nowhere. It follows a migration that the community already approved through an earlier proposal, one that moved Stargaze, its applications, and its NFT collections to the Cosmos Hub. The sunset proposal states this plainly: the Launchpad, the Marketplace, and the supporting dApps have been redeployed on the Hub, and the migration of all NFT projects is complete.
So the chain being wound down is one whose applications and activity have already left. With the products running on the Cosmos Hub, the Stargaze L1 has shifted, in the proposal’s words, from an active network to a chain preparing for decommission. Operational priorities move from growth to an orderly wind-down. What remains is procedural.
That distinction is worth holding onto. A reader skimming headlines might place this next to other recent Cosmos closures. It is not the same kind of event. This is the final administrative step of a migration the community voted for, not a project running out of road.
The planned sequence
The proposal sets out the governance steps that would follow a yes vote. Each is its own binding proposal, voted separately.
A STARS token conversion. Native STARS would convert 1:1 to a Cosmos Hub-issued STARS token, distributed from a snapshot. The proposal describes the result as a fully distributed supply with zero inflation and a non-staking token.
A community pool transition. Part of the community pool would seed a 1:1 conversion pool, letting holders move from classic native STARS to the new tokenfactory STARS on the Cosmos Hub, managed by the Operations DAO. The remainder of the pool would be divided into three subDAOs on the Hub: Operations, Growth, and Creator.
A final sunset execution. Transfers on the Stargaze L1 would be disabled, the chain would move to an archive, read-only mode, and then be fully decommissioned.
The proposal also points to two related discussions already on Commonwealth: the STARS token conversion and community pool framework, and a separate proposal to reduce the Stargaze validator set to 15. Both are part of the same wind-down, and both would come as their own binding votes.
What the signalling proposal asks is not approval of any of these steps. It asks the community to agree that this is the shape of the plan, so that when each binding vote arrives it reads as one piece of a coherent, pre-communicated sequence rather than an isolated change appearing without warning.
Why signal first
When a team already knows where things are headed, the easy path is to start shipping the binding proposals straight away. A snapshot here, a conversion there, a validator reduction next. Each is defensible on its own. Each is also, to someone who has not been following closely, a small shock. Why is the validator set shrinking. Why is the token suddenly non-staking.
A signalling proposal absorbs that up front. It gives delegators, validators, builders, and creators a single document that lays out the destination, the rough timing, and the order of events. By the time the binding votes arrive, no one is reconstructing intent from a string of separate changes.
It costs the team something to do this. It puts the direction up for a public vote before any of the work is locked in, and it can be voted down. That is exactly what makes it good practice. A team willing to ask first is running governance for the community rather than around it.
What this means if you hold STARS
An orderly wind-down still asks something of the people inside it. A few points from the proposal are worth flagging.
The conversion is 1:1, which is the reassuring part. But the new STARS is described as a non-staking token. Staking on the chain ends with the chain. Holders who currently earn staking rewards should understand that those stop.
The conversion is snapshot-based. The exact timing is not set in the signalling proposal; it would come in the binding token conversion proposal. That is the one to watch if you hold or stake STARS.
The validator set is slated to drop to 15 ahead of shutdown, through its own proposal. Most validators currently securing Stargaze would stop doing so before the chain closes.
None of this is in force yet. The signalling vote only asks whether the direction is right. But it is the moment to start paying attention rather than the moment after.
The Plebis view
We track Stargaze, and we will keep tracking it through the wind-down, the archive phase, and into whatever its governance becomes on the Cosmos Hub. Governance does not stop being worth watching when a chain stops producing blocks. How a community closes something down, and whether it keeps its commitments to holders across the move, is governance health in plain view.
Stargaze is offering a small, useful example of how to do this well. Decide in the open. Signal the direction before executing it. Break the hard parts into separate votes. Tell people what is coming and in what order.
Other chains will reach this point eventually, and many will handle it worse. It is worth noticing the one trying to handle it right.
This post discusses a non-binding signalling proposal posted to Stargaze governance on May 26, 2026, which had not been voted on at the time of writing. It is based on the text of that proposal. Nothing here is financial advice. If you hold STARS, read the proposal and its linked binding proposals directly before acting.
