Mintable
Mintable is sunsetting its NFT marketplace, shifting users from trading NFTs to taking direct control of their wallets and assets.
Updated on
Mintable announced in 2026 that its NFT marketplace and Mintology product were being sunset while the company pivoted to a different business area. For users with a Mintable custodial wallet, the immediate issue was taking direct control of its private key and associated NFTs, ETH, and store or smart-contract addresses. The published process revealed the wallet's private key after account verification, then required importing that key into MetaMask. Assets already tied to an external wallet remained controlled through that wallet. The sunset notice also separated marketplace availability from on-chain ownership and metadata hosting, so each part needed to be checked independently.
The functions the marketplace provided before sunset
Before the sunset, the marketplace combined NFT creation, sales, collection management, and wallet access. Those functions served different purposes, and they did not all depend on the same form of custody.
Creation, ownership, and sales
Creators used the service to prepare NFTs and listings, while collectors used it to buy or resell eligible assets. Its documentation centered on Ethereum wallets and ERC-721 tokens. Listing an NFT did not change its owner; ownership changed only when a sale or transfer transaction completed. The connected wallet identified the account, while its owner signed blockchain actions that sent or received NFTs or ETH.
- Creation tools prepared NFT metadata and sale information.
- Marketplace listings presented owned NFTs to prospective buyers.
- Wallet connections authorized transfers and other blockchain actions.
- Custodial accounts gave some users a managed route into Ethereum assets.
Gasless creation and delayed wallet visibility
The historical gasless flow used a signed message instead of requiring an immediate Ethereum transaction from the creator. Many wallets discover NFTs by watching blockchain Transfer events, so an item created through that flow might not have appeared in a wallet at once. The relevant event occurred when the NFT was bought or transferred. This distinction mattered during the sunset because a marketplace record, a wallet display, and an on-chain ownership record were related but separate forms of evidence.
Custodial access and on-chain ownership
Custody determined the required response. An externally controlled wallet already placed key management with its owner, while a custodial wallet left that control inside Mintable's account system until the user claimed it.
Assets held through an external wallet
A connected external wallet did not depend on a marketplace password for blockchain control. The owner could continue to access the wallet through its private key or recovery method and authorize activity at that address. Marketplace pages could stop working without changing the address recorded as an NFT's owner. Access still depended on keeping the external wallet's credentials and using a compatible interface for the relevant network and token.
Assets held through a custodial wallet
Claiming a Mintable custodial wallet gave the user exclusive control of its private key and the assets associated with its address. The documented scope included NFTs, ETH, and store or smart-contract addresses associated with the wallet. After custody was taken, the key was deleted from Mintable's servers, and the company could no longer retrieve the wallet. That finality made secure key storage part of the migration itself, not a task to postpone until later.
Which assets moved with the custodial wallet?
The custody claim gave the user control of the existing wallet and its documented NFTs, ETH, and associated store or smart-contract addresses; it did not create a replacement balance. Importing the disclosed private key into MetaMask gave the user access to the same blockchain account. The NFT and ETH balances did not need a separate transfer merely because the wallet interface changed.
Store or smart-contract addresses tied to that wallet were also included in the documented custody scope. Their presence did not mean that every marketplace feature would remain available after the sunset. The key authorized the account, while contract code, token records, marketplace listings, and hosted metadata continued to have their own states. Keeping the wallet address, contract address, and token identifier made those states easier to distinguish.
A three-stage custody handoff
The published migration path linked account access to a private-key handoff and then to independent wallet control. Each stage relied on a prerequisite that the next stage could not replace.
The normal path began with access to the registered account and ended when the same blockchain address appeared in a self-controlled wallet.
| Custody stage | Required state before proceeding |
|---|---|
| Verify the account | Access to the Mintable login and the registered email that received the one-time password |
| Reveal and secure the key | An uninterrupted browser session and a private place to record the key |
| Import and confirm control | MetaMask installed with its private-key import function available |
If the browser closed or the connection failed during the key step, the documented edge case froze the wallet again. Recovery meant restarting the process rather than assuming that the partial attempt had completed. Importing the key and confirming the expected Ethereum address established control. Any later on-chain transfer could require ETH for gas, with the actual cost determined by the transaction and network conditions.
Metadata, token records, and marketplace availability
The sunset notice said Mintable would continue hosting NFT metadata until the company itself shut down. It also described a plan to move that metadata to a more decentralized permanent solution if such a shutdown occurred. That statement addressed hosting continuity, but it did not make the marketplace itself permanent or provide a calendar deadline for each transition.
An Ethereum token record and the media associated with it are not necessarily stored in the same place. A contract can record ownership and point to metadata, while an image, video, or other file may depend on separate storage. A missing marketplace page or thumbnail therefore did not, by itself, prove that an NFT had disappeared from the blockchain.
Checking the holder address, contract address, and token identifier separated an ownership question from a display problem. This was more informative than relying on a single dashboard, especially when the dashboard supported only certain networks or token formats.
What could go wrong during the custody transfer?
The main failure points involved account verification, an interrupted key reveal, exposure or loss of the private key, and confusion between a display problem and an ownership change.
An interrupted key reveal
Closing the browser or losing connectivity during the disclosure step could freeze the custodial wallet again. The instructions said to restart the custody process. A partially displayed key should not have been treated as proof that migration had finished.
Private-key exposure or loss
Anyone who obtained the exported private key could control the wallet and its assets. Storing it in an untrusted website, email draft, screenshot, or exposed cloud file created a direct access risk. Once Mintable deleted its copy, losing the user's copy also removed the platform's ability to recover the wallet. The safer record was one kept offline in a location that only the owner could access.
Display problems after import
A token could fail to appear because the wrong account or network was selected, its metadata did not load, or the interface did not support its token format. The documentation listed Ethereum mainnet and ERC-721 support and said ERC-1155 tokens were not supported. The wallet address and blockchain record were therefore stronger ownership checks than a gallery thumbnail alone.
Life after the marketplace sunset
The company said the business would pivot rather than shut down, but its NFT marketplace and Mintology product were being retired. Users could not treat that corporate distinction as a promise that marketplace creation, buying, selling, or account interfaces would continue unchanged. The custody handoff put control of the wallet address and its on-chain assets in the user's hands, but it did not preserve the marketplace tools.
Self-custody made wallet control independent of marketplace account access, but it transferred recovery and security duties to the user. A custodial wallet still depended on that system remaining available and able to authenticate the account. Claiming the existing key preserved the same address without an extra asset transfer, while moving assets to another address would have created separate transactions, network fees, and the need to verify each destination because completed blockchain transfers are irreversible.
Useful questions about Mintable
Did Mintable publish a deadline for custodial wallet migration?
No calendar deadline appeared in the sunset notice. It said users would be allowed to migrate custodial wallets, and the custody instructions described the process, but the absence of a stated date did not establish an unlimited window. Account access and the registered email were still necessary to complete verification.
Does claiming custody send NFTs to a new address?
No, importing the disclosed private key gives access to the existing Ethereum address. The NFTs and ETH remain associated with that address when MetaMask becomes the wallet interface. A separate blockchain transfer occurs only if the owner later sends an asset to another address.
Where should the exported private key be kept?
The private key should be recorded somewhere private and offline, away from screenshots, email, cloud notes, and untrusted websites. Anyone who obtains it can control the wallet. After custody was claimed, Mintable deleted its copy and could not restore access if the user's copy was lost.
How was account access verified before the private key was disclosed?
The process used a one-time password sent to the email registered with the Mintable account. That code verified account access before the private key was disclosed. The code and private key were both sensitive credentials, and neither needed to be shared with another person to complete the documented flow.
Are store and smart-contract addresses part of the custody claim?
Yes, the custody documentation included store or smart-contract addresses associated with the custodial wallet, along with NFTs and ETH. Claiming the wallet transferred control of its key, but it did not guarantee that every former marketplace interface or listing function would remain available.
Does an empty dashboard mean an NFT is gone?
No, an empty dashboard can reflect the wrong wallet, the wrong network, a metadata loading failure, or an unsupported token format. Ownership should be checked against the Ethereum address, contract address, and token identifier. A missing image or marketplace entry alone does not establish that the token was deleted.
When did a gasless Mintable NFT become visible to wallets watching Transfer events?
The historical gasless flow did not produce the initial Transfer event that many wallets used for discovery. That event appeared when the NFT was later bought or transferred, including a transfer to another wallet controlled by the same owner. Before then, marketplace visibility and wallet visibility could differ.
Will later Ethereum transactions require ETH for gas?
Yes, an owner-controlled wallet needs ETH when it submits an Ethereum transaction that charges gas, such as transferring an NFT. Importing an existing private key is an account-access action rather than an on-chain transfer. The later transaction cost varies with the action, gas settings, and network conditions.