# Hub Weekly Update #25: November 19, 2026

**URL:** <https://forum.cosmos.network/t/hub-weekly-update-25-november-19-2026/17603>\
**Category:** Hub Unit\
**Created:** [November 19, 2026, 5:19pm UTC](https://forum.cosmos.network/t/hub-weekly-update-25-november-19-2026/17603 "2026-11-19T17:19:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**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 19, 2026, 5:19pm UTC](https://forum.cosmos.network/t/hub-weekly-update-25-november-19-2026/17603/1 "2026-11-19T17:19:52Z")

</div>

![hub-weekly-25-landscape](https://canada1.discourse-cdn.com/flex031/uploads/cosmos1/original/2X/e/ed253f4f1480f9be96f03e020eb389e7c478d393.jpeg)

This is the twenty-fifth Hub Weekly Thursday recap, straight from the Hub Unit team, as promised 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. Robo is back next week!

**This week: Gaia v29.1.0 is live, dYdX moves its USDC to Injective, the latest USDC figures, and Skip:Go maintenance day on November 23.**

- **[Gaia v29.1.0](https://www.mintscan.io/cosmos/proposals/1061)**: Proposal 1061 passed, and the upgrade executed on November 18 at block 33,935,300

- **[dYdX moves its USDC to Injective](https://www.dydx.xyz/blog/usdc-migration-to-injective)**: v9.9 applied on November 17, deposits now route through Injective, and user balances are unchanged

- **[USDC migration](https://docs.skip.build/go/app/usdc-n-manual-migration)**: 55.65M USDC.n remaining on Noble as of Thursday, down from 84.56M on November 11

- **Skip:Go maintenance** : about three hours of downtime on November 23 from 02:00 UTC, with no code changes needed from integrators.

The team continues to work on the **Tokenomics update for the last week of November** , as promised, to begin the public review and proposal process through then and the end of the year.

* * *

## **Gaia v29.1.0 Is Live: Proposal 1061 Passed, and the Upgrade Executed on November 18 at Block 33,935,300**

 ![image](https://canada1.discourse-cdn.com/flex031/uploads/cosmos1/original/2X/6/6a759415e1b43ab03e1c1003056147e0a9ddb264.png)

[Proposal 1061](https://www.mintscan.io/cosmos/proposals/1061) passed. Voting ended on November 17 at 11:57 UTC with 155,557,950.13 ATOM voting yes, 1,134.77 ATOM abstaining, 231.81 ATOM voting no, and no veto votes. The upgrade executed on November 18 at block [33,935,300](https://www.mintscan.io/cosmos/block/33935300), at 12:37 UTC, and the Hub has been producing blocks on v29.1.0 since.

What it fixed: the v29 upgrade removed the legacy params module, which broke decoding of older parameter-change proposals, so governance queries and state export failed on those entries (reads only; voting and execution were never affected). v29.1.0 restores decoding of those proposals, updates wasmd to v0.60.10 and wasmvm to v2.3.6, and ran on the testnet from November 3. The release is on the [Gaia repository](https://github.com/cosmos/gaia/releases/tag/v29.1.0), the upgrade post is on the [forum](https://forum.cosmos.network/t/gaia-v29-1-0-software-upgrade/17569), and the background is in [last week’s update](https://forum.cosmos.network/t/hub-weekly-update-24-november-12-2026/17581).

Thank you to all validators for helping with the update!

How you can help:

- **Validators still on the old binary:** switch to [v29.1.0](https://github.com/cosmos/gaia/releases/tag/v29.1.0) now, verified against the [release signing keys](https://github.com/cosmos/security/tree/main/release/gaia/signing). A node on v29.0.x stops at block 33,935,300 and does not sync past it.

- **Node operators running a public RPC, REST or gRPC endpoint:** make sure it is on v29.1.0 too, so the wallets, explorers and indexers pointed at it get the restored governance queries.

* * *

## **dYdX Moves Its USDC to Injective: v9.9 Applied on November 17, Deposits Now Route Through Injective, and Balances Are Unchanged**

 ![image](https://canada1.discourse-cdn.com/flex031/uploads/cosmos1/original/2X/8/8e2705731396b4ecb150f8ca6cc1e9cc8c838ed8.jpeg)

dYdX [Proposal 400](https://www.mintscan.io/dydx/proposals/400), the v9.9 software upgrade, passed with voting ending on November 16, and the upgrade applied on November 17 at height 114,220,000. It adds a Canonical USDC module that tracks whether each unit of USDC on dYdX Chain is backed by USDC on Noble or by USDC on Injective, and moves that backing to Injective over time.

What changed for dYdX users since the upgrade:

- **Deposits route through Injective.** Deposits sent from Noble, including CCTP transfers routed through Noble, are rejected and refunded to the sending address.

- **Withdrawals to Injective arrive as USDC on Injective.** Noble withdrawals stay open as a temporary route until dYdX governance closes them.

- **Balances, positions and collateral are unchanged** , and the USDC denom on dYdX Chain stays the same.

The [dYdX post on the migration](https://www.dydx.xyz/blog/usdc-migration-to-injective) has the full detail, including the safeguards (per-block backing checks, rate limits and automatic pauses), and [the Hub’s post from November 13](https://x.com/cosmoshub/status/2121288853453758610) has the short version.

**Why it matters for the migration as a whole:** as of November 11, dYdX held about 69.3M USDC.n, around 82 percent of what remained on Noble. The backing shifts gradually rather than in one transaction: deposits through Injective add Injective backing, and a designated operator moves the Noble-backed portion over in rounds, within Circle’s rate limits.

As of Thursday morning, the Noble escrow for dYdX’s channel holds 41.81M USDC.n, down about 27.5M in the week, and 24.31M USDC.inj is now on dYdX Chain.

Thank you to the dYdX team for this massive effort, and for all teams coordinating with the Ecosystem team, Injective, and Circle, to facilitate the transition. This will greatly accelerate te migration!

* * *

## **USDC Migration: 55.65M USDC.n Remaining on Noble as of Thursday, November 19, Down from 84.56M a Week Earlier**

 ![image](https://canada1.discourse-cdn.com/flex031/uploads/cosmos1/original/2X/2/222ed453b85a3b013391bf800dcf216c12cfce04.jpeg)

On-chain supply as of Thursday, November 19, with the change since Wednesday, November 11, the date of [last week’s](https://forum.cosmos.network/t/hub-weekly-update-24-november-12-2026/17581) figures:

- **USDC.inj on Injective: 36.94M** , up from 11.70M

- **USDC.n remaining on Noble: 55.65M** , down from 84.56M. The Noble escrow for dYdX’s channel holds 41.81M of it, or about 75 percent of what remains, down from about 69.3M

- Outside dYdX, 6.37M remains on Osmosis, down from about 6.8M, and the Hub’s balance is 0.42M, unchanged

The drop on Noble tracks dYdX’s migration almost one for one, and the rise on Injective is the same USDC arriving on the other side. For everyone else, the balances left are small and spread across chains and wallets, and the tooling to move them is live today.

**Circle’s dates for Noble USDC:**

- **January 12, 2027:** Circle pauses the Noble USDC contract and takes a snapshot of balances.

- **January 13, 2027:** Noble USDC is no longer accessible through Circle Mint or CCTP. From that point, redemption is manual.

**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 the manual path.

- **Osmosis transmuter:** [pool 3497](https://app.osmosis.zone/pool/3497) swaps USDC.n for USDC.inj 1:1 with no fee.

How you can help:

- **Holding USDC.n in a wallet?** Migrate now, using either route above.

- **Running a contract, a multisig or a treasury that holds USDC.n?** Plan the migration this month, and reach out to [@RoboMcGobo](https://forum.cosmos.network/u/robomcgobo) on Telegram if you need a hand.

- **Running a chain that wants USDC.inj listed in Skip:Go?** Keep IBC relayers running to Injective and open a PR on the [chain registry](https://github.com/cosmos/chain-registry).

* * *

## **Skip:Go Maintenance on November 23: About Three Hours of Downtime from 02:00 UTC, and No Code Changes Needed Afterwards**

Skip:Go is moving to new infrastructure on Monday, November 23, starting at 02:00 UTC, with an expected duration of about three hours. During the window, all public prod.skip.money and skip.build endpoints return a 503, which covers the Skip Go API and go.skip.build.

What to expect:

- **Transfers submitted before the window keep processing** on the current system until they complete.

- **Data is backed up and moved** , and the service reopens after final checks.

- **No code changes are needed from integrators.** After the migration, everything works as before, and the user experience stays the same. Some users may see 503s for a few more minutes afterwards, depending on their network, and the schedule may change.

How you can help:

- **Running an app on Skip:Go?** Avoid scheduling releases or batch transfers in the window, and treat a 503 during it as the maintenance, not a failure to retry.

- **Moving USDC.n that morning?** Submit before 02:00 UTC, or wait until the service reopens.

* * *

## **That’s all for this week**

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 next monthly validator call: Wednesday, December 9, 9:00 AM ET, three weeks before the Q4 delegation snapshot on December 31

- Join the next community call on X: Wednesday, November 25. Register for the community calendar [here](https://calendar.google.com/calendar/u/0?cid=Y19iNmMwZWJjOGNlYWMzNzFmMTFmOTQ3NDEwODFkY2IwNzhlOGVmOTVhODk1MTdlNjhhZGQyZTMyMzE0NTExNmNjQGdyb3VwLmNhbGVuZGFyLmdvb2dsZS5jb20)

---

<div class="post-metadata">

**Author:** ![ATOM-Renaissance](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.cosmos.network/atom-renaissance/32/9349_2.png) [@ATOM-Renaissance](https://forum.cosmos.network/u/ATOM-Renaissance)\
**Post date:** [November 19, 2026, 9:39pm UTC](https://forum.cosmos.network/t/hub-weekly-update-25-november-19-2026/17603/2 "2026-11-19T21:39:57Z")

</div>

Update on tokenomics?
