# Add Noble-issued USDC (\`usdc.noble\`) to the Regen Ledger currency allowlist **URL:** \ **Category:** Governance\ **Tags:** currency-allow-list, relayer\ **Created:** [July 21, 2025, 6:55pm UTC](https://forum.regen.network/t/add-noble-issued-usdc-usdc-noble-to-the-regen-ledger-currency-allowlist/464 "2025-07-21T18:55:12Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![brawlaphant](https://yyz2.discourse-cdn.com/flex004/user_avatar/forum.regen.network/brawlaphant/32/71_2.png) [@brawlaphant](https://forum.regen.network/u/brawlaphant)\ **Post date:** [July 21, 2025, 6:55pm UTC](https://forum.regen.network/t/add-noble-issued-usdc-usdc-noble-to-the-regen-ledger-currency-allowlist/464/1 "2025-07-21T18:55:12Z")
**Governance Proposal: Enable `usdc.noble` on Regen Ledger** **Title:** Add Noble-issued USDC (`usdc.noble`) to the Regen Ledger currency allowlist **Summary:** This proposal enables the use of Cosmos-native USDC — specifically `usdc.noble` — on Regen Ledger by adding it to the `currency_allow_list`. This unlocks USDC for use in the Regen Marketplace and future IBC-native flows, enabling dollar-denominated ecocredit purchases and broader ReFi utility. * * * ### 🧩 **Context & Motivation** - **Noble** is the official Cosmos-native issuance chain for **Circle USDC** - Native USDC already circulates in Cosmos via IBC (e.g., Osmosis, dYdX, Neutron) - Regen currently only supports `axlUSDC`, which is a custodial bridge asset - Enabling `usdc.noble` improves UX, reduces trust assumptions, and positions Regen to settle real-world ESG payments with native stables * * * ### 🛠 **Technical Details** - **IBC Channel Required:** Regen ↔ Noble (to be established with relayer support) - **Initial Denom:** `"usdc.noble"` _(IBC hash will be updated once the channel is live, e.g. `ibc/7A3...`)_ - **Marketplace Config Update:** Add to `currency_allow_list` in `x/marketplace`: ```json { "denom": "usdc.noble", "display_denom": "USDC", "decimals": 6, "enabled": true } ``` - **Frontend Coordination:** Regen Marketplace frontend will be updated to: - **Fee Token (Optional):** Future updates may allow USDC as a transaction fee token (`x/feegrant`), pending community discussion * * * ### 💸 **Future Incentive Alignment (non-binding)** - Follow-up proposals may introduce: * * * ### 🔁 Relayer Coordination Needed This proposal assumes an IBC channel between Regen and Noble will be established. Once passed, relayer support will be needed to activate the channel and register the `usdc.noble` denom on Regen. Interested relayers (e.g., Strangelove, Notional, others) are invited to coordinate in Regen Discord or governance forums. * * * ### 🗳 **Governance Impact** - **Yes** : Adds `usdc.noble` to Regen’s currency allowlist, enabling Cosmos-native stablecoin flows and supporting real-world ESG use cases - **No** : Regen continues to rely on bridged custodial tokens (`axlUSDC`), with reduced credibility and reach ---
**Author:** ![brawlaphant](https://yyz2.discourse-cdn.com/flex004/user_avatar/forum.regen.network/brawlaphant/32/71_2.png) [@brawlaphant](https://forum.regen.network/u/brawlaphant)\ **Post date:** [July 21, 2025, 6:56pm UTC](https://forum.regen.network/t/add-noble-issued-usdc-usdc-noble-to-the-regen-ledger-currency-allowlist/464/2 "2025-07-21T18:56:12Z")
Refer to: [Add USDC.noble to the Regen Marketplace currency AllowList](https://forum.regen.network/t/add-usdc-noble-to-the-regen-marketplace-currency-allowlist/82) ---
**Author:** ![willszal](https://yyz2.discourse-cdn.com/flex004/user_avatar/forum.regen.network/willszal/32/56_2.png) [@willszal](https://forum.regen.network/u/willszal)\ **Post date:** [July 31, 2025, 6:39pm UTC](https://forum.regen.network/t/add-noble-issued-usdc-usdc-noble-to-the-regen-ledger-currency-allowlist/464/3 "2025-07-31T18:39:09Z")
If USDC Noble isn’t on the allowlist yet, I support it getting listed! ---
**Author:** ![SBaxendell](https://avatars.discourse-cdn.com/v4/letter/s/f6c823/32.png) [@SBaxendell](https://forum.regen.network/u/SBaxendell)\ **Post date:** [August 2, 2025, 1:21pm UTC](https://forum.regen.network/t/add-noble-issued-usdc-usdc-noble-to-the-regen-ledger-currency-allowlist/464/4 "2025-08-02T13:21:41Z")
Yes please. I’m surprised this wasn’t done earlier. ---
**Author:** ![brawlaphant](https://yyz2.discourse-cdn.com/flex004/user_avatar/forum.regen.network/brawlaphant/32/71_2.png) [@brawlaphant](https://forum.regen.network/u/brawlaphant)\ **Post date:** [August 2, 2025, 5:42pm UTC](https://forum.regen.network/t/add-noble-issued-usdc-usdc-noble-to-the-regen-ledger-currency-allowlist/464/5 "2025-08-02T17:42:06Z")
Just to clarify for anyone wondering: ✅ This proposal only adds `usdc.noble` to the Regen Ledger currency allowlist. 🔒 It does **not require** IBC channel setup or relayer coordination yet. 🧱 It’s a governance param that **can be set in advance** of technical implementation. That means: - Devs can later open the Noble ↔ Regen IBC channel - Relayers (e.g. Notional/Strangelove) can begin routing packets - UI maintainers can add support to the Marketplace frontend By passing this now, we clear the way for the ecosystem to move smoothly when infra is ready. Let’s get native USDC flowing into real-world climate finance. 🌱 ---
**Author:** ![brawlaphant](https://yyz2.discourse-cdn.com/flex004/user_avatar/forum.regen.network/brawlaphant/32/71_2.png) [@brawlaphant](https://forum.regen.network/u/brawlaphant)\ **Post date:** [August 2, 2025, 5:48pm UTC](https://forum.regen.network/t/add-noble-issued-usdc-usdc-noble-to-the-regen-ledger-currency-allowlist/464/6 "2025-08-02T17:48:37Z")
[Question for Regen devs and governance stewards:](https://forum.regen.network/t/add-kava-issued-usdt-usdt-kava-to-the-regen-ledger-currency-allowlist/465/5) [Since both `usdc.noble` and `usdt.kava` follow the exact same param update process — could they be submitted as a **single on-chain governance proposal** that adds both to the `currency_allow_list`?](https://forum.regen.network/t/add-kava-issued-usdt-usdt-kava-to-the-regen-ledger-currency-allowlist/465/5) [From a coordination and implementation standpoint, bundling them might reduce proposal fatigue and speed up support for native stablecoins.](https://forum.regen.network/t/add-kava-issued-usdt-usdt-kava-to-the-regen-ledger-currency-allowlist/465/5) ---
**Author:** ![RegenChristian](https://avatars.discourse-cdn.com/v4/letter/r/b782af/32.png) [@RegenChristian](https://forum.regen.network/u/RegenChristian)\ **Post date:** [August 6, 2025, 7:13pm UTC](https://forum.regen.network/t/add-noble-issued-usdc-usdc-noble-to-the-regen-ledger-currency-allowlist/464/7 "2025-08-06T19:13:02Z")
I’m fully in favor. Until we enable the IBC channel and have any applications that use these tokens, I’m not sure that it really does much for us, but there is no harm in approving them to the allowlist. I suppose it’s one less step that a dapp would have to take when launching on Regen Ledger. ---
**Author:** ![brawlaphant](https://yyz2.discourse-cdn.com/flex004/user_avatar/forum.regen.network/brawlaphant/32/71_2.png) [@brawlaphant](https://forum.regen.network/u/brawlaphant)\ **Post date:** [August 7, 2025, 3:22am UTC](https://forum.regen.network/t/add-noble-issued-usdc-usdc-noble-to-the-regen-ledger-currency-allowlist/464/8 "2025-08-07T03:22:24Z")
Once IBC channels are live and frontend hooks are in place, this unlocks: - **Direct stablecoin purchases of ecocredits** - **On-chain retirement flows using Noble USDC / Kava USDT** - **Storing and routing capital natively on Regen Ledger** , with climate value built in We just need someone with proposal rights to submit the combined param change and prep the JSON. ---
**Author:** ![Marie](https://avatars.discourse-cdn.com/v4/letter/m/bc8723/32.png) [@Marie](https://forum.regen.network/u/Marie)\ **Post date:** [September 18, 2025, 10:55am UTC](https://forum.regen.network/t/add-noble-issued-usdc-usdc-noble-to-the-regen-ledger-currency-allowlist/464/9 "2025-09-18T10:55:12Z")
@brawlaphant Thanks for the thoughful framing. But when adding an allowed denom to the marketplace, the provided `bank_denom` needs to be a concrete bank denom, eg an IBC hash `ibc/` for IBC assets, see [Buf Schema Registry](https://buf.build/regen/regen-ledger/docs/main:regen.ecocredit.marketplace.v1#regen.ecocredit.marketplace.v1.AllowedDenom) We can determine this hash in advance as long as we know the intended ICS-20 path (e.g., `transfer/channel-…[/…]/uusdc`). Indeed it doesn’t need to be live yet, but the proposal still has to specify the exact `ibc/`. Using a placeholder—like `usdc.noble`—would require a follow-up proposal to remove it and add the correct IBC denom, and could even allow creation of sell orders with a temporary denom that won’t be usable. It looks like that scenario has already played out in [Proposal 39 on Mintscan](https://www.mintscan.io/regen/proposals/39), which we now need to clean up. > [@Add Kava-issued USDT (\`usdt.kava\`) to the Regen Ledger currency allowlist](https://forum.regen.network/t/add-kava-issued-usdt-usdt-kava-to-the-regen-ledger-currency-allowlist/465/5): > > Since both `usdc.noble` and `usdt.kava` follow the exact same param update process — could they be submitted as a **single on-chain governance proposal** that adds both to the `currency_allow_list`? Yes we can include multiple msgs as part of gov v1 proposals.