Support

You can read, research and browse without connecting a wallet. Connect only when you are about to do something onchain.

• Start on Home — that is the MPGR Agent. There is no separate Agent tab.
• Ask a question first (“what is MPGR?”, “research Base markets”, “analyze my portfolio”). The Agent answers from read-only tools.
• When you want an action, ask for it in plain language. The Agent prepares a proposal; nothing is signed until you confirm.

New here? Read About and Docs → getting started.

“Wrong network” in the header

MPGR HUB is Base mainnet only (8453). Tap Wrong network and switch to Base in your wallet, then retry. Adding Base manually is rarely necessary — Coinbase Wallet, Rainbow and most injected wallets already ship it.

The wallet won’t connect

• Use a supported path: Coinbase Wallet, WalletConnect, an injected browser wallet, or the Farcaster Mini App connector.
• If you are inside an in-app browser, open MPGR HUB in your wallet’s own browser or in a normal mobile browser with WalletConnect.
• If a previous connection is stuck, disconnect from the wallet side and refresh the page.

“Authentication required” on an action

Protected writes need a signed session, not just a connected address. When prompted, sign the SIWE message — it is a signature, not a transaction, and it costs no gas. If the session has expired, sign out from Profile and sign in again.

Rate limited

AI, XP, referral, x402 and trade routes are rate-limited per IP and per wallet, with a daily AI token budget. If you hit a limit, wait and retry — it is not a bug and retrying faster will not help.

Before you sign

• Check the amount, the asset, the destination or route, and the network in your wallet, not only in the app.
• Read the risk facts in the confirmation. “Unverified token”, “no liquidity” and “insufficient balance” are blockers, not decorations.
• An approval transaction is not the action itself — for some swaps it is a prerequisite, and its receipt is confirmed before the swap is sent.

After you sign

• The app waits for the receipt and reports success or failure from the receipt status. A failed transaction is reported as failed.
• If a transaction is pending for a long time, check the hash on BaseScan. Congestion and low gas are outside the app’s control.
• If it reverted, the usual causes are slippage exceeded, a stale quote, insufficient balance or a revoked allowance.

The Agent will never do these

• Sign, broadcast or pay on its own.
• Hold your keys, your funds, or a balance on your behalf.
• Ask for your seed phrase or private key.
• Claim a transaction succeeded before it is confirmed on-chain.

“The Agent gave me an unexpected answer”

• Model output is text, not authority. Treat numbers it gives you as a starting point and confirm in the product surfaces.
• If a live value looks wrong or is missing, the correct behaviour is DATA_UNAVAILABLE — not a guess. Wait and retry.
• Clear the conversation and restate the request in one sentence. The intent detector works on a closed intent list, so precise phrasing helps.

“The Agent asked me to confirm something I didn’t ask for”

Cancel it. Nothing has been signed until you approve it in your wallet. Every value-moving action — transfer, swap, B20 order, x402 payment — requires an explicit confirmation, and cancelling costs nothing.

More detail: Docs → MPGR Agent and Docs → Agent workflow.

• “Quote expired”. Quotes are valid for 30 seconds and are refreshed automatically; a worse minimum-output aborts the execution. Request the quote again.
• “No liquidity”. The provider reported no route or no pool liquidity for that pair. Nothing will be signed. Try a smaller size, a different pair, or a different asset.
• Slippage too high. Slippage is clamped to 0.01%–5% (1% default). If a trade needs more than 5%, MPGR HUB will not prepare it — that is intentional protection, not a bug.
• Tokenized stocks behave differently. Coinbase B20 assets (AAPLc, TSLAc, NVDAc and the rest) route through Aerodrome Slipstream USDC pools, not CDP or 0x, and there is no retail mint path.
• Reverted swap. Usually slippage moved against you between quote and execution. Retry with a fresh quote.

See Docs → trading & swaps and Docs → tokenized stocks.

• XP looks stale. The authoritative XP total is the server ledger (/api/xp), not the browser. The app syncs it; a browser value is only a cache.
• Rank looks wrong. The leaderboard is built from the server ranking. Client scores are never used for ranking, so a local value that disagrees with the board is the local value that is wrong.
• Claiming. Real MPGR claims are on-chain through the deployed reward vault. If a claim fails, it is a wallet or network issue — check the transaction on BaseScan.
• Season points reset. Seasons run on UTC calendar months. Season points are the XP you earned inside the current window, so they restart each month by design.
• Referrals. A referral is credited once the referred wallet holds a valid signed session. Self-referral is blocked and logged, and re-attributing a wallet is rejected.

See Docs → rewards, Docs → XP and Docs → seasons.

• A run did not register. Runs are server-issued and verified. If the session expired, lost heartbeat, or your connection dropped, start a new run from MPGR Run after reconnecting.
• XP is capped. MPGR Run awards 8 XP per completed run, capped at 10 XP-earning runs per day. Extra runs still count toward campaign and eligibility logic.
• No cash rewards yet. Competitive financial game payouts are disabled by default behind two operator gates. XP and season progression run regardless.
• Only one game is playable. MPGR Run is the only live title. Everything else in the catalog is marked coming soon and is not playable.
• Performance on mobile. Close other tabs, keep the game tab in the foreground, and make sure the session stays connected during a run.

See Docs → MPGR Run and Roadmap → MPGR Run.

• Stake below the minimum. The staking contract enforces a 100 MPGR minimum per stake.
• Staking has no lock term. You can stake, claim or unstake at any time; rewards accrue continuously.
• Token lock is a commitment. Early unlock is always available but the contract takes a fixed 10% penalty — 90% returns to you, 10% goes to the penalty recipient. That split is executed on-chain, not by the app.
• Numbers look delayed. Contract reads are cached for short TTLs and refreshed in the background; give it a few seconds or reload.
• History is backfilled progressively. Older staking events appear over successive refresh cycles rather than all at once.

See Docs → staking and Docs → token lock.

• MPGR HUB is non-custodial. Nobody on the team can move your funds or recover your wallet.
• There is no official “support DM”. Anyone contacting you first with a fix, an airdrop or a refund is a scam.
• Verify contracts and transactions on BaseScan yourself. Contract addresses are listed in the whitepaper.
• Beware of look-alike tokens. $MPGR has a fixed supply and a published contract address — check it before you buy.
• Do not paste secrets, seed phrases or private keys into the Agent conversation.
• Report vulnerabilities privately through a GitHub Security Advisory. Never post exploit details in a public issue.

See Docs → security model and Whitepaper → risks.

The sections people need most often:

Official channels. Anyone else claiming to be official support is not.

Before you report a bug

• Note the route or page, what you expected and what happened.
• If it involves a transaction, include the hash — but never include a seed phrase, private key or API secret.
• Confirm you are on Base mainnet (8453) and that your session is signed in.

Related: Docs · Roadmap · About · Terms · Privacy