Change neutron-1’s consumer chain phase to STOPPED

Context

• [Hidden link] signalled the Hub's acceptance of Neutron ending the provider-consumer relationship established by[Hidden link] and [Hidden link].
• neutron-1 has already transitioned to a fully sovereign chain, separate from the Cosmos Hub. The validator sets are no longer connected, and Hub validators are not able to run Neutron as a consumer chain.
• The Hub’s provider module still shows Neutron as a consumer chain (gaiad query provider list-consumer-chains returns a chain with chain_id neutron-1, consumer_id 0, and phase CONSUMER_PHASE_LAUNCHED).
• Validators formerly required or opted-in to running Neutron as a consumer chain still see Neutron listed when they check gaiad query provider has-to-validate <valcon address> .
• neutron-1 is no longer able to send an infraction message to the Hub because they are no longer a consumer chain, and consumer_id is unique and assigned by the provider module so it cannot be reused by a new chain.
• There is no direct risk from retaining the neutron-1 consumer chain record.
• It is confusing for mainnet queries to return inaccurate information.

Proposal

• This proposal, if passed, will update Neutron's consumer chain record in the Hub to mark it as stopped.
• The neutron-1 chain will show up after a list-consumer-chains query with phase CONSUMER_PHASE_STOPPED.
• Validators will no longer see it in their has-to-validate query.

Testing

This offboarding process has been tested by Hypha on the provider testnet.

• pion-1 graduated to being a sovereign testnet on March 27, 2025.
• Governance proposal to remove pion-1 as a consumer chain[Hidden link].
• pion-1 shows up after a list-consumer-chains query with phase CONSUMER_PHASE_STOPPED.
• Validators no longer see it in their has-to-validate query.

Governance votes

The following items summarize the voting options and what it means for this proposal:

• YES - You support changing neutron-1's consumer chain record phase to STOPPED.
• NO - You do not support changing neutron-1's consumer chain record phase to STOPPED.
• NO WITH VETO - A 'NoWithVeto' vote indicates a proposal either (1) is deemed to be spam, i.e., irrelevant to Cosmos Hub, (2) disproportionately infringes on minority interests, or (3) violates or encourages violation of the rules of engagement as currently set out by Cosmos Hub governance. If the number of 'NoWithVeto' votes is greater than a third of total votes, the proposal is rejected and the deposits are burned.
• ABSTAIN - You wish to contribute to the quorum but you formally decline to vote either for or against the proposal.