Only 1 Day Left: Terra Classic Community Moves to Protect $62,193 USDC Liquidity
Terra Classic has only one day left to decide on a proposal that could determine what happens to more than 62,193 USDC and 1.23 billion LUNC currently deployed as community owned liquidity.
The proposal seeks to reroute the community’s existing LUNC and USDC liquidity from Noble issued USDC to Injective issued USDC, following Circle’s planned shutdown of CCTP v1. The deadline is becoming increasingly important because CCTP v1 is scheduled to be paused on December 1, 2026.
If the liquidity remains in its current form, the community’s Noble issued USDC could lose its existing redemption path through Ethereum once CCTP v1 is paused.
Why Is the Reroute Important?
The core issue is not the LUNC liquidity itself. The concern is the USDC backing and redemption route connected to the community’s existing liquidity positions.
The Terra Classic community currently has approximately 62,193 USDC and 1.23 billion LUNC deployed across three LUNC/USDC liquidity pools under the framework established by Proposal 12171.
That USDC originally arrived through Noble, which previously served as a native Cosmos minting hub for Circle’s USDC.
However, Circle is moving away from CCTP v1. Noble currently relies on CCTP v1 and is not expected to receive a CCTP v2 upgrade.
Circle’s current timeline indicates that CCTP v1 burn limits will begin declining on October 31, 2026, capacity will continue to be reduced throughout November, and the CCTP v1 contracts will be paused on December 1, 2026.
That creates a time sensitive problem for Noble issued USDC held on Terra Classic.
What Happens to Noble USDC After CCTP v1 Is Paused?
Today, the existing USDC redemption route depends on a series of steps.
USDC can move from Terra Classic through IBC to Noble, then use CCTP to reach Ethereum, where the USDC can ultimately be redeemed through Circle.
Because this route depends on CCTP v1, the planned shutdown creates a risk for USDC that remains connected to the Noble based system.
The proposed migration is therefore designed to move the community’s liquidity toward Injective issued USDC, which is intended to follow the newer USDC issuance standard used within the Cosmos ecosystem.
How Much Liquidity Is Being Protected?
On chain figures verified on September 5, 2026, show the following community liquidity positions:
| DEX | LUNC | USDC |
|---|---|---|
| Terraswap | 417,875,015 | 21,169.12 |
| Terraport | 411,812,561 | 20,577.14 |
| Garuda DeFi | 404,251,874 | 20,519.11 |
| Total | 1,233,939,450 | 62,265.37 |
The community’s own share represents approximately 1,232,496,754 LUNC and 62,193.25 USDC.
The Migration Will Happen in Multiple Stages
The proposal does not call for withdrawing and moving all liquidity at once.
The planned approach is designed to keep LUNC/USDC markets available during the migration.
First, a new IBC client, connection and transfer channel between Terra Classic and Injective will be established. The route will be relayed by LuncGoblins, also known as Fragwuerdig.
A small test transaction will then travel through the complete route before the actual migration begins. The signers will also rehearse the process before moving the community’s larger positions.
After the test phase, each liquidity position is planned to be migrated in two 50 percent passes.
- Terraswap, Terraport and Garuda DeFi will each have 50 percent of their position migrated.
- The remaining 50 percent of each position will then be migrated.
This approach is intended to prevent any of the three LUNC/USDC markets from becoming completely inactive during the migration.
How Will the USDC Move to Injective?
Each tranche will follow a defined route.
- Terra Classic: The LP position is withdrawn and the released USDC is sent out through IBC.
- Ethereum: The USDC is minted through the existing route and then burned toward Injective using CCTP v2.
- Injective: The USDC is minted and sent back to Terra Classic through the newly established IBC channel.
- Terra Classic: The returned USDC is deposited into the multisignature wallet associated with Proposal 12171 before new LUNC/USDC liquidity positions are created.
Because Injective issued USDC is a different denomination, the migrated liquidity will be placed into new LUNC/USDC pairs.
The existing pairs will remain on the respective DEXs but will no longer contain the community’s migrated liquidity.
Why Is the Timing So Important?
The proposal has a clear deadline because Circle’s CCTP v1 shutdown is approaching.
- October 31, 2026: CCTP v1 burn limits begin decreasing.
- November 2026: CCTP v1 capacity continues to decline.
- December 1, 2026: CCTP v1 contracts are scheduled to be paused.
The proposal’s internal migration timeline targets completion before these restrictions become critical.
The first migration pass is targeted for late September, while the second pass is targeted for mid October. The proposal sets October 31 as the hard internal deadline.
What Will the Migration Cost?
Moving the community liquidity will trigger the existing 1.5 percent Terra Classic on chain tax on the LUNC portion when liquidity is withdrawn.
Based on the current community position, the expected tax is approximately $933.
Providing liquidity again does not trigger the same tax, meaning the tax is expected to be paid once rather than twice.
The proposal estimates that the community position will return approximately 0.75 percent smaller, with most of the reduction coming from the LUNC transaction tax.
Routing costs are expected to be relatively small, with the Terra Classic transfer carrying a flat fee of approximately $0.09 per tranche, in addition to Ethereum gas costs required for the CCTP route.
No additional community funds are requested for the migration.
What Are the Main Risks?
The proposal identifies several risks, including delays in establishing the Injective channel, relayer interruptions, migration delays and price movement while LUNC is temporarily held during each tranche.
The phased approach is intended to reduce some of these risks by limiting the amount of liquidity being moved at any one time.
If a relayer stops operating during the migration, packets could remain unrelayed until the relayer resumes or another operator takes over. The proposal treats this primarily as a potential delay rather than an expected loss of funds.
Another consideration is Circle’s work with Noble and Cosmos teams on a potential interim routing solution. According to the proposal, no replacement solution has been shipped yet.
Other Noble USDC Holders Face the Same Deadline
The issue extends beyond the community owned liquidity positions.
Approximately 54,781 USDC of Noble issued USDC is reportedly held on Terra Classic outside the three community liquidity pools, including ordinary wallets and contracts.
Those holders face the same CCTP v1 deadline.
The proposed migration specifically covers the community owned position under Proposal 12171. Individual holders of Noble issued USDC would need to make their own arrangements before the December 1 deadline.
What the Proposal Means for Terra Classic
The proposal is essentially a plan to preserve the utility and redemption path of community owned USDC liquidity before the infrastructure supporting its current route is shut down.
Rather than waiting for CCTP v1 to reach its final shutdown, the proposal seeks to move the liquidity through Ethereum and CCTP v2 before redeploying it on Terra Classic using Injective issued USDC.
With only one day remaining before the proposal deadline, the decision now sits with the Terra Classic community.
The key issue for voters is whether the community should authorize the Proposal 12171 signers to carry out the planned migration before the CCTP v1 shutdown creates a more restrictive environment for Noble issued USDC.
