A Sei user says their USDC.n is now effectively stuck on the blockchain, months after the network warned holders to migrate the Noble-issued stablecoin before its transition away from Cosmos-native infrastructure.
The complaint appeared on the Cosmos Hub Forum on September 25 and remained active through September 27. The user said they hold USDC.n on Sei and are unable to find a working process or support contact to migrate the asset.
According to the post, the holder contacted Circle but was told that Circle could not assist because the asset was not native USDC and that USDC.n was handled through Noble. The user said attempts to reach Noble were unsuccessful, citing a Discord channel they could not verify through and a support email that did not work.
The report is unverified and does not establish that every remaining USDC.n holder is unable to move funds. But it is notable because Sei explicitly warned about this scenario months earlier.
On January 7, Sei said more than $1.4 million of USDC via Noble remained on its network and told holders to swap or migrate before the planned SIP-3 transition. In its official USDC.n migration warning, Sei said the token could become inaccessible or lose utility as the network moved toward an EVM-only architecture.
About 343,550 USDC.n Still Appears to Exist on Sei
The amount remaining has fallen significantly since that warning, but it has not disappeared.
An indexed page for the verified USDC.n contract on Sei explorer Seistream shows approximately 343,550 USDC.n as the token’s maximum total supply and roughly 1,790 holders. The explorer snapshot was crawled in August, meaning it should be treated as an approximate recent figure rather than a real-time September 28 balance.
Because USDC.n is designed to track one U.S. dollar, that suggests roughly $343,550 of the legacy asset was still represented on Sei at the time of the snapshot, down substantially from the more than $1.4 million Sei reported in January.
Not all of that amount can automatically be classified as stranded. Some balances may sit in contracts, liquidity pools or wallets whose owners still have a functioning route to swap them. The fresh forum complaint establishes only that at least one holder says they are currently unable to use or migrate their position.
Still, the remaining supply matters. The transition is no longer a theoretical future event for holders who ignored or missed the migration notices. It has become a question of whether the residual assets can still be converted through infrastructure that was originally designed for the migration.
Similar operational problems have appeared elsewhere when assets change networks. Kraken, KuCoin and Bitget recently experienced funding disruptions after GLMR and MOVR migrated to Base, showing how a token can continue to exist while the infrastructure around deposits, withdrawals and routing changes underneath it.
Sei’s Dedicated USDC.n Migration Tool Is No Longer Available
One part of Sei’s original migration guidance is now notably outdated.
For smaller holders, the January post suggested swapping USDC.n into native USDC through Saphyre or Symphony. For larger positions, Sei linked to a dedicated tool hosted at brrr.fun that was designed to batch the migration.
The intended route was relatively complex: the tool would move USDC.n through Noble, then Polygon, before using Circle’s Cross-Chain Transfer Protocol to bring native USDC back to Sei.
That dedicated link no longer leads to the migration application. It currently redirects to an expired-domain service.
Symphony’s site remains reachable, while another frontend cited by Sei, CCTP Exchange, is also online. But publicly accessible pages reviewed for this article do not establish that a USDC.n holder in the position described on the Cosmos forum can still complete the entire conversion today.
That distinction is important. A migration route being documented historically is not the same thing as it remaining operational after the surrounding network infrastructure has changed.
Sei’s documentation had also described manual alternatives. Holders could bridge USDC.n outward, move through an intermediary chain supporting Circle’s CCTP and return to Sei with native USDC. That route depended on the Cosmos and IBC infrastructure that SIP-3 was specifically designed to wind down.
Sei’s migration timetable itself changed over time. The January warning originally pointed holders toward an end-of-March deadline. In April, Sei said IBC inbound and outbound transfers were still enabled while the network progressively removed legacy functionality. In May, exchanges and custodians were told to finish their EVM integration before June 15 as Cosmos support moved toward deprecation.
Native USDC and USDC.n Are Not the Same Asset
The support problem described by the user also highlights an important distinction that can disappear inside wallet interfaces.
Native USDC on Sei is issued by Circle and uses an EVM token contract. USDC.n is a legacy representation of USDC that reached Sei through Noble and IBC. They may both aim to represent one dollar, but their issuance and transfer infrastructure are different.
Circle and Sei launched native USDC on the network in 2025 alongside CCTP V2, while USDC.n remained available during a migration period. The long-term plan was to shift liquidity toward the native version as Sei simplified its architecture.
That distinction explains why a holder can possess something labelled USDC while discovering that ordinary USDC support channels or routes do not necessarily apply. It is part of the wider fragmentation problem that stablecoin infrastructure is trying to solve: identical dollar exposure can exist through different contracts, bridges and networks with very different operational dependencies.
That contrasts with newer attempts to make stablecoin infrastructure less dependent on multiple bridging and middleware layers.
For users, however, the distinction often becomes obvious only when they attempt to withdraw, bridge or redeem. Other crypto platforms have faced similar customer-access problems, including cases where users reported withdrawals stuck in processing. In the Sei case, the issue is different technically, but the practical outcome for the holder is similar: an on-chain balance can be visible without there being an obvious usable route out.
The Bigger Risk Is the Long Tail After a Blockchain Migration
The most interesting part of this case is not the size of one user’s balance. It is what happens to the last few percent of users after an ecosystem decides a migration is effectively complete.
Projects naturally measure success by how much liquidity has moved. On that measure, Sei’s USDC.n migration appears to have accomplished a lot. The apparent supply has fallen from more than $1.4 million in January to roughly $343,550 in the more recent explorer snapshot.
But migration risk becomes concentrated as the remaining pool gets smaller.
The first 75% of liquidity can move while swap pools are deep, bridges are fully supported, dedicated migration applications remain online and ecosystem teams are actively promoting the transition. The final holders may return months later to find thinner liquidity, deprecated interfaces, expired tools and support responsibilities spread across several organizations.
That creates an awkward situation in decentralized infrastructure. Sei does not custody the user’s funds. Circle does not treat USDC.n as native USDC. Noble supplied the issuance route, while third-party applications handled parts of the migration. Technically, each party can have a legitimate explanation for why the problem belongs somewhere else. For the holder, the result can still be an asset they cannot practically use.
The disappearance of the dedicated migration tool makes that issue more concrete. Sei gave users clear advance warning, but a warning is only one part of migration management. The harder question is how long recovery infrastructure should remain available after a deadline passes, particularly when meaningful balances remain on-chain.
Crypto markets have already seen how access can disappear even though balances remain visible. In another context, users losing withdrawal access to supported assets illustrated the gap between owning a balance and retaining a functioning exit route.
The fresh USDC.n complaint is therefore important even if it remains an isolated case. It is the kind of user-level evidence that tests whether a migration worked not just for most liquidity, but for the people who arrived after the main migration window had closed.
The next question is whether Sei, Noble or another ecosystem participant can provide those remaining holders with a functioning conversion route. If the roughly 343,550 USDC.n shown in the recent explorer snapshot can still be migrated, the issue is largely one of documentation and support. If substantial balances can no longer move, the remaining supply becomes something more serious: a measurable pool of legacy stablecoins left behind by the network transition.
Johan Shamshad is a financial markets writer at Dave Finances covering cryptocurrencies, trading platforms, brokers, fintech, financial regulation, and developments across global markets. He previously worked at Gulf News, adding newsroom experience to his coverage of fast-moving financial and digital-asset markets.
His work focuses on identifying market-moving events, company developments, regulatory changes, product launches, and shifts in trading and financial infrastructure.
Johan contributes news and analysis designed to help readers understand not only what happened, but why a development matters and how it may affect the wider financial landscape.