The information provided in this article is for informational purposes only and does not constitute financial advice. Cryptocurrency investments carry a high degree of risk. Always conduct your own research.

Mint Chain closes its withdrawal portal on October 20: October 10 is the last safe day to submit

Mint Chain has accepted nothing but withdrawals since April 2026, and the operator says the portal closes on October 20, 2026. Because settlement runs in weekly batches and takes up to ten days, October 10 is the last day on which a request safely arrives.

Almost empty hourglass on a steel plate beside a coin bearing a diamond-shaped symbol, with a metal shutter lowering behind it
15 min read
Share:

Mint Chain, the NFT-focused Ethereum layer 2 built by data provider NFTScan, stopped accepting new applications on April 17, 2026 and keeps nothing open but a withdrawal portal. According to the operator, that portal closes on October 20, 2026. Anyone who has not withdrawn by then will, on the same statement, no longer be able to reach their balance. In practice your own cut-off falls earlier: the portal bundles withdrawal requests into weekly batches and quotes a range of up to ten days for funds to land on Ethereum. That makes October 10 the last day on which a request still arrives before October 20 even if the batch cycle runs against you.

That calculation is the whole point of this article, because it appears in none of the coverage. What was reported in April was the date. What has been left open ever since: whether October 20 refers to the request in the portal or to the arrival on Ethereum mainnet. As long as that is unresolved, a cautious holder assumes the second reading and moves their own deadline ten days forward.

Mint Chain has been in withdrawal-only mode since April 17, 2026

Mint Chain launched as a specialist network: a layer 2 on the OP Stack, the same architecture used by Optimism and Base, and tailored to NFT applications. Layer 2 means transactions are executed off the Ethereum main chain and reported back to Ethereum in bundles; the safety of your balance rests on the contract on mainnet, not on the layer-2 operator alone.

Shutting down operations on April 17, 2026 inverted that role. The network processes no new applications, and the only operation it still supports is withdrawal back to mainnet. Independent monitoring service L2BEAT has listed Mint as an archived project since the shutdown and no longer reports any secured value there. That does not mean every address is empty: it means the service stops counting for a network that has been switched off. Anyone who withdrew nothing in the spring has to look for themselves.

The case is the standard sequence at the end of a network. How a shutdown unfolds and what role the mainnet contract plays is set out in our overview of blockchains that have been switched off and how to secure your coins, which describes the same mechanics using a different network.

The Mint Chain withdrawal portal returns four assets to Ethereum mainnet

The portal at mintchain.io/withdraw is reachable and names exactly four positions it sends back: ETH, WBTC, USDC and USDT. Nothing else is listed. The interface is plain: connect a wallet, balances are read out, trigger the withdrawal. For questions the operator gives an address at its own team.

Two of the four positions are stablecoins, tokens pegged to the US dollar. WBTC stands for Wrapped Bitcoin: a token representing a Bitcoin held under a custody contract, which does not itself sit on the Bitcoin chain. That is precisely why WBTC is the most sensitive of the four on a wound-down layer 2: what you hold is a claim, and a claim needs a functioning counterparty.

Before you can see anything at all, the network has to be added to your wallet. How to add a network and use the right block explorer to check whether an address really still holds a balance is covered in our guide to networks, bridges and explorers. An empty portal window is no proof of an empty account if the wallet is pointed at the wrong chain.

Four coins on an industrial conveyor belt running towards a narrow illuminated slot in a steel wall
Withdrawals do not leave the network one by one: the portal collects the requests and sends them out once a week as a batch.

The ten-day figure: weekly batches instead of individual settlement

The sentence the entire timetable hangs on sits as a note beneath the withdrawal form. The operator writes there that withdrawal requests are processed once a week in batches and typically arrive within ten days. Two phrases in that sentence decide everything.

Once a week means the day you submit does not determine when processing starts. Submit shortly after a batch has gone out and you wait up to seven days before anything happens at all. Typically means ten days is the operator's rule of thumb, not a commitment. A figure described as typical can run longer in an individual case.

Add the two together and the span between request and arrival grows wide. A request on October 15 can, on paper, land after October 20. A request on October 10 has room even on an unfavorable batch cycle. That is why October 10 is the deadline that counts in this article, and October 20 merely the deadline that was published.

Why a second week of buffer would be better still

