r/cosmosnetwork • u/Bloqarl • 2d ago
Winding down a Cosmos chain? Turning off IBC send_enabled early strands other chains' tokens on it
Spent part of this week checking a draft docs page on how a Cosmos chain should shut down, and one step that looks harmless isn't.
The page suggested turning off the transfer module's send_enabled before the halt, so nothing new leaves the chain. The catch is that SendTransfer checks that flag before it reaches the branch that burns a voucher going back to its source chain. So once it's off, an ATOM voucher sitting on the dying chain can't go home to the Hub either, and the same goes for every other chain's token on it. Whoever didn't move out before the switch is stuck there when the chain halts.
Credit to the docs author, they reproduced it on a local devnet (Gaia v29.0.1, ibc-go v10.7.0, Hermes) about half an hour later and changed the page.
If only your own token should stop moving, bank send_enabled for that one denom does it and leaves the vouchers alone. Keep IBC transfers on until the return window has closed.
Has any chain team here actually been through a wind-down? I'm curious what you told people holding other chains' tokens on your chain and how much notice you gave them. A wallet team on the same thread asked for exactly that and I don't think there's a common answer yet.