> For the complete documentation index, see [llms.txt](https://docs.kumbaya.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kumbaya.xyz/help/troubleshooting.md). # Troubleshooting Common problems and how to fix them. ## "Slippage exceeded" **What it means**: the price moved more than your tolerance allowed between clicking and confirming. **Fix**: bump your slippage tolerance (gear icon ⚙️ on the swap card), or reduce the trade size. For new launches or thin pools, 1–3% is reasonable. See [**Slippage and gas explained**](/trading/slippage-and-gas.md). ## "Insufficient gas" **What it means**: you don't have enough ETH to pay the network fee. **Fix**: top up your ETH balance. On MegaETH gas is cheap, but you do need a small amount. ## "Token approval required" **What it means**: this is your first time swapping this token from this wallet. The pool needs your permission to move it. **Fix**: click **Approve \[TOKEN]** and sign in your wallet. You only do this once per token per wallet. ## "Pool not found" **What it means**: there's no Kumbaya pool for the exact pair you're trying to swap. **Fix**: try routing through ETH or USDC. Most tokens have an ETH or USDC pool — the swap UI will route through them automatically when possible. ## I can't see my new token If you just got tokens and they're not showing up: 1. **Check the chain.** Make sure your wallet is on MegaETH mainnet (chain ID `4326`). 2. **Refresh the token list.** Kumbaya updates frequently — a hard refresh of the page often fixes it. 3. **Add the token by address.** Click the token picker, paste the contract address. ## My liquidity position shows "Out of Range" That's expected behavior — the current price has moved outside the range you set. You stop earning fees while out of range, but you don't lose the position. Either: * **Wait** for price to move back into your range. * **Rebalance** by removing the position and opening a new one with bounds around the current price. See [**Managing your positions**](/liquidity/manage-positions.md). ## My embedded wallet (social login) is empty after signing in on a new device Embedded wallets are tied to your **login method**. If you signed in with Google originally and now you're using email, you'll have a different wallet. Sign in with the original method and your funds will appear. (This only affects social-login embedded wallets. If you connected an existing external wallet via "Kumbaya Wallet" or "DEX only", that wallet stays the same regardless of which path or login method you use later.) ## I picked "DEX only" and now I can't access the launchpad By design — the DEX only path skips the Kumbaya profile layer, so it can't see launchpad, comments, or tipping. Click on the wallet button top right and you should see a prompt to switch to a **Kumbaya Wallet**. Your existing wallet connection carries over. ## My token shows as "Unclaimed" The on-chain creator address hasn't been linked to your Kumbaya profile yet. If you launched the token, sign in with the wallet that called `ignite()` and click **Claim**. See [**If your token shows as Unclaimed**](/launchpad/unclaimed-tokens.md). ## My transaction is stuck pending Rare on MegaETH given block speed (\~10ms), but if it happens: 1. Wait 30 seconds — most "stuck" transactions on MegaETH clear quickly. 2. Check your wallet for a pending transaction; some wallets let you cancel or speed up. 3. If it's truly stuck, try increasing gas in your wallet's advanced settings. ## I clicked "Claim" but nothing happened Most common cause: the wallet you signed in with isn't the on-chain creator address. Kumbaya verifies the claim signature against the contract's `creator()` value — if your wallet doesn't match, the claim fails silently in some cases. Check the on-chain creator address on the block explorer ([mega.etherscan.io](https://mega.etherscan.io/)) and sign in with that wallet. ## Still stuck? * Check the [**FAQ**](/help/faq.md). * Reach out via [@kumbaya\_xyz](https://twitter.com/kumbaya_xyz) on X. --- # 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://docs.kumbaya.xyz/help/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.