Anyone who wants certainty submits now rather than on October 10. The reason is mundane: a withdrawal that stalls needs time for a second attempt, and a second attempt needs another batch. Between today and October 10 there are several batch runs left. After October 10 there is at best one.

Challenge period and state root: why an OP Stack withdrawal takes days

The operator's ten days are not arbitrary; they have a technical cause. A layer 2 on the OP Stack reports its state to Ethereum in packages. Such a package is called a state root: a kind of certified statement of account for the network, filed on mainnet. Only once that statement is on file does the contract on Ethereum know how much of the layer-2 balance is yours.

Next comes the challenge period, the window for objections. During that time authorized verifiers can dispute a filed statement if it is wrong. While the window is open, the contract releases no funds. At Mint this window runs to at least three and a half days according to L2BEAT, and the withdrawal only becomes executable there seven days after the statement is filed.

The objection window, the weekly batch and the final processing step together add up to the ten-day figure. This is not a backlog that a polite enquiry could shorten, but the built-in latency of this architecture. The same latency explains why a layer-2 withdrawal rarely arrives the same day even on networks that are still running.

What L2BEAT notes on the question of trust

Two further entries in the same monitoring file belong to the picture, uncomfortable as they are. Mint does not even meet the lowest maturity stage there, because fraud proofs are open only to a closed circle of verifiers. And the network's administrative keys can change the contracts with no delay. For you that does not mean a withdrawal fails today. It means the safety of that withdrawal rests on a small group of key holders, and that an early withdrawal gives this circumstance less time than a late one.

Request or arrival: what the operator leaves open about October 20

The withdrawal portal itself names no date. It names the batch rule, the four assets and a contact address. The date of October 20, 2026 comes from the project's announcement of April 17, 2026 and was picked up by several trade publications in the same week, among them PANews and via the TechFlow news chain. The wording there is that users must withdraw their assets before October 20, 2026.

A "before October 20" does not answer the actual question. A withdrawal consists of two events, the request in the portal and the arrival on mainnet, and up to ten days sit between them by the operator's own account. Which of the two the date applies to is stated nowhere. That gap is exactly why October 10 stands as the cut-off in this article: it is the only reading that works under either interpretation.

One caveat belongs here and it stays: the date is an operator statement documented through media reports. The portal that handles the withdrawal does not carry it. Anyone who wants to be certain checks it once more on the project's official channel before submitting.

Hardware wallet with a cable attached to a closed laptop on a dark wooden surface, two coins beside it
The destination of the withdrawal is an Ethereum address whose keys are yours, not an exchange deposit address.

NFT holdings on an NFT chain: the portal names only four assets

This is the hardest point in the case, and it calls for an honest answer. Mint was built as a network for NFTs. The withdrawal portal lists ETH, WBTC, USDC and USDT. NFTs are not there.

What that means for NFTs held on this chain cannot be derived from the portal, and we are not going to assert a route we cannot document. The mechanics are certain: an NFT on a layer 2 is an entry in that chain's contract state. Remove the infrastructure that makes the entry readable and practical availability disappears, even if the entry formally persists. Anyone holding NFTs on Mint takes that question directly to the project team at the contact address given in the portal, and does so now rather than in October.

For the four named assets the opposite applies: there the route is open and documented. Anyone holding both withdraws the four assets first and settles the NFT question in parallel. An unresolved question is no reason to leave a resolved balance sitting.

Contract balance versus genuine holding

With USDC, USDT and WBTC on a layer 2 you are as a rule holding a bridged version: a token issued on the layer 2 whose backing sits in a contract on Ethereum. The withdrawal unwinds that link and releases the backing. What can be left behind when a bridge is no longer operated is something we described in the case of another bridged token: remaining balances after the end of a bridge.

After the deadline: the operator's statement on balances left behind

The announcement is terse on this point and identical in every reproduction: assets not withdrawn by the cut-off will no longer be processed and cannot be retrieved. The word used in the reports is unrecoverable.

Treat that statement as what it is: the operator's account of its own portal. It does not say a contract on Ethereum deletes itself on October 21. It says the operator is discontinuing settlement. Whether anything can still be moved via the mainnet contract afterwards is a question for specialists with access to the contract code, not for a holder with a wallet and a deadline. For the decision in front of you the distinction changes nothing: the reliable route ends on October 20, and your request belongs ten days before that.

