Common errors and fixes during Ritual Testnet usage.
Wallet not connecting
MetaMask or your wallet extension is locked, or the browser blocked the connection popup. WalletConnect may also fail if the project ID is misconfigured.
Wrong network / Switch to Ritual prompt
Your wallet is on a different network (e.g. Ethereum Mainnet). The sidebar shows a red 'Switch to Ritual' warning. Note: the top navbar always shows 'Ritual Testnet' regardless of actual chain — trust the sidebar warning instead.
Not enough testnet gas (RITUAL)
Your wallet has 0 or insufficient testnet RITUAL tokens to pay for transaction gas. You need testnet RITUAL — not real ETH.
Transaction stuck as pending
Transaction was submitted but not yet mined. This can happen due to low gas or RPC congestion on the Ritual Testnet.
Transaction failed
The transaction was submitted but reverted on-chain. Common causes: wrong phase, insufficient payment, contract condition not met, or insufficient gas.
Transaction stuck on 'Confirming…'
VastMint is waiting for the transaction receipt but the RPC endpoint is slow or dropped the connection. This affects mint, deploy, and buy flows.
Mint button says 'Mint Paused'
Every newly deployed collection starts in Paused phase by default. The creator must manually enable Public minting before anyone can mint.
Mint failed
Minting was unsuccessful. Common causes: collection is paused, wallet mint limit reached, collection sold out, insufficient RITUAL, or IPFS metadata not ready.
Whitelist mint failing
Whitelist minting requires a valid Merkle proof. The current UI sends an empty proof, so whitelist minting will always fail even if your wallet is intended to be whitelisted.
NFT image or metadata not loading
IPFS gateway is slow or the content was not fully pinned. NFT images may show broken placeholders in the Marketplace, Dashboard, and collection pages — errors are hidden silently.
NFT not showing in Dashboard
The Dashboard scans blockchain Transfer logs to find your NFTs. RPC range limits, slow indexing, or many collections can cause some NFTs to appear missing even when you own them.
Load More not showing more NFTs
The RPC log scan may have hit range limits and skipped some chunks, returning partial results. Load More may also be hidden if the scan returned an incomplete first page.
List NFT button does nothing
The listing price input silently rejects empty, zero, negative, or comma-decimal values (e.g. '0,05'). No error is shown — the button just does nothing.
NFT not showing in Marketplace
Minting does not automatically list your NFT. You must list it manually from the Dashboard. If already listed, the marketplace may take time to index it.
Approve button not working
The Approve step grants the marketplace contract permission to transfer your NFT. It may appear unresponsive if a previous approval is still pending, or if you are on the wrong network.
List NFT failed
Listing requires prior approval. It also fails if the NFT is already listed, the price is zero, or you are no longer the token owner.
Buy NFT failed
Purchase fails if the listing is no longer active (already sold or cancelled), you are the seller, or you have insufficient RITUAL. Errors on the collection page are hidden — only the buy button resets.
Cancel listing failed / button resets silently
Cancel errors are hidden in multiple places — the button resets with no message. This happens if the listing is already sold, you rejected the transaction, or you are on the wrong network.
Marketplace listings not loading
The marketplace reads all listings on-chain. As listings grow, this can become too expensive for the RPC to handle. A fallback reads only the last 250 listings — older active listings may not appear.
Collection not showing after deploy
The factory contract emits an event on deploy, but the UI scans logs to find it. RPC delays, wrong scan start block, or many existing collections can cause your new collection to appear missing.
Deploy failed — image upload error
Each NFT image is uploaded one-by-one to IPFS. The upload API rate-limits at 10 requests per minute. Larger collections (10+ images) can hit this limit. Files over 10MB or unsupported formats also fail.
Deploy failed — slug conflict or invalid name
Collection names are converted to a URL slug. If the slug is already taken by another collection, or if your name contains only special characters (producing an empty slug), the deploy transaction will revert.
Deploy failed — CSV metadata mismatch
The CSV parser does not support quoted fields or commas inside values. If your metadata descriptions contain commas, or you use Windows line endings, the row count may mismatch your max supply.
RPC error or page loading too long
VastMint uses a single Ritual Testnet RPC endpoint with no fallback. If this endpoint is down or rate-limiting, reads across the entire app will fail — listings, NFT scans, mint prices, and transaction confirmations.
VastMint is on Ritual Testnet — issues are expected. If your problem persists, reach out on @vastmintxyz on X.