Abstract announced on October 6 that it will wind down after almost three years of operation, with the chain itself set to shut down on December 15. Users who haven't moved their assets by then will lose access to any funds left on the network. The notice came at 19:32 UTC. There's no aggregate figure attached to the migration notice for how much user money is still sitting there.
The two totals don't mean the same thing
DefiLlama's chains API listed Abstract with $9.51 million in total value locked at the time of reporting. A separate DefiLlama stablecoin API put circulating stablecoins on the chain at $5.91 million. Those are different measures and shouldn't be added together — TVL covers everything counted as locked value, while the stablecoin figure is just that. Neither number tells you who controls the wallets or how much can actually exit through each route. Users should check their own positions rather than reading the public totals as a personal balance estimate.
Bridging isn't the same as withdrawing from an app
The official starting points are the Migration Hub and the native Abstract bridge. The hub also lists Stargate, Relay, and Jumper as alternatives — four bridge interfaces in total. But a bridge interface doesn't automatically close every position in every application. If your assets are deposited in an app on Abstract, you need to figure out what that app requires before the assets are even available to bridge. Abstract's notice says users must migrate but doesn't claim that connecting one wallet to the hub resolves every application-specific position.
What the native bridge actually does
Abstract's bridge documentation describes the native bridge as moving assets between Ethereum and Abstract, supporting ETH and ERC-20 tokens, and free apart from gas. Deposits from Ethereum take about 15 minutes. Withdrawals from Abstract to Ethereum can take up to 24 hours because of a built-in delay. That delay is the part worth circling. A transaction initiated near the December 15 cutoff may not finish immediately, and a completed signature is not the same as confirmed receipt on the other side. Users can check the destination wallet and transaction status before treating anything as migrated.
Chain ID 2741, and why it's in the notice
Abstract's network documentation describes the chain as an Ethereum Layer 2 built on the ZK Stack — a zero-knowledge rollup that executes transactions away from Ethereum, batches them, and verifies the batches on Ethereum with zero-knowledge proofs. It's EVM compatible, so Ethereum contracts port over with no or minimal changes, subject to documented differences. Applications on Abstract may use contracts that look like their Ethereum counterparts, but the balances live on chain ID 2741 until users or applications send supported assets elsewhere. Verification of transaction batches on Ethereum doesn't mean every Abstract wallet balance already exists as a directly spendable Ethereum balance. The mainnet RPC is https://api.mainnet.abs.xyz and the explorer is https://abscan.org/. Those identifiers matter right now — they're how you tell the production chain, where your funds are, apart from Abstract testnet, which is listed separately.
The shutdown applies to the main network itself, not just an app front end. Abstract says the chain is shutting down. Whether every asset on the chain has a supported route off it is a separate question the bridge list doesn't answer — it gives alternatives if one route doesn't support an asset or wallet setup, but it doesn't guarantee coverage. The clock runs to December 15.
