Wallet & troubleshooting
Resolve common wallet, quote, transaction, and withdrawal issues without losing track of what was submitted.
Connect the right wallet and network
Choose a supported browser wallet and approve the app connection. If the account or network changes, refresh the basket and transaction preview before continuing. Mainnet is chain 4663; testnet is chain 46630.
Opening or refreshing the app does not itself request a wallet signature or network switch. An already approved provider may restore its session silently. Transaction approvals always happen in your wallet.
Common messages
| Situation | What to check |
|---|---|
| Wrong network | Switch the wallet to the configured chain and refresh the preview. |
| Insufficient ETH | Leave room for gas as well as backing and optional pool funding. |
| No active route | Change the token selection; an index listing does not supply liquidity. |
| Price impact or minimum amount fails | Adjust the amount or allocations and get a fresh quote. |
| Quote expired | Request a new preview, especially after waiting for an approval. |
| Shared-pool conflict | Change the selection so the independently quoted legs do not interfere. |
| API or index unavailable | Wait for recovery and inspect the explorer; do not interpret missing data as zero holdings. |
| Basket missing after launch | Keep the successful receipt and vault address while discovery catches up. |
If a wallet request is rejected
The action stops. Review the reason and start it again explicitly when ready. Rejecting a signature does not mean that an earlier submitted transaction was cancelled.
If the wallet shows a pending, replaced, or cancelled transaction, inspect its history and the chain explorer before repeating it. Keep transaction hashes until their final outcome is known. The app retains relevant creation and trade links after submission.
If an approval succeeds but the trade does not
An ERC-20 approval and a sale are separate transactions. An approval can remain active even if you reject, delay, or fail the later sale. Refresh the quote and check the exact requested spender and amount.
Disconnecting the app does not remove onchain token allowances. Manage or revoke those separately through tools you trust.
If a withdrawal token fails
A direct redemption records separate claims. Claim healthy constituents independently instead of assuming that one failed token locks all claims.
Use the withdrawal ID from the receipt if it is missing from this device’s recent list. The receiver is fixed when the withdrawal is created. A claim cannot be redirected by editing a display field.
An underfunded constituent’s claims remain blocked until its required coverage is restored. The vault does not let earlier claimants consume assets reserved for others. See redemption and claims for the full behavior.
Disconnect
Disconnect wallet clears the app session and remembered provider. The app also requests account-permission revocation from wallets that support it. If your wallet does not support that request, remove the site in its connected-sites settings.
Neither disconnection nor clearing browser storage changes onchain balances, approvals, or pending transactions. Keep any withdrawal IDs or transaction links you still need.
Report a problem safely
Useful debugging details include the public transaction hash, chain ID, vault or token address, time, and the visible error. Do not include a seed phrase, private key, server API key, or private RPC URL. No workflow in these docs requires sharing wallet secrets.