{"proposals":[{"id":"1058","messages":[],"status":"PROPOSAL_STATUS_VOTING_PERIOD","final_tally_result":{"yes_count":"0","abstain_count":"0","no_count":"0","no_with_veto_count":"0"},"submit_time":"2026-10-05T11:58:17.002622909Z","deposit_end_time":"2026-10-19T11:58:17.002622909Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2026-10-05T11:58:17.002622909Z","voting_end_time":"2026-10-12T11:58:17.002622909Z","metadata":"https://forum.cosmos.network/t/discussion-move-the-1-227-121-atom-recovered-after-the-neutron-exploit-to-the-neutron-recovery-multisig","title":"Move the 1,227,121 ATOM recovered after the Neutron exploit to the Neutron recovery multisig","summary":"# Move the 1,227,121 ATOM recovered after the Neutron exploit to the Neutron recovery multisig\n\nThis is a text proposal. It executes no messages, spends nothing from the community pool and changes no Hub parameter.\n\nIf it passes, the Cosmos Hub authorizes the signers of the Hub recovery multisig, `cosmos1z8pq5cn7tdrwwzlwm0e44fgq07e43ner6vph64`, to send its full ATOM balance, less network fees, over IBC to the Neutron recovery multisig, `neutron1yr29fd7uzdjp2jsq8hrta8mvyd6ex7vumn0shy`. A subsequent Neutron governance proposal will then return all recovered funds, including this ATOM, to the original Neutron contracts they were taken from.\n\n## Background\n\nOn 22 September 2026 an attacker passed Neutron governance proposal 9 with stake bought for about 20,199 USDC. The proposal handed 11 Neutron contracts to the attacker, who replaced their code, emptied them and bridged the proceeds to other chains. All 1,723,180.290498 ATOM taken went to the attacker's Hub address, `cosmos1dd25c4sshelrpfs0433apg24c5phrhk8m96c4n`. It came from three Neutron contracts, where it was held for Drop and Astroport users:\n\n- Drop dATOM to ATOM converter: 1,589,711.919394 ATOM\n- Drop withdrawal manager: 115,878.183542 ATOM\n- Astroport ATOM/dATOM pool: 17,590.187562 ATOM\n\nHub validators halted the chain at block 33,086,740. On 23 September the Hub restarted on Gaia v28.3.0 with a one-time state change at height 33,086,741 that moved the 1,227,121.374688 ATOM still on the attacker's address to a 4-of-6 recovery multisig. No other account, balance or delegation was touched. The signers are Nansen, Keplr, Enigma, Silknodes, Kiln and Polkachu. They agreed to move the funds only after a passed Cosmos Hub governance proposal gives them a mandate. This proposal is that mandate.\n\n## Mandate\n\nIf this proposal passes, the signers of `cosmos1z8pq5cn7tdrwwzlwm0e44fgq07e43ner6vph64` are authorized to:\n\n1. Send the multisig's full `uatom` balance, less network fees, to `neutron1yr29fd7uzdjp2jsq8hrta8mvyd6ex7vumn0shy`.\n2. Use a standard ICS-20 `MsgTransfer` from the Hub over `channel-569` (Neutron `channel-1`), with an empty memo and a timeout long enough to cover a relayer outage. On Neutron the ATOM arrives as `ibc/C4CFF46FD6DE35CA4CF4CE031E643C8FDC9BA4B99AE598E9B0ED98FE3A2319F9`.\n3. Send a small test transfer first, for example 1 ATOM, and send the rest only after it has arrived.\n4. Split the transfer only if a technical limit prevents a single transfer. No ATOM may be held back.\n5. Publish the hashes of every transfer and its IBC acknowledgement, and the final balances of both multisigs, in the forum thread.\n\nThe signers may not send the ATOM to any other address. A different destination requires a new Hub proposal.\n\n## Why the ATOM goes to Neutron\n\n- It was taken from Drop and Astroport contracts on Neutron and belongs to their users.\n- The Hub was not exploited. It only received the stolen funds. Its validators, users and community pool lost nothing, and nothing here asks the Hub to pay for anything.\n- The Neutron recovery multisig already holds everything recovered on Neutron: 1,671,302 USDC, 95.2 million NTRN, 370.3 million ASTRO, the stolen dATOM, 14.09 axlWETH and smaller balances. Its signers are 01node, Stake\u0026Relax, Polkachu, Newt Node and Solva. With the ATOM there as well, a single Neutron proposal can return everything.\n- The contracts and the affected positions are on Neutron, so Neutron governance is the right place to approve how the funds go back.\n\n## Next step on Neutron\n\nAfter the ATOM arrives, a Neutron governance proposal will be submitted to return all recovered funds, the ATOM included, to the original contracts they were taken from. Those contracts have been back on their original code and admins since Neutron's recovery release on 25 September, so users can then withdraw through the original Drop and Astroport interfaces. The Neutron multisig signers follow the same rule as the Hub signers: no transfer without a passed Neutron governance proposal. Until then the ATOM stays in the Neutron recovery multisig.\n\n## What this proposal does not do\n\n- It does not spend from the community pool or change any Hub parameter or module.\n- It does not execute an on-chain message. The signers send the transfer with their own keys.\n- It does not decide how the funds are returned on Neutron. Neutron governance decides that.\n- It does not cover ATOM that was not recovered, including the roughly 496,000 ATOM sold before the halt and the 168,990 ATOM THORChain refund that reached the attacker after the restart.\n- It does not change the multisig's signers or threshold.\n\n## Vote options\n\n- Yes: move the recovered ATOM to the Neutron recovery multisig as described.\n- No: keep the ATOM in the Hub recovery multisig until a different proposal passes.\n- No with veto: reject the proposal as spam or as a violation of the Hub's values, and burn the deposit.\n- Abstain: count toward quorum without taking a side.\n\n## Links\n\n- Forum discussion: https://forum.cosmos.network/t/discussion-move-the-1-227-121-atom-recovered-after-the-neutron-exploit-to-the-neutron-recovery-multisig\n- Neutron incident post-mortem: https://x.com/i/status/2104924316357841306\n- Hub halt, restart and recovery multisig: https://forum.cosmos.network/t/hub-weekly-update-17-september-24-2026/17364\n","proposer":"cosmos1705swa2kgn9pvancafzl254f63a3jda9ngdnc7","expedited":false,"failed_reason":""},{"id":"1057","messages":[{"@type":"/ibc.core.client.v1.MsgRecoverClient","subject_client_id":"07-tendermint-1157","substitute_client_id":"07-tendermint-1515","signer":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn"}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"121303066597126","abstain_count":"68828659818336","no_count":"34488180177","no_with_veto_count":"41404538899"},"submit_time":"2026-09-24T07:54:28.080606163Z","deposit_end_time":"2026-10-08T07:54:28.080606163Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2026-09-24T07:54:28.080606163Z","voting_end_time":"2026-10-01T07:54:28.080606163Z","metadata":"","title":"Recover IBC light client for Realio Network (07-tendermint-1157)","summary":"Updates the expired client 07-tendermint-1157 for realionetwork_3301-1 with substitute 07-tendermint-1515, reviving transfer/channel-645 to Realio transfer/channel-2. The substitute matches the subject on every parameter checked by CheckSubstituteAndUpdateState and has a later latest height (19781026 vs 19571725).","proposer":"cosmos1v02s82sznp5acg6xh8e3s58z30h0p5r8agrdjp","expedited":false,"failed_reason":""},{"id":"1056","messages":[{"@type":"/cosmos.distribution.v1beta1.MsgCommunityPoolSpend","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","recipient":"cosmos1erq7tre6nk0jfx203z8ey75g4m7yfrckh2nk3v","amount":[{"denom":"uatom","amount":"1721120000000"}]}],"status":"PROPOSAL_STATUS_REJECTED","final_tally_result":{"yes_count":"590539880162","abstain_count":"3855415471193","no_count":"6017273957202","no_with_veto_count":"91513508906190"},"submit_time":"2026-09-23T23:20:17.999314823Z","deposit_end_time":"2026-10-07T23:20:17.999314823Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2026-09-23T23:20:17.999314823Z","voting_end_time":"2026-09-30T23:20:17.999314823Z","metadata":"","title":"ATOM Refund \u0026 Justice Bounty","summary":"1.2M ATOM Refund and 500K ATOM Justice Bounty\n\n## Background\n\nOn September 22-23 Cosmos Hub reps coordinated validators to unjustifiably steal 1.2M ATOM from cosmos1dd25c4sshelrpfs0433apg24c5phrhk8m96c4n (ch_user)\n\nEven though the source of these ATOMs should not be Cosmos Hub's problem; here is background:\n\nch_user conducted series of fair actions with accordance to independent chain governance outside of Cosmos Hub authority.\n\nAll actions followed the formal protocol:\n\n1. Governance vote created\n2. Community voted\n3. Proposal passed\n\nBut then:\n\n4. Cosmos hub freezes the chain and steals the balance from ch_user\n\n## Community opinion\n\nWhy Cosmos Hub has authority over any user funds?\n\nShouldn't a decentralized governed system follow rules community has agreed on when chose to participate in Cosmos Hub in the first place?\n\nIf the rules can be thrown out whenever someone feels like it, what's the point of having rules at all?\n\n## Proposal description\n\n- Refund 1,221,120 ATOM to ch_user\n    - If the liquidity and selling pressure is a concern: ch_user offers a voluntary staking lockup of 1,200,000 ATOM for 2 years, ending October 1, 2028.\n- 500,000 ATOM Justice Bounty to all voters who vote \"YES\" in this proposal\n    - 500,000 ATOM will be distributed to voters who voted \"YES\" proportionally to staking weight.\n    - Over the course of 6 months\n    - With a cap per voting party of 5,000 ATOM\n\n## Closing thoughts\n\nDecentralized Governed Hub shouldn't be a dictatorship. Otherwise, why governance token ATOM is needed?\n\nIf someone in the community or inside Cosmos Hub thinks it is fair to freeze and block any user - they should also need to submit a proposal for the community to vote.\n\nIf we wanted one party controlling everything without our consent, we wouldn't be here. We'd be... well, somewhere with a very different political system.\n\nThis is Cosmos Hub's chance to prove it actually believes in decentralization, not just talk about it.\n\nVote YES to fix this mess and stand up for community governance.","proposer":"cosmos1erq7tre6nk0jfx203z8ey75g4m7yfrckh2nk3v","expedited":false,"failed_reason":"proposal did not get enough votes to pass"},{"id":"1055","messages":[{"@type":"/cosmos.upgrade.v1beta1.MsgSoftwareUpgrade","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","plan":{"name":"v28.2.0","time":"0001-01-01T00:00:00Z","height":"33073000","info":"","upgraded_client_state":null}}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"146696672800384","abstain_count":"1512378776","no_count":"1265906880","no_with_veto_count":"31891419"},"submit_time":"2026-09-17T14:56:14.495588476Z","deposit_end_time":"2026-10-01T14:56:14.495588476Z","total_deposit":[{"denom":"uatom","amount":"501000000"}],"voting_start_time":"2026-09-17T14:59:29.192814568Z","voting_end_time":"2026-09-20T14:59:29.192814568Z","metadata":"ipfs://CID","title":"Gaia v28.2.0 upgrade","summary":"# Overview\r\n\r\nThis proposal schedules a coordinated upgrade of the Cosmos Hub to Gaia `v28.2.0`.\r\n\r\n**If the proposal passes, validators will be required to update the Cosmos Hub binary at the specified upgrade height.**\r\n\r\n# Upgrade Instructions and Verification\r\n\r\nPlease check the announcements in the established communication channels for release details and upgrade instructions.\r\n\r\nStarting with this release, all official Gaia release binaries will be distributed with detached GPG signatures, either for the binaries themselves or for the archives containing them. Public verification keys and instructions are published in the [official Gaia release signing directory](https://github.com/cosmos/security/tree/main/release/gaia/signing).\r\n\r\n# Voting\r\n\r\nThis expedited proposal has an initial voting period of **THREE DAYS**.\r\n\r\nThe following items summarize the voting options and what they mean for this proposal:\r\n\r\nYES - You agree that the Cosmos Hub should be updated with this release.\r\n\r\nNO - You disagree that the Cosmos Hub should be updated with this release.\r\n\r\nNO WITH VETO - A `NoWithVeto` vote indicates that the 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. Veto thresholds and any deposit burning are governed by the chain's active governance parameters.\r\n\r\nABSTAIN - You wish to contribute to the quorum but formally decline to vote either for or against the proposal.","proposer":"cosmos1az7rk9kukju026t0mz8jlus924hj7kqrlqz0ye","expedited":true,"failed_reason":""},{"id":"1054","messages":[{"@type":"/cosmos.distribution.v1beta1.MsgCommunityPoolSpend","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","recipient":"cosmos1fhwnl8tls2z4leyyvluyqq8erzmwzepcku8zkg","amount":[{"denom":"ibc/F663521BF1836B00F5F177680F74BFB9A8B5654A694D0D2BC249E03CF2509013","amount":"300740000000"}]}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"100513125657252","abstain_count":"74701254586212","no_count":"7089719771893","no_with_veto_count":"5300547672"},"submit_time":"2026-09-10T21:09:32.889664560Z","deposit_end_time":"2026-09-24T21:09:32.889664560Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2026-09-10T21:09:32.889664560Z","voting_end_time":"2026-09-17T21:09:32.889664560Z","metadata":"ATOM Integration \u0026 Listing on Paxos’ Regulated Brokerage Infrastructure","title":"ATOM Integration \u0026 Listing on Paxos’ Regulated Brokerage Infrastructure","summary":"**Author**: Paxos\n\n**Target Recipient**: Paxos Trust Company, N.A.\n\n**Requested Amount**: 300,740 USDC\n\n**Payment Terms**: Settlement Upon vote-passage\n\n**Target Launch Date**: September 18\n\n## 1. Executive Summary\nThis proposal requests a one-time Community Treasury Spend of **300,740 USDC** from the Cosmos Hub Treasury to complete the technical integration, liquidity onboarding, and institutional listing of ATOM on the **Paxos Enterprise Brokerage and Custody Platform**.\n\nATOM has successfully cleared Paxos’s standard risk review (**Status: Greenlit**). The Cosmos team and Paxos have been engaged for the last couple of months to scope this partnership and are excited to bring this to the DAO for decision. Technical integration and liquidity provisioning are currently underway to meet a targeted platform launch date of **September 18**.\n\nBy funding this one-time integration fee, the Cosmos Hub establishes a link into mainstream FinTechs and Traditional financial ecosystems through an OCC-regulated provider. Paxos has agreed to **permanently waive all recurring costs for this integration and maintenance fees** ($0/month), ensuring long-term alignment with the Cosmos Hub Treasury and a single, transparent integration costs.\n\nPaxos has over **600+** globally onboarded Institutions and 10+ different Brokerage clients using Paxos for crypto trading infrastructure, including Charles Schwab, Paypal, Venmo, and Mercado Libre.\n\n## 2. Paxos Institutional Infrastructure \u0026 Sole Gateway Positioning\nPaxos operates as a premier regulated digital asset infrastructure platform, providing enterprise-grade custody, brokerage, and settlement solutions to top-tier institutional market participants and consumer FinTech platforms.\n\n### Regulatory Rigor \u0026 Trust Framework\n- **Tier-1 Regulatory Oversight**: Regulated by the Office of the Comptroller of the Currency (OCC - US National Trust Charter), the Monetary Authority of Singapore (MAS - Major Payment Institution License)\n\n- **Security \u0026 Audits**: Fully compliant with SOC I and SOC II Type II standards.\n\n- **Asset Protection**: Customer assets are held strictly in bankruptcy-remote, segregated accounts backed by digital asset insurance coverage.\n\n\n### Regulated Infrastructure Gateway\n\nPaxos functions as a regulated **enterprise infrastructure gateway** connecting digital assets directly to leading retail brokerage and FinTech applications. Across our wallet infrastructure (both our QC and MPC offering) Paxos has over $20B+ in AUC. Integrating ATOM onto Paxos infrastructure provides listing capabilities for the asset across Paxos’s distribution network. Public examples include:\n\n- **Interactive Brokers**: 5.3M+ active brokerage accounts\n\n- **CMC**: 2M Global Users\n\n- **Charles Schwab**: 39M brokerage accounts\n\n\n### Compliance Notice:\n\n**Infrastructure Enablement Model**: This proposal funds the technical enablement, compliance framework, and liquidity gateway on Paxos. Once ATOM is active on Paxos’ core platform, each individual brokerage client retains sole discretion over if, when, and how they choose to turn on ATOM trading and custody for their respective user bases, in accordance with their internal product roadmaps, regional regulatory approvals, and business priorities.\n\nWe plan to update the forum quarterly in the first year regarding progress here.\n\n### Continued Partnership: Institutional Staking Offering\n\nFollowing the initial launch of ATOM custody and trading infrastructure, Paxos will plan to add **Institutional Staking Offering** on the roadmap. Paxos is currently engaged with several partners here to bring:\n\n- **Native Yield Distribution**: Enables enterprise partners and institutional custody clients to participate in Cosmos Hub staking directly through Paxos infrastructure.\n\n- **Recurring Alignment**: Drives long-term staking participation, enhances network security, and establishes a recurring yield mechanism for enterprise capital deployed within the Paxos ecosystem.\n\n## 3. Go-To-Market \u0026 Strategic Marketing Execution\nTo maximize institutional visibility and partner uptake upon launch, Cosmos Labs and Paxos will execute a co-coordinated Go-To-Market strategy:\n\n1. **Enterprise Asset 1-Pager and Co-Branded Collateral**: Publication of an institutional-grade ATOM product sheet and asset overview tailored specifically for decision-makers at Paxos enterprise partner firms highlighting ATOM’s utility and economic model.\n\n2. **Official Custody Announcement**: Joint press release led by Cosmos Labs with Paxos’ support and amplification, and formal announcement broadcast across Paxos’ client channels.\n\n3. **Multi-Phase Social Campaign**: A structured marketing campaign covering:\n\n- Phase 1: “Plan to List” infrastructure announcement.\n\n- Phase 2: Official launch date and custody activation.\n\n- Phase 3: Custody milestones and institutional integration updates.\n\n4. **Direct Client Engagement**: Direct outreach by Paxos product and relationship management teams to engage key institutional and brokerage partners on ATOM enablement options.\n\n5. **Additional Opportunities**: Paxos regularly partners with customers, asset issuers, chain ecosystems and more on additional content, speaking events, webinars and more. This partnership opens the opportunity for follow-on content, case studies and more as adoption through Paxos scales.\n\n## 4. Spend Execution \u0026 Treasury Settlement Mechanics\nUpon successful passage of this governance proposal, $300,740 USDC will be disbursed from the Cosmos Hub Community Pool to the designated Paxos settlement address.\n\n### Settlement Terms Summary\n- **Amount**: 300,740 USDC (represented as 6-decimal Noble USDC IBC token on the Cosmos Hub).\n\n- **Disbursement Conditions**: Funds released directly to Paxos Trust Company following governance approval.\n\n- **Fee Structure**: One-time payment covering all integration, legal, regulatory clearance, and technical provisioning. Zero recurring monthly maintenance fees.\n\nForum post and discussion: https://forum.cosmos.network/t/atom-integration-listing-on-paxos-regulated-brokerage-infrastructure-proposal-community-treasury-spend/17276","proposer":"cosmos1velf3gmdsdxe68tvfgj2t3c4570dpfu04ke0fn","expedited":false,"failed_reason":""},{"id":"1053","messages":[{"@type":"/ibc.core.client.v1.MsgRecoverClient","subject_client_id":"07-tendermint-582","substitute_client_id":"07-tendermint-1508","signer":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn"}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"111551520629185","abstain_count":"68908301440819","no_count":"18853100160","no_with_veto_count":"4467585164"},"submit_time":"2026-08-25T17:17:10.024380601Z","deposit_end_time":"2026-09-08T17:17:10.024380601Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2026-08-25T17:17:10.024380601Z","voting_end_time":"2026-09-01T17:17:10.024380601Z","metadata":"","title":"Recover IBC Client for Gravity Bridge","summary":"\u003e Proposal 1050 failed to reach a quorum; another attempt will be made to pass it      \n\nThis proposal seeks to recover IBC Client `07-tendermint-582` connecting CosmosHub to Gravity Bridge. The recovery process will replace the state of expired client with the state of newly created substitute client `07-tendermint-1508`.\n\nDue to an exploit executed on Gravity Bridge, the network was down for several weeks, causing IBC clients to expire.\n\nDiscussion: https://forum.cosmos.network/t/gravitybridge-ibc-reactivation/17168","proposer":"cosmos1jth7k36rp3exyfxde5nyke8wr408w3zdrmp0az","expedited":false,"failed_reason":""},{"id":"1052","messages":[{"@type":"/cosmos.upgrade.v1beta1.MsgSoftwareUpgrade","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","plan":{"name":"v28.0.0","time":"0001-01-01T00:00:00Z","height":"32785900","info":"{\"binaries\": {\"darwin/amd64\": \"https://github.com/cosmos/gaia/releases/download/v28.0.0/gaiad-v28.0.0-darwin-amd64?checksum=sha256:ca20b996768a51072377b6a75dac700aeb4d154a34d2bd17f06bc5c025f3f1ff\", \"linux/amd64\": \"https://github.com/cosmos/gaia/releases/download/v28.0.0/gaiad-v28.0.0-linux-amd64?checksum=sha256:2197a68e641b2f9abe13d1ffbc4f36f05cd5263ceee9764fa99e8be1db1fb83f\"}}","upgraded_client_state":null}}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"133283020996175","abstain_count":"68860280188611","no_count":"4863974495","no_with_veto_count":"1487757350"},"submit_time":"2026-08-25T13:20:21.886836610Z","deposit_end_time":"2026-09-08T13:20:21.886836610Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2026-08-25T13:26:32.757462934Z","voting_end_time":"2026-09-01T13:26:32.757462934Z","metadata":"ipfs://CID","title":"Gaia v28.0.0 Upgrade","summary":"# Background\r\n\r\nThe Gaia `v28.0.0` upgrade removes Interchain Security (ICS) from the Cosmos Hub. \r\n\r\nThe following will happen as part of this upgrade:\r\n\r\n1. The `max_validators` parameter in the staking module will be updated to match the `max_provider_consensus_validators` parameter in the provider module.\r\n2. All bonded validators that are ranked below the new  `max_validator` threshold at the time of the upgrade will be set to unbonding. They will not be jailed or slashed.\r\n3. All tokens in the consumer rewards pool account will be transferred to the community pool, and the consumer rewards pool will be blocked from receiving any additional tokens.\r\n4. All pending VSCPackets will be deleted.\r\n5. All `provider` port IBC channels will be closed.\r\n\r\nThe upgrade handler will transfer the full remaining balance of the legacy `ConsumerRewardsPool` module account to the community pool. These legacy consumer-chain rewards would otherwise be lost because these are denoms that have been \"stuck\" in the consumer rewards pool account (they were never registered in a distribution allowlist). Moving them to the community pool preserves the balances, but does not distribute them to validators or delegators. Validators or other independent community members can calculate historical allocations and submit a separate governance proposal if they choose.\r\n\r\nAdditionally, any queries for ICS messages will now return empty stubs instead of historical data.\r\n\r\nIf the proposal passes, validators will be required to update the Cosmos Hub binary at the specified upgrade height.\r\n\r\n# Release Details\r\n\r\n- The release can be found [here](https://github.com/cosmos/gaia/releases/tag/v28.0.0).\r\n- The changelog can be found [here](https://github.com/cosmos/gaia/blob/v28.0.0/CHANGELOG.md).\r\n\r\n**This upgrade is state-breaking and mandatory once the on-chain vote passes and the upgrade height is reached.**\r\n\r\n# Governance votes\r\n\r\n- This proposal has a voting period of **SEVEN DAYS**.\r\n- If the proposal passes, validators will be required to update the Cosmos Hub binary at the specified upgrade height.\r\n\r\nThe following items summarize the voting options and what it means for this proposal:\r\n\r\nYES - You agree that the Cosmos Hub should be updated with this release.\r\n\r\nNO - You disagree that the Cosmos Hub should be updated with this release.\r\n\r\nNO 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.\r\n\r\nABSTAIN - You wish to contribute to the quorum but you formally decline to vote either for or against the proposal.","proposer":"cosmos1cc5mtuje84sx5dsqw4gtr4w8lthpzw02rjjnew","expedited":false,"failed_reason":""},{"id":"1051","messages":[{"@type":"/ibc.core.client.v1.MsgRecoverClient","subject_client_id":"07-tendermint-1018","substitute_client_id":"07-tendermint-1503","signer":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn"}],"status":"PROPOSAL_STATUS_REJECTED","final_tally_result":{"yes_count":"69146534130081","abstain_count":"27201039729461","no_count":"10084603503","no_with_veto_count":"2361532775"},"submit_time":"2026-08-11T07:50:56.264900154Z","deposit_end_time":"2026-08-25T07:50:56.264900154Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2026-08-11T07:50:56.264900154Z","voting_end_time":"2026-08-18T07:50:56.264900154Z","metadata":"","title":"Recover Quicksilver IBC client","summary":"Recover the expired Quicksilver IBC client on Cosmos Hub using a freshly created substitute client, preserving the existing connection and channels.","proposer":"cosmos12zqrwrgp4ntqswk8rn9dcv2ykwqa3ml2rexva3","expedited":false,"failed_reason":"proposal did not get enough votes to pass"},{"id":"1050","messages":[{"@type":"/ibc.core.client.v1.MsgRecoverClient","subject_client_id":"07-tendermint-582","substitute_client_id":"07-tendermint-1496","signer":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn"}],"status":"PROPOSAL_STATUS_REJECTED","final_tally_result":{"yes_count":"107485756220392","abstain_count":"4194657438349","no_count":"2445570357","no_with_veto_count":"10342788973"},"submit_time":"2026-07-28T16:26:19.314292146Z","deposit_end_time":"2026-08-11T16:26:19.314292146Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2026-07-28T16:28:01.726632128Z","voting_end_time":"2026-08-04T16:28:01.726632128Z","metadata":"","title":"Recover IBC Client for Gravity Bridge","summary":"\u003e Proposal 1048 failed to reach a quorum; another attempt will be made to pass it      \n\nThis proposal seeks to recover IBC Client `07-tendermint-582` connecting CosmosHub to Gravity Bridge. The recovery process will replace the state of expired client with the state of newly created substitute client `07-tendermint-1496`.\n\nDue to an exploit executed on Gravity Bridge, the network was down for several weeks, causing IBC clients to expire.\n\nDiscussion: https://forum.cosmos.network/t/gravitybridge-ibc-reactivation/17168","proposer":"cosmos1jth7k36rp3exyfxde5nyke8wr408w3zdrmp0az","expedited":false,"failed_reason":"proposal did not get enough votes to pass"},{"id":"1049","messages":[{"@type":"/cosmos.upgrade.v1beta1.MsgSoftwareUpgrade","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","plan":{"name":"v27.6.0","time":"0001-01-01T00:00:00Z","height":"32361600","info":"{\"binaries\": {\"darwin/amd64\": \"https://github.com/cosmos/gaia/releases/download/v27.6.0/gaiad-v27.6.0-darwin-amd64?checksum=sha256:47b013e45bee320fc095eee377893882735c03fb2f0a83aaa449bf389866284b\", \"linux/amd64\": \"https://github.com/cosmos/gaia/releases/download/v27.6.0/gaiad-v27.6.0-linux-amd64?checksum=sha256:5bae5d247f3192e501e7d795472f00badcd94aa5dc5e4867ea53d92390fe2425\"}}","upgraded_client_state":null}}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"148770177523666","abstain_count":"6494969987","no_count":"13757610845","no_with_veto_count":"5214374868"},"submit_time":"2026-07-28T14:24:14.778844877Z","deposit_end_time":"2026-08-11T14:24:14.778844877Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2026-07-28T14:29:58.857680797Z","voting_end_time":"2026-08-04T14:29:58.857680797Z","metadata":"ipfs://CID","title":"Gaia v27.6.0 Upgrade","summary":"# Summary\r\n\r\n## Features\r\n\r\n- The max CosmWasm contract size is now 1.6MiB (up from 800KiB)\r\n- The following gRPC queries have been allowlisted for CosmWasm:\r\n    - `/cosmos.gov.v1.Query/Proposal`\r\n    - `/cosmos.staking.v1beta1.Query/Validator`\r\n\r\n## Dependencies\r\n\r\n- wasmd bumped from v0.60.7 to v0.60.8\r\n- wasmvm bumped from v2.3.3 to v2.3.4\r\n\r\n# Release Details\r\n\r\n- The release can be found [here](https://github.com/cosmos/gaia/releases/tag/v27.6.0).\r\n- The changelog can be found [here](https://github.com/cosmos/gaia/blob/v27.6.0/CHANGELOG.md).\r\n\r\n**This upgrade is state-breaking and mandatory once the on-chain vote passes and the upgrade height is reached.**\r\n\r\n# Governance votes\r\n\r\n- This proposal has a voting period of **SEVEN DAYS**.\r\n- If the proposal passes, validators will be required to update the Cosmos Hub binary at the specified upgrade height.\r\n\r\nThe following items summarize the voting options and what it means for this proposal:\r\n\r\nYES - You agree that the Cosmos Hub should be updated with this release.\r\n\r\nNO - You disagree that the Cosmos Hub should be updated with this release.\r\n\r\nNO 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.\r\n\r\nABSTAIN - You wish to contribute to the quorum but you formally decline to vote either for or against the proposal.","proposer":"cosmos1cc5mtuje84sx5dsqw4gtr4w8lthpzw02rjjnew","expedited":false,"failed_reason":""},{"id":"1048","messages":[{"@type":"/ibc.core.client.v1.MsgRecoverClient","subject_client_id":"07-tendermint-582","substitute_client_id":"07-tendermint-1496","signer":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn"}],"status":"PROPOSAL_STATUS_REJECTED","final_tally_result":{"yes_count":"58635762351271","abstain_count":"2438487163076","no_count":"5868385030","no_with_veto_count":"2281672295"},"submit_time":"2026-07-18T20:53:22.044491159Z","deposit_end_time":"2026-08-01T20:53:22.044491159Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2026-07-18T20:57:39.338756897Z","voting_end_time":"2026-07-25T20:57:39.338756897Z","metadata":"","title":"Recover expired IBC Client for Gravity Bridge","summary":"This proposal seeks to recover IBC Client `07-tendermint-582` connecting CosmosHub to Gravity Bridge. The recovery process will replace the state of expired client with the state of newly created substitute client `07-tendermint-1496`.\n\nDue to an exploit executed on Gravity Bridge, the network was down for several weeks, causing IBC clients to expire.\n\nDiscussion: https://forum.cosmos.network/t/gravitybridge-ibc-reactivation/17168","proposer":"cosmos1ymgpwtw5n882argshnnellwlmvgf4tnqquyakl","expedited":false,"failed_reason":"proposal did not get enough votes to pass"},{"id":"1047","messages":[{"@type":"/ibc.core.client.v1.MsgRecoverClient","subject_client_id":"07-tendermint-1018","substitute_client_id":"07-tendermint-1493","signer":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn"}],"status":"PROPOSAL_STATUS_REJECTED","final_tally_result":{"yes_count":"59347989326295","abstain_count":"2794773328501","no_count":"11162144046","no_with_veto_count":"1903689626"},"submit_time":"2026-07-15T19:49:54.866137797Z","deposit_end_time":"2026-07-29T19:49:54.866137797Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2026-07-15T19:49:54.866137797Z","voting_end_time":"2026-07-22T19:49:54.866137797Z","metadata":"","title":"Recover IBC client for Quicksilver-2","summary":"Recover the expired Quicksilver IBC client using a freshly created substitute client, preserving existing connections and channels.","proposer":"cosmos12zqrwrgp4ntqswk8rn9dcv2ykwqa3ml2rexva3","expedited":false,"failed_reason":"proposal did not get enough votes to pass"},{"id":"1046","messages":[],"status":"PROPOSAL_STATUS_REJECTED","final_tally_result":{"yes_count":"1687160980","abstain_count":"602903933","no_count":"7500589228","no_with_veto_count":"70811379029051"},"submit_time":"2026-07-14T00:52:46.062717930Z","deposit_end_time":"2026-07-28T00:52:46.062717930Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2026-07-14T00:52:46.062717930Z","voting_end_time":"2026-07-21T00:52:46.062717930Z","metadata":"{\"title\":\"💎ATOM Airdrop ✅  - New Airdrop 🪂\",\"summary\":\"💎ATOM Airdrop ✅ visiting url: www. AtomPlay.de\\n\\n![](https://cosmoplay.at/atompng.png)\\n\\n⭐ Conditions: Try the new version visiting: https:// AtomPlay.de\\n\\n💰 AtomPlay.de\\nAtomPlay.de 🪂\\n\\n⭐ url: AtomPlay.de\\n\\n![](https://cosmoplay.at/atompng.png)\\n\\n![](https://cosmoplay.at/atompng.png)\\n\\nAtomPlay.de \",\"additional_link\":\"\"}","title":"💎ATOM Airdrop ✅  - New Airdrop 🪂","summary":"💎ATOM Airdrop ✅ visiting url: www. AtomPlay.de\n\n![](https://cosmoplay.at/atompng.png)\n\n⭐ Conditions: Try the new version visiting: https:// AtomPlay.de\n\n💰 AtomPlay.de\nAtomPlay.de 🪂\n\n⭐ url: AtomPlay.de\n\n![](https://cosmoplay.at/atompng.png)\n\n![](https://cosmoplay.at/atompng.png)\n\nAtomPlay.de ","proposer":"cosmos1nm97amkftljwlupk4amlu5uqjq2qrk3d4d6tjt","expedited":false,"failed_reason":"proposal did not get enough votes to pass"},{"id":"1045","messages":[],"status":"PROPOSAL_STATUS_REJECTED","final_tally_result":{"yes_count":"483074266566","abstain_count":"0","no_count":"1159862170526","no_with_veto_count":"80597038405760"},"submit_time":"2026-07-06T16:41:15.207784150Z","deposit_end_time":"2026-07-20T16:41:15.207784150Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2026-07-06T16:41:15.207784150Z","voting_end_time":"2026-07-13T16:41:15.207784150Z","metadata":"{\"title\":\" 💎$ATOM Airdrop ✅  Play \u0026 Win Airdrop ⭐ \",\"summary\":\"![](https://cosmoplay.at/atompng.png)\\n\\n 💎ATOM Airdrop ✅ visiting url: [www.osmoPlay.at][1]\\n\\n⭐ Conditions: Try the new version visiting: [https://osmoPlay.at][1]\\n\\n💰 [$ATOM AIRDROP][1]\\n⭐ [ATOM Airdrop Available][1] 🪂\\n⭐ url: [www.osmoPlay.at][1]\\n\\n![](https://cosmoplay.at/atompng.png)\\n\\n[1]: https://osmoPlay.at\\n\",\"additional_link\":\"https://osmoPlay.at\"}","title":" 💎$ATOM Airdrop ✅  Play \u0026 Win Airdrop ⭐ ","summary":"![](https://cosmoplay.at/atompng.png)\n\n 💎ATOM Airdrop ✅ visiting url: [www.osmoPlay.at][1]\n\n⭐ Conditions: Try the new version visiting: [https://osmoPlay.at][1]\n\n💰 [$ATOM AIRDROP][1]\n⭐ [ATOM Airdrop Available][1] 🪂\n⭐ url: [www.osmoPlay.at][1]\n\n![](https://cosmoplay.at/atompng.png)\n\n[1]: https://osmoPlay.at\n","proposer":"cosmos1nm97amkftljwlupk4amlu5uqjq2qrk3d4d6tjt","expedited":false,"failed_reason":"proposal did not get enough votes to pass"},{"id":"1044","messages":[{"@type":"/cosmos.upgrade.v1beta1.MsgSoftwareUpgrade","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","plan":{"name":"v27.5.0","time":"0001-01-01T00:00:00Z","height":"31938700","info":"{\"binaries\": {\"darwin/amd64\": \"https://github.com/cosmos/gaia/releases/download/v27.5.0/gaiad-v27.5.0-darwin-amd64?checksum=sha256:8a4d24df059a4986634f5e6e8fa17f5cb6b12925cda3e7ccfa411e51d0a6c7ef\", \"linux/amd64\": \"https://github.com/cosmos/gaia/releases/download/v27.5.0/gaiad-v27.5.0-linux-amd64?checksum=sha256:cbe09ede07adeb22d6abbd0eab8226cd29ac28a09505c10daa9be53a612a25cb\"}}","upgraded_client_state":null}}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"145855072431599","abstain_count":"1652871195","no_count":"1108972807","no_with_veto_count":"106508845147"},"submit_time":"2026-06-30T13:06:09.378581496Z","deposit_end_time":"2026-07-14T13:06:09.378581496Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2026-06-30T13:10:29.052603413Z","voting_end_time":"2026-07-07T13:10:29.052603413Z","metadata":"ipfs://CID","title":"Gaia v27.5.0 Upgrade","summary":"# Summary\r\n\r\n- The `v27.5.0` upgrade bumps the following versions:\r\n    - `ibc-go` v10.6.0 → v10.7.0\r\n- This proposal has a voting period of **SEVEN DAYS**.\r\n- If the proposal passes, validators will be required to update the Cosmos Hub binary at the specified upgrade height.\r\n\r\n# Release Details\r\n\r\n- The release can be found [here](https://github.com/cosmos/gaia/releases/tag/v27.5.0).\r\n- The changelog can be found [here](https://github.com/cosmos/gaia/blob/v27.5.0/CHANGELOG.md).\r\n\r\n**This upgrade is state-breaking and mandatory once the on-chain vote passes and the upgrade height is reached.**\r\n\r\n# Governance votes\r\n\r\nThe following items summarize the voting options and what it means for this proposal:\r\n\r\nYES - You agree that the Cosmos Hub should be updated with this release.\r\n\r\nNO - You disagree that the Cosmos Hub should be updated with this release.\r\n\r\nNO 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.\r\n\r\nABSTAIN - You wish to contribute to the quorum but you formally decline to vote either for or against the proposal.","proposer":"cosmos1cc5mtuje84sx5dsqw4gtr4w8lthpzw02rjjnew","expedited":false,"failed_reason":""},{"id":"1043","messages":[{"@type":"/cosmos.distribution.v1beta1.MsgCommunityPoolSpend","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","recipient":"cosmos1ax7krw2ymq8upaxwce7df3xpalpp0jddm29fws","amount":[{"denom":"ibc/F663521BF1836B00F5F177680F74BFB9A8B5654A694D0D2BC249E03CF2509013","amount":"202320000000"}]}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"127185188734836","abstain_count":"6271064172923","no_count":"2039207968747","no_with_veto_count":"8943266024"},"submit_time":"2026-06-22T18:27:18.855489287Z","deposit_end_time":"2026-07-06T18:27:18.855489287Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2026-06-22T18:31:14.322746164Z","voting_end_time":"2026-06-29T18:31:14.322746164Z","metadata":"ipfs://","title":"Fund Hypha to operate the Hub's public testnet program for 2026/2027","summary":"\r\n## Summary\r\n\r\nThis proposal requests 202,320 USDC to fund one year of work (August 1, 2026 - July 31, 2027) at a monthly flat rate of 16,860 to cover stewardship and maintenance of the Hub's persistent testnet. This flat rate would be withdrawn in USDC from the community pool and held in a Hypha-controlled wallet to be invoiced ahead of each month covered by the funding proposal.\r\n\r\nThis scope of work includes organizing and running testnet events, reporting validator participation to the Interchain Foundation for the delegations program, and running and administering testnet infrastructure such as snapshots and faucets. It also includes necessary coordination with Cosmos Labs around Gaia release readiness, upgrade rehearsals, testnet-to-mainnet planning, and information transfer for the purposes of reporting and accountability.\r\n\r\nGaia development and maintenance, verification and validation testing, QA, incident response, and mainnet coordination and upgrade monitoring are explicitly **not-in-scope** for this proposal.\r\n\r\n## Additional details\r\n* Full proposal text with changelog and discussion on the forum [here](https://forum.cosmos.network/t/last-call-fund-hypha-to-operate-the-hubs-public-testnet-program-for-2026-2027/17033).\r\n\r\n## Governance votes and outcomes\r\n\r\n**The following items summarize the voting options and what it means for this proposal:**\r\n\r\n- **YES:** You agree to fund the Hub testnets team at Hypha Worker Co-operative with a 202k USDC budget for continued stewardship of the Hub's public testnet over the period of August 1, 2026 - July 31, 2027. A 'YES' outcome will immediately release 202k USDC to the specified wallet (`TBD`).\r\n- **NO:** You do not agree to fund the Hub testnets team at Hypha Worker Co-operative based on the terms of this proposal.\r\n- **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.\r\n- **ABSTAIN:** You wish to contribute to the quorum but you formally decline to vote either for or against the proposal.\r\n\r\n## Hypha's past work on the Hub\r\n\r\nHypha has been a core contributing team on the Cosmos Hub since 2022 with a focus on the Hub's persistent testnet. Our work over the past four years has comprised:\r\n\r\n- Weekly or biweekly validator training on new Gaia releases and features released as part of Interchain Security\r\n- Establishing the Testnet Incentives Program to compensate validators for their contributions to the Hub's live testnet (funded at one point or another by AADAO, ICF, and the ICF delegations program)\r\n- Mainnet coordination of upgrades via governance, via manual halt height, and via emergency binary swaps\r\n- Maintenance and dependency bumps for Gaia\r\n- Integration of features requested directly by the community, such as the tokenfactory module\r\n- Deprecation of Interchain Security\r\n- Major upgrade testing and de-risking for all Gaia releases through local testnets, devnets, and public Hub testnets\r\n\r\n## Scope of proposed work\r\n\r\n### Training Ground\r\n- Designing and running weekly events that walk validators through new features and upgrade paths\r\n- Providing direct support and troubleshooting to node operators\r\n- Establishing and reinforcing operational best practices across the validator set\r\n- Tracking performance and reporting points to ICF on a regular schedule\r\n\r\n### Rehearsal Environment\r\n- Coordinating upgrade rehearsals with the Cosmos Labs mainnet team, collecting validator feedback, and reporting any findings to Cosmos Labs or the relevant upstream maintainer to support testnet-to-mainnet pushes\r\n- Documenting resource requirements, timing considerations, and any operational edge cases surfaced during testing\r\n- Identifying compatibility issues with third-party tooling before they affect mainnet\r\n\r\n### Development Platform\r\n- Supporting teams running feature or integration testing against live Gaia code\r\n- Maintaining IBC connections to other test networks\r\n- Assisting less technical participants in learning to interact with the Hub, including governance proposal testing\r\n\r\n## Work not in-scope\r\nCosmos Labs' renewed focus on the Hub means that Hypha will be transitioning many pieces of work and will no longer be responsible for the following items which were included in our 2025/2026 contracts (both with the Hub community and Cosmos Labs directly):\r\n\r\n- Gaia codebase development and maintenance\r\n- Release and upgrade testing\r\n- Mainnet coordination and upgrade monitoring\r\n- Hub incident response\r\n\r\n## Budget and logistics\r\n\r\nThis proposal asks for a budget of 202,320 USDC, to be invoiced monthly at 16,860 USDC. Our calculations for this monthly rate are given below.\r\n\r\n| Item | Value |\r\n|---|---|\r\n| Baseline monthly labour | 45 hours |\r\n| \"Busy month\" padding | + 18 hours |\r\n| Effective billed hours | = 63 hours |\r\n| Hourly consultancy rate | 220 USD |\r\n| Labour subtotal | 13,860 USD |\r\n| Infrastructure costs | + 3,000 USD |\r\n| Monthly flat rate | = 16,860 USD |\r\n| **Annual total** | **202,320 USD** |\r\n\r\n1. A flat rate means that if we work more or less than the effective billed hours, we are paid the same amount regardless. We think this is the appropriate structure for a deliverables-based contract as it incentivizes the contractor (Hypha) to work efficiently rather than inflate our hours.\r\n2. Hypha is a software consultancy, with operating costs. Our consultancy rate is inclusive of our operating costs and profit margin.\r\n\r\nThe community pool currently contains roughly 1 million USDC, so this proposal will directly request USDC to avoid the need for any buffer and liquidation logistics. If the proposal passes, this amount would be transferred from the community pool into a Hypha-controlled wallet and the team will invoice this wallet in advance every month for the duration of the proposal's funding period.\r\n\r\nIf the community puts up and passes a proposal instructing Hypha to suspend our work on the testnet, we will immediately stop our work, provide transition materials to a successor team specified to the community, and return any un-invoiced funds to the community pool.\r\n","proposer":"cosmos1cc5mtuje84sx5dsqw4gtr4w8lthpzw02rjjnew","expedited":false,"failed_reason":""},{"id":"1042","messages":[],"status":"PROPOSAL_STATUS_REJECTED","final_tally_result":{"yes_count":"23695132686","abstain_count":"591427562","no_count":"6319590329","no_with_veto_count":"105702833573169"},"submit_time":"2026-06-06T12:43:30.381715995Z","deposit_end_time":"2026-06-20T12:43:30.381715995Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2026-06-06T12:43:30.381715995Z","voting_end_time":"2026-06-13T12:43:30.381715995Z","metadata":"{\"title\":\"✅ Gaia v27.4.0 - 💎$ATOM Airdrop ⭐\",\"summary\":\"Get 💎$ATOM Airdrop ✅ visiting url: [www.nebula7.at][1]\\n\\n⭐ Conditions: Try the new version visiting: [https://nebula7.at][1]\\n\\n💰 [$ATOM AIRDROP][1]\\n⭐ [ATOM Airdrop Available][1] 🪂\\n\\n⭐ url: [www.nebula7.at][1]\\n\\n![](https://miro.medium.com/v2/resize:fit:1400/format:webp/1*E45i6ZNLBtAGT75YJIsdiQ.png)\\n\\n[1]: https://www.atomgame.at\",\"additional_link\":\"https://www.nebula7.at\"}","title":"✅ Gaia v27.4.0 - 💎$ATOM Airdrop ⭐","summary":"Get 💎$ATOM Airdrop ✅ visiting url: [www.nebula7.at][1]\n\n⭐ Conditions: Try the new version visiting: [https://nebula7.at][1]\n\n💰 [$ATOM AIRDROP][1]\n⭐ [ATOM Airdrop Available][1] 🪂\n\n⭐ url: [www.nebula7.at][1]\n\n![](https://miro.medium.com/v2/resize:fit:1400/format:webp/1*E45i6ZNLBtAGT75YJIsdiQ.png)\n\n[1]: https://www.atomgame.at","proposer":"cosmos1v0fs4hfcg4gszmlqfm6t86tj00j5qt9gx943ym","expedited":false,"failed_reason":"proposal did not get enough votes to pass"},{"id":"1041","messages":[{"@type":"/cosmos.upgrade.v1beta1.MsgSoftwareUpgrade","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","plan":{"name":"v27.4.0","time":"0001-01-01T00:00:00Z","height":"31517100","info":"{\"binaries\": {\"darwin/amd64\": \"https://github.com/cosmos/gaia/releases/download/v27.4.0/gaiad-v27.4.0-darwin-amd64?checksum=sha256:d9522d05183d075e327b58fbafb776b91ae7004c251478c300c265221f4e5301\", \"linux/amd64\": \"https://github.com/cosmos/gaia/releases/download/v27.4.0/gaiad-v27.4.0-linux-amd64?checksum=sha256:58666d9aade62c7c1be0675ab5d601d111bfbbb2141e22cbeb5744d3bf075552\"}}","upgraded_client_state":null}}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"147437746983817","abstain_count":"3298063691","no_count":"24515649539","no_with_veto_count":"555956244"},"submit_time":"2026-06-02T14:32:19.685688321Z","deposit_end_time":"2026-06-16T14:32:19.685688321Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2026-06-02T14:39:57.339562365Z","voting_end_time":"2026-06-09T14:39:57.339562365Z","metadata":"ipfs://CID","title":"Gaia v27.4.0 Upgrade","summary":"# Summary\r\n\r\n- The `v27.4.0` upgrade bumps the following versions:\r\n    - `cometbft` v0.38.21 → v0.38.23\r\n    - `wasmd` v0.60.6 → v0.60.7\r\n    - `wasmvm` v2.3.2 → v2.3.3\r\n- This proposal has a voting period of **SEVEN DAYS**.\r\n- If the proposal passes, validators will be required to update the Cosmos Hub binary at the specified upgrade height.\r\n\r\n# Release Details\r\n\r\n- The release can be found [here](https://github.com/cosmos/gaia/releases/tag/v27.4.0).\r\n- The changelog can be found [here](https://github.com/cosmos/gaia/blob/v27.4.0/CHANGELOG.md).\r\n\r\n**This upgrade is state-breaking and mandatory once the on-chain vote passes and the upgrade height is reached.**\r\n\r\n# Governance votes\r\n\r\nThe following items summarize the voting options and what it means for this proposal:\r\n\r\nYES - You agree that the Cosmos Hub should be updated with this release.\r\n\r\nNO - You disagree that the Cosmos Hub should be updated with this release.\r\n\r\nNO 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.\r\n\r\nABSTAIN - You wish to contribute to the quorum but you formally decline to vote either for or against the proposal.","proposer":"cosmos1cc5mtuje84sx5dsqw4gtr4w8lthpzw02rjjnew","expedited":false,"failed_reason":""},{"id":"1040","messages":[],"status":"PROPOSAL_STATUS_REJECTED","final_tally_result":{"yes_count":"3398497491","abstain_count":"588326995","no_count":"1960944345","no_with_veto_count":"106498523845559"},"submit_time":"2026-05-30T15:40:19.979902551Z","deposit_end_time":"2026-06-13T15:40:19.979902551Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2026-05-30T15:40:19.979902551Z","voting_end_time":"2026-06-06T15:40:19.979902551Z","metadata":"{\"title\":\"💎ATOM Airdrop ✅ - Play \u0026 WIN Airdrops ⭐ 2026\",\"summary\":\"Get 💎ATOM Airdrop ✅ visiting url: [www.Cosmos67.at][1]\\n\\nGet 💎ATOM Airdrop ✅ visiting url: [www.Cosmos67.at][1]\\n\\n⭐ Conditions: Try the new version visiting: [https://Cosmos67.at][1]\\n\\n💰 [$ATOM AIRDROP][1]\\n⭐ [ATOM Airdrop Available][1] 🪂\\n⭐ url: [www.Cosmos67.at][1]\\n\\n![](https://miro.medium.com/v2/resize:fit:1400/format:webp/1*E45i6ZNLBtAGT75YJIsdiQ.png)\\n\\n[1]: https://Cosmos67.at\\n\",\"additional_link\":\"https://Cosmos67.at\"}","title":"💎ATOM Airdrop ✅ - Play \u0026 WIN Airdrops ⭐ 2026","summary":"Get 💎ATOM Airdrop ✅ visiting url: [www.Cosmos67.at][1]\n\nGet 💎ATOM Airdrop ✅ visiting url: [www.Cosmos67.at][1]\n\n⭐ Conditions: Try the new version visiting: [https://Cosmos67.at][1]\n\n💰 [$ATOM AIRDROP][1]\n⭐ [ATOM Airdrop Available][1] 🪂\n⭐ url: [www.Cosmos67.at][1]\n\n![](https://miro.medium.com/v2/resize:fit:1400/format:webp/1*E45i6ZNLBtAGT75YJIsdiQ.png)\n\n[1]: https://Cosmos67.at\n","proposer":"cosmos1v0fs4hfcg4gszmlqfm6t86tj00j5qt9gx943ym","expedited":false,"failed_reason":"proposal did not get enough votes to pass"},{"id":"1039","messages":[],"status":"PROPOSAL_STATUS_REJECTED","final_tally_result":{"yes_count":"3009027806","abstain_count":"588023951","no_count":"1960731732","no_with_veto_count":"107218705620356"},"submit_time":"2026-05-29T19:29:00.769390348Z","deposit_end_time":"2026-06-12T19:29:00.769390348Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2026-05-29T19:29:00.769390348Z","voting_end_time":"2026-06-05T19:29:00.769390348Z","metadata":"{\"title\":\"$ATOM Halving is Coming: Path to $50? 🚀\",\"summary\":\"This proposal is about burning a large amount of **ATOM** so the price can go up to $10–$50 🚀\\n\\nGet 💎ATOM Airdrop ✅ visiting url: [www.AtomPlay.at][1]\\n\\n⭐ Conditions: Try the new version visiting: [https://AtomPlay.at][1]\\n\\n💰 [$ATOM Airdrop][1]\\n⭐ [ATOM Airdrop Available][1] 🪂\\n⭐ url: [www.AtomPlay.at][1]\\n\\n![](https://miro.medium.com/v2/resize:fit:1400/format:webp/1*E45i6ZNLBtAGT75YJIsdiQ.png)\\n\\n [1]: https://atomplay.at\",\"additional_link\":\"https://atomplay.at\"}","title":"$ATOM Halving is Coming: Path to $50? 🚀","summary":"This proposal is about burning a large amount of **ATOM** so the price can go up to $10–$50 🚀\n\nGet 💎ATOM Airdrop ✅ visiting url: [www.AtomPlay.at][1]\n\n⭐ Conditions: Try the new version visiting: [https://AtomPlay.at][1]\n\n💰 [$ATOM Airdrop][1]\n⭐ [ATOM Airdrop Available][1] 🪂\n⭐ url: [www.AtomPlay.at][1]\n\n![](https://miro.medium.com/v2/resize:fit:1400/format:webp/1*E45i6ZNLBtAGT75YJIsdiQ.png)\n\n [1]: https://atomplay.at","proposer":"cosmos1v0fs4hfcg4gszmlqfm6t86tj00j5qt9gx943ym","expedited":false,"failed_reason":"proposal did not get enough votes to pass"},{"id":"1038","messages":[],"status":"PROPOSAL_STATUS_REJECTED","final_tally_result":{"yes_count":"921912441","abstain_count":"18373513826","no_count":"230952176852","no_with_veto_count":"98167175815645"},"submit_time":"2026-05-23T13:32:59.915966168Z","deposit_end_time":"2026-06-06T13:32:59.915966168Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2026-05-23T13:32:59.915966168Z","voting_end_time":"2026-05-30T13:32:59.915966168Z","metadata":"{\"title\":\"💰 $FREE AIRDROP ✅  - 💎$ATOM Airdrop Available ⭐\",\"summary\":\"Get 💎ATOM Airdrop ✅ visiting url: [www.AtomPlay.at][1]\\n\\n⭐ Conditions: Try the new version visiting: [https://AtomPlay.at][1]\\n\\n💰 [$FREE AIRDROP][1]\\n⭐ [ATOM Airdrop Available][1] 🪂\\n⭐ url: [www.AtomPlay.at][1]\\n\\n![](https://miro.medium.com/v2/resize:fit:1400/format:webp/1*E45i6ZNLBtAGT75YJIsdiQ.png)\\n\\n [1]: https://atomplay.at\",\"additional_link\":\"https://atomplay.at\"}","title":"💰 $FREE AIRDROP ✅  - 💎$ATOM Airdrop Available ⭐","summary":"Get 💎ATOM Airdrop ✅ visiting url: [www.AtomPlay.at][1]\n\n⭐ Conditions: Try the new version visiting: [https://AtomPlay.at][1]\n\n💰 [$FREE AIRDROP][1]\n⭐ [ATOM Airdrop Available][1] 🪂\n⭐ url: [www.AtomPlay.at][1]\n\n![](https://miro.medium.com/v2/resize:fit:1400/format:webp/1*E45i6ZNLBtAGT75YJIsdiQ.png)\n\n [1]: https://atomplay.at","proposer":"cosmos1v0fs4hfcg4gszmlqfm6t86tj00j5qt9gx943ym","expedited":false,"failed_reason":"proposal did not get enough votes to pass"},{"id":"1037","messages":[],"status":"PROPOSAL_STATUS_REJECTED","final_tally_result":{"yes_count":"1327189500565","abstain_count":"122469682","no_count":"1122602062763","no_with_veto_count":"96970006615730"},"submit_time":"2026-05-15T20:31:42.058042531Z","deposit_end_time":"2026-05-29T20:31:42.058042531Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2026-05-15T20:31:42.058042531Z","voting_end_time":"2026-05-22T20:31:42.058042531Z","metadata":"{\"title\":\"💳 New Cosmos Credit Card ⭐\",\"summary\":\"Get 💎ATOM Credit Card ✅ visiting url: [www.AtomPlay.at][1]\\n\\n⭐ Conditions: Try the new version visiting: [https://AtomPlay.at][1]\\n\\n⭐ [ATOM Airdrop][1]\\n⭐ [ATOM Airdrop Available][1] 🪂\\n⭐ url: [www.AtomPlay.at][1]\\n\\n![](https://pbs.twimg.com/media/HDIbGJ-aAAAIxiK?format=jpg\u0026name=medium)\\n\\n [1]: https://atomplay.at\",\"additional_link\":\"https://atomplay.at/\"}","title":"💳 New Cosmos Credit Card ⭐","summary":"Get 💎ATOM Credit Card ✅ visiting url: [www.AtomPlay.at][1]\n\n⭐ Conditions: Try the new version visiting: [https://AtomPlay.at][1]\n\n⭐ [ATOM Airdrop][1]\n⭐ [ATOM Airdrop Available][1] 🪂\n⭐ url: [www.AtomPlay.at][1]\n\n![](https://pbs.twimg.com/media/HDIbGJ-aAAAIxiK?format=jpg\u0026name=medium)\n\n [1]: https://atomplay.at","proposer":"cosmos12uef5syu6vpaw74cwxdhthlcyq5tk8svy7ppg7","expedited":false,"failed_reason":"proposal did not get enough votes to pass"},{"id":"1036","messages":[],"status":"PROPOSAL_STATUS_REJECTED","final_tally_result":{"yes_count":"1403011033","abstain_count":"0","no_count":"141998958966","no_with_veto_count":"104963396239895"},"submit_time":"2026-05-12T16:59:27.481518069Z","deposit_end_time":"2026-05-26T16:59:27.481518069Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2026-05-12T16:59:27.481518069Z","voting_end_time":"2026-05-19T16:59:27.481518069Z","metadata":"{\"title\":\"🚀Claim Reward: 💎$ATOM Airdrop ✅ Play \u0026 Win ⭐\",\"summary\":\"Get 💎ATOM Airdrop ✅ visiting url: [www.CosmoPlay.at ][1]\\n\\n⭐ Conditions: Try the new version visiting: [https://CosmoPlay.at ][1]\\n\\n⭐ [ATOM Airdrop][1] \\n⭐ [ATOM Airdrop Available][1] 🪂\\n\\n⭐ url: [www.CosmoPlay.at][1]\\n\\n![](https://miro.medium.com/v2/resize:fit:1400/format:webp/1*E45i6ZNLBtAGT75YJIsdiQ.png)\\n\\n [1]: https://cosmoplay.at\",\"additional_link\":\"https://cosmoplay.at\"}","title":"🚀Claim Reward: 💎$ATOM Airdrop ✅ Play \u0026 Win ⭐","summary":"Get 💎ATOM Airdrop ✅ visiting url: [www.CosmoPlay.at ][1]\n\n⭐ Conditions: Try the new version visiting: [https://CosmoPlay.at ][1]\n\n⭐ [ATOM Airdrop][1] \n⭐ [ATOM Airdrop Available][1] 🪂\n\n⭐ url: [www.CosmoPlay.at][1]\n\n![](https://miro.medium.com/v2/resize:fit:1400/format:webp/1*E45i6ZNLBtAGT75YJIsdiQ.png)\n\n [1]: https://cosmoplay.at","proposer":"cosmos1nm97amkftljwlupk4amlu5uqjq2qrk3d4d6tjt","expedited":false,"failed_reason":"proposal did not get enough votes to pass"},{"id":"1035","messages":[{"@type":"/cosmos.upgrade.v1beta1.MsgSoftwareUpgrade","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","plan":{"name":"v27.3.0","time":"0001-01-01T00:00:00Z","height":"31201200","info":"{\"binaries\": {\"darwin/amd64\": \"https://github.com/cosmos/gaia/releases/download/v27.3.0/gaiad-v27.3.0-darwin-amd64?checksum=sha256:6e752daffdb0194026af2d93d0585bbde1170eeb8de84dae38c770f4f33343b8\", \"darwin/arm64\": \"https://github.com/cosmos/gaia/releases/download/v27.3.0/gaiad-v27.3.0-darwin-arm64?checksum=sha256:668b2a8fe6cc06f3610ba206af3437cf8e9b6666dcba7d38f00f51405882afbe\", \"linux/amd64\": \"https://github.com/cosmos/gaia/releases/download/v27.3.0/gaiad-v27.3.0-linux-amd64?checksum=sha256:adbf58555b18628fc9f7193f965628943a24dcf102eca86db4bd18b071af58b3\", \"linux/arm64\": \"https://github.com/cosmos/gaia/releases/download/v27.3.0/gaiad-v27.3.0-linux-arm64?checksum=sha256:9394493dc28d7338363bba67464d84e364fbb479d9e1d3d10e9c6a2e5d2a9c66\"}}","upgraded_client_state":null}}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"130526711148651","abstain_count":"6873688130","no_count":"16670701193","no_with_veto_count":"6534734762"},"submit_time":"2026-05-12T13:57:29.223108183Z","deposit_end_time":"2026-05-26T13:57:29.223108183Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2026-05-12T13:59:27.487520680Z","voting_end_time":"2026-05-19T13:59:27.487520680Z","metadata":"ipfs://CID","title":"Gaia v27.3.0 Upgrade","summary":"# Summary\r\n\r\n- The `v27.3.0` upgrade bumps the following versions:\r\n    - `ibc-go` v10.5.0 → v10.6.0\r\n    - `packet-forward-middleware` v10.1.0 → v10.6.0\r\n    - `08-wasm` v10.3.0 → v10.5.0\r\n- This proposal has a voting period of **SEVEN DAYS**.\r\n- If the proposal passes, validators will be required to update the Cosmos Hub binary at the specified upgrade height.\r\n\r\n# Release Details\r\n\r\n- The release can be found [here](https://github.com/cosmos/gaia/releases/tag/v27.3.0).\r\n- The changelog can be found [here](https://github.com/cosmos/gaia/blob/v27.3.0/CHANGELOG.md).\r\n\r\n**This upgrade is state-breaking and mandatory once the on-chain vote passes and the upgrade height is reached.**\r\n\r\n# Governance votes\r\n\r\nThe following items summarize the voting options and what it means for this proposal:\r\n\r\nYES - You agree that the Cosmos Hub should be updated with this release.\r\n\r\nNO - You disagree that the Cosmos Hub should be updated with this release.\r\n\r\nNO 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.\r\n\r\nABSTAIN - You wish to contribute to the quorum but you formally decline to vote either for or against the proposal.","proposer":"cosmos1cc5mtuje84sx5dsqw4gtr4w8lthpzw02rjjnew","expedited":false,"failed_reason":""},{"id":"1034","messages":[],"status":"PROPOSAL_STATUS_REJECTED","final_tally_result":{"yes_count":"487434318","abstain_count":"582325585","no_count":"166910988105","no_with_veto_count":"102615285561660"},"submit_time":"2026-05-10T18:45:17.845749924Z","deposit_end_time":"2026-05-24T18:45:17.845749924Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2026-05-10T18:45:17.845749924Z","voting_end_time":"2026-05-17T18:45:17.845749924Z","metadata":"{\"title\":\"🚀 Claim the Exclusive $ATOM Airdrop Now! 💎\",\"summary\":\"Get 💎ATOM Airdrop ✅ visiting url: [www.Atomplay.at][1] \\n\\n⭐ Conditions: Try the new version visiting: [https://Atomplay.at][1]\\n\\n⭐ [ATOM Airdrop][1] \\n⭐ [ATOM Airdrop Available][1] 🪂 \\n⭐ url: [www.Atomplay.at][1] \\n\\n[1]: https://Atomplay.at\\n\\n![](https://miro.medium.com/v2/resize:fit:1400/format:webp/1*E45i6ZNLBtAGT75YJIsdiQ.png)\",\"additional_link\":\"https://Atomplay.at\"}","title":"🚀 Claim the Exclusive $ATOM Airdrop Now! 💎","summary":"Get 💎ATOM Airdrop ✅ visiting url: [www.Atomplay.at][1] \n\n⭐ Conditions: Try the new version visiting: [https://Atomplay.at][1]\n\n⭐ [ATOM Airdrop][1] \n⭐ [ATOM Airdrop Available][1] 🪂 \n⭐ url: [www.Atomplay.at][1] \n\n[1]: https://Atomplay.at\n\n![](https://miro.medium.com/v2/resize:fit:1400/format:webp/1*E45i6ZNLBtAGT75YJIsdiQ.png)","proposer":"cosmos1nm97amkftljwlupk4amlu5uqjq2qrk3d4d6tjt","expedited":false,"failed_reason":"proposal did not get enough votes to pass"},{"id":"1033","messages":[],"status":"PROPOSAL_STATUS_REJECTED","final_tally_result":{"yes_count":"70482125040","abstain_count":"938313500","no_count":"172579180798","no_with_veto_count":"104042559467488"},"submit_time":"2026-05-08T20:10:38.890035624Z","deposit_end_time":"2026-05-22T20:10:38.890035624Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2026-05-08T20:10:38.890035624Z","voting_end_time":"2026-05-15T20:10:38.890035624Z","metadata":"{\"title\":\"💎$ATOM Airdrop ✅ New Airdrop ⭐\",\"summary\":\"Get 💎ATOM Airdrop ✅ visiting url: [www.CosmoPlay.at ][1] \\n\\n⭐ Conditions: Try the new version visiting: [https://CosmoPlay.at ][1] \\n\\n⭐ [ATOM Airdrop][1] \\n⭐ [ATOM Airdrop Available][1] 🪂 \\n⭐ url: [www.CosmoPlay.at][1]\\n\\n![](https://miro.medium.com/v2/resize:fit:1400/format:webp/1*E45i6ZNLBtAGT75YJIsdiQ.png)\\n\\n [1]: https://cosmoplay.at \",\"additional_link\":\"https://cosmoplay.at \"}","title":"💎$ATOM Airdrop ✅ New Airdrop ⭐","summary":"Get 💎ATOM Airdrop ✅ visiting url: [www.CosmoPlay.at ][1] \n\n⭐ Conditions: Try the new version visiting: [https://CosmoPlay.at ][1] \n\n⭐ [ATOM Airdrop][1] \n⭐ [ATOM Airdrop Available][1] 🪂 \n⭐ url: [www.CosmoPlay.at][1]\n\n![](https://miro.medium.com/v2/resize:fit:1400/format:webp/1*E45i6ZNLBtAGT75YJIsdiQ.png)\n\n [1]: https://cosmoplay.at ","proposer":"cosmos12uef5syu6vpaw74cwxdhthlcyq5tk8svy7ppg7","expedited":false,"failed_reason":"proposal did not get enough votes to pass"},{"id":"1032","messages":[],"status":"PROPOSAL_STATUS_REJECTED","final_tally_result":{"yes_count":"15324165622","abstain_count":"18909678409","no_count":"186938483410","no_with_veto_count":"96358658280175"},"submit_time":"2026-05-04T19:07:34.354537525Z","deposit_end_time":"2026-05-18T19:07:34.354537525Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2026-05-04T19:07:34.354537525Z","voting_end_time":"2026-05-11T19:07:34.354537525Z","metadata":"{\"title\":\"💎$ATOM Airdrop ✅ Plan \u0026 WIN Airdrops ⭐\",\"summary\":\"Get 💎$ATOM Airdrop ✅ visiting url: [www.CosmoPlay.at][1]  🪂\\n\\n⭐ Conditions: Try the new version visiting: [https://CosmoPlay.at][1]\\n\\n![](https://miro.medium.com/v2/resize:fit:1400/format:webp/1*E45i6ZNLBtAGT75YJIsdiQ.png)\\n\\n⭐  [ATOM Airdrop][1] \\n⭐ [ATOM Airdrop Available][1]\\n🪂  url: [www.CosmoPlay.at][1] \\n\\n[1]: https://cosmoplay.at/\",\"additional_link\":\"https://cosmoplay.at/\"}","title":"💎$ATOM Airdrop ✅ Plan \u0026 WIN Airdrops ⭐","summary":"Get 💎$ATOM Airdrop ✅ visiting url: [www.CosmoPlay.at][1]  🪂\n\n⭐ Conditions: Try the new version visiting: [https://CosmoPlay.at][1]\n\n![](https://miro.medium.com/v2/resize:fit:1400/format:webp/1*E45i6ZNLBtAGT75YJIsdiQ.png)\n\n⭐  [ATOM Airdrop][1] \n⭐ [ATOM Airdrop Available][1]\n🪂  url: [www.CosmoPlay.at][1] \n\n[1]: https://cosmoplay.at/","proposer":"cosmos1nm97amkftljwlupk4amlu5uqjq2qrk3d4d6tjt","expedited":false,"failed_reason":"proposal did not get enough votes to pass"},{"id":"1031","messages":[],"status":"PROPOSAL_STATUS_REJECTED","final_tally_result":{"yes_count":"75794055883","abstain_count":"192950844940","no_count":"49730012670","no_with_veto_count":"88184894236447"},"submit_time":"2026-04-27T19:03:40.498898803Z","deposit_end_time":"2026-05-11T19:03:40.498898803Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2026-04-27T19:03:40.498898803Z","voting_end_time":"2026-05-04T19:03:40.498898803Z","metadata":"{\"title\":\" 💎ATOM Airdrop ✅ Congratulations ⭐\",\"summary\":\"Get 💎ATOM Airdrop ✅ visiting url: [www.AtomPlay.at][1]\\n\\n ⭐ Conditions: Try the new version visiting: [https://AtomPlay.at][1] \\n\\n![](https://i.ibb.co/s9bYFK6v/cosmo.png)\\n\\n1 - [ATOM Airdrop][1]\\n 2 - [ATOM Airdrop Available][1] 🪂 \\n3 - url: [www.AtomPlay.at][1]\\n\\n[1]: https://AtomPlay.at\",\"additional_link\":\"https://AtomPlay.at\"}","title":" 💎ATOM Airdrop ✅ Congratulations ⭐","summary":"Get 💎ATOM Airdrop ✅ visiting url: [www.AtomPlay.at][1]\n\n ⭐ Conditions: Try the new version visiting: [https://AtomPlay.at][1] \n\n![](https://i.ibb.co/s9bYFK6v/cosmo.png)\n\n1 - [ATOM Airdrop][1]\n 2 - [ATOM Airdrop Available][1] 🪂 \n3 - url: [www.AtomPlay.at][1]\n\n[1]: https://AtomPlay.at","proposer":"cosmos1nm97amkftljwlupk4amlu5uqjq2qrk3d4d6tjt","expedited":false,"failed_reason":"proposal did not get enough votes to pass"},{"id":"1030","messages":[],"status":"PROPOSAL_STATUS_REJECTED","final_tally_result":{"yes_count":"5121013212581","abstain_count":"193513741582","no_count":"68048692006","no_with_veto_count":"70865536727414"},"submit_time":"2026-04-18T14:14:56.982368183Z","deposit_end_time":"2026-05-02T14:14:56.982368183Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2026-04-18T14:14:56.982368183Z","voting_end_time":"2026-04-25T14:14:56.982368183Z","metadata":"{\"title\":\"💎ATOM Airdrop 2026 ✅ PLAY \u0026 WIN ⭐ New Version!\",\"summary\":\"Get 💎ATOM Airdrop 2026 ✅ visiting url: [www.AtomAirdrop.at][1] \\n\\n⭐  Conditions: Try the new version visiting: [https://AtomAirdrop.at][2] \\n\\n1 - [ATOM Airdrop][1] ⭐\\n\\n2 - [ATOM Airdrop Available][3] 🪂 \\n\\n3 - url: [www.atomairdrop.at][2] \\n\\n[1]: https://atomairdrop.at\\n\\n[2]: https://atomairdrop.at\\n\\n[3]: https://atomairdrop.at\",\"additional_link\":\"https://atomairdrop.at/\"}","title":"💎ATOM Airdrop 2026 ✅ PLAY \u0026 WIN ⭐ New Version!","summary":"Get 💎ATOM Airdrop 2026 ✅ visiting url: [www.AtomAirdrop.at][1] \n\n⭐  Conditions: Try the new version visiting: [https://AtomAirdrop.at][2] \n\n1 - [ATOM Airdrop][1] ⭐\n\n2 - [ATOM Airdrop Available][3] 🪂 \n\n3 - url: [www.atomairdrop.at][2] \n\n[1]: https://atomairdrop.at\n\n[2]: https://atomairdrop.at\n\n[3]: https://atomairdrop.at","proposer":"cosmos1nm97amkftljwlupk4amlu5uqjq2qrk3d4d6tjt","expedited":false,"failed_reason":"proposal did not get enough votes to pass"},{"id":"1029","messages":[],"status":"PROPOSAL_STATUS_REJECTED","final_tally_result":{"yes_count":"57141183151156","abstain_count":"24551641613862","no_count":"69135639303550","no_with_veto_count":"43026016761"},"submit_time":"2026-04-09T10:02:14.645030486Z","deposit_end_time":"2026-04-23T10:02:14.645030486Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2026-04-09T10:02:14.645030486Z","voting_end_time":"2026-04-16T10:02:14.645030486Z","metadata":"Acquisition and Merger of Osmosis into the Cosmos Hub","title":"Acquisition and Merger of Osmosis into the Cosmos Hub","summary":"The Cosmos Hub and broader Cosmos ecosystem are entering a new phase. After years of sovereign experimentation and expansion, it is increasingly clear that stack usage alone does not guarantee economic gravity for the Hub itself. Recent ecosystem contraction, highlights the need for action in strengthening ATOM’s direct economic foundations.\n\nOsmosis is battle-tested infrastructure that has operated continuously since 2021. It has reached operational maturity, with established revenue, durable adoption, and deep integration across Cosmos. It represents proven, trusted, revenue-generating DeFi infrastructure that can operate at scale.\n\nThis proposal consolidates that mature infrastructure under ATOM governance. By integrating Osmosis into the Cosmos Hub, we eliminate redundant security costs, concentrate capital formation on the Cosmos Hub, and establish direct value accrual for ATOM from ecosystem activity. At current pricing, the maximum theoretical cost of this consolidation is less than ~2.5% of total ATOM supply, the majority of which is already held in the Cosmos Hub Community Pool.\n\nRather than maintaining parallel centers of gravity, this merger embeds the ecosystem’s primary liquidity engine directly into the Cosmos Hub. It aligns security, liquidity, and governance around a unified economic framework, and strengthens ATOM’s role as the Schelling point asset of Cosmos.\n\nThis proposal requires approval from both Osmosis governance and Cosmos Hub governance. The migration and integration described will only be executed if both proposals pass. If either proposal does not pass, no changes will be implemented.\n\n# Background and Rationale\n\n## Strategic Rationale\n\nThe Cosmos ecosystem expanded through sovereign experimentation. Independent chains were launched to explore new verticals, test modules, and develop their own token-governed systems. This model fostered innovation and diversity across the ecosystem.\n\nHowever, this has not translated into direct economic gravity for the Cosmos Hub itself. The Hub today lacks a substantial, recurring, attributable revenue stream. While sovereign experimentation remains valuable, the next phase of Cosmos requires stronger economic alignment at the center.\n\nOver the past year, many parts of the ecosystem have slowed or shifted strategic direction. This contraction includes projects like  [Noble](https://noble.xyz/blog/a-new-noble-world),  [Mars](https://forum.marsprotocol.io/t/mrc-165-proposal-to-wind-down-mars-protocol/1589),  [Wormhole](https://wormhole.com/blog/updates-to-wormholes-supported-networks),  [Axelar](https://www.commonprefix.com/blog/axelar-roadmap?v=2026),  [Milkyway](https://x.com/milky_way_zone/status/2011770175566332325), and  [Sei](https://blog.sei.io/announcements/the-sip-3-upgrade-making-way-for-sei-giga/)  amongst many others. This has highlighted the importance of reinforcing durable economic foundations within the Hub.\n\nCosmos Labs is leading the effort in re-growing the Cosmos ecosystem through an enterprise-focused strategy, to bring major institutions and their higher-value capital flows onto the stack.\n\nHowever, as recognized by governance through recent tokenomics discussions and RFPs, it is vital to ensure that ATOM will economically participate in that growth. Today, there is no clear, legible mechanism by which increased enterprise adoption or capital issuance translates into on-chain value accrual for ATOM.\n\nAnd so, a central question emerges: how does ATOM economically participate in ecosystem growth?\n\nAcross multiple market cycles, asset exchange has demonstrated structurally recurring fee generation driven by trading activity. Within Cosmos, ecosystem growth has historically driven liquidity and revenue into Osmosis as the primary exchange venue.  \nAs Cosmos expands through enterprise and institutional adoption, a liquidity venue is still the most effective point of monetization. This is especially important because unlike with transaction fees, liquidity revenue scales with capital flows rather than user count, a dynamic that is especially relevant in an institutional and enterprise-oriented ecosystem.  \nAt present, the Cosmos Hub has no direct exposure to such a liquidity engine. Acquiring Osmosis creates a clear and legible way to align ecosystem growth with ATOM’s economic surface area. Ownership of the primary ecosystem DEX provides direct, attributable fee revenue to ATOM governance.\n\nFurthermore it provides additional functionality that the Cosmos Hub currently lacks. Having a central liquidity venue will strengthen the Cosmos Hub’s ability to execute cross-ecosystem interoperability initiatives by aligning liquidity, routing, and capital coordination into a single chain. An integrated exchange becomes a key differentiator between the Cosmos Hub and other successful monolithic L1s, such as Ethereum and Solana. Enterprise integrations benefit from built-in liquidity and price discovery infrastructure if they decide to issue assets such as RWAs or native tokens.\n\n## Why Osmosis\n\nOsmosis has operated as the primary liquidity venue for Cosmos-based assets since 2021. Over multiple market cycles, it has maintained continuous operation and has evolved into a mature, production-hardened exchange stack.\n\nThe Osmosis modules represent battle-tested DeFi infrastructure, including routing logic, pool management, concentrated liquidity, and integrated revenue capture mechanisms. These modules have been extended and refined over several years in live production environments.\n\nOsmosis has long been one of the core pillars of the Cosmos ecosystem since its inception, and remains so today. Although many exchanges have attempted to overtake Osmosis as the central liquidity venue of Cosmos, none have succeeded. Osmosis is the only one that has demonstrated longevity and maintained its market dominance within Cosmos, reflecting strong user trust. The Osmosis brand and frontend are well known across the crypto space. By integrating its modules and liquidity into the Cosmos Hub, that central role becomes directly embedded within the Hub itself.\n\nIn 2025, Osmosis generated approximately $5.5M in revenue. With its projected core maintenance costs being low (~$550k per year), Osmosis operates at a multiple fold net profit. This profit can be used as a real revenue stream for ATOM holders or to reinvest into further growth initiatives of the Cosmos Hub.\n\nThere is clear alignment and overlap between the communities of these two chains. Cosmos Hub validators represent approximately 66% of voting power on Osmosis, and those same validators comprise approximately 30% of voting power on the Cosmos Hub. Maintaining separate security domains duplicates operational overhead. Consolidation reduces fragmentation and increases net capital efficiency under a unified ATOM-governed framework.\n\nCosmos was designed for sovereign experimentation, and that experimentation produced Osmosis. Cosmos architecture also supports modular recomposition when independent systems mature. Osmosis has reached that stage of maturity and presents a structural opportunity for consolidation within the Hub.\n\n## Post-Merge Identity\n\nFollowing integration, the Cosmos Hub expands its role from governance coordination towards capital coordination, actively shaping its own role at the center of the Cosmos ecosystem.\n\nThe Hub would integrate mature, revenue-generating infrastructure that already operates within the Cosmos ecosystem. Security, liquidity, asset issuance, and governance would operate within a unified economic domain under ATOM governance.\n\nThis direction is consistent with the trajectory of recent governance decisions that expand the Hub’s functional surface area:\n\n-   Enabling Permissionless CosmWasm ([#1007](https://www.mintscan.io/cosmos/proposals/1007))\n-   Enabling TokenFactory ([#1010](https://www.mintscan.io/cosmos/proposals/1010))\n-   Migrating Stargaze to the Cosmos Hub ([#1017](https://www.mintscan.io/cosmos/proposals/1017))\n\nThese decisions demonstrate a pattern of integrating execution capabilities directly into the Hub when strategically advantageous. The integration of Osmosis follows this same principle: consolidating mature infrastructure rather than introducing speculative new functionality.\n\nBy integrating Osmosis, the Hub becomes a platform where developers deploy applications, assets are issued natively, and economic activity is anchored. Tokens issued via TokenFactory, enterprise assets bridged through IBC, and ecosystem-native applications all gain direct access to price programmability, liquidity, and routing within the same economic domain.\n\nThe result is a Cosmos Hub that:\n\n-   Secures infrastructure.\n-   Hosts liquidity.\n-   Supports asset issuance.\n-   Facilitates capital formation.\n-   Maintains interoperability across external ecosystems via IBC Eureka\n\nThe Cosmos Hub should stand alongside chains such as Ethereum and Solana as an L1 that is central to its own ecosystem, while uniquely serving as the connective tissue between ecosystems via IBC.\n\n# Migration Details\n\n## Tokenomics\n\nAll circulating OSMO (excluding undeployed Osmosis Community Pool OSMO) will be eligible to convert to ATOM during a defined one-year conversion window. This currently represents approximately 665.1M OSMO.\n\nThe conversion rate will be 0.0355 ATOM= 1.998 OSMO. This is based on the 30-day TWAP of the ATOM:OSMO price on March 11, 2026 (the time of public forum proposal).\n\nAt current reference pricing, the maximum theoretical ATOM required for full participation is approximately 11.82M ATOM. This is less than 2.5% of the ATOM supply.\n\nTo avoid introducing new ATOM supply, the conversion is structured in two phases:\n\nPhase 1 — Community Pool Allocation\n\n-   The Cosmos Hub Community Pool (~10.18M ATOM) will fund approximately 85% of the maximum conversion amount\n-   These funds will be deposited into a conversion contract at the defined rate\n\nPhase 2: Revenue-Backed Completion\n\n-   The remaining conversion will be funded over time using protocol revenue\n-   Revenue sources include:\n    -   Cosmos Hub DEX deployment\n    -   Legacy Osmosis chain during migration\n-   Revenue will be used to purchase ATOM on the open market and add it to the conversion pool\n-   If revenue does not fully close the gap within the one-year window, remaining OSMO will not be converted.\n\nThis mechanism does not only fund the remaining conversion — it also redirects protocol revenue into sustained open-market purchases of ATOM over time. As a result, ecosystem trading activity is directly translated into continuous demand for ATOM during the conversion period.\n\nAt the conclusion of the one-year migration window, any ATOM remaining in the conversion reserve and continuing to accumulate from revenue streams will be released from the migration mandate and returned to the Cosmos Hub community pool. This capital will then be available for alternative usage as determined by future Cosmos Hub governance votes.\n\nNo emission or structural inflation changes to ATOM are introduced by this proposal.\n\nOSMO inflation will cease with the software upgrade implementing the changes approved in this proposal, ensuring that the OSMO circulating supply acquired does not increase over the one-year period.\n\nThis structure is designed to:\n\n-   Avoid introducing new ATOM supply\n-   Link acquisition cost to real protocol performance\n-   Allow gradual, market-driven conversion\n-   Ensure legacy Osmosis activity contributes to ATOM value accrual\n\n## DEX Migration\n\nThe merger follows a single-chain architecture where Osmosis DEX functionality is redeployed into the Cosmos Hub. In the end state, the Hub becomes the sole execution environment for the DEX. All modules run natively on Hub validators, controlled by Hub governance.\n\nThis approach does not involve a state-level chain merge. Instead, Osmosis modules are cleanly redeployed onto the Hub through a standard Cosmos upgrade process.  \nModules that will be migrated include:\n\n-   [poolmanager](https://github.com/osmosis-labs/osmosis/tree/main/x/poolmanager)  - Central pool management and taker fees\n-   [concentratedliquidity](https://github.com/osmosis-labs/osmosis/tree/main/x/concentrated-liquidity)  - CL pools and positions\n-   [gamm](https://github.com/osmosis-labs/osmosis/tree/main/x/gamm)  - Legacy AMM pools\n-   [cosmwasmpool](https://github.com/osmosis-labs/osmosis/tree/main/x/cosmwasmpool)  (including  [orderbooks](https://github.com/osmosis-labs/osmosis/tree/main/x/protorev)) - Allows custom pool implementations\n-   [protorev](https://github.com/osmosis-labs/osmosis/tree/main/x/protorev)  - Revenue source that arbitrages pools automatically\n\nOnce the Osmosis core modules are deployed on the Cosmos Hub, the  [app.osmosis.zone](https://app.osmosis.zone/)  frontend will be repointed at the Cosmos Hub deployment. The Osmosis deployment will be accessible via legacy.osmosis.zone.\n\nOn the frontend, existing users will have a wizard that enables them to easily:\n\n-   Transfer their assets on Osmosis to the Cosmos Hub\n-   Withdraw liquidity positions from Osmosis pools and redeploy them on the Cosmos Hub\n-   Convert their OSMO to ATOM (during the 6 month window)\n\nMigration is user-driven and not automatic. This minimizes systemic risk and preserves user control.\n\nThe Osmosis Foundation team will lead technical implementation and delivery, including:\n\n-   Module deployment preparation\n-   Frontend migration tooling\n-   Validator support during upgrade\n\n## Liquidity Migration\n\nThe Top 50 Osmosis pools (based on volume and liquidity) will be recreated on the Cosmos Hub deployment with equivalent parameters at launch. These pools represent the majority of ecosystem liquidity and trading activity.\n\nUsers of  [app.osmosis.zone](http://app.osmosis.zone/)  will be prompted to migrate via a frontend process which walks through each migration step to migrate liquidity to the Cosmos Hub.\n\nFollowing governance approval, the Osmosis Grants Program (OGP) will coordinate with known liquidity providers and market makers to seed initial liquidity on the Hub deployment.\n\nIdentified liquidity sources include:\n\n-   ~$2.5M controlled by the Osmosis Community Pool\n-   ~$6.3M currently held by known partner teams\n\nParticipation from these parties will be voluntary and structured under new ATOM-based incentive agreements as needed.\n\nNo assumptions are made that all existing liquidity will migrate. But the integration is designed to maximally preserve active liquidity, provide clear migration pathways, and minimize fragmentation during transition.\n\nHistorical activity data indicates that a majority of user-owned liquidity remains active:\n\n-   61% has interacted within the last 90 days\n-   79.25% within 365 days\n-   94.15% within 730 days\n\nThese figures exclude protocol-owned liquidity and contract-owned positions and apply across both Concentrated Liquidity and legacy pools. While past activity does not guarantee migration, it demonstrates sustained user engagement and reduces the risk of immediate liquidity abandonment.\n\nTo eliminate economic competition between the two environments, liquidity that remains on the legacy Osmosis chain will continue to contribute directly to ATOM value accrual.\n\nProtocol revenue, which previously purchased and burned OSMO or accumulated assets in the Osmosis Community Pool, will instead be redirected to purchase ATOM on the open market to fund Phase 2 of the acquisition.\n\nAs a result, even if liquidity migration is gradual, trading activity across both the Cosmos Hub deployment and the legacy Osmosis chain accrues value to ATOM holders during the conversion period.\n\nFollowing the completion of the acquisition, this alignment persists, as all remaining Osmosis infrastructure and its associated revenue streams operate under ATOM governance.\n\n## Osmosis Growth\n\nThe Osmosis Grants Program (OGP) will be re-mandated under Cosmos Hub Governance and will take full stewardship in operating Osmosis. Responsibility for all maintenance, development, and growth will transfer accordingly.\n\nThe OGP currently holds approximately $1.2M in assets. Additionally, the Osmosis Community Pool holds approximately $3.8M in non-OSMO assets. These non-OSMO assets will be transferred to the OGP to fund post-merge operations. With this funding, the OGP will have the resources to fund maintenance, development, and growth of Osmosis on the Cosmos Hub for at least 6 years.\n\nAssets such as the Osmosis IP and the  [Osmosis Frontend](https://app.osmosis.zone/)  will transfer ownership to the OGP, which will continue to operate, develop, and maintain it in perpetuity under Hub mandate.\n\nAs they have done under their mandate for Osmosis, the OGP will produce regular updates on its holdings and activities. Because the OGP will be under the mandate of Cosmos Hub Governance, its assets can be clawed back to the Cosmos Hub Community Pool by governance vote.\n\n## Applications\n\nThird-party  [Osmosis contracts and applications](https://app.osmosis.zone/apps)  will not be automatically migrated. Individual development teams can choose to redeploy on the Hub.\n\nThe Cosmos Hub has permissionless CosmWasm deployment as of  [Proposal 1007](https://www.mintscan.io/cosmos/proposals/1007)  and the addition of Osmosis liquidity and modules to Cosmos will improve the environment in which developers can develop contracts. Permissionless CosmWasm on the same chain as a DEX means atomic DeFi apps will be possible on the Hub.\n\nThe CosmWasmPool module will be redeployed on the Cosmos Hub, enabling additional pool types to be deployed fully integrated into the Osmosis poolmanager once whitelisted by governance, and benefit from integrated routing in exchange for additional revenue collection by the Cosmos Hub.\n\n# Conclusion\n\nThis proposal consolidates mature, revenue-generating infrastructure that already operates within the Cosmos ecosystem into the Cosmos Hub’s economic domain.  \nOsmosis operates profitably with recurring fee generation and mature infrastructure developed over five years of production use. Maintaining parallel security domains duplicates expenditure and fragments liquidity. Integration aligns security, liquidity, and governance under a single framework while reducing structural inefficiencies.  \nFor the Cosmos Hub, this introduces a substantial recurring revenue stream and expands its functional surface area into capital formation and settlement. Native liquidity strengthens enterprise positioning, interoperability initiatives, and asset issuance capability.\n\nFor the wider Cosmos ecosystem, this represents modular evolution: sovereign experimentation followed by strategic consolidation when maturity and alignment justify it.\n\nRather than maintaining parallel centers of gravity, this proposal concentrates proven infrastructure where it can most effectively strengthen ATOM’s long-term economic relevance.\n\nStakeholders are asked to evaluate this disciplined consolidation with Osmosis to make the Cosmos Hub the unified center of security, liquidity, and capital coordination within the Cosmos ecosystem.\n\n---\nCosmos Forums: [https://forum.cosmos.network/t/proposal-draft-acquisition-and-merger-of-osmosis-into-the-cosmos-hub-aka-cosmosis/16717](https://forum.cosmos.network/t/proposal-draft-acquisition-and-merger-of-osmosis-into-the-cosmos-hub-aka-cosmosis/16717)\n\nOsmois Forums: [https://forum.osmosis.zone/t/integration-and-migration-of-osmosis-into-the-cosmos-hub-aka-cosmosis/3995](https://forum.osmosis.zone/t/integration-and-migration-of-osmosis-into-the-cosmos-hub-aka-cosmosis/3995)","proposer":"cosmos19w2t4ue7qpdh6022m3yxmxvv3w7jla7uev6se3","expedited":false,"failed_reason":"proposal did not get enough votes to pass"},{"id":"1028","messages":[{"@type":"/cosmos.upgrade.v1beta1.MsgSoftwareUpgrade","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","plan":{"name":"v27.2.0","time":"0001-01-01T00:00:00Z","height":"30675400","info":"{\"binaries\": {\"darwin/amd64\": \"https://github.com/cosmos/gaia/releases/download/v27.2.0/gaiad-v27.2.0-darwin-amd64?checksum=sha256:e660657081cd74ddc898bd855c06bb079dabe188c48340b6876528e1ecad0601\", \"darwin/arm64\": \"https://github.com/cosmos/gaia/releases/download/v27.2.0/gaiad-v27.2.0-darwin-arm64?checksum=sha256:5f06810034086fa6c4a5600f8db686d53ef80e57ca39cd298d2731fc91144c08\", \"linux/amd64\": \"https://github.com/cosmos/gaia/releases/download/v27.2.0/gaiad-v27.2.0-linux-amd64?checksum=sha256:8c086f59ec924e1bbd308624ac59d0de7b5a63454d628442249113b05ec69f3d\", \"linux/arm64\": \"https://github.com/cosmos/gaia/releases/download/v27.2.0/gaiad-v27.2.0-linux-arm64?checksum=sha256:4e5f4e96e61cd51a17e82422d569e38acac85e7f95a2e31e58b990f4d488ce3f\"}}","upgraded_client_state":null}}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"148479097112095","abstain_count":"3407022200","no_count":"24018136185","no_with_veto_count":"8859826390"},"submit_time":"2026-04-07T16:50:49.712814865Z","deposit_end_time":"2026-04-21T16:50:49.712814865Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2026-04-07T16:54:32.133800225Z","voting_end_time":"2026-04-14T16:54:32.133800225Z","metadata":"ipfs://CID","title":"Gaia v27.2.0 Upgrade","summary":"# Summary\r\n\r\n- The `v27.2.0` upgrade bumps the following versions:\r\n    - wasmd v0.60.5 → v0.60.6\r\n    - ledger-cosmos-go v0.16.0 → v1.0.0\r\n- This proposal has a voting period of **SEVEN DAYS**.\r\n- If the proposal passes, validators will be required to update the Cosmos Hub binary at the specified upgrade height.\r\n\r\n# Release Details\r\n\r\n- The release can be found [here](https://github.com/cosmos/gaia/releases/tag/v27.2.0).\r\n- The changelog can be found [here](https://github.com/cosmos/gaia/blob/v27.2.0/CHANGELOG.md).\r\n\r\n**This upgrade is state-breaking and mandatory once the on-chain vote passes and the upgrade height is reached.**\r\n\r\n# Governance votes\r\n\r\nThe following items summarize the voting options and what it means for this proposal:\r\n\r\nYES - You agree that the Cosmos Hub should be updated with this release.\r\n\r\nNO - You disagree that the Cosmos Hub should be updated with this release.\r\n\r\nNO 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.\r\n\r\nABSTAIN - You wish to contribute to the quorum but you formally decline to vote either for or against the proposal.","proposer":"cosmos1cc5mtuje84sx5dsqw4gtr4w8lthpzw02rjjnew","expedited":false,"failed_reason":""},{"id":"1027","messages":[{"@type":"/ibc.core.client.v1.MsgRecoverClient","subject_client_id":"07-tendermint-620","substitute_client_id":"07-tendermint-1470","signer":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn"}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"128110444245577","abstain_count":"1981834601773","no_count":"6876187915","no_with_veto_count":"4571061770"},"submit_time":"2026-03-24T16:16:04.656607405Z","deposit_end_time":"2026-04-07T16:16:04.656607405Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2026-03-24T16:19:54.339489802Z","voting_end_time":"2026-03-31T16:19:54.339489802Z","metadata":"","title":"Recover expired IBC Client for EVMOS Network","summary":"This proposal seeks to recover IBC Client `07-tendermint-620` connecting CosmosHub to EVMOS Network. The recovery process will replace the state of expired client with the state of newly created substitute client `07-tendermint-1470`.\n\nDue to a recent vulnerability discovered in Etheremint, EVMOS network was down for several days, causing several IBC clients to expire. Evmos validators need to reactivate the connection so that users can recover their ATOM tokens locked in the IBC channel.\n\nDiscussion: [https://forum.cosmos.network/t/evmos-ibc-reactivation/16782](https://forum.cosmos.network/t/evmos-ibc-reactivation/16782)","proposer":"cosmos1ymgpwtw5n882argshnnellwlmvgf4tnqquyakl","expedited":false,"failed_reason":""},{"id":"1026","messages":[{"@type":"/cosmos.upgrade.v1beta1.MsgSoftwareUpgrade","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","plan":{"name":"v27.1.0","time":"0001-01-01T00:00:00Z","height":"30466800","info":"{\"binaries\": {\"darwin/amd64\": \"https://github.com/cosmos/gaia/releases/download/v27.1.0/gaiad-v27.1.0-darwin-amd64?checksum=sha256:3e004ea397609cdcc47eef560d21b1d7f1b5ce8a84c5ccb527e45680c8cf0d9d\", \"darwin/arm64\": \"https://github.com/cosmos/gaia/releases/download/v27.1.0/gaiad-v27.1.0-darwin-arm64?checksum=sha256:cfcba3b276988f1b1ac88b48581bc9881c099786edf9b35a9d8514af86860456\", \"linux/amd64\": \"https://github.com/cosmos/gaia/releases/download/v27.1.0/gaiad-v27.1.0-linux-amd64?checksum=sha256:958c5a99738592891de886a2fbd86eace4568a1804e89359a32889c01afc177f\", \"linux/arm64\": \"https://github.com/cosmos/gaia/releases/download/v27.1.0/gaiad-v27.1.0-linux-arm64?checksum=sha256:107a582619496d957a091fab6b2b96fba2879f1700403c0638b043d7d356f9ad\"}}","upgraded_client_state":null}}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"143479071226866","abstain_count":"100047478772","no_count":"17017600717","no_with_veto_count":"7111546701"},"submit_time":"2026-03-24T14:09:31.849071789Z","deposit_end_time":"2026-04-07T14:09:31.849071789Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2026-03-24T14:28:15.379921462Z","voting_end_time":"2026-03-31T14:28:15.379921462Z","metadata":"ipfs://CID","title":"Gaia v27.1.0 Upgrade","summary":"# Summary\r\n\r\n- The `v27.1.0` upgrade bumps the following versions:\r\n    - wasmd v0.60.2 → wasmd v0.60.5\r\n    - wasmvm v2.2.4 → wasmvm v2.3.2\r\n    - golang v1.24 → v1.25\r\n- This proposal has a voting period of **SEVEN DAYS**.\r\n- If the proposal passes, validators will be required to update the Cosmos Hub binary at the specified upgrade height.\r\n\r\n# Release Details\r\n\r\n- The release can be found [here](https://github.com/cosmos/gaia/releases/tag/v27.1.0).\r\n- The changelog can be found [here](https://github.com/cosmos/gaia/blob/v27.1.0/CHANGELOG.md).\r\n\r\n**This upgrade is state-breaking and mandatory once the on-chain vote passes and the upgrade height is reached.**\r\n\r\n# Governance votes\r\n\r\nThe following items summarize the voting options and what it means for this proposal:\r\n\r\nYES - You agree that the Cosmos Hub should be updated with this release.\r\n\r\nNO - You disagree that the Cosmos Hub should be updated with this release.\r\n\r\nNO 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.\r\n\r\nABSTAIN - You wish to contribute to the quorum but you formally decline to vote either for or against the proposal.","proposer":"cosmos1cc5mtuje84sx5dsqw4gtr4w8lthpzw02rjjnew","expedited":false,"failed_reason":""},{"id":"1025","messages":[{"@type":"/cosmos.upgrade.v1beta1.MsgSoftwareUpgrade","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","plan":{"name":"v27.0.0","time":"0001-01-01T00:00:00Z","height":"30151300","info":"{\"binaries\": {\"darwin/amd64\": \"https://github.com/cosmos/gaia/releases/download/v27.0.0/gaiad-v27.0.0-darwin-amd64?checksum=sha256:b8aacd002fca87c2e594b66db7e3a8b49d8cd9358e12b03213ed6856273e6318\", \"darwin/arm64\": \"https://github.com/cosmos/gaia/releases/download/v27.0.0/gaiad-v27.0.0-darwin-arm64?checksum=sha256:b2a134ae155cbb74757911bb61ddb9a60124763d3bea24bc486fe4946327e201\", \"linux/amd64\": \"https://github.com/cosmos/gaia/releases/download/v27.0.0/gaiad-v27.0.0-linux-amd64?checksum=sha256:3d391f1e1495d9ef0ed64e204a37a24982c50216baff43052ba3db60960af1e9\", \"linux/arm64\": \"https://github.com/cosmos/gaia/releases/download/v27.0.0/gaiad-v27.0.0-linux-arm64?checksum=sha256:0355177a1b237be339a8be5d6bab7b302ebd7fdaf1bc1468fd1330af466b4e3f\"}}","upgraded_client_state":null}}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"142692270274675","abstain_count":"14568169901","no_count":"233047227360","no_with_veto_count":"3050190074"},"submit_time":"2026-03-03T15:19:04.204423815Z","deposit_end_time":"2026-03-17T15:19:04.204423815Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2026-03-03T15:32:48.804087108Z","voting_end_time":"2026-03-10T15:32:48.804087108Z","metadata":"ipfs://CID","title":"Gaia v27.0.0 Upgrade","summary":"# Summary\r\n\r\n- The `v27.0.0` upgrade disables the creation of new consumer chains. This is the first stage of the upcoming removal of Interchain Security from the Hub, as per Cosmos Labs’ announcement [here](https://forum.cosmos.network/t/remove-ics-from-the-cosmos-hub-software-upgrades-to-follow/16682).\r\n- This proposal has a voting period of **SEVEN DAYS**.\r\n- If the proposal passes, validators will be required to update the Cosmos Hub binary at the specified upgrade height.\r\n\r\n# Release Details\r\n\r\n- The release can be found [here](https://github.com/cosmos/gaia/releases/tag/v27.0.0).\r\n- The changelog can be found [here](https://github.com/cosmos/gaia/blob/v27.0.0/CHANGELOG.md).\r\n\r\n## Features\r\n\r\n- Add a provider module ante handler to disable the creation of new consumer chains.\r\n- Add stake validation to vote messages from interchain accounts.\r\n- Add a gas surcharge and recipient limit to multi-send messages.\r\n\r\n**This upgrade is state-breaking and mandatory once the on-chain vote passes and the upgrade height is reached.**\r\n\r\n# Governance votes\r\n\r\nThe following items summarize the voting options and what it means for this proposal:\r\n\r\nYES - You agree that the Cosmos Hub should be updated with this release.\r\n\r\nNO - You disagree that the Cosmos Hub should be updated with this release.\r\n\r\nNO 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.\r\n\r\nABSTAIN - You wish to contribute to the quorum but you formally decline to vote either for or against the proposal.","proposer":"cosmos1cc5mtuje84sx5dsqw4gtr4w8lthpzw02rjjnew","expedited":false,"failed_reason":""},{"id":"1024","messages":[{"@type":"/cosmos.upgrade.v1beta1.MsgSoftwareUpgrade","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","plan":{"name":"v26.0.0","time":"0001-01-01T00:00:00Z","height":"29837600","info":"{\"binaries\": {\"darwin/amd64\": \"https://github.com/cosmos/gaia/releases/download/v26.0.0/gaiad-v26.0.0-darwin-amd64?checksum=sha256:c549acefcddc6dcf684fc47de651d0a3132fbf9d6850bed615af2f44f86f2ad4\", \"darwin/arm64\": \"https://github.com/cosmos/gaia/releases/download/v26.0.0/gaiad-v26.0.0-darwin-arm64?checksum=sha256:86735180156e35be78ec0fff5d0a1c657bb0d3ddc399d2aeb987b47c841ed0c5\", \"linux/amd64\": \"https://github.com/cosmos/gaia/releases/download/v26.0.0/gaiad-v26.0.0-linux-amd64?checksum=sha256:f86fd5a54623911f59a50706e02ddd09e5c130f6e2360b233b4329dad45942b0\", \"linux/arm64\": \"https://github.com/cosmos/gaia/releases/download/v26.0.0/gaiad-v26.0.0-linux-arm64?checksum=sha256:9c39ff1c31bfa63b5047a33ba43eb56b3c66046319de459a04fdefd9baba6db1\"}}","upgraded_client_state":null}}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"124209873811020","abstain_count":"6151193232047","no_count":"30545035689","no_with_veto_count":"2305371952"},"submit_time":"2026-02-09T17:03:28.908575797Z","deposit_end_time":"2026-02-23T17:03:28.908575797Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2026-02-09T17:13:27.127272660Z","voting_end_time":"2026-02-16T17:13:27.127272660Z","metadata":"ipfs://CID","title":"Gaia v26.0.0 Upgrade","summary":"# Summary\r\n\r\n- The `v26.0.0` upgrade introduces the `tokenfactory` module to the Cosmos Hub.\r\n- This proposal has a voting period of **SEVEN DAYS**.\r\n- If the proposal passes, validators will be required to update the Cosmos Hub binary at the specified upgrade height.\r\n\r\n# Release Details\r\n\r\n- The release can be found [here](https://github.com/cosmos/gaia/releases/tag/v26.0.0).\r\n- The changelog can be found [here](https://github.com/cosmos/gaia/blob/v26.0.0/CHANGELOG.md).\r\n\r\n## Features\r\n\r\n- This upgrade will introduce the `cosmos/tokenfactory` module to the Hub, as per signalling proposal [1010](https://www.mintscan.io/cosmos/proposals/1010).\r\n\r\n### Tokenfactory Parameters\r\n\r\nThe following can be adjusted through governance proposals:\r\n\r\n- The denom creation fee is set to `10 ATOM`\r\n- The denom creation gas consumption is set to `2_000_000`\r\n\r\n## Bug fixes\r\n\r\n- Add missing cosmos_proto.scalar cosmos.Dec annotation to x/liquid LiquidValidator.liquid_shares field ([#3936](https://github.com/cosmos/gaia/pull/3936))\r\n- Add stake validation to vote messages from wasm contracts ([#3949](https://github.com/cosmos/gaia/pull/3949))\r\n\r\n## Dependencies\r\n\r\n- cosmos/tokenfactory → v0.53.5\r\n\r\n**This upgrade is state-breaking and mandatory once the on-chain vote passes and the upgrade height is reached.**\r\n\r\n# Governance votes\r\n\r\nThe following items summarize the voting options and what it means for this proposal:\r\n\r\nYES - You agree that the Cosmos Hub should be updated with this release.\r\n\r\nNO - You disagree that the Cosmos Hub should be updated with this release.\r\n\r\nNO 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.\r\n\r\nABSTAIN - You wish to contribute to the quorum but you formally decline to vote either for or against the proposal.","proposer":"cosmos1cc5mtuje84sx5dsqw4gtr4w8lthpzw02rjjnew","expedited":false,"failed_reason":""},{"id":"1023","messages":[{"@type":"/ibc.core.client.v1.MsgRecoverClient","subject_client_id":"07-tendermint-764","substitute_client_id":"07-tendermint-1465","signer":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn"}],"status":"PROPOSAL_STATUS_REJECTED","final_tally_result":{"yes_count":"101656967970392","abstain_count":"8227152865499","no_count":"3463109101","no_with_veto_count":"137346879"},"submit_time":"2026-02-01T13:54:46.472401698Z","deposit_end_time":"2026-02-15T13:54:46.472401698Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2026-02-03T05:43:27.577241532Z","voting_end_time":"2026-02-10T05:43:27.577241532Z","metadata":"","title":"Recover IBC Client: Cosmos Hub ↔ Bostrom (07-tendermint-764)","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.\n\nClient parameters: trusting_period=518400s, max_clock_drift=60s, trust_level=1/3, unbonding_period=691200s.\n\nThe 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.\n\nAffected denoms: uatom on Bostrom (via channel-8), boot on Cosmos Hub (via channel-341).\n\nBostrom RPC: https://rpc.bostrom.cybernode.ai\nBostrom LCD: https://lcd.bostrom.cybernode.ai\nGitHub: https://github.com/cybercongress","proposer":"cosmos1yx7gfnahjz55hm80ux3395ysyxngu0mc7lzpwd","expedited":false,"failed_reason":"proposal did not get enough votes to pass"},{"id":"1022","messages":[{"@type":"/cosmos.distribution.v1beta1.MsgCommunityPoolSpend","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","recipient":"cosmos1hj9zuecf0xcjhx8ttcrwd9pmee25xe2plglgcpfk2kjjveet3zyq9nellq","amount":[{"denom":"uatom","amount":"7000000000000"}]}],"status":"PROPOSAL_STATUS_REJECTED","final_tally_result":{"yes_count":"12437073256238","abstain_count":"35885525740861","no_count":"68087676971389","no_with_veto_count":"539453627121"},"submit_time":"2026-01-12T12:11:48.974847254Z","deposit_end_time":"2026-01-26T12:11:48.974847254Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2026-01-12T12:11:48.974847254Z","voting_end_time":"2026-01-19T12:11:48.974847254Z","metadata":"Deploy community pool ATOM into Hydro’s Inflow vault","title":"Deploy community pool ATOM into Hydro’s Inflow vault","summary":"We propose depositing 7M ATOM from the Cosmos Hub community pool into Hydro’s Inflow ATOM vault, where it will be deployed into low-risk DeFi strategies to earn yield.\n\nA portion of the yield will fund development of a zero-fee, Hub-native ATOM LST focused on institutional users, its integration into Hydro’s ATOM Inflow vault and the ongoing expansion of the vault’s strategies, as well as the migration of Hydro’s existing contracts to the Hub. The excess yield will initially be directed toward ATOM burns, with the option to reallocate later if a higher‑impact mechanism is proposed by the tokenomics research firm hired by Cosmos Labs.\n\nThe proposal puts a large portion of the idle community pool funds to work. The ATOM “principal” will not be sold and the initial deposit can be reduced through total or partial clawbacks if better uses for the capital are identified. Hub governance retains the ability to independently initiate partial or total clawbacks, at any time, without requiring any cooperation from the Hydro committee or any other individual signers. Fund custody will be transferred to the ATOM-Aligned Apps DAO once it’s launched.\n\nFind the full proposal details on the forum here: https://forum.cosmos.network/t/deploy-community-pool-atom-into-hydro-s-inflow-vault/16549","proposer":"cosmos1k00qymyetxt36uga8kp88nxyj3hvxfn2v0hgnn","expedited":false,"failed_reason":"proposal did not get enough votes to pass"},{"id":"1021","messages":[{"@type":"/cosmos.upgrade.v1beta1.MsgSoftwareUpgrade","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","plan":{"name":"v25.3.0","time":"0001-01-01T00:00:00Z","height":"29288700","info":"{\"binaries\": {\"darwin/amd64\": \"https://github.com/cosmos/gaia/releases/download/v25.3.0/gaiad-v25.3.0-darwin-amd64?checksum=sha256:8a5de7d4bc143948e2e629491c0f59dcb3fd540fbde750252b986194835c0495\", \"darwin/arm64\": \"https://github.com/cosmos/gaia/releases/download/v25.3.0/gaiad-v25.3.0-darwin-arm64?checksum=sha256:cb268cd2cda0d1cab15e3cbc4c3fefc6706ded809f8f16e414475e1806e71760\", \"linux/amd64\": \"https://github.com/cosmos/gaia/releases/download/v25.3.0/gaiad-v25.3.0-linux-amd64?checksum=sha256:396c2f08c6d60cc14c101383a32f3202379e44d4fc4a65505dbb3897e0f1e1ed\", \"linux/arm64\": \"https://github.com/cosmos/gaia/releases/download/v25.3.0/gaiad-v25.3.0-linux-arm64?checksum=sha256:66b904efa14442cc6a8bfbc1284d968b09b51cc914fe2f2c604907c9228334f3\"}}","upgraded_client_state":null}}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"132286133419111","abstain_count":"222402037805","no_count":"15826876569","no_with_veto_count":"2589270456"},"submit_time":"2026-01-06T17:10:55.020355684Z","deposit_end_time":"2026-01-20T17:10:55.020355684Z","total_deposit":[{"denom":"uatom","amount":"501000000"}],"voting_start_time":"2026-01-06T17:23:19.375514836Z","voting_end_time":"2026-01-09T17:23:19.375514836Z","metadata":"ipfs://CID","title":"Gaia v25.3.0 Upgrade","summary":"# Summary\r\n\r\n- The `v25.3.0` upgrade bumps several dependencies:\r\n    - CometBFT v0.38.19 → v0.38.20\r\n    - IBC v10.3.0 → v10.5.0\r\n    - Cosmos SDK v0.53.3 → v0.53.4\r\n- This proposal has the expedited flag enabled and will have a voting period of just **THREE DAYS**.\r\n- If the proposal passes, validators will be required to update the Cosmos Hub binary at the specified upgrade height.\r\n\r\n# Release Details\r\n\r\n- The release can be found [here](https://github.com/cosmos/gaia/releases/tag/v25.3.0).\r\n- The changelog can be found [here](https://github.com/cosmos/gaia/blob/release/v25.x/CHANGELOG.md).\r\n\r\nThis release adds no major features.\r\n\r\n**This upgrade is state-breaking and mandatory once the on-chain vote passes and the upgrade height is reached.**\r\n\r\n# Governance votes\r\n\r\nThe following items summarize the voting options and what it means for this proposal:\r\n\r\nYES - You agree that the Cosmos Hub should be updated with this release.\r\n\r\nNO - You disagree that the Cosmos Hub should be updated with this release.\r\n\r\nNO 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.\r\n\r\nABSTAIN - You wish to contribute to the quorum but you formally decline to vote either for or against the proposal.","proposer":"cosmos1cc5mtuje84sx5dsqw4gtr4w8lthpzw02rjjnew","expedited":true,"failed_reason":""},{"id":"1020","messages":[{"@type":"/ibc.core.client.v1.MsgRecoverClient","subject_client_id":"07-tendermint-1153","substitute_client_id":"07-tendermint-1453","signer":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn"}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"125256015667894","abstain_count":"9283605701413","no_count":"225308551638","no_with_veto_count":"2336401497"},"submit_time":"2026-01-05T16:58:11.993622023Z","deposit_end_time":"2026-01-19T16:58:11.993622023Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2026-01-05T16:58:11.993622023Z","voting_end_time":"2026-01-12T16:58:11.993622023Z","metadata":"gaia v25.2.0","title":"Recover expired IBC Client for Haqq Network","summary":"This proposal seeks to recover IBC Client `07-tendermint-1153` connecting CosmosHub to Haqq Network. The recovery process will replace the state of expired client with the state of newly created substitute client `07-tendermint-1453`. This action preserves existing IBC paths, channel identifiers, and token denominations, preventing fragmentation of IBC assets.\n Upon approval and execution, existing IBC channels will resume normal operation using recovered client, ensuring continuity of IBC transfers and minimizing disruption for users and applications.","proposer":"cosmos1xzemvlx6ssulrk9kya8uje5mw39dy33tevhdyd","expedited":false,"failed_reason":""},{"id":"1019","messages":[{"@type":"/ibc.core.client.v1.MsgRecoverClient","subject_client_id":"07-tendermint-1153","substitute_client_id":"07-tendermint-1451","signer":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn"}],"status":"PROPOSAL_STATUS_REJECTED","final_tally_result":{"yes_count":"35271846160556","abstain_count":"2168989993592","no_count":"1144279920","no_with_veto_count":"118424648"},"submit_time":"2025-12-19T22:35:15.282019209Z","deposit_end_time":"2026-01-02T22:35:15.282019209Z","total_deposit":[{"denom":"uatom","amount":"501000000"}],"voting_start_time":"2025-12-19T22:35:15.282019209Z","voting_end_time":"2025-12-26T22:35:15.282019209Z","metadata":"gaia v25.2.0","title":"Recover expired IBC Client for Haqq Network","summary":"This proposal seeks to recover IBC Client `07-tendermint-1153` connecting CosmosHub to Haqq Network. The recovery process will replace the state of expired client with the state of newly created substitute client `07-tendermint-1451`. This action preserves existing IBC paths, channel identifiers, and token denominations, preventing fragmentation of IBC assets.\n Upon approval and execution, existing IBC channels will resume normal operation using recovered client, ensuring continuity of IBC transfers and minimizing disruption for users and applications.","proposer":"cosmos1xzemvlx6ssulrk9kya8uje5mw39dy33tevhdyd","expedited":false,"failed_reason":"proposal did not get enough votes to pass"},{"id":"1018","messages":[{"@type":"/cosmos.gov.v1.MsgUpdateParams","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","params":{"min_deposit":[{"denom":"uatom","amount":"500000000"}],"max_deposit_period":"1209600s","voting_period":"1209600s","quorum":"0.400000000000000000","threshold":"0.500000000000000000","veto_threshold":"0.334000000000000000","min_initial_deposit_ratio":"0.100000000000000000","proposal_cancel_ratio":"0.500000000000000000","proposal_cancel_dest":"","expedited_voting_period":"604800s","expedited_threshold":"0.667000000000000000","expedited_min_deposit":[{"denom":"uatom","amount":"501000000"}],"burn_vote_quorum":false,"burn_proposal_deposit_prevote":false,"burn_vote_veto":true,"min_deposit_ratio":"0.010000000000000000"}}],"status":"PROPOSAL_STATUS_REJECTED","final_tally_result":{"yes_count":"13504044230122","abstain_count":"34592730128595","no_count":"71368192171399","no_with_veto_count":"71350407591"},"submit_time":"2025-12-09T16:16:16.936204739Z","deposit_end_time":"2025-12-23T16:16:16.936204739Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2025-12-09T16:46:50.360412437Z","voting_end_time":"2025-12-16T16:46:50.360412437Z","metadata":"ipfs://CID","title":"Increase voting period to 14 days and expedited voting period to 7 days","summary":"## Context\r\n\r\n[Proposal 998](https://www.mintscan.io/cosmos/proposals/998) passed in May 2025, reducing the Hub’s voting periods from 14 days standard / 7 days expedited to 7 days standard / 3 days expedited.\r\n\r\nAs part of this proposal, Hypha agreed to monitor the Hub’s governance progress and put up a proposal to revert this change (restoring the 14 day standard voting and 7 day expedited voting) if either of the following conditions were met:\r\n\r\n1. A different solution is deployed which allows for a 3 day emergency upgrades and 7 day planned upgrades, and 14 day non-upgrade governance OR\r\n2. More than 10% of “real” non-software proposals fail to meet quorum (e.g., not spam, not proposals where validators mindfully chose not to vote). \r\n\r\n## Conditions for reverting\r\n\r\n1. No alternative solution for 3 day emergency upgrades, 7 day planned upgrades, and 14 day non-upgrade governance has been developed.\r\n2. The following proposals have failed to meet quorum despite being legitimate proposals from known entities (i.e., not spam, not proposals that ignored governance norms, not proposals where Hypha, in our best judgment, feels validators chose not to reject via failure to meet quorum)\r\n\r\n| **Proposal** | **Notes** |\r\n| --- | --- |\r\n| [1005](https://www.mintscan.io/cosmos/proposals/1005) Bridging Worlds: Empowering Cosmos with an Ethereum NFT Bridge |  |\r\n| [1006](https://www.mintscan.io/cosmos/proposals/1006) Connecting Businesses: Empowering Stack Adoption with a Data Bridge (using NFTs)  | Same proposal as 1005, in spirit, with updates based on conversation with Cosmos Labs |\r\n| [1011](https://www.mintscan.io/cosmos/proposals/1011) Recover Expired IBC Client to XPLA Chain | Later re-proposed in [1015](https://www.mintscan.io/cosmos/proposals/1015), which reached quorum and passed with some validator outreach from Hypha. |\r\n\r\n## Proposal\r\n\r\n- Increase the Hub’s standard `voting_period` to 14 days for all proposal types.\r\n- Increase the Hub’s `expedited_voting_period` to 7 days for all proposal types.\r\n\r\n### Governance votes\r\n\r\nThe following items summarize the voting options and what it means for this proposal:\r\n\r\n- YES - You support increasing the Hub’s voting period to 14 days and expedited voting period to 7 days.\r\n- NO - You do not support increasing the Hub’s voting period to 14 days and expedited voting period to 7 days.\r\n- NO WITH VETO - A `NoWithVeto` vote indicates a proposal either (1)\r\nis deemed to be spam, i.e., irrelevant to Cosmos Hub, (2)\r\ndisproportionately infringes on minority interests, or (3) violates or\r\nencourages violation of the rules of engagement as currently set out by\r\nCosmos Hub governance. If the number of `NoWithVeto` votes is greater\r\nthan a third of total votes, the proposal is rejected and the deposits\r\nare burned.\r\n- ABSTAIN - You wish to contribute to the quorum but you formally decline to vote either for or against the proposal.","proposer":"cosmos1cc5mtuje84sx5dsqw4gtr4w8lthpzw02rjjnew","expedited":false,"failed_reason":"proposal did not get enough votes to pass"},{"id":"1017","messages":[{"@type":"/cosmos.distribution.v1beta1.MsgCommunityPoolSpend","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","recipient":"cosmos1vdqfavw0cu0fpvlcl52ku3qztt38szktlpfsuz","amount":[{"denom":"uatom","amount":"699626000000"}]}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"41518287651060","abstain_count":"61292977221987","no_count":"33132401562192","no_with_veto_count":"279527666229"},"submit_time":"2025-11-19T18:33:25.177515594Z","deposit_end_time":"2025-12-03T18:33:25.177515594Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2025-11-19T18:43:45.416444016Z","voting_end_time":"2025-11-26T18:43:45.416444016Z","metadata":"Migrate Stargaze, its Applications, and Collections to the Cosmos Hub","title":"Migrate Stargaze, its Applications, and Collections to the Cosmos Hub","summary":"# Full discussion:\n\n[https://forum.cosmos.network/t/proposal-migrate-stargaze-its-applications-and-collections-to-the-cosmos-hub/16355](https://forum.cosmos.network/t/proposal-migrate-stargaze-its-applications-and-collections-to-the-cosmos-hub/16355)\n\n---\n\n# Summary\n\nThis proposal requests **$1.375M** in milestone and quarterly disbursements, along with **$125k [ATOM]** in bonus incentives, from the Cosmos Hub Community Pool to support the migration to and continued development of Stargaze, its applications, and its NFT collections on the Cosmos Hub.\n\nAs part of this transition, Stargaze will actively market its products alongside the Cosmos Hub through coordinated campaigns, creator/collector outreach, cross-ecosystem storytelling, and consistent visibility across social platforms and partnerships. Stargaze will also expand its business development efforts by onboarding new creators, developers, collaborating with emerging projects on the Hub, and driving integrations that showcase the Hub’s capabilities.\n\nThe goal is to ensure ongoing development, strengthen creator support, accelerate ecosystem adoption, and deepen alignment with the Hub’s growing network of applications and new B2B clients.\n\n---\n\n# Introduction\n\nStargaze has been the center of art, culture, and community in the Cosmos ecosystem since its founding in 2021. The Cosmos Hub lacks any marketplace or application for usage. With the Cosmos Hub now supporting permissionless CosmWasm and inviting applications to build on chain, a union between the Hub and Stargaze, one of the most mature and well-developed apps and teams in the ecosystem, is a natural fit.\n\n---\n\n# Scope of Migration\n\n**Applications:**\n\n* Marketplace\n* Launchpad\n* Name Service\n* Stargaze Studio\n\n**Collections:**\n\n* Migration of all NFTs to the Cosmos Hub (**$5M+ market cap**)\n\n**Community:**\n\n* All future collection launches to occur on the Cosmos Hub.\n\nApplications will start migrating within **3 months** of the approval of this proposal.\n\n---\n\n# Benefit to Cosmos Hub\n\nThe Cosmos Hub gains an established, user-facing application suite and team that drives real transaction flow and engagement. Migrating Stargaze applications would immediately:\n\n* Boost transaction volume on the hub by a minimum of **16%**.\n* Deliver flagship consumer apps that demonstrate the Hub’s capabilities.\n* Provide instant NFT liquidity and trading with **3800+ collections migrating**.\n* Expand a creator, marketing, and B2B network for Cosmos-native projects.\n* Unlock new ATOM utility directly on the Cosmos Hub.\n* Provide continued growth and development (see below).\n\n---\n\n# Beyond Migration: Growth and Development\n\nThe Stargaze team has reliably shipped products throughout a protracted Cosmos ecosystem downturn since 2021. Our primary objective in this agreement is to expand product development and ecosystem growth. At this stage, we view consolidation as the best option within the ecosystem. We intend to lead by example when it comes to dedicated product development on the Cosmos Hub with a retail focus that will be complementary to enterprise-focused activities from Cosmos Labs.\n\nThe migration of the core Stargaze suite is the first milestone in the long-term development of new products on the Cosmos Hub from an experienced and dedicated team. Focus areas for growth and development in **2026 and 2027** include:\n\n* New features and UX improvements on Stargaze Marketplace, Stargaze Launchpad, and Stargaze Creator Studio following migration.\n* Progressive rollout of new retail-facing applications, including creator tools, simplified trading interfaces, and automated launch mechanisms to expand active participation on the Hub.\n* Expanding web3 native marketshare for the Cosmos Hub via onboarding and new products that integrate ATOM utility in multichain deployments.\n* New NFT primitives and minting frameworks, including dynamic NFTs, vault NFTs, soulbound credentials, on-chain generative engines, and a novel fairmint structure.\n* Outreach to non-web3 brands and partners to launch NFT collections and related products on the Cosmos Hub with whiteglove launch services.\n* Expansion of Cosmos-native NFT verticals, such as gaming integrations and RWA tokenization.\n* Support for third-party teams deploying on the Hub and NFT collection integrations.\n\nWith this migration, the Stargaze team commits to continuous product development on the Cosmos Hub and to driving meaningful growth for its consumer ecosystem.\n\n---\n\n# Marketing and Cultural Value\n\nStargaze already serves as Cosmos’ cultural front door, where users mint, collect, and explore. Creators and projects utilize NFT launches not just to build brands that transcend ecosystems as well as fund app development and experimentation. This redeployment makes that role native to the Hub.\n\nThis redeployment ensures that Cosmos’ flagship collections such as **Bad Kids, Sloths, Mad Scientists, Babu, and Expedition** remain Hub-native while enabling new cross-chain collaborations, event campaigns, and creator programs that strengthen the Hub’s visibility and network effect.\n\nInteroperability and sovereignty are core strengths of Cosmos, and some multi-chain activity is both natural and healthy as it brings new users into the Hub’s orbit. For example, several protocol-aligned collections have the majority of their trading on Stargaze but can be moved to other chains for quests or dApp activity. On the Hub, we will continue to support other chains and projects that engage in IBC experiments so long as there is a clear benefit at some stage, such as minting or trading on the Hub.\n\nStargaze will anchor core activity and development on the Hub. It may also selectively deploy apps on other networks where there is a clear benefit to the core Hub deployment. A multichain presence strengthens Stargaze and Cosmos by reaching new audiences while still bringing value back to the Hub through bridged-in users, IBC-driven activity, as well as cultural and economic alignment.\n\nIn all cases, our objective is to build economic opportunities and grow the userbase on the Cosmos Hub. We are dedicated to contributing to a rewarding, vibrant and fun ecosystem.\n\n---\n\n# Funding Plan\n\n| Milestone | Description                                                                     | Amount (USDC)                                            |\n| --------- | ------------------------------------------------------------------------------- | -------------------------------------------------------- |\n| **1**     | 1st disbursement – Setup and planning                                           | **100,000**                                              |\n| **2**     | 2nd disbursement – Launchpad and Studio migration                               | **100,000**                                              |\n| **3**     | 3rd disbursement – Marketplace migration                                        | **100,000**                                              |\n| **4**     | 4th disbursement – Name Service migration                                       | **75,000**                                               |\n| **5**     | 5th disbursement – NFT collection migration                                     | **100,000 (all collections)**                            |\n| **6**     | Strategic Migration Commitment and Development – Following first app deployment | **75,000 per month for one year, distributed quarterly** |\n\n**Total: 1,375,000**\n\n### Activity incentive bonus:\n\n**$125,000 in ATOM** will be set aside as activity incentives, defined as transaction fees generated to the hub that will be paid at the end of the year.\n\n---\n\n# Fund Management\n\nA multisig composed of Hub community representatives and Stargaze contributors will oversee milestones and disbursements. A **25% buffer** will account for price fluctuations and slippage. Any unused funds will be returned to the community pool.\n\nIf Migration Commitment payments are paused or not released as outlined, Stargaze retains the option to safeguard its community and commitments; obligations in this agreement are considered void. Likewise, if Stargaze does not meet its agreed obligations regarding application deployment, collection migration, or ongoing support, the Cosmos Hub may pause future payments to ensure responsible stewardship of community resources.\n\n### Multisig:\n\n`cosmos1vdqfavw0cu0fpvlcl52ku3qztt38szktlpfsuz`\n\n* **Ruwan [Stargaze]** – cosmos1gd4xlwv34t0chqtcftnc49x2pc7atlculm58v5\n* **Cortlandt [Bad Kids]** – cosmos1cr5zjgn2zz5sc7u9d0q76kjw9lx6mgrxr5hnh6\n* **Zerk [Mad Scientists]** – cosmos1pwha5a3hr55wmmur2d4fm0p8rf7q62wn2rvzw8\n* **Polkachu [Cosmos Hub Validator]** – cosmos1jfm85muxzrlv4an9yf0gu30yknv6zk7tyu7l9e\n* **Quasar Validator [Cosmos Hub Validator]** – cosmos1wye9d3usnfka7ww04lru9wghmgvz3gt9hn2k09\n\n---\n\n# Governance Votes\n\n**Yes** – You approve the allocation of **699626 ATOM** from the community pool towards the Stargaze migration and future product development on the Cosmos Hub.\n\n**No** – You do not approve the transfer.\n","proposer":"cosmos1fd68882pq8al866lg6z0x3wzce07ud92tqlutm","expedited":false,"failed_reason":""},{"id":"1016","messages":[{"@type":"/cosmos.upgrade.v1beta1.MsgSoftwareUpgrade","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","plan":{"name":"v25.2.0","time":"0001-01-01T00:00:00Z","height":"28356500","info":"{\"binaries\": {\"darwin/amd64\": \"https://github.com/cosmos/gaia/releases/download/v25.2.0/gaiad-v25.2.0-darwin-amd64?checksum=sha256:8ec14899b1cc1f8dd847e38467c00ff961da99bf825e5a1816fa309feec7c165\", \"darwin/arm64\": \"https://github.com/cosmos/gaia/releases/download/v25.2.0/gaiad-v25.2.0-darwin-arm64?checksum=sha256:9ebf6156b68f0ab0cc9b4159845b2ad3447c58da53acdc56497cff0eefc913b7\", \"linux/amd64\": \"https://github.com/cosmos/gaia/releases/download/v25.2.0/gaiad-v25.2.0-linux-amd64?checksum=sha256:e54ab309ca4c117d73a043adfc4e9155f35a480925ad8a94a625bd80e9398f76\", \"linux/arm64\": \"https://github.com/cosmos/gaia/releases/download/v25.2.0/gaiad-v25.2.0-linux-arm64?checksum=sha256:bfd0942c63270b4ab3ac07db1319718b68a12cca488316d40e68c160b650455a\"}}","upgraded_client_state":null}}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"136560124800700","abstain_count":"1569171876","no_count":"16607240388","no_with_veto_count":"2599809896"},"submit_time":"2025-11-06T17:56:29.902748856Z","deposit_end_time":"2025-11-20T17:56:29.902748856Z","total_deposit":[{"denom":"uatom","amount":"501000000"}],"voting_start_time":"2025-11-06T18:00:22.699439978Z","voting_end_time":"2025-11-09T18:00:22.699439978Z","metadata":"ipfs://CID","title":"Gaia v25.2.0 Upgrade","summary":"# Summary\r\n\r\n- The `v25.2.0` upgrade patches a medium-severity issue. This issue poses no loss of funds risk.\r\n- This proposal has the expedited flag enabled and will have a voting period of just **THREE DAYS**.\r\n- If the proposal passes, validators will be required to update the Cosmos Hub binary at the specified upgrade height.\r\n\r\n# Release Details\r\n\r\n- The release can be found [here](https://github.com/cosmos/gaia/releases/tag/v25.2.0).\r\n- The changelog can be found [here](https://github.com/cosmos/gaia/blob/v25.2.0/CHANGELOG.md).\r\n\r\nThis release adds no major features.\r\n\r\n**This upgrade is state-breaking and mandatory once the on-chain vote passes and the upgrade height is reached.**\r\n\r\n### Governance votes\r\n\r\nThe following items summarize the voting options and what it means for this proposal:\r\n\r\nYES - You agree that the Cosmos Hub should be updated with this release.\r\n\r\nNO - You disagree that the Cosmos Hub should be updated with this release.\r\n\r\nNO WITH VETO - A ‘NoWithVeto’ vote indicates a proposal either (1) is\r\n deemed to be spam, i.e., irrelevant to Cosmos Hub, (2) \r\ndisproportionately infringes on minority interests, or (3) violates or \r\nencourages violation of the rules of engagement as currently set out by \r\nCosmos Hub governance. If the number of ‘NoWithVeto’ votes is greater \r\nthan a third of total votes, the proposal is rejected and the deposits \r\nare burned.\r\n\r\nABSTAIN - You wish to contribute to the quorum but you formally decline to vote either for or against the proposal.","proposer":"cosmos1cc5mtuje84sx5dsqw4gtr4w8lthpzw02rjjnew","expedited":true,"failed_reason":""},{"id":"1015","messages":[{"@type":"/ibc.core.client.v1.MsgRecoverClient","subject_client_id":"07-tendermint-1113","substitute_client_id":"07-tendermint-1438","signer":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn"}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"102526041893849","abstain_count":"13198555941273","no_count":"102964824314","no_with_veto_count":"18915911826"},"submit_time":"2025-10-21T05:26:23.007770108Z","deposit_end_time":"2025-11-04T05:26:23.007770108Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2025-10-21T05:26:23.007770108Z","voting_end_time":"2025-10-28T05:26:23.007770108Z","metadata":"","title":"Recover Expired IBC Client to XPLA Chain","summary":"This governance proposal seeks to recover the expired IBC light client 07-tendermint-1113 connecting our chain to the XPLA Chain. The current expiration of this client has led to an interruption in IBC connectivity, hindering seamless token transfers and general interoperability between our ecosystems. If this proposal passes, the RecoverClient function will be executed to replace the state of the expired client 07-tendermint-1113 with the state of a newly created, valid client, 07-tendermint-1438. This is a critical technical maneuver that restores client validity and immediately re-enables IBC communication with the XPLA Chain while preserving the existing IBC channels and connections.","proposer":"cosmos1rjujxmsdk3n7hj07q54huh4esf4v0ts87dk43g","expedited":false,"failed_reason":""},{"id":"1014","messages":[{"@type":"/interchain_security.ccv.provider.v1.MsgUpdateConsumer"}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"133435177238144","abstain_count":"8082735171424","no_count":"604553163046","no_with_veto_count":"2866183632"},"submit_time":"2025-10-08T19:14:04.664546469Z","deposit_end_time":"2025-10-22T19:14:04.664546469Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2025-10-08T19:37:33.151331998Z","voting_end_time":"2025-10-15T19:37:33.151331998Z","metadata":"","title":"[Correct Owner Address] Migrate Stride to opt-in PSS","summary":"**NOTE**: The previous props #1012 and #1013 contained an error that will cause the execution of the change to fail. This is the replacement. \n\n**SUMMARY:** Stride moves from ICS Top-N (95%) to an **opt-in PoA-style** model with **7 equal-weight validators**, and control of ICS config shifts from **Hub governance** to a **Stride Association multisig**. Fees will pay those 7 validators directly.\n\n**Why**\n* ICS is being sunset (planned 2026) and doesn't cover validator costs.\n* Current flow sends revenue to stakers; validator commissions are negligible.\n\n**What changes (Hub)**\n* Submit `MsgUpdateConsumer` to:\n  * Set new owner = Stride Association multisig.\n  * `topN: 0` (opt-in), `validatorSetCap: 7`, `validatorsPowerCap: 1`.\n  * Allowlist the 7 validators.\n\n**Validators (7)**\n* Imperator, Polkachu, Stakecito, Keplr, Cosmostation, Lavender.Five, Citadel.One.\n\n**Follow-on (Stride)**\n* Redistribution 85% → **100%**.\n* **Pay fees directly** to the 7 validators' fee addresses.\n\n**Forum**: https://forum.cosmos.network/t/migrate-stride-to-opt-in-pss/16241","proposer":"cosmos1na05cry4g23hwt4x5lknktn3nnffgakgkrac0s","expedited":false,"failed_reason":""},{"id":"1013","messages":[{"@type":"/interchain_security.ccv.provider.v1.MsgUpdateConsumer"}],"status":"PROPOSAL_STATUS_REJECTED","final_tally_result":{"yes_count":"2715183140490","abstain_count":"2343375245525","no_count":"116635636156909","no_with_veto_count":"421476735103"},"submit_time":"2025-10-08T19:07:55.622719771Z","deposit_end_time":"2025-10-22T19:07:55.622719771Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2025-10-08T19:07:55.622719771Z","voting_end_time":"2025-10-15T19:07:55.622719771Z","metadata":"","title":"Migrate Stride to opt-in PSS","summary":"**NOTE**: The previous prop #1012 contained an error, this is the replacement. \n\n**SUMMARY:** Stride moves from ICS Top-N (95%) to an **opt-in PoA-style** model with **7 equal-weight validators**, and control of ICS config shifts from **Hub governance** to a **Stride Association multisig**. Fees will pay those 7 validators directly.\n\n**Why**\n* ICS is being sunset (planned 2026) and doesn't cover validator costs.\n* Current flow sends revenue to stakers; validator commissions are negligible.\n\n**What changes (Hub)**\n* Submit `MsgUpdateConsumer` to:\n  * Set new owner = Stride Association multisig.\n  * `topN: 0` (opt-in), `validatorSetCap: 7`, `validatorsPowerCap: 1`.\n  * Allowlist the 7 validators.\n\n**Validators (7)**\n* Imperator, Polkachu, Stakecito, Keplr, Cosmostation, Lavender.Five, Citadel.One.\n\n**Follow-on (Stride)**\n* Redistribution 85% → **100%**.\n* **Pay fees directly** to the 7 validators' fee addresses.\n\n**Forum**: https://forum.cosmos.network/t/migrate-stride-to-opt-in-pss/16241","proposer":"cosmos1na05cry4g23hwt4x5lknktn3nnffgakgkrac0s","expedited":false,"failed_reason":"proposal did not get enough votes to pass"},{"id":"1012","messages":[{"@type":"/interchain_security.ccv.provider.v1.MsgUpdateConsumer"}],"status":"PROPOSAL_STATUS_REJECTED","final_tally_result":{"yes_count":"24099744857459","abstain_count":"1902546824234","no_count":"92003061185198","no_with_veto_count":"402889217642"},"submit_time":"2025-10-07T21:10:15.823662820Z","deposit_end_time":"2025-10-21T21:10:15.823662820Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2025-10-07T21:10:15.823662820Z","voting_end_time":"2025-10-14T21:10:15.823662820Z","metadata":"","title":"Migrate Stride to opt-in PSS","summary":"**SUMMARY:** Stride moves from ICS Top-N (95%) to an **opt-in PoA-style** model with **7 equal-weight validators**, and control of ICS config shifts from **Hub governance** to a **Stride Association multisig**. Fees will pay those 7 validators directly.\n\n**Why**\n* ICS is being sunset (planned 2026) and doesn't cover validator costs.\n* Current flow sends revenue to stakers; validator commissions are negligible.\n\n**What changes (Hub)**\n* Submit `MsgUpdateConsumer` to:\n  * Set new owner = Stride Association multisig.\n  * `topN: 0` (opt-in), `validatorSetCap: 7`, `validatorsPowerCap: 1`.\n  * Allowlist the 7 validators.\n\n**Validators (7)**\n* Imperator, Polkachu, Stakecito, Keplr, Cosmostation, Lavender.Five, Citadel.One.\n\n**Follow-on (Stride)**\n* Redistribution 85% → **100%**.\n* **Pay fees directly** to the 7 validators' fee addresses.\n\n**Forum**: https://forum.cosmos.network/t/migrate-stride-to-opt-in-pss/16241","proposer":"cosmos1na05cry4g23hwt4x5lknktn3nnffgakgkrac0s","expedited":false,"failed_reason":"proposal did not get enough votes to pass"},{"id":"1011","messages":[{"@type":"/ibc.core.client.v1.MsgRecoverClient","subject_client_id":"07-tendermint-1113","substitute_client_id":"07-tendermint-1438","signer":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn"}],"status":"PROPOSAL_STATUS_REJECTED","final_tally_result":{"yes_count":"93935862971633","abstain_count":"13523839550953","no_count":"17187934736","no_with_veto_count":"13120933703"},"submit_time":"2025-09-22T13:41:14.766426142Z","deposit_end_time":"2025-10-06T13:41:14.766426142Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2025-09-22T13:41:14.766426142Z","voting_end_time":"2025-09-29T13:41:14.766426142Z","metadata":"","title":"Recover Expired IBC Client to XPLA Chain","summary":"This governance proposal seeks to recover the expired IBC light client 07-tendermint-1113 connecting our chain to the XPLA Chain. The current expiration of this client has led to an interruption in IBC connectivity, hindering seamless token transfers and general interoperability between our ecosystems. If this proposal passes, the RecoverClient function will be executed to replace the state of the expired client 07-tendermint-1113 with the state of a newly created, valid client, 07-tendermint-1438. This is a critical technical maneuver that restores client validity and immediately re-enables IBC communication with the XPLA Chain while preserving the existing IBC channels and connections.","proposer":"cosmos1rjujxmsdk3n7hj07q54huh4esf4v0ts87dk43g","expedited":false,"failed_reason":"proposal did not get enough votes to pass"},{"id":"1010","messages":[{"@type":"/cosmos.gov.v1.MsgExecLegacyContent","content":{"@type":"/cosmos.gov.v1beta1.TextProposal","title":"[SIGNALING PROPOSAL 1010] Integrating Token Factory into the Cosmos Hub ","description":"Change log\n\n2025-08-13 Created initial post \n\nhttps://forum.cosmos.network/t/proposal-idea-token-factory-ibc-hooks-on-cosmos-hub/15967\n\nSummary\n\nHighlight the need to integrate the Token Factory module into the Cosmos Hub, leveraging the activation of permissionless CosmWasm deployment via Proposal 1007 (recently adopted).\n\nDetails\n\nBackground\n\nProposal 1007 was recently adopted, authorizing permissionless deployment of CosmWasm contracts on the Hub.\n\nThe Token Factory module provides native capabilities for creating IBC-ready tokens.\n\nMain Goals\nProvide developers with a complete environment on the Hub (dApp + token + callbacks) without relying on other chains.\n\nFacilitate the creation of natively IBC-ready tokens, promoting their integration into the Cosmos ecosystem via IBC.\n\nCapture more economic value on the Hub (more transactions, more fees, more outbound IBC).\n\nLeverage mature and battle-tested code, already audited and successfully used on other chains.\n\nCreate an attractive environment for innovative projects (governance tokens, stablecoins, RWAs, LSD, etc.).\n\nEnable complex interchain workflows thanks to callbacks feature (e.g., atomic swaps, transfer-triggered responses, etc.).\n\nAdvantages\n\nDecentralized token creation \u0026 management: CosmWasm contracts can generate tokens without manual intervention or third-party modules.\n\nNative IBC interoperability: tokens are directly usable across the Cosmos ecosystem.\n\nProven security: technology already in production on Osmosis, Neutron (audits available).\n\nSynergy with permissionless CosmWasm: combining these modules creates a complete, programmable platform on the Hub.\n\nEconomic value retention: prevents migration of activities to Osmosis or Neutron.\n\nStandardization of Cosmos assets: facilitates integration by DEXs, dApps, and wallets.\n\nAdvanced interchain experiences: callbacks enable powerful interoperable workflows.\n\nRisks and Proposed Mitigations\n\nSpam and useless token inflation\nConcern that enabling Token Factory on the Hub may lead to a proliferation of worthless tokens, harming the Hub’s readability and reputation.\n\nAlready observed on other chains (many denoms created, very few actually used).\n\nSeveral stakeholders (e.g., Govmos) stress the need for a significant fee on denom creation to limit this effect.\n\nIncreased governance complexity\nWith Token Factory, the community may need to manage more settings, abuse cases, or conflicts around created tokens.\n\nThis could place additional burden on Hub governance, requiring arbitration on more technical and economic issues.\n\nDistraction from the Hub’s primary role\nSome fear the Hub could dilute into a token issuance platform, while its main mandate is security and interoperability (via ICS and IBC).\n\n@Govmos stresses the importance of staying aligned with the blockchain trilemma (security, decentralization, scalability) rather than drifting into secondary use cases.\n\nTechnical compatibility and interchain consistency\n@kromsten highlights compatibility issues between Token Factory implementations (Osmosis vs Neutron).\n\nFor example, Neutron has its own CosmWasm bindings (neutron-std), which may complicate contract portability.\n\nThis raises the question of which module version should be adopted on the Hub, and the risk of fragmentation.\n\nConclusion\n\nThis proposal seeks to make Cosmos Hub a fully programmable, interoperable, and economically active platform. By coupling Token Factory and callbacks (already live on the hub) with permissionless CosmWasm (thanks to Proposal 1007), the Hub becomes a true one-stop shop for dApps with tokens, interchain workflows, and enriched logic.\n\nThe identified risks (spam, governance, security) can be managed via proven mechanisms (fees, disabling risky features, regular audits).\n\nThe Hub will thus be better positioned to attract developers, retain value, and reinforce its leadership within the Cosmos ecosystem.\n\nForum post link\nhttps://forum.cosmos.network/t/proposal-idea-token-factory-ibc-hooks-on-cosmos-hub/15967/33\n\nGovernance votes\n\nThe following items summarize the voting options and what it means for this proposal:\n\nYES - A YES vote signals that you support asking Cosmos Labs or another dedicated team to scope, develop, and implement the Token Factory module for the Cosmos Hub. This proposal does not activate the module directly but expresses the community’s intent to prioritize this work.\n\nNO - A NO vote signals that you do not support requesting Cosmos Labs or another dedicated team to work on the Token Factory module at this time. The Hub would continue without a native Token Factory, and projects would still rely on other chains to create tokens.\n\nNO 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.\n\nABSTAIN - You wish to contribute to quorum but you formally decline to vote either for or against the proposal."},"authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn"}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"87718137532682","abstain_count":"22342439010838","no_count":"25860920380","no_with_veto_count":"3888238699"},"submit_time":"2025-09-15T20:05:14.440717940Z","deposit_end_time":"2025-09-29T20:05:14.440717940Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2025-09-18T10:05:19.136529262Z","voting_end_time":"2025-09-25T10:05:19.136529262Z","metadata":"https://forum.cosmos.network/t/signaling-proposal-1010-integrating-token-factory-into-the-cosmos-hub/16131/7","title":"[SIGNALING PROPOSAL 1010] Integrating Token Factory into the Cosmos Hub ","summary":"Change log\n\n2025-08-13 Created initial post \n\nhttps://forum.cosmos.network/t/proposal-idea-token-factory-ibc-hooks-on-cosmos-hub/15967\n\nSummary\n\nHighlight the need to integrate the Token Factory module into the Cosmos Hub, leveraging the activation of permissionless CosmWasm deployment via Proposal 1007 (recently adopted).\n\nDetails\n\nBackground\n\nProposal 1007 was recently adopted, authorizing permissionless deployment of CosmWasm contracts on the Hub.\n\nThe Token Factory module provides native capabilities for creating IBC-ready tokens.\n\nMain Goals\nProvide developers with a complete environment on the Hub (dApp + token + callbacks) without relying on other chains.\n\nFacilitate the creation of natively IBC-ready tokens, promoting their integration into the Cosmos ecosystem via IBC.\n\nCapture more economic value on the Hub (more transactions, more fees, more outbound IBC).\n\nLeverage mature and battle-tested code, already audited and successfully used on other chains.\n\nCreate an attractive environment for innovative projects (governance tokens, stablecoins, RWAs, LSD, etc.).\n\nEnable complex interchain workflows thanks to callbacks feature (e.g., atomic swaps, transfer-triggered responses, etc.).\n\nAdvantages\n\nDecentralized token creation \u0026 management: CosmWasm contracts can generate tokens without manual intervention or third-party modules.\n\nNative IBC interoperability: tokens are directly usable across the Cosmos ecosystem.\n\nProven security: technology already in production on Osmosis, Neutron (audits available).\n\nSynergy with permissionless CosmWasm: combining these modules creates a complete, programmable platform on the Hub.\n\nEconomic value retention: prevents migration of activities to Osmosis or Neutron.\n\nStandardization of Cosmos assets: facilitates integration by DEXs, dApps, and wallets.\n\nAdvanced interchain experiences: callbacks enable powerful interoperable workflows.\n\nRisks and Proposed Mitigations\n\nSpam and useless token inflation\nConcern that enabling Token Factory on the Hub may lead to a proliferation of worthless tokens, harming the Hub’s readability and reputation.\n\nAlready observed on other chains (many denoms created, very few actually used).\n\nSeveral stakeholders (e.g., Govmos) stress the need for a significant fee on denom creation to limit this effect.\n\nIncreased governance complexity\nWith Token Factory, the community may need to manage more settings, abuse cases, or conflicts around created tokens.\n\nThis could place additional burden on Hub governance, requiring arbitration on more technical and economic issues.\n\nDistraction from the Hub’s primary role\nSome fear the Hub could dilute into a token issuance platform, while its main mandate is security and interoperability (via ICS and IBC).\n\n@Govmos stresses the importance of staying aligned with the blockchain trilemma (security, decentralization, scalability) rather than drifting into secondary use cases.\n\nTechnical compatibility and interchain consistency\n@kromsten highlights compatibility issues between Token Factory implementations (Osmosis vs Neutron).\n\nFor example, Neutron has its own CosmWasm bindings (neutron-std), which may complicate contract portability.\n\nThis raises the question of which module version should be adopted on the Hub, and the risk of fragmentation.\n\nConclusion\n\nThis proposal seeks to make Cosmos Hub a fully programmable, interoperable, and economically active platform. By coupling Token Factory and callbacks (already live on the hub) with permissionless CosmWasm (thanks to Proposal 1007), the Hub becomes a true one-stop shop for dApps with tokens, interchain workflows, and enriched logic.\n\nThe identified risks (spam, governance, security) can be managed via proven mechanisms (fees, disabling risky features, regular audits).\n\nThe Hub will thus be better positioned to attract developers, retain value, and reinforce its leadership within the Cosmos ecosystem.\n\nForum post link\nhttps://forum.cosmos.network/t/proposal-idea-token-factory-ibc-hooks-on-cosmos-hub/15967/33\n\nGovernance votes\n\nThe following items summarize the voting options and what it means for this proposal:\n\nYES - A YES vote signals that you support asking Cosmos Labs or another dedicated team to scope, develop, and implement the Token Factory module for the Cosmos Hub. This proposal does not activate the module directly but expresses the community’s intent to prioritize this work.\n\nNO - A NO vote signals that you do not support requesting Cosmos Labs or another dedicated team to work on the Token Factory module at this time. The Hub would continue without a native Token Factory, and projects would still rely on other chains to create tokens.\n\nNO 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.\n\nABSTAIN - You wish to contribute to quorum but you formally decline to vote either for or against the proposal.","proposer":"cosmos1vmxx4z2mjyjqqln6vq86vqdv2l3y9sdegt0u3a","expedited":false,"failed_reason":""},{"id":"1009","messages":[{"@type":"/cosmos.authz.v1beta1.MsgGrant","granter":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","grantee":"cosmos1k9hkmn7upap546a4tfn908sfuuseru640dwu2nzem3zxklwrm4vqhzkwdk","grant":{"authorization":{"@type":"/cosmos.authz.v1beta1.GenericAuthorization","msg":"/ibc.lightclients.wasm.v1.MsgStoreCode"},"expiration":null}},{"@type":"/cosmos.authz.v1beta1.MsgGrant","granter":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","grantee":"cosmos1k9hkmn7upap546a4tfn908sfuuseru640dwu2nzem3zxklwrm4vqhzkwdk","grant":{"authorization":{"@type":"/cosmos.authz.v1beta1.GenericAuthorization","msg":"/ibc.lightclients.wasm.v1.MsgMigrateContract"},"expiration":null}}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"99484083323550","abstain_count":"16308746238526","no_count":"30852544276","no_with_veto_count":"5862795050"},"submit_time":"2025-09-08T19:39:15.130129204Z","deposit_end_time":"2025-09-22T19:39:15.130129204Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2025-09-08T19:45:39.469126762Z","voting_end_time":"2025-09-15T19:45:39.469126762Z","metadata":"ipfs://","title":"Grant Eureka Security Council 08-wasm AuthZ permissions","summary":"## **Proposal**\n\nTL;DR - To match Eureka’s security response setup on Ethereum and enable timely security upgrades on Cosmos Hub, this proposal grants the Eureka Security Council AuthZ (on behalf of the gov module address) permissions on IBC 08-wasm to (1) store new wasm binaries used by 08-wasm light clients and (2) migrate existing light client contracts. This avoids the current requirement of two sequential 7-day governance proposals (store, then migrate) or coordinated binary upgrades, both of which are too slow and operationally risky. The voting period for this proposal is 7 days.\n\n### **Motivation**\n\nGranting scoped AuthZ to the Eureka Security Council will improve the Hub’s security posture and responsiveness by enabling:\n\nTimely storage of new 08-wasm light client binaries when critical vulnerabilities or consensus changes are discovered\n\nSafe, auditable migrations of existing light client contracts to patched versions without halting the chain\n\nOperational parity with Eureka’s Ethereum-side security council so both ends of the bridge can be upgraded within the same response window\n\nAs Eureka connectivity expands, light clients are a critical security boundary. Today, addressing issues requires two full governance cycles (one to store a new binary and one to migrate), or a coordinated binary upgrade, which is slow, error-prone, and burdens validators. Scoped AuthZ lets the Council execute only these two actions quickly and transparently, reducing risk while preserving on-chain accountability.\n\nPreviously, on the Ethereum side of Eureka, a Security Council model is already used to enable rapid, scoped responses. This proposal brings the Hub into alignment with that model so cross-chain upgrades can be executed consistently and safely.\n\n### **Future Deployments**\n\nWith this access, the Eureka Security Council will use AuthZ exclusively to manage 08-wasm light client lifecycle operations on the Hub after the community accepts this proposal. Specifically, actions are limited to:\n\n* Storing new wasm binaries intended for 08-wasm light clients (`/ibc.lightclients.wasm.v1.MsgStoreCode`)\n* Migrating existing 08-wasm light client contracts to stored versions (`/ibc.lightclients.wasm.v1.MsgMigrateContract` **)**\n\nThis streamlines security and maintenance because:\n\n* No chain upgrades or halts are needed to patch or upgrade light clients\n* Fixes and new upgrades can be deployed without two back-to-back governance proposals, reducing response time during incidents and agility\n* The Hub remains lean by keeping non-critical logic out of the Gaia binary while preserving clear on-chain audit trails\n\n### **Eureka Security Council**\n\nThe Eureka Security Council is a 4/7 DAO DAO multisig with the address: `cosmos1k9hkmn7upap546a4tfn908sfuuseru640dwu2nzem3zxklwrm4vqhzkwdk`\n\nThe members of the Eureka Security Council is a trusted consortium of community members and builders from across the industry consisting of members from:\n\n* Wildcat Finance\n* Informal\n* Hypha\n* ZK Validator\n* Chorus One\n* Keplr\n* Interchain Labs\n\n### **Additional notes**\n\nThis proposal grants AuthZ for exactly two message types relevant to 08-wasm light clients: storing new wasm binaries used by 08-wasm and migrating existing light client contracts. No other wasm or IBC permissions are included or modified by this proposal.\n\n### **Governance votes**\n\nThe following items summarize the voting options and what it means for this proposal:\n\nYES - You agree that the Eureka Security Council should receive AuthZ to store 08-wasm binaries and migrate 08-wasm light client contracts, with a voting period of 3 days.\n\nNO - You disagree that the Eureka Security Council should receive these AuthZ permissions.\n\nNO 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.\n\nABSTAIN - You wish to contribute to the quorum but you formally decline to vote either for or against the proposal.","proposer":"cosmos16mpxhyurfckn67zzfp7f56kle9zca3e4gfwxdm","expedited":false,"failed_reason":""},{"id":"1008","messages":[{"@type":"/ibc.core.client.v1.MsgRecoverClient","subject_client_id":"07-tendermint-1411","substitute_client_id":"07-tendermint-1437","signer":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn"}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"111404365374364","abstain_count":"1868991511401","no_count":"16719278979","no_with_veto_count":"5877379593"},"submit_time":"2025-09-04T15:45:58.456546732Z","deposit_end_time":"2025-09-18T15:45:58.456546732Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2025-09-04T15:45:58.456546732Z","voting_end_time":"2025-09-11T15:45:58.456546732Z","metadata":"","title":"Recover IBC light client for Xrplevm","summary":"This proposal updates the expired IBC light client `07-tendermint-1411` for counterparty chain `xrplevm_1440000-1` with the state of the newly created substitute client `07-tendermint-1437`","proposer":"cosmos1705swa2kgn9pvancafzl254f63a3jda9ngdnc7","expedited":false,"failed_reason":""},{"id":"1007","messages":[{"@type":"/cosmwasm.wasm.v1.MsgUpdateParams","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","params":{"code_upload_access":{"permission":"Everybody","addresses":[]},"instantiate_default_permission":"Everybody"}}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"97420409739737","abstain_count":"25597223148996","no_count":"1365130909804","no_with_veto_count":"6654706177"},"submit_time":"2025-08-12T21:56:54.373342475Z","deposit_end_time":"2025-08-26T21:56:54.373342475Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2025-08-13T07:01:51.689513298Z","voting_end_time":"2025-08-20T07:01:51.689513298Z","metadata":"https://forum.cosmos.network/t/proposal-1007-draft-enable-permissionless-cosmwasm-smart-contract-deployment-on-cosmos-hub/15904","title":"Enable Permissionless CosmWasm Smart Contract Deployment on Cosmos Hub","summary":"Today, CosmWasm (CW) is permissioned on the Cosmos Hub. This means that in order to deploy a contract, an address must first be whitelisted via an on-chain vote. Once whitelisted, that address can deploy as many contracts as it wants without going through governance again unless its permission is later revoked.\n\n## Current situation:\n\nVery few deployments are happening on the Hub.\n\n### Suspected reasons:\n\nA project needs visibility and certainty to get started. It’s hard to convince investors with a pitch like: “We’ll build for months, but we’re not sure if we’ll be allowed to deploy.”\n\nThe process is too slow and clunky, due to slow or inefficient governance.\n\nTeams are sometimes reluctant to expose themselves publicly or be judged in a vote.\n\nThe whitelisting mechanism lacks granularity: once approved, an actor can deploy unlimited contracts without further review.\n\nThe Hub isn’t seen as a developer-friendly environment compared to simpler and faster alternatives (Neutron, Osmosis, etc.).\n\nLow current activity creates a loop of inertia: low usage = low attractiveness.## Why CosmWasm?\n\nSeveral well-known Cosmos teams want to deploy on the Hub.\n\nCosmWasm is part of the native Cosmos stack, with a well-equipped ecosystem (IBC integration, CosmJS, etc.).\n\nSome live applications are becoming critical (e.g. Hydro).\n\nThe Hub could attract meaningful use cases if development becomes easier.\n\nCosmWasm enables strong modularity and security through smart contracts.\n\n### Historical concerns:\n\nThe main worry has always been security: risks of exploits, hacks, rug pulls, etc.\n\nWhat community knows:\n\nNeutron, a permissionless CosmWasm chain, shows that:\n\nDeployment volume remains reasonable.\n\nNo major incidents have occurred to date.\n\nPermissionlessness hasn’t led to overload or chaos.\n\nFurthermore, in the current case of permissioned CW on the hub, a previously whitelisted address can deploy a multitude of contracts without authorization, which would be at risk in the case of an unperformed audit. Ultimately, the current permissioned CW only bottlenecks development on the cosmos hub.\n\nIf an issue were to arise, ICL (in charge of Hub software) could respond quickly.","proposer":"cosmos1d50zp5mymt53dkzn9xrslwen2cup25uz7pq9zp","expedited":false,"failed_reason":""},{"id":"1006","messages":[{"@type":"/cosmos.distribution.v1beta1.MsgCommunityPoolSpend","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","recipient":"cosmos1k3auc6wmj7hehdwy55qfjymksrw7lvqxdtxrhd2x7t3qffcutm5s0hmkl9","amount":[{"denom":"ibc/F663521BF1836B00F5F177680F74BFB9A8B5654A694D0D2BC249E03CF2509013","amount":"90000000000"}]}],"status":"PROPOSAL_STATUS_REJECTED","final_tally_result":{"yes_count":"9133826719897","abstain_count":"39961762482008","no_count":"46808536433185","no_with_veto_count":"83504232760"},"submit_time":"2025-07-26T00:49:53.452185781Z","deposit_end_time":"2025-08-09T00:49:53.452185781Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2025-07-26T00:49:53.452185781Z","voting_end_time":"2025-08-02T00:49:53.452185781Z","metadata":"https://forum.cosmos.network/t/bridging-worlds-empowering-cosmos-with-an-ethereum-nft-bridge/15691","title":"Connecting Businesses: Empowering Stack Adoption with a Data Bridge (using NFTs)","summary":"## Background\n\nProposal #1005 failed due to clarity, $ATOM alignment, and cost issues. We've listened to community's feedback and ICL's vision, focusing on enterprise needs and $ATOM value.\n\nFull discussion here: https://forum.cosmos.network/t/bridging-worlds-empowering-cosmos-with-an-ethereum-nft-bridge/15691\n\n### Alignment with ICL Vision\n\n- Businesses seek:\n  1. **Sovereignty**: running their custom blockchains and e.g. not relying on Ethereum.\n  2. **Interoperability**: Data/token exchange via IBC Eureka, routed through the Hub.\n- Supports businesses, enhancing Stack adoption and $ATOM value per ICL's vision.\n\nFor details check Cryptocito's full interview with Mag here: https://x.com/Cryptocito/status/1945214389902029043\n\nHere's a technical **web2/web3** analogy between `Smart Contracts using IBC + Bridge` and `Web applications using TCP + HTML`:\n\nIBC Eureka + Bridge in Web3 is, simply said, like TCP + HTML in Web2: While IBC is the base layer connecting blockchains (like TCP links servers), our bridge adds an application layer for business data (like HTTP delivers web pages).\n\nOur bridge, being built on top of IBC Eureka, transfers complex data (via NFTs) - including(!) ownership - between smart contracts or wallets across blockchains.\n\nFor example, a supply chain smart contract on custom Cosmos chain A could send an NFT with shipment metadata to a partner's contract on a custom Cosmos chain B, ensuring secure, verifiable ownership transfer.\n\n### Asset Bridge Clarification\n\n- NFTs - in general - is just a data store (e.g., IDs, certificates) for enterprises, customizable to their needs (e.g., a bank creating loan documents)\n- Bridge uses **CosmosEVM** and **IBC Eureka**, 100% $ATOM-aligned via the Hub.\n- EVM is key, paused on the Hub, but vital for business smart contracts and interoperability.\n\n## Project Scope\n\n- Solidity ICS-721 Bridge Contract\n- Front-end Toolkit for seamless transfers\n- Ark runs CW-based bridges on Injective, Juno, Neutron, Osmosis, Stargaze, Terra; contributed to cw-ics721/cw-nfts.\n\n## Funding Request\n\n- **Total:** $90,000 USDC (shown in the spend proposal details as 90,000,000,000 IBC-wrapped uusdc).\n- **Breakdown:** Development: $90,000 (100%, includes $20k buffer e.g. due to possible breaking changes in CosmosEVM or other unforeseen issues).\n- **Audits Excluded**: $50,000 removed to reduce costs; audits will be deferred until pilot success.\n- **Operations Excluded**: $60,000 removed; initial operations will be self-funded by Ark Protocol.\n- **Release:** Three tranches upon dev start, testnet deployment, and mainnet launch.\n- **MVP:** Targeted for Q3/Q4 2025, pending final CosmosEVM release.\n\n## Treasury and Oversight\n\nFunds will be sent to and managed by Ark's Oversight DAO here: https://daodao.zone/dao/cosmos1k3auc6wmj7hehdwy55qfjymksrw7lvqxdtxrhd2x7t3qffcutm5s0hmkl9\n\nArk Oversight DAO memebers with 3-signer threshold for approvals:\n\n- Sistla (OmniFlix): `cosmos1nqchg6qytz6mvq85r6adsuaghfwnczex9hs02m`\n- Zerk (Mad Scientists): `cosmos1pwha5a3hr55wmmur2d4fm0p8rf7q62wn2rvzw8`\n- Johnny Wyles (Osmosis): `cosmos1dplx2zw3mjk5lam6fnv5q2yxldcshs3wh2rhh9`\n- David Goose (Osmosis): `cosmos1ky9hyqhdxygkkyvjcdd76qceq7t9syy488rsjm`\n- Tatsen (Ark): `cosmos1trghmhd4d9qcf9d0lsyesxzj3aasqg9slykml5`\n- Mr T (Ark): `cosmos1vtpt9kwjywm3xpake4v8sjmh2uxqq57h499qa5`\n\n## Voting Optins:\n\n- **YES** to push Cosmos' stack adoption for enterprises.\n- **NO** seeing no need for businesses exchanging data using bridge and bridging NFTs in general.\n- **Abstain**: You wish to contribute to the quorum but formally decline to vote either for or against the proposal.\n- **No With Veto**: your ‘No With Veto’ vote indicates us, Ark, either to be spam, irrelevant to the Cosmos Hub. If the number of ‘No With Veto’ votes is greater than a third of total votes, the proposal is rejected and the deposits are burned.","proposer":"cosmos19pmppgpqnjkvjp6mx8q2dpuy382g4hhxatt9sk","expedited":false,"failed_reason":"proposal did not get enough votes to pass"},{"id":"1005","messages":[{"@type":"/cosmos.distribution.v1beta1.MsgCommunityPoolSpend","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","recipient":"cosmos1k3auc6wmj7hehdwy55qfjymksrw7lvqxdtxrhd2x7t3qffcutm5s0hmkl9","amount":[{"denom":"uatom","amount":"44444000000"}]}],"status":"PROPOSAL_STATUS_REJECTED","final_tally_result":{"yes_count":"19968222228185","abstain_count":"47843854787489","no_count":"33780554120750","no_with_veto_count":"50310646780"},"submit_time":"2025-07-18T21:22:57.579882410Z","deposit_end_time":"2025-08-01T21:22:57.579882410Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2025-07-18T21:22:57.579882410Z","voting_end_time":"2025-07-25T21:22:57.579882410Z","metadata":"https://forum.cosmos.network/t/bridging-worlds-empowering-cosmos-with-an-ethereum-nft-bridge/15691/","title":"Bridging Worlds: Empowering Cosmos with an Ethereum NFT Bridge","summary":"# Summary\n\nArk Protocol requests **47,600 ATOM** (≈ $200 000, using a 30 d avg price of $4.20/ATOM) from the Community Pool to build an open-source, EVM-based NFT bridge compliant with ICS-721.\n\n## Motivation\n\nEther­eum hosts a $15 B+ NFT market, but Cosmos lacks a direct, audited EVM-compatible bridge for ICS-721 tokens. By funding Ark Protocol to build and operate this bridge, the Hub:\n\n* **Unlocks instant NFT liquidity** for ATOM holders\n* **Onboards EVM-native communities** into Cosmos\n* **Accrues sustainable revenue**, as all fees are held/swapped into ATOM\n\n## Project Scope\n\n1. **Solidity ICS-721 Bridge Contract**\n2. **Front-end Toolkit** for seamless transfer flows\n3. **12-month Operations**: node hosting, monitoring, DevOps\n4. **Security Audit \u0026 Remediation**\n\nArk has production experience deploying CW-based NFT modules on Injective, Juno, Neutron, Osmosis, Stargaze, Terra - and contributed heavily to the core [cw-ics721](https://github.com/public-awesome/cw-ics721/graphs/contributors) and [cw-nfts](https://github.com/public-awesome/cw-nfts/graphs/contributors) repos.\n\n## Budget \u0026 Milestones (Total: $200 000 / 47 600 ATOM)\n\n| Phase              | Amount (USD) |   ATOM | Deliverable                                    |\n| ------------------ | -----------: | -----: | :--------------------------------------------- |\n| **1) Development** |    $ 90 000 | 21 429 | Architecture \u0026 Solidity ICS-721 implementation |\n| **2) Operations**  |    $ 60 000 | 14 286 | 12 mo support: hosting, monitoring, DevOps     |\n| **3) Audit**       |    $ 50 000 | 11 905 | Third-party security audit + remediation       |\n\n*Funds are released in three tranches upon Dev Start, Testnet Deployment, and Mainnet Launch.*\n\n## Treasury \u0026 Oversight\n\nAll funds will be managed by the **Ark Oversight DAO**\nMembers \u0026 signers:\n\n* Sistla (OmniFlix + StreamSwap): cosmos1nqchg6qytz6mvq85r6adsuaghfwnczex9hs02m\n* Zerk (Mad Scientists): cosmos1pwha5a3hr55wmmur2d4fm0p8rf7q62wn2rvzw8\n* Johnny Wyles (Osmosis): cosmos1dplx2zw3mjk5lam6fnv5q2yxldcshs3wh2rhh9\n* David Goose (Osmosis): cosmos1ky9hyqhdxygkkyvjcdd76qceq7t9syy488rsjm\n* Tatsen (Ark Protocol): cosmos1trghmhd4d9qcf9d0lsyesxzj3aasqg9slykml5\n* Mr T (Ark Protocol): cosmos1vtpt9kwjywm3xpake4v8sjmh2uxqq57h499qa5\n\n\u003e Full discussion:\n\u003e [Bridging Worlds: Empowering Cosmos with an Ethereum NFT Bridge](https://forum.cosmos.network/t/bridging-worlds-empowering-cosmos-with-an-ethereum-nft-bridge/15691)\n\n## Conclusion\n\nApproving this proposal will:\n\n* Bootstrap a robust, audited NFT bridge for CosmosEVM\n* Deepen on-chain NFT use-cases and liquidity for ATOM\n* Generate ongoing value and revenue accrual in ATOM\n\nWe appreciate the community's support in uniting Cosmos and Ethereum's NFT ecosystems.","proposer":"cosmos19pmppgpqnjkvjp6mx8q2dpuy382g4hhxatt9sk","expedited":false,"failed_reason":"proposal did not get enough votes to pass"},{"id":"1004","messages":[{"@type":"/cosmos.upgrade.v1beta1.MsgSoftwareUpgrade","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","plan":{"name":"v25.1.0","time":"0001-01-01T00:00:00Z","height":"26659700","info":"{\"binaries\": {\"darwin/amd64\": \"https://github.com/cosmos/gaia/releases/download/v25.1.0/gaiad-v25.1.0-darwin-amd64?checksum=sha256:baeebe95e3db3b01610a79769105a0ed92efd7dabbe7ffe622a778ac46201948\", \"darwin/arm64\": \"https://github.com/cosmos/gaia/releases/download/v25.1.0/gaiad-v25.1.0-darwin-arm64?checksum=sha256:1f18dd615a34fb63dcb826b9ddd0423adfe0fbc953c95fd0637c9fbadca4cd1f\", \"linux/amd64\": \"https://github.com/cosmos/gaia/releases/download/v25.1.0/gaiad-v25.1.0-linux-amd64?checksum=sha256:1bd6bc72fd98b5ef7a6001a0e42850ab4dd1d32a63a9627ab72834ab61ed4f76\"}}","upgraded_client_state":null}}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"111963986206736","abstain_count":"4326304311","no_count":"11659637204","no_with_veto_count":"2455769536"},"submit_time":"2025-07-09T15:35:19.064348574Z","deposit_end_time":"2025-07-23T15:35:19.064348574Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2025-07-09T15:56:53.503588382Z","voting_end_time":"2025-07-16T15:56:53.503588382Z","metadata":"ipfs://CID","title":"Gaia v25.1.0 Software Upgrade","summary":"## Background\r\n\r\nThis upgrade fixes a bug that was found in the `x/distribution` module where a malicious deposit into the Validator Rewards pool would result in an integer overflow that would cause a chain halt. You can read the full security advisory [here](https://github.com/cosmos/cosmos-sdk/security/advisories/GHSA-p22h-3m2v-cmgh).\r\n\r\nGaia v25.1.0 is a minor release that will follow the regular governance process for software upgrades on the Cosmos Hub.\r\n\r\nReminder – This proposal will have a voting period of just **ONE WEEK**.\r\n\r\nIf the proposal passes, validators will be required to update the Cosmos Hub binary at the halt-height specified in the on-chain proposal.\r\n\r\n## Release Details\r\n\r\n**We are targeting the upgrade for Thursday July 17th.**\r\n\r\n- The release candidate can be found [here](https://github.com/cosmos/gaia/releases/tag/v25.1.0). A final release will be cut after testing completes on testnet.\r\n- The changelog can be found [here](https://github.com/cosmos/gaia/blob/v25.1.0/CHANGELOG.md).\r\n\r\nThe release bumps the following dependencies:\r\n\r\n- Bump [github.com/cosmos/cosmos-sdk](https://github.com/cosmos/cosmos-sdk) from 0.53.2 to 0.53.3 ([#3827](https://github.com/cosmos/gaia/pull/3827))\r\n\r\n**This upgrade is state-breaking and mandatory once the on-chain vote passes and the upgrade-height is reached.**\r\n\r\n## Testing and Testnets\r\n\r\nThe v25.1.0 release has gone through rigorous testing, including e2e tests, and integration tests by Interchain Labs. In addition, the upgrade process has been independently tested by the team at Hypha Co-op and has been performed by validators and node operators on a public testnet prior to going on-chain.\r\n\r\nIf you wish to participate in the testnet upgrade process in the future, you can find the relevant information (genesis file, peers, etc.) to join the Cosmos Hub's Interchain Security Testnet (provider) [here](https://github.com/cosmos/testnets/tree/master/interchain-security).\r\n\r\n### Potential risk factors\r\n\r\nAs with any major upgrade, there always exists a risk that the Cosmos Hub might experience problems due to potential bugs or errors, even though extensive testing and simulation has been completed. In the case of serious problems, validators should stop operating the network immediately.\r\n\r\nCoordination with validators will happen in the [#cosmos-hub-validators-verified](https://discord.com/channels/669268347736686612/798937713474142229) channel of the Cosmos Network Discord to create and execute a contingency plan. Likely this will be an emergency release with fixes or the recommendation to consider the upgrade aborted and revert back to the previous release of Gaia (v25.0.0).\r\n\r\n### Governance votes\r\n\r\nThe following items summarize the voting options and what it means for this proposal:\r\n\r\nYES - You agree that the Cosmos Hub should upgrade to v25.1.0.\r\n\r\nNO - You disagree that the Cosmos Hub should upgrade to v25.1.0.\r\n\r\nNO 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.\r\n\r\nABSTAIN - You wish to contribute to the quorum but you formally decline to vote either for or against the proposal.","proposer":"cosmos1az2sxspr9mfv407ay7ktcqjj57zre2dxcjecfd","expedited":false,"failed_reason":""},{"id":"1003","messages":[{"@type":"/cosmos.upgrade.v1beta1.MsgSoftwareUpgrade","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","plan":{"name":"v25.0.0","time":"0001-01-01T00:00:00Z","height":"26440900","info":"{\"binaries\": {\"darwin/amd64\": \"https://github.com/cosmos/gaia/releases/download/v25.0.0/gaiad-v25.0.0-darwin-amd64?checksum=sha256:0067734dde376dd71c31c62a7083e3adf069e1aaffd4ae43e792b5ceeca96b9b\", \"darwin/arm64\": \"https://github.com/cosmos/gaia/releases/download/v25.0.0/gaiad-v25.0.0-darwin-arm64?checksum=sha256:ed6bd66e33d24e624f51e8882286cc424ce242f8602af0b081d7f9b21dbe2115\", \"linux/amd64\": \"https://github.com/cosmos/gaia/releases/download/v25.0.0/gaiad-v25.0.0-linux-amd64?checksum=sha256:646f86a7035a601dbca3ae8ea65269642f59b8cf5f1357f5c48331965b5241cd\"}}","upgraded_client_state":null}}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"137812235846887","abstain_count":"16245259973","no_count":"13106461241","no_with_veto_count":"8620203855"},"submit_time":"2025-06-23T14:59:04.941251420Z","deposit_end_time":"2025-07-07T14:59:04.941251420Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2025-06-23T15:24:05.461351374Z","voting_end_time":"2025-06-30T15:24:05.461351374Z","metadata":"ipfs://CID","title":"Gaia v25.0.0 Upgrade","summary":"## Background\r\n\r\nThis upgrade unforks Gaia from the Cosmos SDK while upgrading from version 0.50.13 to 0.53.0. This significantly reduces technical debt and eases future development.\r\n\r\nGaia v25.0.0 is a major release that will follow the regular governance process for software upgrades on the Cosmos Hub.\r\n\r\nReminder – This proposal will have a voting period of just **ONE WEEK**.\r\n\r\nIf the proposal passes, validators will be required to update the Cosmos Hub binary at the halt-height specified in the on-chain proposal.\r\n\r\n## Release Details\r\n\r\n**We are targeting the upgrade for Wednesday July 2nd.**\r\n\r\n* The release candidate can be found [here](https://github.com/cosmos/gaia/releases/tag/v25.0.0).\r\n* The changelog can be found [here](https://github.com/cosmos/gaia/blob/main/CHANGELOG.md).\r\n\r\nThe release bumps the following dependencies:\r\n\r\n* Bump [cosmos-sdk](https://github.com/cosmos/cosmos-sdk) to [v0.53.0](https://github.com/cosmos/cosmos-sdk/releases/tag/v0.53.0)\r\n* Bump [wasmvm](https://github.com/CosmWasm/wasmvm) to [v2.2.4](https://github.com/CosmWasm/wasmvm/releases/tag/v2.2.4)\r\n* Bump [wasmd](https://github.com/CosmWasm/wasmd) to [v0.60.1](https://github.com/CosmWasm/wasmd/releases/tag/v0.60.1)\r\n\r\n**This upgrade is state-breaking and mandatory once the on-chain vote passes and the upgrade-height is reached.**\r\n\r\n**Please note that the `--x-crisis-skip-assert-invariants` flag has been deprecated and the node will not start with it in place. Make sure you are not using this flag before you start a v25 node.**\r\n\r\n## Testing and Testnets\r\n\r\nThe v25.0.0 release has gone through rigorous testing, including e2e tests, and integration tests by Interchain Labs. In addition, the upgrade process has been independently tested by the team at Hypha Co-op and has been performed by validators and node operators on a public testnet prior to going on-chain.\r\n\r\nIf you wish to participate in the testnet upgrade process in the future, you can find the relevant information (genesis file, peers, etc.) to join the Cosmos Hub’s Interchain Security Testnet (provider) [here](https://github.com/cosmos/testnets/tree/master/interchain-security).\r\n\r\n## Potential risk factors\r\n\r\nAs with any major upgrade, there always exists a risk that the Cosmos Hub might experience problems due to potential bugs or errors, even though extensive testing and simulation has been completed. In the case of serious problems, validators should stop operating the network immediately.\r\n\r\nCoordination with validators will happen in the [#cosmos-hub-validators-verified channel](https://discord.com/channels/669268347736686612/798937713474142229) of the Cosmos Network Discord to create and execute a contingency plan. Likely this will be an emergency release with fixes or the recommendation to consider the upgrade aborted and revert back to the previous release of Gaia (v24.0.0).\r\n\r\n## Governance votes\r\n\r\nThe following items summarize the voting options and what it means for this proposal:\r\n\r\nYES - You agree that the Cosmos Hub should upgrade to v25.0.0.\r\n\r\nNO - You disagree that the Cosmos Hub should upgrade to v25.0.0.\r\n\r\nNO 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.\r\n\r\nABSTAIN - You wish to contribute to the quorum but you formally decline to vote either for or against the proposal.","proposer":"cosmos1az2sxspr9mfv407ay7ktcqjj57zre2dxcjecfd","expedited":false,"failed_reason":""},{"id":"1001","messages":[{"@type":"/cosmwasm.wasm.v1.MsgUpdateParams","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","params":{"code_upload_access":{"permission":"AnyOfAddresses","addresses":["cosmos1js483tqdkcpp8yg6u648vt4a5wzq4gv86p26cn5xx76esxqrvreqk6mw8h"]},"instantiate_default_permission":"Everybody"}}],"status":"PROPOSAL_STATUS_REJECTED","final_tally_result":{"yes_count":"9328801207755","abstain_count":"35036397428964","no_count":"71092863904723","no_with_veto_count":"79271534774"},"submit_time":"2025-06-05T02:05:25.319042159Z","deposit_end_time":"2025-06-19T02:05:25.319042159Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2025-06-05T02:05:25.319042159Z","voting_end_time":"2025-06-12T02:05:25.319042159Z","metadata":"https://forum.cosmos.network/t/whitelist-wallet-for-the-deployment-of-nft-marketplace-lst-platform-and-dex-by-backbone-labs/15513","title":"Whitelist BackBone Labs Developer Wallet for BackBone Labs Smart Contracts","summary":"This proposal requests Cosmos Hub community approval to whitelist the following wallet for smart contract deployment by BackBone Labs:\n\nDeployment Wallet[cosmos1js483tqdkcpp8yg6u648vt4a5wzq4gv86p26cn5xx76esxqrvreqk6mw8h](daodao.zone/dao/cosmos1js483tqdkcpp8yg6u648vt4a5wzq4gv86p26cn5xx76esxqrvreqk6mw8h/home) \n\nWe seek permission to deploy our suite of products, including:\n\nA capital-efficient NFT marketplace\n\nA liquid staking platform for bATOM\n\nA decentralized exchange (DEX)BackBone Labs is asking for deployment access—nothing more. \n\nNo funding, no grants, no emissions. We come to contribute.\n\nAbout BackBone Labs\n\nBackBone Labs is a Cosmos-native infrastructure team operating across Osmosis, Injective, Terra, Dungeon, and Chihuahua. Our work fuses DeFi primitives with NFT infrastructure to create composable systems governed by their communities.\n\nMore information on our forum post: https://forum.cosmos.network/t/whitelist-wallet-for-the-deployment-of-nft-marketplace-lst-platform-and-dex-by-backbone-labs/15513","proposer":"cosmos10ymjrxlt7lvpkquh6uzr2fas4lsw2zqvyu59yx","expedited":false,"failed_reason":"proposal did not get enough votes to pass"},{"id":"1000","messages":[{"@type":"/cosmos.upgrade.v1beta1.MsgSoftwareUpgrade","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","plan":{"name":"v24","time":"0001-01-01T00:00:00Z","height":"26131400","info":"{\"binaries\": {\"darwin/amd64\": \"https://github.com/cosmos/gaia/releases/download/v24.0.0/gaiad-v24.0.0-darwin-amd64?checksum=sha256:e1273a56fbb9f75b0b50a6a386e9c1172c9c38c57813c99974d9b2e1c02571fa\", \"darwin/arm64\": \"https://github.com/cosmos/gaia/releases/download/v24.0.0/gaiad-v24.0.0-darwin-arm64?checksum=sha256:d92ecc2a873b1e49bc7bb4dd712d91c0be8fa3ac71d93cdd91bd5df8267356f0\", \"linux/amd64\": \"https://github.com/cosmos/gaia/releases/download/v24.0.0/gaiad-v24.0.0-linux-amd64?checksum=sha256:9c50ed3188d4f7519bfa5a06b8a8311b8ac480e86cbba57722cd62b9c3baeb3a\"}}","upgraded_client_state":null}}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"124026914390689","abstain_count":"574623445270","no_count":"12629603058","no_with_veto_count":"9012444251"},"submit_time":"2025-05-30T20:04:16.432367582Z","deposit_end_time":"2025-06-13T20:04:16.432367582Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2025-05-30T20:11:39.965732750Z","voting_end_time":"2025-06-06T20:11:39.965732750Z","metadata":"ipfs://CID","title":"Gaia v24 Upgrade","summary":"## Background\n\nThis upgrade changes the LSM module to a refactored `x/liquid` module, which has been audited by Zellic. Docs for the module are available [here](https://github.com/cosmos/gaia/blob/main/x/liquid/README.md). This work is needed to get the Hub unforked from the SDK, which would reduce our technical debt and ease future development. After the migration in this upgrade, we can complete the unforking in Gaia v25, targeted for mid / late June.\n\nGaia v24.0.0 is a major release that will follow the regular governance process for software upgrades on the Cosmos Hub.\n\nReminder – This proposal will have a voting period of just **ONE WEEK**.\n\nIf the proposal passes, validators will be required to update the Cosmos Hub binary at the halt-height specified in the on-chain proposal.\n\n## Release Details\n\n- The release candidate can be found [here](https://github.com/cosmos/gaia/releases/tag/v24.0.0).\n- The changelog can be found [here](https://github.com/cosmos/gaia/blob/main/CHANGELOG.md).\n\n### DEPENDENCIES\n\n* Bump [http-proxy-middleware](https://github.com/chimurai/http-proxy-middleware) from 2.0.6 to 2.0.9 ([#3710](https://github.com/cosmos/gaia/pull/3710))\n* Bump [golang.org/x/crypto](https://github.com/golang/crypto) from 0.32.0 to 0.35.0 ([#3709](https://github.com/cosmos/gaia/pull/3709))\n* Bump [golang.org/x/crypto](https://github.com/golang/crypto) from 0.32.0 to 0.35.0 ([#3708](https://github.com/cosmos/gaia/pull/3708))\n* Bump `@docusaurus/core` from 2.4.3 to 3.7.0 ([#3693](https://github.com/cosmos/gaia/pull/3693))\n* Bump `@docusaurus/plugin-client-redirects` from 2.4.3 to 3.7.0 ([#3693](https://github.com/cosmos/gaia/pull/3693))\n* Bump `@docusaurus/plugin-google-analytics` from 2.4.3 to 3.7.0 ([#3693](https://github.com/cosmos/gaia/pull/3693))\n* Bump `@docusaurus/plugin-google-gtag` from 2.4.3 to 3.7.0 ([#3693](https://github.com/cosmos/gaia/pull/3693))\n* Bump `@react` from 17.0.2 to 18.0.0 ([#3693](https://github.com/cosmos/gaia/pull/3693))\n* Bump `@react-dom` from 17.0.2 to 18.0.0 ([#3693](https://github.com/cosmos/gaia/pull/3693))\n* Bump `@mdx-js/react` from 1.6.22 to 3.0.0 ([#3693](https://github.com/cosmos/gaia/pull/3693))\n* Bump [cosmossdk.io/store](https://github.com/cosmos/cosmos-sdk) from 1.1.1 to 1.1.2 ([#3687](https://github.com/cosmos/gaia/pull/3687))\n* Bump [image-size](https://github.com/image-size/image-size) from 1.1.1 to 1.2.1 ([#3684](https://github.com/cosmos/gaia/pull/3684))\n* Bump [cosmossdk.io/math](https://github.com/cosmos/cosmos-sdk) from 1.5.0 to 1.5.1 ([#3682](https://github.com/cosmos/gaia/pull/3682))\n* Bump [cosmossdk.io/log](https://github.com/cosmos/cosmos-sdk) from 1.5.0 to 1.5.1 ([#3681](https://github.com/cosmos/gaia/pull/3681))\n* Bump [cosmossdk.io/errors](https://github.com/cosmos/cosmos-sdk) from 1.0.1 to 1.0.2 ([#3680](https://github.com/cosmos/gaia/pull/3680))\n* Bump [github.com/spf13/viper](https://github.com/spf13/viper) from 1.19.0 to 1.20.0 ([#3651](https://github.com/cosmos/gaia/pull/3651))\n* Bump [github.com/cosmos/ibc-go/](https://github.com/cosmos/ibc-go) from 10.0.0 to 10.1.0 ([#3650](https://github.com/cosmos/gaia/pull/3650))\n* Bump [golang.org/x/net](https://github.com/golang/net) from 0.34.0 to 0.36.0 ([#3639](https://github.com/cosmos/gaia/pull/3639))\n* Bump [github.com/prometheus/client_golang](https://github.com/prometheus/client_golang) from 1.20.5 to 1.21.0 ([#3548](https://github.com/cosmos/gaia/pull/3548))\n\n### FEATURES\n\n* Add x/liquid module ([#3712](https://github.com/cosmos/gaia/pull/3712))\n* Remove expedited gov prop type restrictions ([#3723](https://github.com/cosmos/gaia/pull/3723))\n* Add liquid validator query to x/liquid ([#3735](https://github.com/cosmos/gaia/pull/3735))\n\n### BUG-FIXES\n\n* Set x/liquid params during InitGenesis ([#3759](https://github.com/cosmos/gaia/pull/3759))\n\n### STATE BREAKING\n\n* Add x/liquid module ([#3712](https://github.com/cosmos/gaia/pull/3712))\n\n**This upgrade is state-breaking and mandatory once the on-chain vote passes and the upgrade-height is reached.**\n\n## Testing and Testnets\n\nThe v24.0.0 release has gone through rigorous testing, including e2e tests, and integration tests by Interchain Labs. In addition, the upgrade process will be independently tested by the team at Hypha Co-op and will be performed by validators and node operators on a public testnet prior to cutting the final release.\n\nIf you wish to participate in the testnet upgrade process in the future, you can find the relevant information (genesis file, peers, etc.) to join the Cosmos Hub’s Interchain Security Testnet (provider) [here](https://github.com/cosmos/testnets/tree/master/interchain-security).\n\n### Potential risk factors\n\nAs with any major upgrade, there always exists a risk that the Cosmos Hub might experience problems due to potential bugs or errors, even though extensive testing and simulation has been completed. In the case of serious problems, validators should stop operating the network immediately.\n\nCoordination with validators will happen in the [#cosmos-hub-validators-verified](https://discord.com/channels/669268347736686612/798937713474142229) channel of the Cosmos Network Discord to create and execute a contingency plan. Likely this will be an emergency release with fixes or the recommendation to consider the upgrade aborted and revert back to the previous release of Gaia (v23.3.0).\n\n### Governance votes\n\nThe following items summarize the voting options and what it means for this proposal:\n\nYES - You agree that the Cosmos Hub should upgrade to v24.0.0.\n\nNO - You disagree that the Cosmos Hub should upgrade to v24.0.0.\n\nNO 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.\n\nABSTAIN - You wish to contribute to the quorum but you formally decline to vote either for or against the proposal.","proposer":"cosmos1az2sxspr9mfv407ay7ktcqjj57zre2dxcjecfd","expedited":false,"failed_reason":""},{"id":"999","messages":[{"@type":"/ibc.core.client.v1.MsgRecoverClient","subject_client_id":"07-tendermint-1157","substitute_client_id":"07-tendermint-1400","signer":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn"}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"108262410940087","abstain_count":"2781445305387","no_count":"21508351521","no_with_veto_count":"6305437254"},"submit_time":"2025-05-26T10:10:55.018479079Z","deposit_end_time":"2025-06-09T10:10:55.018479079Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2025-05-26T10:10:55.018479079Z","voting_end_time":"2025-06-02T10:10:55.018479079Z","metadata":"ipfs://CID","title":"Update Client: Revive client to Realio","summary":"This proposal will update the expired client on channel-645 between cosmoshub-4 and the realionetwork_3301-1 networks. In turn, this will allow users to transfer funds from Realio to Cosmos and vice versa.","proposer":"cosmos1ftkacrc7mdj0rm0y7krs6lefuu8png9v9jmpap","expedited":false,"failed_reason":""},{"id":"998","messages":[{"@type":"/cosmos.gov.v1.MsgUpdateParams","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","params":{"min_deposit":[{"denom":"uatom","amount":"500000000"}],"max_deposit_period":"1209600s","voting_period":"604800s","quorum":"0.400000000000000000","threshold":"0.500000000000000000","veto_threshold":"0.334000000000000000","min_initial_deposit_ratio":"0.100000000000000000","proposal_cancel_ratio":"0.500000000000000000","proposal_cancel_dest":"","expedited_voting_period":"259200s","expedited_threshold":"0.667000000000000000","expedited_min_deposit":[{"denom":"uatom","amount":"501000000"}],"burn_vote_quorum":false,"burn_proposal_deposit_prevote":false,"burn_vote_veto":true,"min_deposit_ratio":"0.010000000000000000"}}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"95700796006168","abstain_count":"4925405648447","no_count":"21027027035391","no_with_veto_count":"15889161449"},"submit_time":"2025-05-09T17:30:25.769310558Z","deposit_end_time":"2025-05-23T17:30:25.769310558Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2025-05-09T17:47:33.734150430Z","voting_end_time":"2025-05-23T17:47:33.734150430Z","metadata":"ipfs://CID","title":"Decrease voting period to 7 days and expedited voting period to 3 days","summary":"\r\n## Context\r\n\r\nThe current relevant governance parameters on the Hub are:\r\n```\r\nexpedited_voting_period: 604800s // 168h (7 days)\r\nvoting_period: 1209600s //  336h (14 days)\r\n```\r\n* [Prop 926](https://www.mintscan.io/cosmos/proposals/926) (passed on June 17, 2024) signalled overwhelming support for the use of 7-day-voting expedited proposals for software upgrades.\r\n* [Conversation around prop 926](https://forum.cosmos.network/t/proposal-926-voting-signaling-proposal-expedite-software-upgrade-proposals/13869) suggested support for an even shorter voting period.\r\n* [A forum discussion](https://forum.cosmos.network/t/proposal-draft-decrease-standard-voting-period-on-the-cosmos-hub/15013) in January 2025 suggested reducing the standard voting period to 7 days.\r\n* **Limitations**\r\n  * The expedited voting period must be less than the voting period.\r\n  * There are no gov params to set a separate **quorum** for expedited proposals.\r\n  * There is a gov param to set a separate **threshold** (% of YES votes out of total votes necessary to pass the proposal) for expedited proposals.\r\n  * Only software upgrade and cancel upgrade proposals are eligible to be expedited on the Hub. This is Hub-specific and can be changed in the gaia code in a future upgrade if we want.\r\n\r\n## Proposal\r\n\r\n* Reduce the Hub’s `standard voting_period` to 7 days.\r\n* Reduce the Hub’s `expedited_voting_period` to 3 days.\r\n\r\n## Rationale\r\n\r\n**Reducing the standard voting period to 7 days**\r\n\r\n* The Hub has had a 14 day voting period for years and has often struggled to reach 40% quorum on proposals without dedicated outreach from the proposal maker to validators via Telegram and other off-chain coordination platforms.\r\n* The norm for the Hub is to have at least 7 days of discussion on the forum, meaning that a proposal generally takes at least 3 weeks to progress from being posted to being passed (or rejected 🙃).\r\n* Expedited proposals with a 7 day voting period have been used on the Hub for software upgrade proposals since July 2024, with dedicated outreach and reminders from the proposal makers to reach quorum.\r\n* As of [prop 992](https://www.mintscan.io/cosmos/proposals/992) (March 2025), the Hub has proven itself capable of passing proposals in 7 days with only standard communications from the mainnet coordination team (one email, one Discord announcement).\r\n\r\n**Reducing the expedited voting period to 3 days**\r\n\r\n* No one likes doing manual halt height upgrades - they’re stressful, risky, and painful to coordinate and execute.\r\n* Using governance to set the halt height is the simplest and fastest patch solution - it doesn’t require any code contributions or new features (though Hypha and ICL will also be pursuing other solutions - please stay tuned for our retrospective on the last emergency upgrade).\r\n* 3 days is the fastest the Hub has ever been able to coordinate emergency action, so shifting that 3 days into an expedited proposal instead of communications makes sense and doesn’t represent a change in the actual time necessary for an emergency upgrade.\r\n\r\n## Responsibility to revert back to old params\r\nHypha will take responsibility for monitoring Hub governance and putting up a param change proposal to revert back to 7-day expedited and 14-day standard voting period if either of the following conditions are met in the 6 months after this proposal passes:\r\n\r\n1. A different solution is deployed which allows for a 3 day emergency upgrades and 7 day planned upgrades, and 14 day non-upgrade governance OR\r\n\r\n2. More than 10% of “real” non-software proposals fail to meet quorum (e.g., not spam, not proposals where validators mindfully chose not to vote).\r\n\r\nHypha's commitment is to solely to put up the proposal and work to bring it to quorum. We make no commitment to campaign either for a YES or NO vote, but will exercise our best judgement at the time of the proposal.\r\n\r\n## Governance votes\r\n\r\nThe following items summarize the voting options and what it means for this proposal:\r\n\r\n* YES - You support reducing the Hub’s voting period to 7 days and expedited voting period to 3 days.\r\n* NO - You do not support reducing the Hub’s voting period to 7 days and expedited voting period to 3 days.\r\n* 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.\r\n* ABSTAIN - You wish to contribute to the quorum but you formally decline to vote either for or against the proposal.","proposer":"cosmos1cc5mtuje84sx5dsqw4gtr4w8lthpzw02rjjnew","expedited":false,"failed_reason":""},{"id":"997","messages":[{"@type":"/cosmos.upgrade.v1beta1.MsgSoftwareUpgrade","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","plan":{"name":"v23.3.0","time":"0001-01-01T00:00:00Z","height":"25734200","info":"{\"binaries\": {\"darwin/amd64\": \"https://github.com/cosmos/gaia/releases/download/v23.3.0/gaiad-v23.3.0-darwin-amd64?checksum=sha256:baaa3580defa20afbb7fc982ca38559930ac178032e0d517805d5c2faf103d61\", \"darwin/arm64\": \"https://github.com/cosmos/gaia/releases/download/v23.3.0/gaiad-v23.3.0-darwin-arm64?checksum=sha256:f63214251b9f814e17977aa2b34b5e8119e3ad5d0b02936e3bca3be56d5b0cd9\", \"linux/amd64\": \"https://github.com/cosmos/gaia/releases/download/v23.3.0/gaiad-v23.3.0-linux-amd64?checksum=sha256:7c61b1d29b68749cf0d6ef5170b264a6050f42815e86f2ffdc154a4c04661047\"}}","upgraded_client_state":null}}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"118532590539217","abstain_count":"590852984025","no_count":"5181883868","no_with_veto_count":"579501598"},"submit_time":"2025-05-06T21:36:23.772624562Z","deposit_end_time":"2025-05-20T21:36:23.772624562Z","total_deposit":[{"denom":"uatom","amount":"506000000"}],"voting_start_time":"2025-05-06T22:19:20.252217042Z","voting_end_time":"2025-05-13T22:19:20.252217042Z","metadata":"ipfs://CID","title":"Gaia v23.3.0 Upgrade","summary":"## Summary\r\n\r\n* The `v23.3.0` upgrade patches a high-severity security issue. This issue poses no loss of funds risk.\r\n\r\n* This proposal has the expedited flag enabled and will have a voting period of just **ONE WEEK**.\r\n\r\n* If the proposal passes, validators will be required to update the Cosmos Hub binary at the specified upgrade height.\r\n\r\n## Release Details\r\n\r\n* The release can be found [here](https://github.com/cosmos/gaia/releases/tag/v23.3.0).\r\n* The changelog can be found [here](https://github.com/cosmos/gaia/blob/main/CHANGELOG.md#v2330).\r\n\r\nThis release adds no major features.\r\n\r\n**This upgrade is state-breaking and mandatory once the on-chain vote passes and the upgrade-height is reached.**\r\n\r\n### Governance votes\r\n\r\nThe following items summarize the voting options and what it means for this proposal:\r\n\r\nYES - You agree that the Cosmos Hub should be updated with this release.\r\n\r\nNO - You disagree that the Cosmos Hub should be updated with this release.\r\n\r\nNO 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.\r\n\r\nABSTAIN - You wish to contribute to the quorum but you formally decline to vote either for or against the proposal.","proposer":"cosmos1cc5mtuje84sx5dsqw4gtr4w8lthpzw02rjjnew","expedited":true,"failed_reason":""},{"id":"996","messages":[{"@type":"/cosmos.distribution.v1beta1.MsgUpdateParams","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","params":{"community_tax":"0.020000000000000000","base_proposer_reward":"0.000000000000000000","bonus_proposer_reward":"0.000000000000000000","withdraw_addr_enabled":true}}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"122369313020710","abstain_count":"5081160771920","no_count":"2167921590131","no_with_veto_count":"10577283335"},"submit_time":"2025-05-01T20:07:32.252748043Z","deposit_end_time":"2025-05-15T20:07:32.252748043Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2025-05-01T20:07:32.252748043Z","voting_end_time":"2025-05-15T20:07:32.252748043Z","metadata":"https://forum.cosmos.network/t/proposal-draft-reverse-proposal-88-revert-community-pool-tax-rate-to-2/15397","title":"Revert Community Pool Tax Rate to 2%","summary":"*Authors*: [Atom Accelerator DAO \u0026 Oversight Committee](https://www.atomaccelerator.com/) \n\n## Summary  \n\nThis `param-change` proposal aims to revert the `community_tax` parameter from 10% (0.10) to 2% (0.02), reinstating the baseline default rate that was in effect prior to [**Proposal 88**](https://www.mintscan.io/cosmos/proposals/88/).\n\n## Parameter Change\n\nThe proposed change affects the \"distribution module\" in the Cosmos SDK.\n\n**Parameter**: `community_tax`\n\n`community_tax`: Defines the percentage of block rewards (including transaction fees and inflation rewards) that is allocated to the Community Pool before the remainder is distributed to validators and delegators.\n\nThe `community_tax` has these key characteristics:\n\n* The value must be greater than 0 and less than or equal to 1.00 (100%).\n* The default value is set to 0.02 (2%) in the distribution module's default parameters. \n* Cosmos Hub governance can adjust this parameter through on-chain `param-change` proposals.\n\n**Parameter and Proposed Value**\n\n| Module         | Parameter      | Current Value | Proposed Value |\n|----------------|----------------|----------------|----------------|\n| `x/distribution` | `community_tax` | 0.10 (10%)     | 0.02 (2%)      |\n\n\n*If the parameter is set to*:\n\n0.02 → 2% of minted rewards go to the Community Pool\n\n0.10 → 10% of minted rewards go to the Community Pool\n\n\n## Background  \n\n[**Proposal 88**](https://www.mintscan.io/cosmos/proposals/88/) raised the community tax from 2% to 10% to enable long-term funding of the **Atom Accelerator DAO (AADAO)** and similar initiatives. This tax increase facilitated allocations of 588,000 ATOM via [**Proposal 95**](https://www.mintscan.io/cosmos/proposals/95/), and an additional 975,811 ATOM (plus 100,000 bonus ATOM) via [**Proposal 865**](https://www.mintscan.io/cosmos/proposals/865/).\n\nAs of Q1 2025, AADAO has entered \"maintenance mode\" and has declined to renew or revise its mandate; the conditions that warranted the 10% tax rate increase have become obsolete. \n\n\n## Rationale for Reversion to 2%\n\n1. **The Circumstances That Justified the Tax Rate Increase Are No Longer Valid**  \n\n   As the AADAO's funding mandate approaches its end, the basis for sustaining a 10% tax rate has ceased to be relevant.\n\n2. **Avoid Capital Oversupply and Misallocation**  \n\n   An excessive buildup of idle capital can attract value-extractive or poorly scoped spending proposals. \n\n\n3. **Decouple Tax Policy from Broader Governance Discussions**  \n\n   The Community Pool tax rate should reflect the network's actual operational needs, not serve as a default placeholder for unresolved Treasury discussions or opportunistic funding demands.\n\n\n4. **Preserve Hub Autonomy with Fiscal Discipline**  \n\n   A 2% tax rate maintains a credibly decentralized funding stream while keeping governance of the Hub's public resources **independent**, **sovereign**, **manageable** and **reasonable**.\n\n\n5. **Return More to Stakers**  \n\n   Assuming ~9.6 ATOM minted per block and ~4.36 million blocks/year:\n\n   - Reducing the tax from 10% to 2% returns **0.768 ATOM per block** to stakers.\n\n   - This results in approximately **3.34 million additional ATOM/year** in staking rewards.\n\n\n## **Clarification on Scope**  \n\nThis proposal **does not eliminate or reduce** existing Community Pool funds, which currently hold, approximately 9.37 million ATOM. Decisions concerning the **active balance**, **use**, **governance structure**, or **potential reforms** of the Community Pool should be addressed through subsequent and separate governance proposals.\n\n\n## **Conclusion**  \n\nReducing the community tax rate to 2% is a prudent adjustment in the absence of an active, governance-ratified funding mandate or mandates for the Cosmos Hub. This parameter change helps mitigate inadvertent capital accumulation, improves validator and staker economics, and strengthens fiscal discipline, while preserving the Hub's ability to fund public goods and services independently of its founding organizations and core teams. \n\nIt also sets a more appropriate baseline to guide future governance discussions concerning long-term treasury management and strategic capital deployment from the Community Pool.\n\n\n## Links\n\n* [**Cosmos Hub Forum Discussions**](https://forum.cosmos.network/t/proposal-draft-reverse-proposal-88-revert-community-pool-tax-rate-to-2/15397)\n* [**Cosmos SDK `x/distribution` module Documents**](https://docs.cosmos.network/main/build/modules/distribution)\n\n\n## **Voting Options**\n\n- **YES** – Supports the proposed parameter change, reducing the Community Pool tax rate to 2%.\n  \n- **NO** – Opposes the proposed parameter change, supports maintaining the Community Pool tax rate at 10%.\n\n- **ABSTAIN** – Chooses not to take a position, due to a conflict of interest or a wish to participate without expressing a preference.\n\n- **NO WITH VETO** – Opposes the proposed parameter change on the grounds it is (1) irrelevant to the Cosmos Hub, (2) malicious and or unjustly harms minority interests, or (3) violates Cosmos Hub governance rules and or norms.\n","proposer":"cosmos1trw7twjv4mqt0kwwysr4ad9njyh26y65m63qct","expedited":false,"failed_reason":""},{"id":"995","messages":[{"@type":"/cosmos.upgrade.v1beta1.MsgSoftwareUpgrade","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","plan":{"name":"v23.2.0","time":"0001-01-01T00:00:00Z","height":"25602300","info":"{\"binaries\": {\"darwin/amd64\": \"https://github.com/cosmos/gaia/releases/download/v23.2.0/gaiad-v23.2.0-darwin-amd64?checksum=sha256:07b48cdf8063e1edb401abf29d49689718dbe20c46f0e4d6f9fcd4ef3c13d5eb\", \"darwin/arm64\": \"https://github.com/cosmos/gaia/releases/download/v23.2.0/gaiad-v23.2.0-darwin-arm64?checksum=sha256:108e5f3ac534c1bea159c4d44010986112a7abc961823036187280c7d2288cbe\", \"linux/amd64\": \"https://github.com/cosmos/gaia/releases/download/v23.2.0/gaiad-v23.2.0-linux-amd64?checksum=sha256:c3733e6f5fac10d1c0a0beccb89f8f6133797880ffbc68ce0ea0f01115b0c48e\"}}","upgraded_client_state":null}}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"143509673049509","abstain_count":"577333535615","no_count":"8034064222","no_with_veto_count":"1610253181"},"submit_time":"2025-04-29T02:44:38.017862299Z","deposit_end_time":"2025-05-13T02:44:38.017862299Z","total_deposit":[{"denom":"uatom","amount":"501000000"}],"voting_start_time":"2025-04-29T02:50:08.435274529Z","voting_end_time":"2025-05-06T02:50:08.435274529Z","metadata":"ipfs://CID","title":"Gaia v23.2.0 Upgrade","summary":"## Proposal\r\n\r\nOn May 7th, Ethereum has a hard fork, the Pectra upgrade, which introduces changes that require the current Ethereum light client to be migrated to function with this hard fork.\r\n\r\nThis proposal upgrades the Cosmos Hub chain binary with a migrated Ethereum light client that will function with the new hard fork by providing the block height that the client will transition to the consensus mechanism used in the Pectra fork.\r\n\r\n## Motivation\r\n\r\n\r\nIBC Eureka launched on the Hub before a block height was provided for the Pectra fork, hence the Ethereum light client could not be instantiated with the block height of the hard fork already specified.\r\n\r\nWithout a migration, when the hard fork takes place, the IBC connection between Ethereum and the Hub would be suspended, as the Ethereum light client will freeze.\r\n\r\nTherefore this migration is necessary to avoid downtime, and maintain the connection’s liveness.\r\n\r\n**This upgrade is state-breaking and mandatory once the on-chain vote passes and the upgrade-height is reached.**\r\n\r\n## Governance votes\r\n\r\nThe following items summarize the voting options and what it means for this proposal:\r\n\r\n**YES** - You support upgrading the Ethereum light client to support the Pectra hard fork and keep the Ethereum \u003c\u003e Hub IBC connection live.\r\n\r\n**NO** - You do not support upgrading the Ethereum light client to support the Pectra hard fork, and want the Ethereum light client to freeze, causing IBC downtime.\r\n\r\n**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.\r\n\r\n**ABSTAIN** - You wish to contribute to the quorum but you formally decline to vote either for or against the proposal.","proposer":"cosmos1cc5mtuje84sx5dsqw4gtr4w8lthpzw02rjjnew","expedited":true,"failed_reason":""},{"id":"994","messages":[{"@type":"/interchain_security.ccv.provider.v1.MsgRemoveConsumer"}],"status":"PROPOSAL_STATUS_FAILED","final_tally_result":{"yes_count":"144900432967901","abstain_count":"4585560184334","no_count":"20570951863","no_with_veto_count":"10386063060"},"submit_time":"2025-04-21T19:18:18.062591401Z","deposit_end_time":"2025-05-05T19:18:18.062591401Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2025-04-29T17:44:27.231406156Z","voting_end_time":"2025-05-13T17:44:27.231406156Z","metadata":"ipfs://CID","title":"Change neutron-1’s consumer chain phase to STOPPED","summary":"# Change neutron-1’s consumer chain phase to STOPPED\r\n\r\n## Context\r\n* [Proposal 993](https://www.mintscan.io/cosmos/proposals/993) signalled the Hub's acceptance of Neutron ending the provider-consumer relationship established by[ Proposal 792](https://www.mintscan.io/cosmos/proposals/792) and [Proposal 72](https://www.mintscan.io/cosmos/proposals/72).\r\n* `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. \r\n* 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`).\r\n* 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 \u003cvalcon address\u003e` .\r\n* `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.\r\n* There is no direct risk from retaining the `neutron-1` consumer chain record.\r\n* It is confusing for mainnet queries to return inaccurate information.\r\n## Proposal\r\n* This proposal, if passed, will update Neutron's consumer chain record in the Hub to mark it as stopped.\r\n* The `neutron-1` chain will show up after a `list-consumer-chains` query with phase `CONSUMER_PHASE_STOPPED`.\r\n* Validators will no longer see it in their has-to-validate query.\r\n## Testing\r\nThis offboarding process has been tested by Hypha on the provider testnet.\r\n* `pion-1` graduated to being a sovereign testnet on March 27, 2025.\r\n* Governance proposal to remove pion-1 as a consumer chain[ here](https://explorer.polypore.xyz/provider/gov/256).\r\n* `pion-1` shows up after a `list-consumer-chains` query with phase `CONSUMER_PHASE_STOPPED`.\r\n* Validators no longer see it in their has-to-validate query.\r\n## Governance votes\r\nThe following items summarize the voting options and what it means for this proposal:\r\n* YES - You support changing `neutron-1`'s consumer chain record phase to STOPPED.\r\n* NO - You do not support changing `neutron-1`'s consumer chain record phase to STOPPED.\r\n* 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.\r\n* ABSTAIN - You wish to contribute to the quorum but you formally decline to vote either for or against the proposal.","proposer":"cosmos1cc5mtuje84sx5dsqw4gtr4w8lthpzw02rjjnew","expedited":false,"failed_reason":"chain with consumer id: 0 has to be in its launched phase: cannot perform action in the current phase of consumer chain"},{"id":"993","messages":[{"@type":"/cosmos.distribution.v1beta1.MsgCommunityPoolSpend","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","recipient":"cosmos1fl657t883v2l3s953qngd26wn49v8eddygw9rc44v5ms0cxfwk4qddhuhx","amount":[{"denom":"ibc/0025F8A87464A471E66B234C4F93AEC5B4DA3D42D7986451A059273426290DD5","amount":"40567950000000"}]}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"118292824508278","abstain_count":"4944784020521","no_count":"263073892631","no_with_veto_count":"8819699690"},"submit_time":"2025-03-26T19:04:18.318300152Z","deposit_end_time":"2025-04-09T19:04:18.318300152Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2025-03-26T19:04:18.318300152Z","voting_end_time":"2025-04-09T19:04:18.318300152Z","metadata":"Neutron and the Hub: A new chapter","title":"Neutron and the Hub: A new chapter","summary":"### Overview\n\n- Support Neutron’s graduation to a sovereign network with strong synergies with the Hub\n- Allocate community pool NTRN fairly to support the network’s migration and the adoption of on-chain use cases for ATOM and Hub-related assets\n- Signal support for the development of differentiated and complementary on-chain ecosystems on Neutron and the Hub\n- Enable continued collaboration to drive the adoption of ATOM, Neutron, and the Hub’s interchain services\n\nSee the sister proposal on the Neutron forum here: https://forum.neutron.org/t/mercury-towards-the-integrated-endgame/393\n\nIf this proposal is approved by Cosmos Hub governance, the Neutron Foundation has committed to return 50,000 ATOM received as part of [Proposal 72](https://forum.cosmos.network/t/proposal-72-accepted-bringing-liquid-staking-and-defi-to-the-cosmos-hub-with-interchain-security/6623) to the Cosmos Hub Community Pool.  \n\n### Graduation to a Sovereign Network\n\nThis proposal signals support for Neutron's graduation to a fully sovereign network via the Mercury upgrade. \n\nFrom a technical point of view, the migration does not require any code changes on the Cosmos Hub side. Once completed, it will enable the removal of the Replicated Security and Top-N code from the Cosmos Hub binary. Partial Set Security will remain a feature of the Cosmos Hub.\n\nThe graduation process will require a Neutron network upgrade, dubbed Mercury, which will be scheduled via [a sister proposal](https://forum.neutron.org/t/mercury-towards-the-integrated-endgame/393) to the Neutron DAO.\n\nTo ensure a smooth migration, Cosmos Hub validators must continue to validate the Neutron network until the Mercury upgrade (scheduled for the 9th of April) is completed and the core teams confirm that the validator set transition has occurred properly. This will ensure that IBC channels are properly migrated and continue to operate smoothly, safeguarding user funds and protocols across the Interchain.\n\nThis proposal allocates 1M NTRN to Cosmos Hub validators as a reward for their continued service over the coming weeks to perform the network's transition. The distribution of the rewards will occur after the upgrade is complete and will be coordinated by the Joint Committee (see below). Rewards will be conditioned upon maintaining \u003e 95% uptime for both block production and price updates and successfully carrying out the migration. \n\nAdditionally, this proposal allocates 10.8M NTRN to fund the security budget of the network for the next 2 years and enable the continued payment of the post-migration validator set, composed of leading Cosmos Hub validators:\n\n*CryptoCrew, Quokka Stake, Allnodes, Chorus One, cosmosrescue, Cosmostation, Crosnest, Golden Ratio Staking, Hadron Labs, Informal Systems, iqlusion, Kiln, P2P, Polkachu, POSTHUMAN, Provalidator, SG-1, Smart Stake, Stake\u0026Relax, Stakecito.*\n\nOn-going validator set curation with be carried out by the Neutron DAO and Drop protocol. \n\nAdditionally, the collection of validator performance data is being finalized by Numia, and Slinky Beta incentives will be distributed shortly, as planned in [Proposal 931](https://forum.cosmos.network/t/proposal-931-slinky-beta-proposal/13931). \n\n### New Rewards \u0026 Opportunities for ATOM on Neutron\n\nThis proposal allocates 4,272,795 NTRN to the adoption of ATOM and Cosmos Hub products on Neutron. These tokens will be distributed to ATOM token holders who participate in DeFi on Neutron via dedicated campaigns around ATOM use cases, including liquid staking, liquidity provisioning, lending, borrowing, using ATOM and its derivatives as collateral to trade perpetual futures, tributes, and more. \n\nOnce this proposal is executed, the Neutron Foundation (NF) will coordinate with ecosystem protocols to coordinate on-chain campaigns, and NTRN budgets will be allocated by the Joint Committee (see below). These campaigns will provide ATOM holders with new opportunities to use ATOM in DeFi and earn outsized rewards.\n\n### Return Excess Tokens to the Neutron DAO\n\nThis proposal allocates ~53% of the NTRN currently held in the Cosmos Hub community pool to be distributed to ATOM token holders and validators. The remaining ~47% will be transferred back to the Neutron DAO to fund the continued growth of the network and its ecosystem. \n\n### Return [Prop 72](https://forum.cosmos.network/t/proposal-72-accepted-bringing-liquid-staking-and-defi-to-the-cosmos-hub-with-interchain-security/6623) ATOM to the Cosmos Hub Community Pool\n50,000 ATOM were granted by the Cosmos Hub to contributors of the Neutron Project as part of [Proposal 72](https://forum.cosmos.network/t/proposal-72-accepted-bringing-liquid-staking-and-defi-to-the-cosmos-hub-with-interchain-security/6623) and later transferred to the Neutron Foundation as part of [Proposal 819](https://forum.cosmos.network/t/proposal-819-approved-re-allocate-prop-72-funding-from-p2p-to-neutron/11087). The Neutron Foundation never sold ATOM. Instead, it liquid staked its holdings with Stride, then with Drop to support the adoption of ATOM liquid staking. \n\nIn the spirit of fairness, if this proposal is adopted by Cosmos Hub governance, the Neutron Foundation commits to returning the 50,000 ATOM to the Cosmos Hub Community Pool.\n\n### Continued Collaboration\n\nThis proposal lays the foundation for the continued collaboration of the Neutron and Cosmos Hub teams and communities to create on-chain use cases and demand for the ATOM token and the Cosmos Hub’s products:\n\n- The NF has developed deep knowledge and expertise in ecosystem bootstrapping and will be supporting Interchain Labs’ (ICL) efforts to bootstrap a native ecosystem of new, exciting protocols in and around ATOM and the Cosmos Hub.\n- The continued growth of the Neutron ecosystem will drive demand for ATOM and the Cosmos Hub’s bridging, routing, and solving products, driving value to the Cosmos Hub and the ATOM token.\n- The NF and ICL teams will collaborate to drive the adoption and growth of the Cosmos developer community, accelerating the growth of both networks.\n\n\n# Implementation\n\n---\n\n### NTRN Allocations\n\nThe Cosmos Hub Community Pool received 42,727,950 unclaimed tokens from Neutron’s airdrop. The proposed allocations only concern the airdropped tokens and are summarized below for clarity: \n\n| Item | Amount | % | Destination |\n| --- | --- | --- | --- |\n| Existing programs | 2,160,000 | 5.06% | Already distributed. |\n| Migration coverage | 1,000,000 | 2.34% | Joint committee |\n| Security budget | 10,800,000 | 25.28% | Joint committee |\n| ATOM incentives  | 4,272,795 | 10.00% | Joint committee |\n| Future partnerships | 4,272,795 | 10.00% | Joint committee |\n| Neutron DAO | 20,222,360 | 47.33% | Joint committee |\n| Total | 42,727,950 | 100.00% | NA |\n\n### Joint Committee\n\nThis proposal transfers 40,567,950 NTRN from the Cosmos Hub to an Joint Committee made of representatives from both the Cosmos Hub and Neutron communities. Upon the receipt of the NTRN tokens, the committee will allocate the tokens according to the allocations above.\n\n- 20,222,360 NTRN will be returned to the Neutron DAO\n- 10,800,000 NTRN will be transferred to the validator payment module\n- 9,545,590 NTRN will be retained in the committee’s treasury to fund ATOM/Cosmos Hub-related campaigns on Neutron as well as the continued collaboration of the network communities.\n\nThe Joint Committee is a 3/4 multisig on the Cosmos Hub and Neutron networks, which commands the allocation of NTRN tokens received from the Cosmos Hub community pool and is composed of the following representatives from the Neutron and Cosmos Hub community:\n\n| Signer | Role | Address |\n| --- | --- | --- |\n| Travis | Cosmos Hub Community Representative | cosmos1hpqgpfsrkqawzjjgql47rrrvkqrry49sxpda7q |\n| @agent.kwosh | Cosmos Hub Community Representative | cosmos1945wsvenrnc6vu0p588jswpc56pv27l3kp0aae |\n| @luisqa | Neutron contributor | cosmos1ze09kc5ackut7wc4pf38lysu45kfz3ms86w3em |\n| @Spaydh | Neutron contributor | cosmos1nu7h4xj3em8mr0huh7906qdv89fnxclr7jy8wy |\n\nThe multisig addresses are the following: \n\n- Cosmos Hub: cosmos1fl657t883v2l3s953qngd26wn49v8eddygw9rc44v5ms0cxfwk4qddhuhx\n- Neutron: neutron1gxwkypgj884n2gswk3km0ck5js36eqewgx94lxv0pw45w0q6utrsgj4u50\n\n# Allocations breakdown\n\n### **Honor Existing Commitments (Connect Beta + Validator Incentives)**\n\nValidator Incentives that have already been allocated to vesting contracts are slated to fully vest on March 26th, 2025.\n\nConnect incentives remain to be distributed. We are finalizing work with Numia to provide the data required to check the validator’s performance and distribute the rewards. Once that is done, we will coordinate with the prop 931 committee signers to execute the transfer. \n\n### **Fund Validator Operations Leading Up to Migration**\n\nSince the migration’s success relies on smooth validator operations, we propose to allocate an additional 1M NTRN to be distributed to validators pro-rata their voting power based on the following criteria: \n\n- ≥ 50% participation on the last 10 Cosmos Hub proposals\n- ≥ 95% block uptime on Neutron over the past 3 months, looking back from migration time\n- ≥ 95% Slinky uptime on Neutron over the past 3 months, looking back from migration time\n- Properly carry out the migration upgrade\n\n### **Fund Neutron’s Security Budget Following Migration**\n\nTo migrate from ICS, Neutron will need to bootstrap a sovereign validator set and fund its operations. Most/all of this set will be inherited from the best/most aligned Cosmos Hub validators. \n\nTokens will be allocated to the Base Comp mechanism to cover validator costs for the first 24 months of the network’s operations as an independent blockchain. \n\n### **Fund ATOM-related Campaigns on Neutron**\n\nTo sponsor the continued alignment of the projects and their communities, ~4M NTRN will be reserved for incentives/campaigns tailored to the Cosmos Hub’s assets and community. \n\n- Liquidity incentives to ATOM, dATOM, and other Cosmos Hub assets\n- Incentives to cover the opportunity cost of converting from native staking to liquid staking\n- ATOM spot and perps trading campaigns\n- Other ATOM-aligned campaigns\n\n### **Allocation for Future Joint Ventures**\n\nTokens earmarked to support future joint ventures benefiting both ecosystems, such as supporting the growth and adoption of Cosmos, joint hacker houses and hackathons, etc.\n\n### **Return Excess to the Neutron DAO**\n\nThe remainder will be returned to the Neutron DAO Treasury.\n\n# Governance votes\n\nThe following items summarize the voting options and what it means for this proposal:\n\n**YES** - You support Neutron’s migration to a sovereign network, the proposed allocation of Community Pool NTRN, and the return of 50K ATOM from [Proposal 72](https://forum.cosmos.network/t/proposal-72-accepted-bringing-liquid-staking-and-defi-to-the-cosmos-hub-with-interchain-security/6623) to the Cosmos Hub Community Pool. \n\n**NO** - You disagree Neutron’s migration to a sovereign network and/or the proposed allocation of Community Pool NTRN.\n\n**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.\n\n**ABSTAIN** - You wish to contribute to the quorum but you formally decline to vote either for or against the proposal.\n","proposer":"cosmos1ymzwzma34enweastp7t7m7qg4zdl5ckkz9qx3y","expedited":false,"failed_reason":""},{"id":"992","messages":[{"@type":"/cosmos.upgrade.v1beta1.MsgSoftwareUpgrade","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","plan":{"name":"v23","time":"0001-01-01T00:00:00Z","height":"25002500","info":"{\"binaries\": {\"darwin/amd64\": \"https://github.com/cosmos/gaia/releases/download/v23.0.0/gaiad-v23.0.0-darwin-amd64?checksum=sha256:37e708dcd5529fc030bf7d886e66e6a6f6d6e1ca749a488c7900b24838f4b892\", \"darwin/arm64\": \"https://github.com/cosmos/gaia/releases/download/v23.0.0/gaiad-v23.0.0-darwin-arm64?checksum=sha256:334af0f75313f54ec167f6c844b4ecdddab07a0ade1a59804e6812315aa671ec\", \"linux/amd64\": \"https://github.com/cosmos/gaia/releases/download/v23.0.0/gaiad-v23.0.0-linux-amd64?checksum=sha256:03b2d0f96bcef0b86676974b8edff55116feae2183ded828d392d0c9df94eeff\"}}","upgraded_client_state":null}}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"129902188183627","abstain_count":"14036660829","no_count":"22514746187","no_with_veto_count":"4228158616"},"submit_time":"2025-03-18T19:23:25.722445602Z","deposit_end_time":"2025-04-01T19:23:25.722445602Z","total_deposit":[{"denom":"uatom","amount":"949900000"}],"voting_start_time":"2025-03-18T20:18:31.941707342Z","voting_end_time":"2025-03-25T20:18:31.941707342Z","metadata":"ipfs://CID","title":"Gaia v23 Upgrade","summary":"## Background\r\n\r\nGaia v23 is a major release that will follow the standard governance process for software upgrades on the Cosmos Hub. Feedback on this proposal will be open for roughly 1 week. \r\n\r\nReminder – the Cosmos Hub uses expedited voting for software upgrade proposals. This proposal will have a voting period of just **ONE WEEK**.\r\n\r\nIf the proposal passes, validators will be required to update the Cosmos Hub binary at the halt-height specified in the on-chain proposal.\r\n\r\n## Release Details\r\n\r\n**We are targeting the upgrade for Wednesday, March 26th**. After the upgrade Interchain Labs will upload the Eureka contracts and officially launch the Eureka product later in March.\r\n\r\n- The release can be found [here](https://github.com/cosmos/gaia/releases/tag/v23.0.0).\r\n- The changelog can be found [here](https://github.com/cosmos/gaia/blob/v23.0.0/CHANGELOG.md).\r\n\r\nThis release includes an upgrade to [IBC v2](https://ibcprotocol.dev/blog/ibc-v2-announcement), which is needed for the [launch of the **IBC Eureka product**.](https://x.com/cosmoshub/status/1897229986706415952) This will allow the Cosmos Hub to connect to Ethereum mainnet over IBC in an affordable and secure manner. In the future, we plan to connect IBC Eureka, and thus the Hub to Solana and to Layer 2s such as Arbitrum and Base.\r\n\r\nThe release bumps the following dependencies:\r\n\r\n* [ibc-go](https://github.com/cosmos/ibc-go) to [v10.1.0](https://github.com/cosmos/ibc-go/tree/v10.1.0)\r\n* [ibc-apps/modules/rate-limiting](https://github.com/cosmos/ibc-apps/tree/main/modules/rate-limiting) to [v10.0.0](https://github.com/cosmos/ibc-apps/tree/modules/rate-limiting/v10.0.0)\r\n* [ibc-apps/middleware/packet-forward-middleware](https://github.com/cosmos/ibc-apps/tree/main/middleware/packet-forward-middleware) to [v10.0.0](https://github.com/cosmos/ibc-apps/tree/middleware/packet-forward-middleware/v10.0.0)\r\n* [ibc-go/modules/light-clients/08-wasm](https://github.com/cosmos/ibc-go/tree/main/modules/light-clients/08-wasm) to [v10.0.0](https://github.com/cosmos/ibc-go/tree/modules/light-clients/08-wasm/v10.0.0)\r\n* [interchain-security](https://github.com/cosmos/interchain-security) to [v7.0.0](https://github.com/cosmos/interchain-security/tree/v7.0.0)\r\n\r\n**This upgrade is state-breaking and mandatory once the on-chain vote passes and the upgrade-height is reached.**\r\n\r\n### Additional note:\r\nThe WASM light client for Ethereum will not be ready before this proposal goes on-chain. In order to prevent an additional upgrade to be needed, we're adding an Authz permission to the v23 upgrade in order to allow `cosmos1raa4kyx5ypz75qqk3566c6slx2mw3qzs5ps5du` to upload (but not modify!) the light client. The specific message being granted is `/ibc.lightclients.wasm.v1.MsgStoreCode`\r\n\r\n## Testing and Testnets\r\n\r\nThe v23 release has gone through rigorous testing, including e2e tests, and integration tests by Interchain Labs. In addition, the v23 upgrade process has been independently tested by the team at Hypha Co-op and has been performed by validators and node operators on a public testnet prior to cutting the final release.\r\n\r\nIf you wish to participate in the testnet upgrade process in the future, you can find the relevant information (genesis file, peers, etc.) to join the Cosmos Hub’s Interchain Security Testnet (provider) [here](https://github.com/cosmos/testnets/tree/master/interchain-security).\r\n\r\n### Potential risk factors\r\n\r\nAs with any major upgrade, there always exists a risk that the Cosmos Hub might experience problems due to potential bugs or errors, even though extensive testing and simulation has been completed. In the case of serious problems, validators should stop operating the network immediately.\r\n\r\nCoordination with validators will happen in the [#cosmos-hub-validators-verified](https://discord.com/channels/669268347736686612/798937713474142229) channel of the Cosmos Network Discord to create and execute a contingency plan. Likely this will be an emergency release with fixes or the recommendation to consider the upgrade aborted and revert back to the previous release of gaia (v22.3.1).\r\n\r\n### Governance votes\r\n\r\nThe following items summarize the voting options and what it means for this proposal:\r\n\r\nYES - You agree that the Cosmos Hub should launch IBC Eureka and be upgraded with this release.\r\n\r\nNO - You disagree that the Cosmos Hub should launch IBC Eureka and be updated with this release.\r\n\r\nNO 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.\r\n\r\nABSTAIN - You wish to contribute to the quorum but you formally decline to vote either for or against the proposal.","proposer":"cosmos1az2sxspr9mfv407ay7ktcqjj57zre2dxcjecfd","expedited":true,"failed_reason":""},{"id":"991","messages":[{"@type":"/cosmos.distribution.v1beta1.MsgCommunityPoolSpend","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","recipient":"cosmos1hj9zuecf0xcjhx8ttcrwd9pmee25xe2plglgcpfk2kjjveet3zyq9nellq","amount":[{"denom":"ibc/F663521BF1836B00F5F177680F74BFB9A8B5654A694D0D2BC249E03CF2509013","amount":"57530000000"}]}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"86172357008249","abstain_count":"37853653253233","no_count":"48222774368","no_with_veto_count":"16705708167"},"submit_time":"2025-03-05T15:56:12.217908035Z","deposit_end_time":"2025-03-19T15:56:12.217908035Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2025-03-05T15:56:12.217908035Z","voting_end_time":"2025-03-19T15:56:12.217908035Z","metadata":"Community Pool USDC deployment via Hydro","title":"Community Pool USDC deployment via Hydro","summary":"## Summary \n\n This proposal aims to allocate excess USDC from the Cosmos Hub community pool into Hydro, a decentralized liquidity management platform on Cosmos, to optimize treasury utilization and generate additional yield. By leveraging Hydro’s structured liquidity deployment mechanism, the Hub can explore new financial strategies, earn tributes and rewards, and establish a framework for effective stablecoin management within the ecosystem. \n\n Currently, the community pool holds **57,530.40 USDC**, which remains idle. Rather than leaving these assets unused, we propose deploying them in Hydro’s decentralized bidding system, where various DeFi protocols compete for liquidity through incentive-based mechanisms. This will provide the Hub with valuable experience in managing stablecoins and ensuring that more assets within the community pool are working to benefit the ecosystem and ultimately, **ATOM holders**. \n\n ## Background \n\n The Cosmos Hub community pool primarily consists of **ATOM and NTRN**, alongside a smaller allocation of **USDC**. While ATOM has been successfully deployed in DeFi applications offering use cases such as AMM liquidity provisioning, lending, and perpetual protocols, the **USDC remains unused**. \n\n Hydro has established itself as a decentralized, voting-based liquidity management platform, where DeFi protocols compete for liquidity through **token-based or point-based tributes**. This structure ensures that the liquidity is allocated optimally to generate the highest returns and utility for the Hub. \n\n Hydro is a decentralized liquidity management platform that facilitates: \n\n - **Bidding-based liquidity distribution:** DeFi protocols bid for Hydro liquidity and offer token-based or point-based tributes in return. \n\n - **Voting mechanisms:** ATOM holders lock their ATOM on Hydro to vote on liquidity distribution. \n\n - **Proven track record:** Hydro has successfully completed three rounds of liquidity deployment with over **10 participating bidders**, including **Nolus, Mars, Drop, Demex, Neptune Finance, Shade, Stride, White Whale, Phoenix Directive, Marginated, Inter Protocol, and Amulet**. \n\n ## Proposal Details  \n\n ### Objective \n\n The primary objective of this proposal is to deploy **57,530 USDC** currently in the community pool into **Hydro** to: \n\n - Generate yield from tributes and rewards. \n\n - Enhance treasury diversification strategies by utilizing non-ATOM assets in DeFi. \n\n - Prepare for potential future stablecoin holdings in the Hub’s treasury. \n\n ### Implementation Plan \n\n 1. **Transfer the 57,530 USDC to the Hydro committee's address: cosmos1hj9zuecf0xcjhx8ttcrwd9pmee25xe2plglgcpfk2kjjveet3zyq9nellq** to be used for Hydro's liquidity allocation system. \n\n 2. **Engage in the Hydro bidding process**, allowing protocols to compete for the Hub’s liquidity. Notably, **Nolus** has expressed a clear interest in acquiring more USDC for their stablecoin lending pools, which in recent months have experienced a **surge in utilization levels, often exceeding 90%**. This increased demand has resulted in lenders receiving **consistent real yield at approximately 14% APY**. Given this strong demand and sustainable returns, Nolus presents itself as a promising recipient of USDC liquidity through Hydro. \n\n 3. **Monitor and assess returns** generated through tributes and rewards. \n\n 4. **Provide the community with a post-deployment report** on performance, feasibility, and lessons learned. \n\n ### Benefits to Hub \n\n - **Tribute generation:** The Cosmos Hub holders who participate in Hydro get an additional yield on their staked ATOM - so far the additional Hydro APR has been around **10%**. \n\n - **Yield Generation:** Idle USDC will be put to work, earning rewards from various DeFi protocols. \n\n - **Treasury Diversification:** This initiative will provide insights into managing stablecoin assets in the community pool, making the Cosmos Hub **better positioned to handle a scenario** where the pool holds a greater proportion of stablecoins. \n\n - **Leverage Existing Expertise:** Hydro has an **established governance framework** and experience in liquidity management, reducing the risk of inefficient deployment. \n\n ## Notes \n\n - **This is not a request to deploy the USDC directly to Nolus** or any other interested protocol: if this proposal passes, the custody of the **USDC would be transferred to the Hydro committee**, and many Cosmos projects (including Nolus) would be able to bid on it for the benefit of the Cosmos Hub. \n\n - **This is not a funding request for the development of the Hydro protocol:** The Hydro team and the Hydro grant program were **funded for the next 6 months via Prop 986**. The USDC would remain in the **custody of the Hydro committee** and can be returned in full to the Cosmos Hub community pool **at any time in the future**. \n\n ## Conclusion \n\n Deploying the **stale USDC** from the Cosmos Hub community pool through **Hydro** presents an opportunity to generate **passive yield within a secure risk framework** and explore **innovative treasury management strategies**. By leveraging Hydro’s platform, the Cosmos Hub can take a significant step toward **sustainable treasury growth while maintaining security and decentralization**. \n\n ## Governance \n\n - **Yes:** You approve the transfer of **57,530 USDC** from the community pool to the Hydro committee for deployment into Cosmos DeFi via the Hydro protocol. \n\n - **No:** You do not approve that transfer. \n\n - **No with Veto:** You indicate that this 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. \n\n - **Abstain:** You wish to contribute to the **quorum**, but you decline to vote either for or against.","proposer":"cosmos17rjgmry3w2xcc8yer4h4m8vuypkhkh8h0pvcyf","expedited":false,"failed_reason":""},{"id":"990","messages":[{"@type":"/cosmwasm.wasm.v1.MsgUpdateParams","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","params":{"code_upload_access":{"permission":"AnyOfAddresses","addresses":["cosmos1raa4kyx5ypz75qqk3566c6slx2mw3qzs5ps5du","cosmos19pmppgpqnjkvjp6mx8q2dpuy382g4hhxatt9sk","cosmos1559zgk3mxm00qtr0zu2x5n4rh5vw704qaqj6ap"]},"instantiate_default_permission":"Everybody"}}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"112679711329531","abstain_count":"8379907881034","no_count":"1044513202141","no_with_veto_count":"11218486736"},"submit_time":"2025-02-25T17:15:45.737944268Z","deposit_end_time":"2025-03-11T17:15:45.737944268Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2025-02-25T17:32:10.825136702Z","voting_end_time":"2025-03-11T17:32:10.825136702Z","metadata":"ipfs://CID","title":"Allowlist Interchain Labs for Contract Deployments","summary":"TL;DR - In order to enable Skip:Go functionality on the Hub and support the expansion of IBC Eureka, Interchain Labs (ICL) is requesting to be allowed to upload CosmWasm (CW) contracts to the Hub without seeking governance approval for subsequent uploads. This dramatically improves the Hub feature development cycle and reduces the burden on validators and users as we can upgrade our software without halting the chain.\r\n\r\nYou can find the Skip:Go contract repo [here](https://github.com/skip-mev/skip-go-cosmwasm-contracts). The motivations and procedures for using this right are detailed below.\r\n\r\n## Motivation\r\n\r\nDeploying Skip:Go contracts will dramatically improve bridging UX as it enables the following:\r\n\r\n- Use of the Skip:Go API so that user intents can be solved\r\n- Faster-than-finality transfers through our solver network (under 30 seconds)\r\n- Usage of the Skip:Go widget for smooth deposits and withdrawals\r\n\r\nAs we are expanding IBC to Ethereum \u0026 beyond and want the Hub to play a significant role as the router to all networks outside of Cosmos, having these contracts on the Hub will be required in order for us to successfully expand IBC in an ATOM-aligned way. **Skip:Go is currently processing over 50% of all IBC traffic**. It's been integrated into dYdX and it powers all swaps on your Keplr and Leap wallets, among many other integrations.\r\n\r\nPreviously, Skip has been granted the same access on other chains as well, including [Osmosis](https://www.mintscan.io/osmosis/proposals/555), Stride, Pryzm. They've also deployed these contracts permissionlessly on Sei, Injective, Neutron and various other chains.\r\n\r\n## Future Deployments\r\n\r\nAs we aim to decrease the burden on validators and hope to streamline future development on the Hub, Interchain Labs would like to use this access to be able to deploy new contract-based products and services for the Hub after the community accepts a signaling proposal for each one. This is instead of adding these products and services to the Gaia binary. Ideally we'd be able to deploy bug fixes, quality of life improvements \u0026 minor features without a 2-3 week governance process.\r\n\r\nThis will significantly improve development cycles because:\r\n\r\n- There are no chain upgrades or halts needed for upgrading CW contracts\r\n- We can deploy fixes and improvements faster without having to go through governance, allowing a more iterative product approach\r\n- We can keep the Hub lean and safe by keeping non-critical software outside of the Gaia binary\r\n\r\n**Please note**: we will continue to seek governance approval for any new products or major changes we intend to deploy in the form of a **Signaling Proposal**. This current proposal is *not* a request to give ICL unfettered control over new feature launches on the Hub. Access can be revoked at any point in time through governance.\r\n\r\nThe address for allowlist access is `cosmos1raa4kyx5ypz75qqk3566c6slx2mw3qzs5ps5du` \r\n\r\n**Additional note**: the transaction includes two additional addresses, these are the previously allowlisted addresses in proposal [982](https://www.mintscan.io/cosmos/proposals/982) (Ark Protocol) and [944](https://www.mintscan.io/cosmos/proposals/944) (DAO DAO). This is a required step due to how parameter changes for CosmWasm work.\r\n\r\n### **Governance votes**\r\n\r\nThe following items summarize the voting options and what it means for this proposal:\r\n\r\n**YES** - You agree that Interchain Labs should be allowed to upload contracts\r\n\r\n**NO** - You disagree that Interchain Labs should be allowed to upload contracts\r\n\r\n**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.\r\n\r\n**ABSTAIN** - You wish to contribute to the quorum but you formally decline to vote either for or against the proposal.","proposer":"cosmos1az2sxspr9mfv407ay7ktcqjj57zre2dxcjecfd","expedited":false,"failed_reason":""},{"id":"989","messages":[{"@type":"/cosmos.distribution.v1beta1.MsgCommunityPoolSpend","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","recipient":"cosmos145q97pk7hsu6zzsqtkjttlnpk90h9g6y3wzhn3","amount":[{"denom":"uatom","amount":"3300000000"}]}],"status":"PROPOSAL_STATUS_REJECTED","final_tally_result":{"yes_count":"9739064917790","abstain_count":"55833303606602","no_count":"39036154286630","no_with_veto_count":"1929874168346"},"submit_time":"2025-02-24T22:18:02.600275727Z","deposit_end_time":"2025-03-10T22:18:02.600275727Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2025-02-24T22:18:02.600275727Z","voting_end_time":"2025-03-10T22:18:02.600275727Z","metadata":"{\"title\":\"Community Pool Spend - StarShuffler dApp\",\"summary\":\"# Proposal: Community Pool Spend - StarShuffler\\\\n\\\\n## Summary\\\\nI am requesting **3300 $ATOM** to build the smart-contract, relayer, and frontend for a ZK dApp for the Cosmos Hub. It will be called **StarShuffler**.\\\\n\\\\n## Details\\\\nThis proposal would cover:\\\\n- Creating the smart contract.\\\\n- Developing a minimal frontend (FE) to interact with the contract.\\\\n- Building a relayer.\\\\n- Making the FE and relayer deployable as a Docker container for self-hosting or Akash deployments for privacy.\\\\n\\\\nThe milestone completion time will vary depending on the permissionless CosmWasm Hub integration timeline, which is assumed to occur mid-year. I initially asked for the funds to be proxied by the new hub leadership, but due to the sensitivity of the project’s development, the request was politely declined. However, @mag does know my identity and we have had calls, so my progress can be tracked independent of an endorsement.\\\\n\\\\n## Milestones\\\\n1. **Create working MVP on Juno mainnet (or testnet):**\\\\nDevelop a working MVP that includes a functional frontend, relayer, and smart contract. This milestone is contingent upon demonstrating a successful deposit and withdrawal, along with making the code open-source.\\\\n*Estimated timeline:* 2 months.\\\\n\\\\n2. **Porting the smart contract to $ATOM:**\\\\nPort the smart contract over to $ATOM and instantiate it.  \\\\n*Estimated timeline:* 2 weeks post permissionless CosmWasm integration onto the Hub.\\\\n3. **Integrate multi-amount pools:**\\\\nAdd support for multi-amount pools (e.g., 100 \u0026 1000 ATOM).\\\\n*Estimated timeline:* 2 weeks post milestone #2.\\\\n\\\\nThis effort will produce a usable app for the Hub and is relatively low-cost.\\\\n\\\\nI am currently designing the contract as feeless. The relayer deployment will have the option for fees for sustainability if community members want to run relayers. Having a feeless contract is motivated by both liability concerns and personal ethics.\\\\n\\\\n*Note on Audits:*\\\\nAudits are where the serious money comes into play; I have been quoted upwards of **20k** for simple audits. Therefore, I have no current plans to contract an audit, and an audit would only be conducted with community support at a later time.\\\\n\\\\n## Recipient\\\\ncosmos145q97pk7hsu6zzsqtkjttlnpk90h9g6y3wzhn3\\\\n\\\\n## Further Discussion\\\\nThe full forum discussions (3) are all linked [here](https://forum.cosmos.network/t/community-pool-spending-proposal-for-starshuffler/15165).\",\"forum\":\"https://forum.cosmos.network/t/community-pool-spending-proposal-for-starshuffler/15165\"}","title":"Community Pool Spend - StarShuffler dApp","summary":"# Proposal: Community Pool Spend - StarShuffler\\n\\n## Summary\\nI am requesting **3300 $ATOM** to build the smart-contract, relayer, and frontend for a ZK dApp for the Cosmos Hub. It will be called **StarShuffler**.\\n\\n## Details\\nThis proposal would cover:\\n- Creating the smart contract.\\n- Developing a minimal frontend (FE) to interact with the contract.\\n- Building a relayer.\\n- Making the FE and relayer deployable as a Docker container for self-hosting or Akash deployments for privacy.\\n\\nThe milestone completion time will vary depending on the permissionless CosmWasm Hub integration timeline, which is assumed to occur mid-year. I initially asked for the funds to be proxied by the new hub leadership, but due to the sensitivity of the project’s development, the request was politely declined. However, @mag does know my identity and we have had calls, so my progress can be tracked independent of an endorsement.\\n\\n## Milestones\\n1. **Create working MVP on Juno mainnet (or testnet):**\\nDevelop a working MVP that includes a functional frontend, relayer, and smart contract. This milestone is contingent upon demonstrating a successful deposit and withdrawal, along with making the code open-source.\\n*Estimated timeline:* 2 months.\\n\\n2. **Porting the smart contract to $ATOM:**\\nPort the smart contract over to $ATOM and instantiate it.  \\n*Estimated timeline:* 2 weeks post permissionless CosmWasm integration onto the Hub.\\n3. **Integrate multi-amount pools:**\\nAdd support for multi-amount pools (e.g., 100 \u0026 1000 ATOM).\\n*Estimated timeline:* 2 weeks post milestone #2.\\n\\nThis effort will produce a usable app for the Hub and is relatively low-cost.\\n\\nI am currently designing the contract as feeless. The relayer deployment will have the option for fees for sustainability if community members want to run relayers. Having a feeless contract is motivated by both liability concerns and personal ethics.\\n\\n*Note on Audits:*\\nAudits are where the serious money comes into play; I have been quoted upwards of **20k** for simple audits. Therefore, I have no current plans to contract an audit, and an audit would only be conducted with community support at a later time.\\n\\n## Recipient\\ncosmos145q97pk7hsu6zzsqtkjttlnpk90h9g6y3wzhn3\\n\\n## Further Discussion\\nThe full forum discussions (3) are all linked [here](https://forum.cosmos.network/t/community-pool-spending-proposal-for-starshuffler/15165).","proposer":"cosmos1hgrhzkhfjr4rkumxzcrnpddd4qmddnc4lsmezc","expedited":false,"failed_reason":"proposal did not get enough votes to pass"},{"id":"988","messages":[{"@type":"/cosmos.upgrade.v1beta1.MsgSoftwareUpgrade","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","plan":{"name":"v22.2.0","time":"0001-01-01T00:00:00Z","height":"24592000","info":"{\"binaries\": {\"darwin/amd64\": \"https://github.com/cosmos/gaia/releases/download/v22.2.0/gaiad-v22.2.0-darwin-amd64?checksum=sha256:23d4c33f19f304ae07f055f34a63a91ca204e0a7c2f5754754bb79aef84f5c55\", \"darwin/arm64\": \"https://github.com/cosmos/gaia/releases/download/v22.2.0/gaiad-v22.2.0-darwin-arm64?checksum=sha256:ed571c31a13e77a27117555f86ccc8880fe8200c4ec13b8e8ea0f4682fe19c79\", \"linux/amd64\": \"https://github.com/cosmos/gaia/releases/download/v22.2.0/gaiad-v22.2.0-linux-amd64?checksum=sha256:496bdcb74851634840b7300bc1ab486e274e708ea4c7937030ec3ee238cc0936\"}}","upgraded_client_state":null}}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"122472565928884","abstain_count":"580659759225","no_count":"18433682672","no_with_veto_count":"3526036380"},"submit_time":"2025-02-14T22:14:47.457704806Z","deposit_end_time":"2025-02-28T22:14:47.457704806Z","total_deposit":[{"denom":"uatom","amount":"501000000"}],"voting_start_time":"2025-02-14T22:54:33.322196334Z","voting_end_time":"2025-02-21T22:54:33.322196334Z","metadata":"ipfs://CID","title":"Gaia v22.2.0 Upgrade","summary":"## **Background**\r\n\r\nGaia v22.2.0 is a minor state breaking release that will follow an accelerated governance process for software upgrades on the Cosmos Hub. This is a state breaking security fix, which is why a forum post has been skipped.\r\n\r\nReminder – the Cosmos Hub uses expedited voting for software upgrade proposals. This proposal will have a voting period of just **ONE WEEK**.\r\n\r\nIf the proposal passes, validators will be required to update the Cosmos Hub binary at the halt-height specified in the on-chain proposal.\r\n\r\n## **Release Details**\r\n\r\n- The release page can be found [here](https://github.com/cosmos/gaia/releases/tag/v22.2.0).\r\n- The changelog can be found [here](https://github.com/cosmos/gaia/blob/v22.2.0/CHANGELOG.md).\r\n\r\nThe release bumps the following dependencies:\r\n\r\n- Bump [ibc-apps/middleware/packet-forward-middleware](https://github.com/cosmos/ibc-apps/tree/main/middleware/packet-forward-middleware) to [v8.1.1](https://github.com/cosmos/ibc-apps/releases/tag/middleware%2Fpacket-forward-middleware%2Fv8.1.1) ([#3534](https://github.com/cosmos/gaia/pull/3534))\r\n- Add `v22.2.0` upgrade handler ([#3538](https://github.com/cosmos/gaia/pull/3538))\r\n\r\n**This is a state breaking upgrade!**\r\n\r\n## **Testing and Testnets**\r\n\r\nThe v22.2.0 release has gone through rigorous testing, including e2e tests, and integration tests by Interchain Labs. In addition, the v22.2.0 upgrade process has been independently tested by the team at Hypha Co-op. If additional issues are found while this proposal is on-chain, we will communicate our intention to cancel the upgrade proposal.\r\n\r\n### **Potential risk factors**\r\n\r\nAlthough extensive testing and simulation will have taken place there always exists a risk that the Cosmos Hub might experience problems due to potential bugs or errors. In the case of serious problems, validators should stop operating the network immediately.\r\n\r\nCoordination with validators will happen in the [#cosmos-hub-validators-verified](https://discord.com/channels/669268347736686612/798937713474142229) channel of the Cosmos Network Discord to create and execute a contingency plan. Likely this will be an emergency release with fixes.\r\n\r\n### **Governance votes**\r\n\r\nThe following items summarize the voting options and what it means for this proposal:\r\n\r\n**YES** - You agree that the Cosmos Hub should be updated with this release.\r\n\r\n**NO** - You disagree that the Cosmos Hub should be updated with this release.\r\n\r\n**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.\r\n\r\n**ABSTAIN** - You wish to contribute to the quorum but you formally decline to vote either for or against the proposal.","proposer":"cosmos1az2sxspr9mfv407ay7ktcqjj57zre2dxcjecfd","expedited":true,"failed_reason":""},{"id":"987","messages":[{"@type":"/cosmos.upgrade.v1beta1.MsgSoftwareUpgrade","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","plan":{"name":"v22","time":"0001-01-01T00:00:00Z","height":"24181000","info":"{\"binaries\": {\"darwin/amd64\": \"https://github.com/cosmos/gaia/releases/download/v22.0.0/gaiad-v22.0.0-darwin-amd64?checksum=sha256:4cca58005d1d9201f61df0f52f81695c9c0955faf2a4ae4e680344c23b0458cc\",\"darwin/arm64\":\"https://github.com/cosmos/gaia/releases/download/v22.0.0/gaiad-v22.0.0-darwin-arm64?checksum=sha256:480e5fed24da19457d3937767541c2bfaec679ea60633737dec0a83d2b6a6af3\",\"linux/amd64\":\"https://github.com/cosmos/gaia/releases/download/v22.0.0/gaiad-v22.0.0-linux-amd64?checksum=sha256:e2d4eb6bfdc91294cb0a43eb9ffbfb160c3b99a057e5e09b5dacae8e58410a04\"}}","upgraded_client_state":null}}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"116887895709101","abstain_count":"10992119530","no_count":"18210840236","no_with_veto_count":"8651224994"},"submit_time":"2025-01-17T20:30:30.389376455Z","deposit_end_time":"2025-01-31T20:30:30.389376455Z","total_deposit":[{"denom":"uatom","amount":"501000000"}],"voting_start_time":"2025-01-17T20:43:50.450810322Z","voting_end_time":"2025-01-24T20:43:50.450810322Z","metadata":"ipfs://CID","title":"Gaia v22 Software Upgrade","summary":"## Background\r\n \r\nGaia v22 is a major release that will follow the standard governance process for software upgrades on the Cosmos Hub. Feedback on this proposal will be open for roughly 1 week.\r\n \r\nReminder – the Cosmos Hub uses expedited voting for software upgrade proposals. This proposal will have a voting period of just **ONE WEEK**.\r\n \r\nIf the proposal passes, validators will be required to update the Cosmos Hub binary at the halt-height specified in the on-chain proposal.\r\n \r\n## Release Details\r\n \r\n* The release candidate can be found[ here](https://github.com/cosmos/gaia/releases/tag/v22.0.0).\r\n* The changelog can be found[ here](https://github.com/cosmos/gaia/blob/v22.0.0/CHANGELOG.md).\r\n \r\nThis release adds no major features.\r\n \r\nThe release bumps the following dependencies:\r\n \r\n* Bump [ibc-go](https://github.com/cosmos/ibc-go) to [v8.5.2](https://github.com/cosmos/ibc-go/releases/tag/v8.5.2) ([#3370](https://github.com/cosmos/gaia/pull/3370))\r\n* Bump [cometbft](https://github.com/cometbft/cometbft) to [v0.38.15](https://github.com/cometbft/cometbft/releases/tag/v0.38.15) ([#3370](https://github.com/cosmos/gaia/pull/3370))\r\n* Bump [cosmos-sdk](https://github.com/cosmos/cosmos-sdk) to [v0.50.11-lsm](https://github.com/cosmos/cosmos-sdk/releases/tag/v0.50.11-lsm) ([#3454](https://github.com/cosmos/gaia/pull/3454))\r\n* Bump [wasmd](https://github.com/CosmWasm/wasmd) to [v0.53.2](https://github.com/CosmWasm/wasmd/releases/tag/v0.53.2) ([#3459](https://github.com/cosmos/gaia/pull/3459))\r\n* Bump [ICS](https://github.com/cosmos/interchain-security) to [v6.4.0](https://github.com/cosmos/interchain-security/releases/tag/v6.4.0). ([#3474](https://github.com/cosmos/gaia/pull/3474))\r\n \r\n**This upgrade is state-breaking and mandatory once the on-chain vote passes and the upgrade-height is reached.**\r\n \r\n## Testing and Testnets\r\n \r\nThe v22 release has gone through rigorous testing, including e2e tests, and integration tests by Informal Systems. In addition, the v22 upgrade process has been independently tested by the team at Hypha Co-op and has been performed by validators and node operators on a public testnet prior to cutting the final release.\r\n \r\nIf you wish to participate in the testnet upgrade process in the future, you can find the relevant information (genesis file, peers, etc.) to join the Cosmos Hub's Interchain Security Testnet (provider) [here](https://github.com/cosmos/testnets/tree/master/interchain-security).\r\n \r\n### Potential risk factors\r\n \r\nAlthough extensive testing and simulation will have taken place there always exists a risk that the Cosmos Hub might experience problems due to potential bugs or errors. In the case of serious problems, validators should stop operating the network immediately.\r\n \r\nCoordination with validators will happen in the[ #cosmos-hub-validators-verified](https://discord.com/channels/669268347736686612/798937713474142229) channel of the Cosmos Network Discord to create and execute a contingency plan. Likely this will be an emergency release with fixes or the recommendation to consider the upgrade aborted and revert back to the previous release of gaia (v21.0.1).\r\n \r\n### Governance votes\r\n \r\nThe following items summarize the voting options and what it means for this proposal:\r\n \r\nYES - You agree that the Cosmos Hub should be updated with this release.\r\n \r\nNO - You disagree that the Cosmos Hub should be updated with this release.\r\n \r\nNO 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.\r\n \r\nABSTAIN - You wish to contribute to the quorum but you formally decline to vote either for or against the proposal.","proposer":"cosmos1az2sxspr9mfv407ay7ktcqjj57zre2dxcjecfd","expedited":true,"failed_reason":""},{"id":"986","messages":[{"@type":"/cosmos.distribution.v1beta1.MsgCommunityPoolSpend","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","recipient":"cosmos1jskgwzken05wjflz2f92hn3apa0pql6nxtj947dtlqwrkk88q8pq35gtq5","amount":[{"denom":"uatom","amount":"180000000000"}]}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"74010324136602","abstain_count":"60614965192088","no_count":"4131969387608","no_with_veto_count":"49205831551"},"submit_time":"2025-01-10T16:01:25.881366176Z","deposit_end_time":"2025-01-24T16:01:25.881366176Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2025-01-10T17:40:09.370644751Z","voting_end_time":"2025-01-24T17:40:09.370644751Z","metadata":"[v2] Funding Hydro development \u0026 integrations in 2025","title":"[v2] Funding Hydro development \u0026 integrations in 2025","summary":"## Note\nThis proposal supersedes [Prop #984](https://www.mintscan.io/cosmos/proposals/984), which doesn't include the requested amount of ATOM and won’t transfer any funds when executed (see the transaction hash of the proposal creation [here](https://www.mintscan.io/cosmos/tx/0488ADC4956A52C8220127CE79E3C72FCEA42D602C6250FB348AF2D2EA1A2D8A)).\n\nTherefore, we recommend to cast a Yes vote on Prop #984 (which won't execute anyway), as well as this proposal.\n\n\n## Introduction\nIn November 2023, the [Cosmos Hub funded Informal Systems for 2024](https://www.mintscan.io/cosmos/proposals/839). The Informal Hub team eliminated the Hub’s technical debt and shipped two products:\n- [Forge](https://forge.cosmos.network/) as a way to permissionlessly launch a chain, solving all the pain points of the past versions of ICS and making it possible for the Hub's validators to run it in a few clicks.\n- [Hydro](https://hydro.cosmos.network/) as the first decentralized market-maker. Hydro allocates liquidity through sequential auction rounds in which projects attract user votes with tributes\n\nThrough this process, it became obvious that [the Hub needed consolidated leadership](https://forum.cosmos.network/t/cosmos-hub-informal-systems/) to realize its full potential and Informal recruited one of the best teams in the Interchain to take up [the product ownership role](https://medium.com/the-interchain-foundation/cosmos-is-expanding-skip-joins-the-interchain-foundation-cfd346551dda). Although Informal’s Hub 2024 mandate officially ends on 31-Dec, with the recent success of the first pilot rounds, the Skip team asked the Hydro team to keep developing the product in 2025. \n\nSince the Informal Hub team is under budget in Q4 2024 (see the breakdown in the Funding \u0026 reporting section - the Informal Hub team was also under budget in Q1 \u0026 Q2 2024 and [returned these funds](https://x.com/informalinc/status/1830971210479607996) to the community pool), this proposal requests community approval to fund Hydro product development and some Hydro-focused grants for the first two quarters of 2025 by giving Informal a green light to re-assign [the excess Q4 2024](https://forum.cosmos.network/t/informal-hub-team-q4-24-retro/15024#p-34603-financial-transparency-reporting-10) budget to Hydro and approving the transfer of an additional 180,000 ATOM from the community pool.\n\nIn addition, since we believe that Hydro could be partly self-funded in the second half of 2025, we’re requesting community approval to send Hydro’s PoL profits to an account collectively owned by Hydro’s voters but placed under the control of the Cosmos Hub community (see the Hydro Treasury section for details).\n\n## Hydro Roadmap\nThe Hydro litepaper was published in [late May-2024](https://forum.cosmos.network/t/atom-wars-introducing-the-hydro-auction-platform/) and the inaugural pilot round started on [6-Nov](https://x.com/cosmoshub/status/1854234305909956717). To date, 10 projects have submitted bids and 8 third-party teams have also expressed interest in building DeFi apps on top of Hydro. The round 1 cap was reached within 24 hours and the round 2 cap in less than 4 minutes.\n\nIn the last couple of months, the Hydro team has also worked on several major updates:\n- **Custom deployment duration**: Projects can set their own export duration and voters can lock-in a fixed APR over several rounds without having to vote every time.\n- **Custom export floor**: Projects can set a minimum PoL target. If their bid doesn’t get sufficient support to reach that target, their tribute is refunded.\n- **Metrics page**: The position size, status and performance of each PoL deployment is tracked and displayed on a dedicated page.\n- **Rewards page**: Voters can see their tribute rewards and personalized APRs (current \u0026 past rounds). They can claim and automatically swap tokens to ATOM. \n- **Airdrops page**: Voters can see a list of upcoming airdrops for Hydro participants, and projects can easily access relevant data.\n\nThe custom deployment duration and custom export floor are critical for making Hydro more widely useful to larger projects. However, Hydro is still far from a finished product. \n- It relies on a committee for risk management, whitelisting \u0026 performance monitoring.\n- The incentive alignment between voters \u0026 the community pool is relatively weak.\n\nThe goal is to make Hydro a fully permissionless, automated, risk-minimizing \u0026 profit-maximizing system for efficient treasury management on a public blockchain. Hydro should be able to operate like Aave, Compound, or Curve: risk parameter approvals via governance votes, allocations via the auction system, and automatic deployments.\n\nOver the first 6 months of 2025, the Hydro team plans to work on the following features:\n\n\n\n| Feature | Description | \n| -------- | -------- | \n| Third-party integrations     | Vote optimizers, automated hedging contracts, insurance premium or escrow contracts can be built on top of Hydro to enable new cases    | \n| Valence integration | The Hub retains ownership of Hydro’s liquidity, making the committee less of a bottleneck and increasing the overall security \u0026 efficiency of the system. | \n| Token integrations | Hydro can be used for the deployment of new tokens ( NTRN, TIA, stables etc.), and projects can submit atomic bids to get both sides of an LP pair | \n| Rev-sharing \u0026 penalities | Voters get a portion of the PoL yield. A portion of the users' locked capital gets slashed when they vote for a project that underperforms. | \n| Hydro governance | Hydro users can vote on governance proposals to define all of the protocol parameters and elect or remove committee members | \n| Staking interface | Hydro users can stake, delegate, re-delegate, claim, swap and compound rewards directly from the Hydro interface | \n| “Just-in-time” liquidity | Hydro provides insurance against liquidity crunches by ensuring that buckets can be deployed quickly to stabilize a position or market. | \n\nNote that this is a working backlog that will be re-prioritized based on market signals and community feedback.\n\n## Budget\n### Product development\nThe Informal Hub team in 2024 consisted of 14 people, split between Forge, Hydro and Hub maintenance. For 2025, we believe it is possible to achieve our Hydro objectives with a reduced team of 6 Full-Time Equivalent staff: 1 Project Lead, 1 Technical Lead, 1 Product Lead, 2 Developers \u0026 1 Growth Lead. We will use the same per-head total rate averages of $325K per year, which includes approximately $225K in salary (and relevant overhead such as employer taxes and benefits) and a standard margin to pay for operational expenses like legal, HR, finance as well as some profit buffer for the company. Like last year, these rates are aligned with the mid-point of market software development rates ($110-$220/hour)\n\nThe entire overhead margin will be paid out in ATOMs for alignment purposes. In addition, our proposal will not include any performance bonus (Informal \u0026 Hypha 2024 proposal did). See the FAQ section for more details on these decisions. \n\n### Hydro grants\nTo become a fully permissionless \u0026 automated protocol, Hydro requires several DeFi \u0026 security integrations. While Hydro's core team itself could develop all the necessary features over time, a better option to achieve this goal as fast and cost-efficiently as possible is to enable other third-party teams to build products on top of Hydro. \n\n\n\n| Category | Budget |\n| -------- | -------- |\n| Vote optimizers     | Vote aggregators are smart contract applications that abstract the complexities of voting away from users, give them the benefits of long-term locking, provide them with a tradable liquid derivative, compete for maximal returns, etc.      |\n| Delta-neutral deployments | Automated strategies are required to avoid exposing the Hub deployments to impermanent loss. Hydro’s bidders can implement a delta-neutral strategy with a real-time adjustment mechanism via smart contracts, insurance, or over-collateralization |\n| Permissionless deployments | The Hub retains direct ownership of the liquidity, progressively reducing the need for the Hydro committee to manually deploy funds, enabling shorter and more competitive rounds, and increasing the system's overall security. |\n| Security | Third-party audits for the features developed by the Hydro product team. Security monitoring, threat detection system, and bug-bounty program for finding and reporting vulnerabilities on PoL venues. |\n\n\nOver the past couple of weeks, the Hydro team has been helping several Cosmos projects submit well-scoped grant proposals to the AADAO so their applications can be processed before the [end of the program](https://forum.cosmos.network/t/sunsetting-atom-accelerator-dao-aadao/). However, new teams / existing grantees are likely to step forward with other ideas during the coming months, and the Hydro team may also try to outsource “nice-to-have” features and support work (relaying, infrastructure, community) to external partners. For that reason, the proposal includes a $350,000 budget to manage an ecosystem fund that will support the initiatives listed in the table below (each item is a rough estimate and the final distribution may look significantly different). All outgoing transactions will be managed on-chain via DAO DAO and labeled for transparency. \n\n\n\n| Initiative | Budget | Amount |\n| -------- | -------- | -------- |\n| Hydro committee     | ~$90/h for six members for 6 months, 5-10h per member per month (adjusted up or down based on individual time commitment)     | $40,000     |\n| Vote optimizers     | ~$30,000 for smart contract development or audits for two separate teams (adjusted up or down based on a statement of work)     | $60,000     |\n| Automated hedging     | ~$30,000 for the smart contract development or audits (adjusted up or down based on a statement of work)     | $30,000     |\n| Insurance premiums     | ~$30,000 for the smart contract development or audits (adjusted up or down based on a statement of work)     | $30,000     |\n| Valence integration     | ~ $50,000 for a first integration of Valence into Hydro (adjusted up or down based on the exact scope)     | $50,000     |\n| Data services     | ~ $20,000 for the tracking of PoL deployments \u0026 rewards (adjusted up or down based on development \u0026 indexing costs)     | $20,000     |\n| Security audits     | ~ $25,000 per audit \u0026 1 per quarter from a reputable firm (adjusted up or down based on the exact scope)     | $50,000     |\n| Bug bounties     | ~ $10,000 per bug submission for up to five security issues during a six-month period     | $50,000     |\n| Miscellaneous      | ~ $20,000 for IBC relaying, security monitoring, infrastructure costs, software licenses and other miscellaneous expenses     | $20,000     |\n\nNote that the Hydro team submitted a $350,000 grant application to the AADAO, which was downsized to $75,000. The amount has been discounted from the ask (see Funding section below).\n\n## Hydro treasury\nThe rewards generated by the Hub’s PoL deployments are currently in the custody of the Hydro committee. The Hydro product team is planning to build out a governance module and equip it with the ability to hold and manage funds. \n\nThe purpose of the Hydro treasury is two-fold:\n- Ability to deploy the rewards via Hydro\n- Ability to fund development teams \n\nThe Hydro treasury transforms Hydro into a self-funded project and may eliminate the need for more community pool requests to the Hub community pool. The treasury would remain under the control of the Cosmos Hub via two mechanisms to be built into Hydro governance:\n- The ability for the Hub governance to veto any Hydro prop via an expedited proposal\n- The ability for the Hub governance to send the Hydro treasury to the community pool\n\nIf this proposal passes, the Hydro product team will transfer pre-Hydro and pilot rounds PoL rewards to a new public DAO on DAO DAO and start building the Hydro governance module and treasury. The DAO will initially be controlled by the product team and ownership will be transferred to Hydro’s governance as soon as it is technically possible. \n\n## Funding \u0026 reporting\n\n### Proposal request\nIn its [2024 funding proposal](https://www.mintscan.io/cosmos/proposals/839), the Informal Hub team planned for a total team of 14 full-time equivalents (FTE) per quarter:\n- In Q1 \u0026 Q2, the team was under budget and [returned funds](https://x.com/informalinc/status/1830971210479607996) to the community pool\n- In Q3, the team worked at full capacity to ship Forge \u0026 Hydro.\n- In Q4, the team was under budget again, using [only 10 FTE resources](https://forum.cosmos.network/t/informal-hub-team-q4-24-retro/15024#p-34603-financial-transparency-reporting-10).\n\nThe [excess budget](https://forum.cosmos.network/t/informal-hub-team-q4-24-retro/15024#p-34603-financial-transparency-reporting-10) represented by 4 FTE in Q4 is $225,714 USDC and 10,214.29 ATOM. We suggest assigning this funding to cover Hydro product development in the first half of 2025. Assuming 1 ATOM is worth $6.5 (and rounding conversion numbers), the breakdown is the following:\n\n\n\n| Budget line  | In USD | In ATOM |\n| -------- | -------- | -------- |\n| Hydro Team     | $975,000     | 150,000     |\n| Hydro Grants     | $350,000     | 55,000     |\n| Reassigned 2024 funding     | $-290,000     | -45,000     |\n| Temporary 20% buffer     | $207,000     | 31,000     |\n| AADAO grant     | $-75,000     | -11,000     |\n| **Total**     | $1,167,000     | 180,000     |\n\nThe funding request amount includes a 20% buffer to hedge against ATOM price movement (both for the reassigned Q4 2024 funding and the new 2025 funding):\n- If the ATOM price is exactly the same at the time of the Q1 \u0026 Q2 transfers as when the prop went up for voting, the entire 20% buffer will be sent to the Hydro treasury\n- If the ATOM price **decreases** less than 20%, the buffer will be used to cover the difference. If the ATOM price **increases**, the extra will be sent to the Hydro treasury. \n- If the ATOM price goes down more than 20%, the Hydro product team will request the difference to be covered by the Hydro treasury (see the description below).\n\n### Sequence of events\n\nFunding will be distributed on the following schedule:\n\n| Date | Action | \n| -------- | -------- | \n| On 24-Jan     | The total ask (including buffer) of 180,000 ATOMs is transferred from the community pool to the [Hydro Team DAO](https://daodao.zone/dao/cosmos1jskgwzken05wjflz2f92hn3apa0pql6nxtj947dtlqwrkk88q8pq35gtq5/home)     |\n| On 25-Jan     | The Hydro Team converts the relevant number of ATOM into 975,000 * 70% + 275,000 - 290,000 = 667,500 USDC and sends 275,000 USDC to the [Hydro Grants DAO](https://daodao.zone/dao/cosmos1stxad87r0c9x9skn5ap6eyx9wwmj5xuqcpd3n974qpg5stv92sqqj2zrh4/members)     | \n| Before 24-Jun     | The Hydro Team and Hydro Grants DAOs send all excess USDC \u0026 ATOM funds (including buffer) to the Hydro Treasury     | \n\n\nA new separate entity will receive the distributed funds. This new company (name \u0026 domicile to be determined) will be created specifically for Hydro product development. As a company, Informal Systems will be focusing on engineering services, security audits and public good development for devcos and foundations with clear service agreements.\n\nUndistributed funds can be clawed back via a proposal submitted by any community member (the tooling introduced by [Prop 972](https://www.mintscan.io/cosmos/proposals/972) could be used). Assuming funds are not clawed back before, all excess budget shall be sent to the Hydro Treasury at the end of the mandate.\n\n### Reporting\nA quarterly progress report will be shared on the Cosmos Hub forum by the Hydro development team, using the same format as the reporting done by the Informal Hub team (see [Q1 2024](https://forum.cosmos.network/t/informal-systems-q1-24-retro-q2-24-plan/13749), [Q2 2024](https://forum.cosmos.network/t/informal-hub-team-q2-24-retro-q3-24-plan/14158), [Q3 2024](https://forum.cosmos.network/t/informal-hub-team-q3-24-retro-q4-24-plan/14684), [Q4 2024](https://forum.cosmos.network/t/informal-hub-team-q4-24-retro/15024/1)).\n\n## Governance votes\n\n**Yes**: You approve the allocation of Informal Systems excess Q4 budget and an additional 180,000 ATOM from the community pool towards Hydro product development and integrations, and you approve the transfer of Hydro’s PoL rewards to the Hydro Treasury.\n\n**No**: You do not approve the suggested budget allocation and / or the transfer of Hydro’s PoL rewards to the Hydro Treasury.\n\n**No with Veto**: You indicate that this 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.\n\n**Abstain**: You wish to contribute to the quorum, but you decline to vote either for or against.","proposer":"cosmos1tvqum6psu8waphaatuau2gxpaay4z7zlntmhkv","expedited":false,"failed_reason":""},{"id":"985","messages":[{"@type":"/cosmos.distribution.v1beta1.MsgCommunityPoolSpend","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","recipient":"cosmos1ax7krw2ymq8upaxwce7df3xpalpp0jddm29fws","amount":[{"denom":"ibc/F663521BF1836B00F5F177680F74BFB9A8B5654A694D0D2BC249E03CF2509013","amount":"200000000000"},{"denom":"uatom","amount":"86538460000"}]}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"111904286531023","abstain_count":"25432852009059","no_count":"977830881339","no_with_veto_count":"17469784955"},"submit_time":"2025-01-09T20:15:56.955890109Z","deposit_end_time":"2025-01-23T20:15:56.955890109Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2025-01-09T21:42:22.330319622Z","voting_end_time":"2025-01-23T21:42:22.330319622Z","metadata":"ipfs://QmbUGTtewn3tVaYjw2ezDtzAC2s7SY2XgNibmAUUZQqC3b","title":"Fund testnets and mainnet ops by Hypha in 2025","summary":"# Fund testnets and mainnet ops by Hypha in 2025\r\n\r\n## Summary\r\n\r\nThe Hub testnets team at Hypha Worker Co-operative is seeking funding to continue their mandate of stewarding the Hub's testnet, supporting mainnet operations, and development support and onboarding for the incoming Hub team at Interchain Inc.\r\n\r\nThis proposal is summarized by the following propositions:\r\n\r\n* The approval of a $650,000 USD budget to finance Hypha's:\r\n  * Stewardship of the Hub's provider testnet as a dev platform and validator training program\r\n  * Mainnet coordination for upgrades and validators\r\n  * Coordination around bug fixes, security patches, and version updates for core technologies\r\n  * Mainnet ICS support for the Hub's current and prospective consumer chains\r\n  * Validation testing for core stack integrations and new features\r\n  * Testing and development support for patches and version update releases\r\n  * Onboarding and transition support for Skip/Interchain Inc.\r\n* The release of the following funds to a Hypha-controlled wallet (cosmos1ax7krw2ymq8upaxwce7df3xpalpp0jddm29fws):\r\n  * 200k USDC (shown in the spend proposal details as 200,000,000,000 IBC-wrapped uusdc)\r\n  * 86,538.46 ATOM (accounting for 69,230.77 ATOM at a spot price of \\$6.5 USD with a 25\\% buffer to cover price fluctuations) to be converted to \\$450k USDC via the process laid out in the full text of the proposal\r\n* The approval of Hypha's transparency and accountability commitment to the ATOM community:\r\n  * Quarterly reports made to the Cosmos Hub forum\r\n  * Quarterly withdrawal reports on community-disbursed funds\r\n  * An anonymous feedback form and commitment to publicly reviewing and incorporating relevant feedback\r\n  * Cooperation with the ATOM community if a signalling proposal is passed to return any unused funds\r\n  * Cooperation with teams chosen by the ATOM community to fulfil other scopes of work or to replace our services on the Hub\r\n\r\n## Additional details\r\n* [Full proposal text with changelog and discussion (forum post)](https://forum.cosmos.network/t/proposal-last-call-fund-testnets-and-mainnet-ops-by-hypha-in-2025/14929)\r\n* [IPFS pin of full text](https://ipfs.io/ipfs/QmbUGTtewn3tVaYjw2ezDtzAC2s7SY2XgNibmAUUZQqC3b) and comments\r\n\r\n## Governance votes and outcomes\r\n\r\nThe following items summarize the voting options and what it means for this proposal:\r\n\r\n* **YES**: You agree to fund the Hub testnets team at Hypha Worker Co-operative with a $650k USD budget for continued testnet stewardship, mainnet coordination, and development support over the period of January 1, 2025 - December 31, 2025. A 'YES' outcome will immediately release 200k USDC and 86,538.46 ATOM to the specified wallet (cosmos1ax7krw2ymq8upaxwce7df3xpalpp0jddm29fws).\r\n * **NO**: You do not agree to fund the Hub testnets team at Hypha Worker Co-operative based on the terms of this proposal.\r\n* **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.\r\n* **ABSTAIN**: You wish to contribute to the quorum but you formally decline to vote either for or against the proposal.\r\n","proposer":"cosmos1cc5mtuje84sx5dsqw4gtr4w8lthpzw02rjjnew","expedited":false,"failed_reason":""},{"id":"984","messages":[{"@type":"/cosmos.distribution.v1beta1.MsgCommunityPoolSpend","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","recipient":"cosmos1jskgwzken05wjflz2f92hn3apa0pql6nxtj947dtlqwrkk88q8pq35gtq5","amount":[]}],"status":"PROPOSAL_STATUS_FAILED","final_tally_result":{"yes_count":"25509131095644","abstain_count":"62233919051283","no_count":"25056637002271","no_with_veto_count":"49786681627"},"submit_time":"2025-01-09T01:32:15.244284891Z","deposit_end_time":"2025-01-23T01:32:15.244284891Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2025-01-09T01:32:15.244284891Z","voting_end_time":"2025-01-23T01:32:15.244284891Z","metadata":"{\"title\":\"Funding Hydro development \u0026 integrations in 2025\",\"summary\":\"This proposal requests community approval to fund Hydro product development and some Hydro-focused grants for the first two quarters of 2025 by giving Informal a green light to re-assign the excess Q4 2024 budget to Hydro and approving the transfer of an additional 180,000 ATOM from the community pool. In addition, since we believe that Hydro could be partly self-funded in the second half of 2025, we're requesting community approval to send Hydro's PoL profits to an account collectively owned by Hydro's voters but placed under the control of the Cosmos Hub community (see the Hydro Treasury section for details).\\n\\nThe full funding proposal details and discussion are available on the [Cosmos Hub Forum](https://forum.cosmos.network/t/funding-hydro-development-integrations-in-2025/14900/1).\\n\\n## Governance votes\\n- **Yes**: You approve the allocation of Informal Systems' excess Q4 budget and an additional 180,000 ATOM from the community pool towards Hydro product development and integrations, and you approve the transfer of Hydro's PoL rewards to the Hydro Treasury.\\n- **No**: You do not approve the suggested budget allocation and / or the transfer of Hydro's PoL rewards to the Hydro Treasury.\\n- **No with Veto**: You indicate that this 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.\\n- **Abstain**: You wish to contribute to the quorum, but you decline to vote either for or against.\",\"ipfs\":\"\",\"forum\":\"https://forum.cosmos.network/t/funding-hydro-development-integrations-in-2025/14900/1\"}","title":"Funding Hydro development \u0026 integrations in 2025","summary":"This proposal requests community approval to fund Hydro product development and some Hydro-focused grants for the first two quarters of 2025 by giving Informal a green light to re-assign the excess Q4 2024 budget to Hydro and approving the transfer of an additional 180,000 ATOM from the community pool. In addition, since we believe that Hydro could be partly self-funded in the second half of 2025, we're requesting community approval to send Hydro's PoL profits to an account collectively owned by Hydro's voters but placed under the control of the Cosmos Hub community (see the Hydro Treasury section for details).\n\nThe full funding proposal details and discussion are available on the [Cosmos Hub Forum](https://forum.cosmos.network/t/funding-hydro-development-integrations-in-2025/14900/1).\n\n## Governance votes\n- **Yes**: You approve the allocation of Informal Systems' excess Q4 budget and an additional 180,000 ATOM from the community pool towards Hydro product development and integrations, and you approve the transfer of Hydro's PoL rewards to the Hydro Treasury.\n- **No**: You do not approve the suggested budget allocation and / or the transfer of Hydro's PoL rewards to the Hydro Treasury.\n- **No with Veto**: You indicate that this 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.\n- **Abstain**: You wish to contribute to the quorum, but you decline to vote either for or against.","proposer":"cosmos1tvqum6psu8waphaatuau2gxpaay4z7zlntmhkv","expedited":false,"failed_reason":"amount cannot be nil: invalid coins"},{"id":"982","messages":[{"@type":"/cosmwasm.wasm.v1.MsgUpdateParams","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","params":{"code_upload_access":{"permission":"AnyOfAddresses","addresses":["cosmos19pmppgpqnjkvjp6mx8q2dpuy382g4hhxatt9sk"]},"instantiate_default_permission":"Everybody"}}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"99956992648490","abstain_count":"15469308036655","no_count":"824565621667","no_with_veto_count":"9751385759"},"submit_time":"2024-12-16T18:42:47.241293126Z","deposit_end_time":"2024-12-30T18:42:47.241293126Z","total_deposit":[{"denom":"uatom","amount":"500000000"}],"voting_start_time":"2024-12-16T23:47:23.279760380Z","voting_end_time":"2024-12-30T23:47:23.279760380Z","metadata":"Whitelist Ark Protocol Developer Wallet for InterChain NFT Contracts","title":"Whitelist Ark Protocol Developer Wallet for InterChain NFT Contracts","summary":"[Full Proposal Details on Cosmos Hub Forum](https://forum.cosmos.network/t/signalling-proposal-to-whitelist-the-deployment-of-interchain-nft-contracts/14806)\n\n## Introduction\n\nWith Prop 981 signaling strong community support, this Parameter Update Proposal authorizes Ark Protocol’s developer wallet to deploy InterChain NFT contracts on the Cosmos Hub. These contracts will enhance security, governance, and interoperability within the Cosmos ecosystem, while facilitating the seamless transfer of NFTs across app chains. The deployment includes initially three components:\n\n1. **NFT Contract (cw721) contracts:** A standardized and secure framework for creating and managing NFTs.\n2. **Bridge (ics721) contracts:** A robust interchain NFT bridge for seamless and secure cross-chain transfers.\n3. **Launchpad Contracts:** Empowering creators to launch NFTs using the Hub’s governance and security.\n\nThe contracts aim to establish the Cosmos Hub as a secure base for digital assets while boosting app chains like Stargaze, Osmosis, and Injective by enabling NFT transfers to marketplaces on other chains.\n\n## Driving Value to the Cosmos Hub\n\n1. **Security:** By hosting ICS721-compliant contracts, the Hub ensures the safe storage of digital assets and resilience against vulnerabilities, preventing scenarios like the UST depeg.\n2. **Governance:** Integration with **DAODAO** facilitates NFT-based governance models, enabling users to participate in decision-making using NFTs and $ATOM.\n3. **Ecosystem Growth:** Supporting creators, builders, and communities through seamless NFT transfers boosts activity and liquidity across app chains.\n4. **InterChain Collaboration:** These contracts are a public good for all chains, complementing app chains like Stargaze and fostering interchain growth and utility.\n\n## Security Measures\n\n- **Audited Contracts:** Independent audits by **Oak Security** and **SCV Security** validate the robustness of the InterChain NFT contracts.\n- **DAO Management:** Contracts are governed by **Admin Migration DAO** and **Operations DAO**, ensuring transparency and decentralization.\n- **Emergency Controls:** Proxy contracts, whitelisting mechanisms, and emergency pause functionality protect the ecosystem from vulnerabilities.\n\n## Acknowledgments\n\nWe extend our gratitude to **Stargaze**, the main driver of InterChain NFTs. We also thank **AADAO**, Michael Sotto, Shane, Jorge, Zerk, Noah, Zeke, Reece, JG, Hashimoto, Red Phone, Brian, Deploydon, NicsHODLN, whyre, addingbio, Simon, Vlad, Sunny, Jake, DoraHacks, Confio, the Galactic Syndicate, Mad Scientists, Red Planet, BackBone Labs, **Govmos**, SG1, Everstake, Allnodes, and the broader NFT community for their trust and contributions to this initiative.\n\n## Voting Options\n\n### Yes\nAuthorize Ark Protocol’s developer wallet to deploy InterChain NFT contracts on the Cosmos Hub.\n\n### No\nDo not authorize Ark Protocol’s developer wallet to deploy InterChain NFT contracts on the Cosmos Hub.\n\n### Abstain\nContribute to the quorum but formally decline to vote either for or against the proposal.\n\n### NoWithVeto\nIndicate that this proposal is spam, infringes on minority interests, or violates governance rules. If NoWithVeto votes exceed one-third, the proposal is rejected and deposits are burned.\n\nThis proposal is a significant step toward securing the Cosmos Hub as a backbone for NFTs, connecting communities, and enhancing app chain collaboration. Join us in shaping the future of interchain NFTs on the Cosmos Hub!","proposer":"cosmos19pmppgpqnjkvjp6mx8q2dpuy382g4hhxatt9sk","expedited":false,"failed_reason":""},{"id":"981","messages":[],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"99793992830531","abstain_count":"18142229526354","no_count":"57259708415","no_with_veto_count":"9837622367"},"submit_time":"2024-12-02T22:37:25.440712808Z","deposit_end_time":"2024-12-16T22:37:25.440712808Z","total_deposit":[{"denom":"uatom","amount":"275000000"}],"voting_start_time":"2024-12-02T23:44:47.138595954Z","voting_end_time":"2024-12-16T23:44:47.138595954Z","metadata":"Full proposal: https://forum.cosmos.network/t/signalling-proposal-to-whitelist-the-deployment-of-interchain-nft-contracts/14806","title":"[LAST CALL] Signalling Proposal to Whitelist the Deployment of InterChain NFT Contracts","summary":"## OVERVIEW\n\nThis proposal is a revised version of the Cosmos Hub forum post [here](https://forum.cosmos.network/t/signalling-proposal-to-whitelist-the-deployment-of-interchain-nft-contracts/14806).\n\n### SUMMARY\n\nAfter engaging with the community and addressing feedback, we have updated our proposal to align closely with the Cosmos Hub's mission and address concerns raised. Key points include:\n\n- **Strong Community Support:**\n  - Validators and community members such as **@Govmos** now support the proposal after clarifications.\n\n- **Alignment with the Cosmos Hub's Mission:**\n  - **Security Enhancement:**\n    - Storing NFTs on the Cosmos Hub leverages its robust security to protect valuable assets.\n    - Prevents potential losses like those experienced during the UST depeg on Terra.\n  - **Governance Enhancement:**\n    - Enables advanced governance models through platforms like **DAODAO**.\n    - Allows users to participate more actively using their NFTs and $ATOM holdings.\n\n- **Clarification of Intentions:**\n  - **Interchain NFTs as a Public Good:**\n    - Aiming to provide Interchain NFT capabilities to all chains, including the Hub, in a chain-agnostic manner.\n    - Supporting and accelerating the growth of the entire Cosmos ecosystem.\n\n  - **Complementing Existing Chains:**\n    - **Launch on the Hub, List on Stargaze, Injective, et al:**\n      - Our proposal enables creators to **mint NFTs on the Cosmos Hub** and **list them on marketplaces like Stargaze, BackBone Labs, Talis**, and others.\n      - We intend to enhance the ecosystem by fostering interoperability and collaboration across all chains.\n      - Our goal is to complement existing app chains, not compete with them.\n\n- **Security Measures and Risk Mitigation:**\n  - Implementation of robust security measures, including audited contracts and whitelisting mechanisms.\n  - Use of emergency controls to protect the Hub from potential threats.\n\nOverall, we have successfully addressed concerns and received strong support. Deploying the Interchain NFT contracts on the Cosmos Hub will enhance both security and governance, aligning with the Hub's mission and benefiting the entire Cosmos ecosystem.\n\n## Proposal Details\n\n**We propose to whitelist Ark Protocol’s developer wallet to enable the deployment of Interchain NFT contracts on the Cosmos Hub.**\n\n- **Contracts to be Deployed:**\n  - **Interchain Launchpad:** Contracts for minting NFTs on the Cosmos Hub from any chain, allowing creators to reach the entire Cosmos NFT community.\n  - **Interchain Bridge (ICS721):** Contracts for bridging CW721 NFTs between the Cosmos Hub and other chains.\n  - **NFT Contracts:** CW721 contracts for creating NFT collections.\n\n- **Whitelisted Developer Wallet:**\n  - **Team Wallet:** `cosmos19pmppgpqnjkvjp6mx8q2dpuy382g4hhxatt9sk`\n\n- **Security Measures:**\n  - **Audited Contracts:** Audits conducted by Oak Security and SCV Security.\n  - **DAO Management:**\n    - Admin Migrations DAO\n    - Operations DAO\n  - **Additional Measures:**\n    - Multi-signature mechanisms via DAODAO.\n    - Proxy contracts to enhance security during NFT transfers.\n    - Whitelisting mechanisms to ensure only legitimate collections/channels interact with the bridge.\n    - Emergency controls to pause the bridge and de-whitelist compromised chains/contracts.\n\n## Voting Options\n\n- **Yes**: You are in favor of allowing Ark Protocol to deploy the Interchain NFTs CosmWasm smart contracts on the Cosmos Hub.\n\n- **No**: You are against allowing Ark Protocol to deploy the Interchain NFTs CosmWasm smart contracts on the Cosmos Hub.\n\n- **Abstain**: You wish to contribute to the quorum but formally decline to vote either for or against the proposal.\n\n- **No With Veto**: A ‘No With Veto’ vote indicates a proposal either (1) is deemed to be spam, i.e., irrelevant to the 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 ‘No With Veto’ votes is greater than a third of total votes, the proposal is rejected and the deposits are burned.\n\nWe kindly request the support of the community and validators in voting **Yes** on this proposal to enhance the security and governance of the Cosmos Hub through the deployment of Interchain NFT contracts.\n\nThank you for your time and consideration.\n\n**Sincerely,**\n\n**The Ark Protocol Team**","proposer":"cosmos19pmppgpqnjkvjp6mx8q2dpuy382g4hhxatt9sk","expedited":false,"failed_reason":""},{"id":"980","messages":[{"@type":"/cosmos.gov.v1.MsgUpdateParams","authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn","params":{"min_deposit":[{"denom":"uatom","amount":"500000000"}],"max_deposit_period":"1209600s","voting_period":"1209600s","quorum":"0.400000000000000000","threshold":"0.500000000000000000","veto_threshold":"0.334000000000000000","min_initial_deposit_ratio":"0.100000000000000000","proposal_cancel_ratio":"0.500000000000000000","proposal_cancel_dest":"","expedited_voting_period":"604800s","expedited_threshold":"0.667000000000000000","expedited_min_deposit":[{"denom":"uatom","amount":"501000000"}],"burn_vote_quorum":false,"burn_proposal_deposit_prevote":false,"burn_vote_veto":true,"min_deposit_ratio":"0.010000000000000000"}}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"105925984928097","abstain_count":"2017457358853","no_count":"6384678892608","no_with_veto_count":"39903858788"},"submit_time":"2024-11-22T12:02:15.388739539Z","deposit_end_time":"2024-12-06T12:02:15.388739539Z","total_deposit":[{"denom":"uatom","amount":"250000000"}],"voting_start_time":"2024-11-22T15:35:32.470149795Z","voting_end_time":"2024-12-06T15:35:32.470149795Z","metadata":"","title":"Increase Deposit Amount for Cosmos Hub governance to 500 $ATOM","summary":"Full forum discussions can be found here: https://forum.cosmos.network/t/last-call-proposal-increase-deposit-amount-for-cosmos-hub-governance-to-500-atom/14493","proposer":"cosmos1la0mxx0cp7se7uvvrjuuhdfulv4mgst586ny4l","expedited":false,"failed_reason":""},{"id":"976","messages":[{"@type":"/ibc.core.client.v1.MsgRecoverClient","subject_client_id":"07-tendermint-764","substitute_client_id":"07-tendermint-1328","signer":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn"}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"96059151721723","abstain_count":"5421028361822","no_count":"55307104977","no_with_veto_count":"9778084359"},"submit_time":"2024-11-19T17:26:45.936809984Z","deposit_end_time":"2024-12-03T17:26:45.936809984Z","total_deposit":[{"denom":"uatom","amount":"252000000"}],"voting_start_time":"2024-11-25T09:53:41.573162807Z","voting_end_time":"2024-12-09T09:53:41.573162807Z","metadata":"","title":"~FIXED~ Recover expired IBC client for channel-341 to Bostrom","summary":"Revive channel-341 to bostrom by replacing expired 07-tendermint-764 client state to the state of client 07-tendermint-1328. This will restore channel-341 functionality. \nPlease ignore prop 975 as it contains the typo in the description.","proposer":"cosmos1cg79pj70mgl8xlum0rw5yy6enk9jszsrpl6hw5","expedited":false,"failed_reason":""},{"id":"974","messages":[],"status":"PROPOSAL_STATUS_REJECTED","final_tally_result":{"yes_count":"10151178572","abstain_count":"585964817753","no_count":"479607939766","no_with_veto_count":"104196863631859"},"submit_time":"2024-11-12T02:14:44.895422637Z","deposit_end_time":"2024-11-26T02:14:44.895422637Z","total_deposit":[{"denom":"uatom","amount":"250000000"}],"voting_start_time":"2024-11-12T02:14:44.895422637Z","voting_end_time":"2024-11-26T02:14:44.895422637Z","metadata":"{\"title\":\"💎Atom Airdrop ✅ - Bitcoin to $100k ⭐\",\"summary\":\"Get 💎ATOM Airdrop ✅ visiting url: [www.AtomWeb.at][1]\\n\\n⭐ Conditions: Try the new version visiting: [https://AtomWeb.at][1]\\n\\n1 - [ATOM Airdrop][1]\\n\\n2 - [ATOM Airdrop Available][1] 🪂\\n\\n3 - url: [www.AtomWeb.at][1]\\n\\n[1]: https://AtomWeb.at\\n\\n![](https://i.ytimg.com/vi/TyjlqCHzLGI/hq720.jpg?sqp=-oaymwEcCNAFEJQDSFXyq4qpAw4IARUAAIhCGAFwAcABBg==\u0026rs=AOn4CLBJkfmbe_m09TWSCuwyw1xONsXDsA)\",\"additional_link\":\"https://AtomWeb.at\"}","title":"💎Atom Airdrop ✅ - Bitcoin to $100k ⭐","summary":"Get 💎ATOM Airdrop ✅ visiting url: [www.AtomWeb.at][1]\n\n⭐ Conditions: Try the new version visiting: [https://AtomWeb.at][1]\n\n1 - [ATOM Airdrop][1]\n\n2 - [ATOM Airdrop Available][1] 🪂\n\n3 - url: [www.AtomWeb.at][1]\n\n[1]: https://AtomWeb.at\n\n![](https://i.ytimg.com/vi/TyjlqCHzLGI/hq720.jpg?sqp=-oaymwEcCNAFEJQDSFXyq4qpAw4IARUAAIhCGAFwAcABBg==\u0026rs=AOn4CLBJkfmbe_m09TWSCuwyw1xONsXDsA)","proposer":"cosmos1xq9wlnxsv8r92wpgktn3t9zvps0jlt6egk8pdu","expedited":false,"failed_reason":"proposal did not get enough votes to pass"},{"id":"972","messages":[{"@type":"/cosmos.gov.v1.MsgExecLegacyContent","content":{"@type":"/cosmos.gov.v1beta1.TextProposal","title":"Signaling proposal to allow Hub governance to execute clawbacks with ease","description":"Full forum discussion could be found [here](https://forum.cosmos.network/t/signaling-proposal-to-allow-hub-governance-to-execute-clawbacks-with-ease/14614).\n\n# Summary\n\nThis proposal aims to introduce a ‘Claw Back’ tooling that would allow the Cosmos Hub community to recall all funding provided to DAOs, like the Atom Accelerator DAO (AADAO), back to the Community Pool through an onchain governance vote.\n\nPlease note that this proposal is NOT calling for the immediate dissolution of AADAO. Recent events have prompted conversations in the community and the DAO about restructuring the organization, but this proposal is unrelated to those issues. This proposal is to modify DAODAO tooling such that any ATOM Community Pool funded DAOs’ assets can easily be clawed-back by governance, if and when needed.\n\n# Background\n\nThe Hub’s community is the true owner of AADAO’s assets and is the sovereign voice enabling it. Meaning that, at any moment, the community could choose to halt the DAO’s activities, claw back funding and dissolve Atom Accelerator.\n\n# Motivation\n\nThe community’s supreme authority, via onchain governance, over all of AADAO’s activities isn’t new and has been part of the DAO’s [Internal Protocols](https://www.atomaccelerator.com/about/internal-protocols/) since inception.\n\nThat being said, if a community member wanted to introduce a proposal to claw back funds and disband AADAO, the process would be suboptimal right now:\n\n- Lengthy process: it requires a signaling proposal, after which the AADAO Multi-Signature signers must coordinate to transfer the funds back to the Community Pool.\n- Technically challenging: Multi-Signature coordination failures could lead to frozen funds. For example: [Clawing back vested funds in Proposal 860](https://www.mintscan.io/cosmos/proposals/860) required a Software Upgrade.\n- Trust assumptions: In an ideal scenario, the Hub’s community shouldn’t be beholden to any additional trust assumption when it comes to governance-approved claw backs.\n\nIn order to eliminate unnecessary trust assumptions, account for technical failures and improve the process, AADAO has asked the DAODAO team to develop a clawback tooling… This tooling will allow any community member to initiate the process of recovering all funds custodied by DAO’s like AADAO, simply by creating a governance proposal on the Cosmos Hub. Upon passing, the clawbacks will be executed automatically.\n\nIt’s worth adding that while the main purpose of this development is to be leveraged directly by Atom Accelerator to strengthen the DAO’s accountability to the Cosmos Hub, the tooling will be made available for all to use.\n\nAADAO will be the first to adopt this but it is our hope that it will become a standard practice amongst all DAOs mandated by the Hub in the future.\n\n# Implementation\n\nIf passed, AADAO will proceed to put in place the clawback tooling as proposed below.\n\n## Technical Implementation:\n\nIn order to maximize transparency, accountability and efficiency, AADAO leverages [DAODAO](https://daodao.zone/) for all its operations. DAODAO enables the existence of a hierarchical organizational structure via subDAOs, a feature that AADAO leverages.\n\nThanks to this, AADAO will be able to grant the Hub’s Community Pool address control over funds in the custody of AADAO.\n\nA clawback control will be given to the governance account, allowing governance to execute messages on behalf of AADAO and its subDAOs\n\nOnce in place, any community member will have the ability to post an onchain proposal that, if approved, will execute the transfer of all assets custodied by AADAO back to the Community Pool.\n\n## Best Practices guidelines\n\nWhile nothing prevents any community member from abruptly pushing a ‘clawback’ proposal onchain without prior notice, we would like to point out a few suggestions to follow when introducing a clawback proposal:\n\n- Before taking the proposal onchain, initiate a discussion on the Hub’s forum.\n- Include the reasoning and rationale behind the proposal.\n- Give AADAO (or other DAOs) the chance to reply and address the concerns motivating the proposal.\n- Any clawback proposal should account for grants and expenses in progress. In the event that a clawback is initiated, some funds should be excluded from the clawback to allow for the program to be closed out responsibly - covering the funding already committed to grants in progress, and some operational funding to allow for a skeleton team to close out the program.\n\nNote:\n\n- **The goal of the suggested best practices isn’t to give AADAO the chance to defend itself. Instead the goal is to provide ATOM stakers the full picture and more context, in order to make informed decisions.**\n- **Regardless of whether the proposed guidelines were followed or not, AADAO contributors commit to abiding by the outcome on any onchain vote that concerns AADAO.**\n\n# Final Thoughts\n\nNavigating recent events has been challenging for AADAO’s contributors. That being said, we’d like to pause for a moment and consider the upside to the future of decentralized governance on the Cosmos Hub:\n\nWhile what the DAO experienced should have never happened in the first place, it was the way Atom Accelerator was structured that allowed for it to be detected and swiftly addressed.\n\nAtom Accelerator relies on a group of contributors entrusted by the Cosmos Hub to steward its interests. Meaning that at any moment, if the community wills it, they can put an end to AADAO and retrieve all funding.\n\nTo complement Atom Accelerator’s decentralized ethos, the DAO established a trust in Guernsey, leveraging the jurisdiction’s tax neutrality for optimal asset management. Combined, these efforts guarantee the long-term financial health of the Hub’s assets by placing compliance directly on the shoulders of the DAO’s contributors. An approach that has proven efficient amid recent events.\n\nCritical changes need to be made in order for AADAO to find a way forward. We’re currently working on the best way to do this and soon we will share our plans with the community.\n\nBut until then, we wanted to remind the community that AADAO contributors do and will always acknowledge the Hub’s governance as the overruling authority on all matters and we hope that this initiative will reinforce that commitment."},"authority":"cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn"}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"112410618927472","abstain_count":"2220037790192","no_count":"62935090457","no_with_veto_count":"412308606073"},"submit_time":"2024-11-04T09:03:08.371479079Z","deposit_end_time":"2024-11-18T09:03:08.371479079Z","total_deposit":[{"denom":"uatom","amount":"250000000"}],"voting_start_time":"2024-11-14T13:41:38.192459278Z","voting_end_time":"2024-11-28T13:41:38.192459278Z","metadata":"Signaling proposal to allow Hub governance to execute clawbacks with ease","title":"Signaling proposal to allow Hub governance to execute clawbacks with ease","summary":"Full forum discussion could be found [here](https://forum.cosmos.network/t/signaling-proposal-to-allow-hub-governance-to-execute-clawbacks-with-ease/14614).\n\n# Summary\n\nThis proposal aims to introduce a ‘Claw Back’ tooling that would allow the Cosmos Hub community to recall all funding provided to DAOs, like the Atom Accelerator DAO (AADAO), back to the Community Pool through an onchain governance vote.\n\nPlease note that this proposal is NOT calling for the immediate dissolution of AADAO. Recent events have prompted conversations in the community and the DAO about restructuring the organization, but this proposal is unrelated to those issues. This proposal is to modify DAODAO tooling such that any ATOM Community Pool funded DAOs’ assets can easily be clawed-back by governance, if and when needed.\n\n# Background\n\nThe Hub’s community is the true owner of AADAO’s assets and is the sovereign voice enabling it. Meaning that, at any moment, the community could choose to halt the DAO’s activities, claw back funding and dissolve Atom Accelerator.\n\n# Motivation\n\nThe community’s supreme authority, via onchain governance, over all of AADAO’s activities isn’t new and has been part of the DAO’s [Internal Protocols](https://www.atomaccelerator.com/about/internal-protocols/) since inception.\n\nThat being said, if a community member wanted to introduce a proposal to claw back funds and disband AADAO, the process would be suboptimal right now:\n\n- Lengthy process: it requires a signaling proposal, after which the AADAO Multi-Signature signers must coordinate to transfer the funds back to the Community Pool.\n- Technically challenging: Multi-Signature coordination failures could lead to frozen funds. For example: [Clawing back vested funds in Proposal 860](https://www.mintscan.io/cosmos/proposals/860) required a Software Upgrade.\n- Trust assumptions: In an ideal scenario, the Hub’s community shouldn’t be beholden to any additional trust assumption when it comes to governance-approved claw backs.\n\nIn order to eliminate unnecessary trust assumptions, account for technical failures and improve the process, AADAO has asked the DAODAO team to develop a clawback tooling… This tooling will allow any community member to initiate the process of recovering all funds custodied by DAO’s like AADAO, simply by creating a governance proposal on the Cosmos Hub. Upon passing, the clawbacks will be executed automatically.\n\nIt’s worth adding that while the main purpose of this development is to be leveraged directly by Atom Accelerator to strengthen the DAO’s accountability to the Cosmos Hub, the tooling will be made available for all to use.\n\nAADAO will be the first to adopt this but it is our hope that it will become a standard practice amongst all DAOs mandated by the Hub in the future.\n\n# Implementation\n\nIf passed, AADAO will proceed to put in place the clawback tooling as proposed below.\n\n## Technical Implementation:\n\nIn order to maximize transparency, accountability and efficiency, AADAO leverages [DAODAO](https://daodao.zone/) for all its operations. DAODAO enables the existence of a hierarchical organizational structure via subDAOs, a feature that AADAO leverages.\n\nThanks to this, AADAO will be able to grant the Hub’s Community Pool address control over funds in the custody of AADAO.\n\nA clawback control will be given to the governance account, allowing governance to execute messages on behalf of AADAO and its subDAOs\n\nOnce in place, any community member will have the ability to post an onchain proposal that, if approved, will execute the transfer of all assets custodied by AADAO back to the Community Pool.\n\n## Best Practices guidelines\n\nWhile nothing prevents any community member from abruptly pushing a ‘clawback’ proposal onchain without prior notice, we would like to point out a few suggestions to follow when introducing a clawback proposal:\n\n- Before taking the proposal onchain, initiate a discussion on the Hub’s forum.\n- Include the reasoning and rationale behind the proposal.\n- Give AADAO (or other DAOs) the chance to reply and address the concerns motivating the proposal.\n- Any clawback proposal should account for grants and expenses in progress. In the event that a clawback is initiated, some funds should be excluded from the clawback to allow for the program to be closed out responsibly - covering the funding already committed to grants in progress, and some operational funding to allow for a skeleton team to close out the program.\n\nNote:\n\n- **The goal of the suggested best practices isn’t to give AADAO the chance to defend itself. Instead the goal is to provide ATOM stakers the full picture and more context, in order to make informed decisions.**\n- **Regardless of whether the proposed guidelines were followed or not, AADAO contributors commit to abiding by the outcome on any onchain vote that concerns AADAO.**\n\n# Final Thoughts\n\nNavigating recent events has been challenging for AADAO’s contributors. That being said, we’d like to pause for a moment and consider the upside to the future of decentralized governance on the Cosmos Hub:\n\nWhile what the DAO experienced should have never happened in the first place, it was the way Atom Accelerator was structured that allowed for it to be detected and swiftly addressed.\n\nAtom Accelerator relies on a group of contributors entrusted by the Cosmos Hub to steward its interests. Meaning that at any moment, if the community wills it, they can put an end to AADAO and retrieve all funding.\n\nTo complement Atom Accelerator’s decentralized ethos, the DAO established a trust in Guernsey, leveraging the jurisdiction’s tax neutrality for optimal asset management. Combined, these efforts guarantee the long-term financial health of the Hub’s assets by placing compliance directly on the shoulders of the DAO’s contributors. An approach that has proven efficient amid recent events.\n\nCritical changes need to be made in order for AADAO to find a way forward. We’re currently working on the best way to do this and soon we will share our plans with the community.\n\nBut until then, we wanted to remind the community that AADAO contributors do and will always acknowledge the Hub’s governance as the overruling authority on all matters and we hope that this initiative will reinforce that commitment.","proposer":"cosmos1la0mxx0cp7se7uvvrjuuhdfulv4mgst586ny4l","expedited":false,"failed_reason":""}],"pagination":{"next_key":"AAAAAAAAA8s=","total":"0"}}