Fake withdrawal portals: the scam pattern around networks that shut down

A publicly announced deadline is an invitation to fraud, and the reasons are uncomfortably good: the occasion is real, the time pressure is real, and the target group is known. Around networks that have been switched off, rebuilt withdrawal pages show up regularly, along with direct messages from supposed support staff and invitations to help groups.

Three markers separate the genuine process from the imitation. First: a withdrawal portal never asks for your seed phrase, the recovery sentence for your wallet. If it is requested, the process is over. Second: the portal address comes from a source you already had before the shutdown date, from a bookmark, the documentation or a trade publication, and never from a message that approached you. Third: nobody from support writes first. Support replies.

Then there is the approval itself. Connecting a wallet means giving a signature, and a malicious signature can release more than the single action you have in mind. What matters with such approvals, and which patterns stand out when a wallet connection is being forced, is set out in our piece on supposed checks that demand a wallet connection. Anyone facing a withdrawal of this size is best served by a wallet whose keys sit on a device of their own; we have set the differences between the custody types side by side in our comparison of software wallets.

The destination address is the second stumbling block

The portal pays out to an Ethereum address. Enter one whose keys belong to you. An exchange deposit address is risky at this point: many exchanges do not automatically credit incoming funds from bridges and settlement contracts, and an incoming transfer that is not credited automatically needs a support case. A support case takes time. Time is exactly what is short here.

For tax the withdrawal is not a sale: acquisition date and holding period run on

For investors in Germany the classification is pleasingly clear. Transferring your own coins from one address you control to another is not a disposal under income tax law. No taxable event arises, the acquisition date stands, and the one-year holding period under Section 23 runs on without interruption. A withdrawal from a layer 2 to Ethereum mainnet is exactly such a transfer.

In practice that means you give up no holding period through the withdrawal and trigger no tax. Two things are still worth the effort. Record the transaction with date, amount and the transaction hashes on both chains, so your portfolio tracker can reconcile the balances later, and treat a swap before the withdrawal as a separate event: swapping on the layer 2 before withdrawing is a sale, and sales within the first year are taxable.

The reverse case, should the deadline pass

Should a balance genuinely remain unreachable after the cut-off, that is not an automatically deductible loss. A loss from a private disposal requires a disposal, and an unreachable balance is not one. The treatment of such cases is not settled and depends on a case-by-case review by your tax office. That is the most expensive part of this deadline: a loss that does not count for tax is a double loss. Which is precisely why this section sits behind the cut-off rather than in front of it.

Mint Chain: How to proceed now

The sequence is short, and it has an expiry date. Do it in one go instead of pushing it into October.

  1. Establish the balance and prepare the destination. Add the Mint network to your wallet and check whether ETH, WBTC, USDC or USDT are still sitting there. Have an Ethereum address ready whose keys are yours; which custody type suits your amount is shown by the comparison of hardware wallets.
  2. Submit the withdrawal by October 10. Connect the wallet to the operator's withdrawal portal, submit the four assets and note the transaction hash. Only once the assets have arrived on Ethereum do you decide on the next step; if that runs via an exchange, choosing the venue belongs to that decision and not to the withdrawal: the crypto exchanges compared.
  3. Document the transaction and track the deadline. Write down the date, the amount and both transaction hashes, and check by October 20 that the arrival on Ethereum has actually been booked. That the acquisition date and holding period run on unchanged should be stated in your records too; the tools in our overview of tax software and portfolio trackers help with that.

If anything remains unclear after submitting, the contact address in the Mint Chain withdrawal portal is the only point of contact the operator names itself. Anything else that writes to you about this subject has not identified itself.

(As of September 30, 2026. This article is not investment advice. Prices and fee structures change; check the terms with the provider before you buy.)

Frequently asked questions about Mint Chain

Transparency note: This article was produced with the assistance of artificial intelligence and reviewed by our editorial team before publication. All figures and claims were checked against the primary sources linked in the text. The feature image was generated with AI.

Related articles

Which topics should we dive deeper into?

Select what genuinely interests you. Your picks feed directly into our editorial planning.

Crypto news that's actually worth your time.

Weekly. 60 seconds. Carefully curated by our editors: no hype, no promo flood, no spam.

Subscribe

More on this topic

View All

More from CryptoTicker