# Hub Weekly Update #23: November 5, 2026 **URL:** \ **Category:** Hub Unit\ **Created:** [November 5, 2026, 5:25pm UTC](https://forum.cosmos.network/t/hub-weekly-update-23-november-5-2026/17540 "2026-11-05T17:25:13Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![qxnico](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.cosmos.network/qxnico/32/7846_2.png) [@qxnico](https://forum.cosmos.network/u/qxnico)\ **Post date:** [November 5, 2026, 5:25pm UTC](https://forum.cosmos.network/t/hub-weekly-update-23-november-5-2026/17540/1 "2026-11-05T17:25:13Z")
![hub-weekly-23-landscape](https://canada1.discourse-cdn.com/flex031/uploads/cosmos1/original/2X/8/8a9c61db8169379e3318e8e1f3ca5d3ed550c18d.jpeg) This is the twenty-third of Hub Weekly Thursday recaps, straight from the Hub Unit team, per the cadence we committed to in the [From Chaos to Stability to Growth](https://forum.cosmos.network/t/from-chaos-to-stability-to-growth-the-plan-to-build-the-cosmos-hub-roadmap-in-public/) post. Every Thursday, we will call out significant Cosmos Hub updates on the forum, with a short companion thread on X, recapping announcements, live events like validator or community calls, and ecosystem updates! For more info, see the linked posts, and contact me or [@RoboMcGobo](https://forum.cosmos.network/u/robomcgobo) on telegram to submit news for the weekly. This week Robo is out, so I am covering 🙂 **This week: the Hub’s Token Transparency Framework filing, ATOM on Paxos Crypto Brokerage, Q3 delegations, USDC migration figures, and Proposal 1060 executed.** - The Hub’s **[Token Transparency Framework filing](https://blockworks.com/token-transparency/filing/cosmos-hub)** is live on Blockworks - ATOM on **[Paxos Crypto Brokerage](https://docs.paxos.com/guides/developer/blockchains)**, now publicly announced - **[Q3 ICF delegations](https://medium.com/the-interchain-foundation/icf-delegation-program-q3-2026-selected-validators-3f78967f3e25)**: 14.47M ATOM to 50 validators, executed and verified on chain - The USDC migration figures as of Friday, October 30, the dates that matter before January 12, and the two ways to move USDC.n today, via the **[migration guide](https://docs.skip.build/go/app/usdc-n-manual-migration)** or the Osmosis transmuter - **[Proposal 1060](https://forum.cosmos.network/t/migrate-community-pool-usdc-n-to-usdc-inj-via-a-community-multisig/17492)** passed on November 3, the community multisig executed, and 566,067 USDC.inj is back in the community pool - **[Gaia v29.1.0](https://github.com/cosmos/gaia/releases/tag/v29.1.0-rc0)**: the governance-query fix is on testnet, with the mainnet upgrade planned around November 18 - **[Reactive Network](https://blog.reactive.network/reactive-mainnet-migration-complete/)** completed its mainnet migration to CometBFT on October 28 * * * ## Token Transparency Framework: The Hub’s Filing Is Live on Blockworks ![image](https://canada1.discourse-cdn.com/flex031/uploads/cosmos1/original/2X/6/6067615c248e444a2ca7e9592daab6e72a6b30d3.jpeg) The Cosmos Hub’s [Token Transparency Framework filing](https://blockworks.com/token-transparency/filing/cosmos-hub) is live. [Blockworks announced it](https://x.com/Blockworks/status/2118025520655073526) on November 4, and the Hub account posted a [thread](https://x.com/cosmoshub/status/2118027607375835222) the same day. TTF is Blockworks’ standardized, open-source disclosure format: every project answers the same 19 questions, so tokenholders can compare networks on equal terms. The filing covers five groups: Project and Team; Token Supply and Allocation; Transactions and Market Structures; Resource Disclosures; and Token Addresses and Deployments. In practice, that means how ATOM was distributed at genesis and vested, how decisions are made and who holds admin powers, how the teams building the Hub are funded, the foundation, companies and people behind the Hub, market makers, exchanges and liquidity deals, paid advisory and influencer deals, labeled treasury and operational addresses, and past exploits affecting ATOM. Anyone evaluating ATOM, from a retail holder to an institution, can now check how the Hub is structured and funded in the same format as every other filer. * * * ## Paxos: ATOM on Paxos Crypto Brokerage, Announced ![image](https://canada1.discourse-cdn.com/flex031/uploads/cosmos1/original/2X/7/76670424b9efe4775803c9d7c3c4ab0aadcaecc3.png) We covered the listing in [issue #21](https://forum.cosmos.network/t/hub-weekly-update-21-october-22-2026/17498). Today, [Paxos announced the integration publicly](https://x.com/Paxos/status/2118390914859352187): ATOM is live on Paxos Crypto Brokerage for trading and custody, so the fintechs, brokerages, and platforms built on Paxos can offer ATOM to their customers using the integration they already run. The integration was funded from the community pool through [Proposal 1054](https://www.mintscan.io/cosmos/proposals/1054), which passed in September, and ATOM is listed on Paxos’ [Assets and Blockchains](https://docs.paxos.com/guides/developer/blockchains) page. * * * ## Q3 ICF Delegations: 14.47M ATOM Delegated to 50 Validators, Executed and Verified on Chain ![image](https://canada1.discourse-cdn.com/flex031/uploads/cosmos1/original/2X/d/d13fea399ebe28906cb020f94b8189c996da718c.png) The ICF published the [Q3 2026 selected validators](https://medium.com/the-interchain-foundation/icf-delegation-program-q3-2026-selected-validators-3f78967f3e25) on November 2, and the delegations have been executed by the ICF’s custodians and verified on-chain. The round uses the September 30 snapshot at block 33,200,403. - **47 validators** qualified for the default tranche at **275,575.17 ATOM each**. - **InfStones** holds a new ecosystem growth delegation of **597,794 ATOM** to build and operate an institutional-grade ATOM staking API covering delegating, undelegating, redelegating, claiming rewards, and reporting, so custodians and brokerages can offer ATOM staking through channels they already run. - **Solva (CryptoCrew)** holds **75,000 ATOM** on top of its default delegation, awarded through the PebbleDB Snapshot Provider RFP. - Across both tranches, **14,474,826.99 ATOM** went to 50 validators. Changes to the criteria this cycle, as shared on the October 14 validator call: - Governance participation uses a rolling 12-month lookback, counting only proposals where the validator was in the active set. - Validators need to be in the active set on at least 90 of the last 100 days. - Hypha testnet points and testnet uptime are required. - Ecosystem growth delegations are added on top of any default delegation. - Downtime and jailing from September 7 to 30 were excused for this cycle. - Rounds are now named for the quarter of their snapshot, so the round announced in August as Q3 is now labeled Q2. The next adjustment uses a snapshot at the last block before 00:00 UTC on January 1, 2027, and evaluates testnet participation from October through December. Validators not yet in the testnet program should join now; the Hub’s [testnets repository](https://github.com/cosmos/testnets) has the details. * * * ## USDC Migration: 87.28M USDC.n Still on Noble as of Friday, October 30, with dYdX Holding about 80% of it ![image](https://canada1.discourse-cdn.com/flex031/uploads/cosmos1/original/2X/f/f5a8ee50e49f2d519a0098eaa8fe9ee72bacdfe9.jpeg) Here is where the on-chain supply stood as of Friday, October 30: - **Injective USDC (USDC.inj) on Injective: 10.88M** - **Still to migrate from Noble (USDC.n): 87.28M** Of the USDC.n still outstanding, roughly 70.35M, or about 80%, sits on dYdX. dYdX is adopting USDC.inj as its USDC standard, so the bulk of what remains moves when dYdX’s migration runs. This is being worked on with the team, who have proposed a streamlined solution to do so. Outside dYdX, the next largest balances are on Osmosis (about 7.55M) and Neutron (about 2.06M), with the rest spread across smaller chains, wallets, multisigs and contracts. Two-click migration on Skip: Go has been live since September. One-click migration is waiting on an Injective mainnet upgrade, scheduled for mid-November per the [Quarterly](https://forum.cosmos.network/t/cosmos-quarterly-2-q3-26-hardening-interop-and-the-hub-tokenomics-roadmap/17517). ### **Circle’s dates for Noble USDC:** - **October 13:** new minting of USDC on Noble stopped. - **October 31:** legacy CCTP V1 burn limits on Noble stepped down to zero. - **January 12, 2027:** Circle pauses the Noble USDC contract and the CCTP routes to and from Noble, and takes a snapshot of Noble balances. - **January 13, 2027:** Noble USDC is no longer accessible through Circle Mint or CCTP. Redemption of snapshotted balances moves to a manual process with Circle via their Help Desk. The snapshot covers balances on Noble itself. USDC.n held on other Cosmos chains, in wallets, contracts, or multisigs, should be migrated before January 12 rather than left for the redemption window. ### **Two ways to migrate today:** - **Skip:Go:** the [Noble to Injective route](https://go.skip.build/?src_chain=noble-1&src_asset=uusdc&dest_chain=injective-1&dest_asset=erc20:0xa00C59fF5a080D2b954d0c75e46E22a0c371235a) moves USDC.n to USDC.inj in one flow. The [migration guide](https://docs.skip.build/go/app/usdc-n-manual-migration) walks through it step by step, including USDC.n held on chains other than Noble. - **Osmosis transmuter:** the [USDC.inj transmuter pool](https://app.osmosis.zone/pool/3497) swaps USDC.n for USDC.inj 1:1 with no fee, as long as the pool holds USDC.inj liquidity. This is the route the community multisig used for the community pool migration below. ### How you can help: - If you hold USDC.n in a wallet, migrate it now through either route above. - If your team holds USDC.n in a contract, multisig, treasury or escrow, plan the migration this month and reach out on Telegram ([@RoboMcGobo](https://forum.cosmos.network/u/robomcgobo)) if the standard routes do not cover your setup. - If your chain wants to be listed as a USDC.inj destination on Skip:Go, run IBC relayers to Injective first, then open a [chain registry](https://github.com/cosmos/chain-registry) PR adding the USDC.inj asset and channel. * * * ## Proposal 1060: Passed November 3, Executed by the Community Multisig, and 566,067 USDC.inj Is Back in the Community Pool [Proposal 1060](https://www.mintscan.io/cosmos/proposals/1060) closed on November 3 at 15:22 UTC and passed. 99.98% of Yes, No, and NoWithVeto votes were Yes, 37.6% of the ATOM that voted chose Abstain, and turnout was about 54% of bonded ATOM. The proposal was a single community pool spend of 566,067.055810 USDC.n to a 4-of-6 DAODAO multisig with one mandate: migrate the USDC.n to USDC.inj and return it to the pool. The signers, Arlai (Hydro), Johnny Wyles (Osmosis), Lexa Michaelides (Hypha), Polkachu, David (Crosnest) and Zoltan (Silk Nodes), had [pre-posted three DAODAO proposals](https://forum.cosmos.network/t/migrate-community-pool-usdc-n-to-usdc-inj-via-a-community-multisig/17492/10) on October 31 so execution could start as soon as the funds landed: - **[A5](https://daodao.zone/dao/cosmos1amny2nf23uauu79lzp299tvh9v4a62uuxvh8xyj7qavrm0adztsq5sz864/proposals/A5):** migrate 283,033 USDC.n to USDC.inj (swap 1 of 2) - **[A6](https://daodao.zone/dao/cosmos1amny2nf23uauu79lzp299tvh9v4a62uuxvh8xyj7qavrm0adztsq5sz864/proposals/A6):** migrate 283,034.055810 USDC.n to USDC.inj (swap 2 of 2) - **[A7](https://daodao.zone/dao/cosmos1amny2nf23uauu79lzp299tvh9v4a62uuxvh8xyj7qavrm0adztsq5sz864/proposals/A7):** return 566,067.055810 USDC.inj to the community pool via MsgFundCommunityPool The funds landed in the multisig on November 3; all three DAODAO proposals executed the same evening, and the multisig returned the funds within its 24-hour target. The route was Cosmos Hub to Noble to Osmosis to Injective and back to the Cosmos Hub, in two swaps. **Transaction hashes from the proposal thread:** - Return of 566,067.055810 USDC.inj to the community pool: [5936893FC5133584F815A123CCA233CA51AD54BEE9448D721809765280F06016](https://www.mintscan.io/cosmos/tx/5936893FC5133584F815A123CCA233CA51AD54BEE9448D721809765280F06016) - Community pool address, where the USDC.inj now sits: [cosmos1jv65s3grqf6v6jl3dp4t6c9t9rk99cd88lyufl](https://www.mintscan.io/cosmos/address/cosmos1jv65s3grqf6v6jl3dp4t6c9t9rk99cd88lyufl) - The October 22 test migration of 1 USDC.n that validated the route before the vote: [89ADEBCE3180437C7DD53C4688DBC628C9F71B9AB129B98E7CECB56E90DDE866](https://explorer.skip.build/?tx_hash=89ADEBCE3180437C7DD53C4688DBC628C9F71B9AB129B98E7CECB56E90DDE866&chain_id=cosmoshub-4) Arlai posted the [execution confirmation](https://forum.cosmos.network/t/migrate-community-pool-usdc-n-to-usdc-inj-via-a-community-multisig/17492/12), and [@RoboMcGobo](https://forum.cosmos.network/u/robomcgobo) posted the [final update](https://forum.cosmos.network/t/migrate-community-pool-usdc-n-to-usdc-inj-via-a-community-multisig/17492/13) in the thread on November 4, and the Hub account confirmed it on X the same day. Thank you to the six signers for turning this around in one evening, and to everyone who voted. With the community pool done, the USDC.n left on the Hub sits in individual wallets, validator accounts, and multisigs. If that includes you, the two routes in the section above work the same way for USDC.n held on the Hub. No other Cosmos Hub proposal ended this week. * * * ## Gaia v29.1.0: Governance-Query Fix Is on Testnet, Mainnet Proposal Planned Around November 10 and Upgrade Around November 18 The v29 upgrade on October 28 removed the legacy params module as groundwork for SDK 0.55, and that broke decoding of 21 older parameter-change proposals. Since then, some governance queries return a 500 error: the full proposals list, filtering by status (for example, proposals in voting period), lookups and tallies for those 21 proposals, and gaiad export. This only affects reads. Block production, voting, and proposal execution work normally. If you need these queries before the fix lands, reverse pagination (newest first) works as a workaround. [Gaia v29.1.0](https://github.com/cosmos/gaia/releases/tag/v29.1.0-rc0) restores decoding of historical ParameterChangeProposal content, which repairs the proposal list, status-filtered and single-proposal queries, tally queries, and state export. It also bumps wasmd to 0.60.10 and wasmvm to 2.3.6. The release is state-breaking and ships with an upgrade handler, so it goes through a coordinated software upgrade proposal. **Timeline:** - **November 2:** v29.1.0-rc0 released. - **November 3:** the provider testnet upgraded to v29.1.0-rc0 at 14:00 UTC. - **Around November 10:** software upgrade proposal planned on mainnet. - **Around November 18:** mainnet upgrade planned. Validators: test against rc0 on the testnet now, and watch for the on-chain proposal next week. Explorer and API operators: the fix is coming, and the workaround above holds until then. * * * ## Reminder: Cosmos Quarterly #2 and the Governance Schedule ![image](https://canada1.discourse-cdn.com/flex031/uploads/cosmos1/original/2X/a/a44332c714a5a76d2fde07a9b56d5a3ed08ec0b7.jpeg) The [Cosmos Quarterly #2](https://forum.cosmos.network/t/cosmos-quarterly-2-q3-26-hardening-interop-and-the-hub-tokenomics-roadmap/17517) went up on October 29 in place of last week’s Hub Weekly, covering Q3 across the Ecosystem, Open Source and Enterprise pillars. The part that affects every ATOM holder is the governance schedule: a process post around November 20 with the review dates, Gauntlet’s full report and the [public tokenomics dashboard](https://atom-tokenomics-dashboard.fly.dev), then review steps from early December through January, tokenomics first and the roadmap last, with one proposal per step. The thread is active, so reply there with the questions you want answered in the process post, or bring them to the validator call on November 11! * * * That’s all for this week - thanks to everyone engaging across the forum, validator channels, and Telegram. Looking forward to next week’s update! Please let us know if you like the Weekly format, and what else you’d like to hear from us. - [Follow the Hub on X for updates](https://x.com/cosmoshub) - Join the monthly validator call: Wednesday, November 11, 9:00 AM ET - Join the next community call: Register for the community calendar [here](https://calendar.google.com/calendar/u/0?cid=Y19iNmMwZWJjOGNlYWMzNzFmMTFmOTQ3NDEwODFkY2IwNzhlOGVmOTVhODk1MTdlNjhhZGQyZTMyMzE0NTExNmNjQGdyb3VwLmNhbGVuZGFyLmdvb2dsZS5jb20)