> For the complete documentation index, see [llms.txt](https://mixfun.gitbook.io/mixfun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mixfun.gitbook.io/mixfun/support/troubleshooting.md). # Troubleshooting > Common errors, their causes, and how to resolve them. ## Deposit Errors | Message | Resolution | | -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | | "Invalid denomination" | The amount does not match a deployed pool. Pick one of the listed denominations. See [Denominations](/mixfun/reference/denominations.md). | | "Pool does not exist" | The token or denomination combination has no deployed pool. Pick a different one, or contact MixFun if you need a new pool. | | "Insufficient SOL for gas" | Your wallet does not have enough SOL for the Solana priority fee on the deposit. Top up a small amount of SOL. | | "Transaction expired" | Solana network congestion. Retry the deposit; nothing is lost. | ## Withdrawal Errors | Message | Resolution | | ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | "Note already spent" | The nullifier for this note is already recorded on-chain. The note has been withdrawn. A note can only withdraw once. | | "Invalid proof" | The zero-knowledge proof failed verification. Regenerate the proof in the app. If it keeps failing, the note may be corrupted; re-paste the note. | | "Merkle root mismatch" | The proof was generated against an old merkle tree state. Regenerate the proof; the app will pick up the latest root. | | "Target account cannot receive" | The recipient wallet cannot receive the token. For SPL tokens, the withdrawal creates the associated token account automatically; if this still errors, verify the mint's token program (standard SPL vs. Token2022). | ## Relayer Errors | Message | Resolution | | --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | | "Relayer rejected" | The proof or request did not pass relayer validation. Check the error detail; often it is an invalid proof or a nullifier that has already been submitted. | | "Duplicate nullifier" | You or someone else already submitted a withdrawal with this note. | | "Relayer timeout" | The relayer could not land the transaction in its retry window, often due to network congestion. Retry later, or submit directly if your wallet has SOL. | ## Swap Errors | Message | Resolution | | --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | "Intent expired" | The engine could not fill your swap within its window (no matching counterparty, slippage too tight for Jupiter fallback). Your deposit is still in the swap pool. Cancel and resubmit with wider slippage, or withdraw the deposit directly as the input token. | | "Slippage exceeded" | The filled price moved past your maximum slippage. Resubmit with a wider slippage tolerance. | | "Jupiter route unavailable" | Jupiter V6 has no route for the pair at current prices. Wait and retry, or choose a different output token. | ## Stealth Errors | Symptom | Resolution | | ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | | "No announcements found" | No one has sent you a stealth payment yet, or the scan time window is too narrow. Widen the scan window or verify the sender actually published an announcement. | | "Stealth address has no SOL" | The stealth address needs SOL for gas to spend. Use the stealth relayer, or fund the address first (funding from a known wallet may defeat some of the privacy). | | "Meta-address registration failed" | Usually a temporary service issue. Retry. If persistent, your wallet may be rejecting the SIWS signature; disconnect and reconnect. | ## Wallet & Connection Errors | Symptom | Resolution | | ---------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | | "Connect Wallet" does nothing | Ensure the Phantom wallet extension is installed and unlocked. | | Wrong network (manual observation) | MixFun runs on Solana mainnet. Switch your wallet to mainnet in its extension settings. The app does not force-switch networks for you. | | Sign-in fails silently | The wallet may be rejecting the SIWS signature request. Approve in the wallet popup, or disconnect and reconnect. | ## Still stuck? For anything not covered here, contact MixFun support. Include: the flow, the step, the exact error message, and your wallet's public address if relevant. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://mixfun.gitbook.io/mixfun/support/troubleshooting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.