Governance · #1023
Recover IBC Client: Cosmos Hub ↔ Bostrom (07-tendermint-764)
Rejected ·MsgRecoverClient · ends 276d ago
Current tally
- Yes
- 92.5%
- No
- 0%
- Abstain
- 7.5%
- No with veto
- 0%
Cast a vote
KeplrVoting is closed for this proposal.
Summary
Recover expired IBC light client 07-tendermint-764 which tracks the Bostrom chain (bostrom). This client is required for IBC channel channel-341 (Cosmos Hub) ↔ channel-8 (Bostrom) to function.
Client parameters: trusting_period=518400s, max_clock_drift=60s, trust_level=1/3, unbonding_period=691200s.
The Bostrom team has already submitted governance proposals on the Bostrom side (#57) to recover the corresponding Bostrom-side client (07-tendermint-15 tracking cosmoshub-4). Once both sides are recovered, the existing channel will be fully operational — no new channels needed.
Affected denoms: uatom on Bostrom (via channel-8), boot on Cosmos Hub (via channel-341).
Bostrom RPC: https://rpc.bostrom.cybernode.ai
Bostrom LCD: https://lcd.bostrom.cybernode.ai
GitHub: https://github.com/cybercongress
Client parameters: trusting_period=518400s, max_clock_drift=60s, trust_level=1/3, unbonding_period=691200s.
The Bostrom team has already submitted governance proposals on the Bostrom side (#57) to recover the corresponding Bostrom-side client (07-tendermint-15 tracking cosmoshub-4). Once both sides are recovered, the existing channel will be fully operational — no new channels needed.
Affected denoms: uatom on Bostrom (via channel-8), boot on Cosmos Hub (via channel-341).
Bostrom RPC: https://rpc.bostrom.cybernode.ai
Bostrom LCD: https://lcd.bostrom.cybernode.ai
GitHub: https://github.com/cybercongress