The Problems
The Dungeon and Terra 2.0 (phoenix-1) IBC bridges are currently non-functional because the IBC light clients on Terra Classic’s side 07-tendermint-285 (Dungeon) and 07-tendermint-286 (Terra 2.0) have expired after exceeding their 17-day trusting period without a MsgUpdateClient being submitted,
caused by extended relayer service interruptions and unreliable RPC endpoints.
The Cosmos Hub path is also broken because the client 07-tendermint-1464 on Cosmos Hub’s side expired for the same reason, and compounding this, the Cosmos Hub relayer wallet (cosmos1jgjc2hca8hdf3pgcd550x78zs0ke2lc2lzg9nf) is nearly depleted with only 573 uatom remaining, making it unable to relay anything. The expired Cosmos Hub client was also causing rly to spam a failed MsgUpdateClient attempt every ~5 seconds on the terra-cosmoshub-path, which was consuming relayer threads and causing context cancellations on the Dungeon path meaning even packets that were in-flight on the Dungeon bridge were timing out and being returned to senders. We have resolved the spam issue by updating the systemd service to only start terra-atomone-path and terra-secret-path, so AtomOne and Secret Network bridges are now running cleanly.
Solutions
For Dungeon and Terra 2.0 recovery, since both chains (dungeon-1 and phoenix-1) still have active clients tracking Terra Classic (their clients are up to date), the fix only requires action on Terra Classic — specifically submitting two ClientUpdateProposal governance proposals, each pairing the expired client with a freshly created substitute client, which requires a community vote on Terra Classic with a LUNC deposit and a ~7 day voting period. Crucially, allow_update_after_expiry: true is already set on both expired clients, meaning governance is permitted to revive them.
- not worth solutions
Opening new channels is not recommended as it would change all IBC denoms, breaking every frontend, DEX listing, and wallet integration currently using the existing ibc/… token addresses. For Cosmos Hub, a separate MsgRecoverClient governance proposal needs to be submitted on Cosmos Hub (which runs ibc-go v10), and the relayer wallet needs an ATOM top-up before that path can be reactivated.
Thank you
Nicolas Boulay + Node Nexus
For DO Win #LUNC