[GigaHierz]

Refs #2314, #2320, #2324, #2343

Each weekly assistant report lists readers' questions that returned no citation. The recurring in-scope ones were wallet and funds basics: connecting MetaMask, finding an address, recovering a wallet, tokens not showing, moving money in or out.

What changed

• home/wallets.mdx: new ## Troubleshooting (five short entries) and ## Related; description rewritten to use the words readers ask with. No new addresses, numbers or availability claims.
• Review fixes:
  • "Recover a wallet" (was "You cannot sign in or recover a wallet") now says recovery depends on the recovery phrase or private key, that no one else can recover the funds, and never to share the phrase with anyone claiming to be support. It no longer tells readers to contact support.
  • Removed the /home/manage/self-custody bullet from ## Related: that page is a Celo CLI plus Ledger guide for ReleaseGold beneficiaries.
  • The MetaMask entry embeds the one-click AddNetworkButton (as home/celo.mdx does) and links the network overview, instead of the developer-oriented setup page.
  • The missing-token entry tells readers to use the Celo Mainnet column of the stablecoin contracts table.
• Edited in place, so no page moves (story: Split wallet docs into an end-user page and a developer wallet-integration page #2256 will split this page later; this keeps the edit small).
• Another open PR (docs(wallets): split the wallet docs into an end-user page and a developer integration page #2350) edits the same file. Whichever merges second should reconcile the description (keep "connect MetaMask, find your address and move funds in or out") and ## Related.

Deliberately not written (need an owner's input)

• Country availability (e.g. "can I use it in Nigeria"): needs a statement from the wallet/ramp owners; the page only says availability depends on the provider.
• Official partnership contact/form, and whether any rewards/points program exists.
• Questions about a specific "relayer" or third-party tokens: ambiguous or not Celo docs.
• Probe/injection and off-topic questions: no doc change.

Verification

$ mint broken-links
success no broken links found
$ bash scripts/check-orphans.sh
No orphan pages found.

mint dev render check: the Troubleshooting section renders and the "Add Celo Mainnet to your wallet" button shows (Playwright).

🤖 Generated with Claude Code

[palango]

Good scope: the questions picked are the ones readers keep asking, and leaving availability, partnerships and rewards out is the right call. All internal links resolve, and the description and section order follow AGENTS.md.

Two entries send readers to the wrong place, though, and I'd fix those before merge (inline comments). The recovery one matters most because of the scam risk. The other two inline comments are smaller.

One thing I couldn't check: whether current MetaMask builds already list Celo among their built-in networks. If they do, "MetaMask does not show Celo until the network is added" needs softening.

[palango]

This is wrong for every wallet on this page, and the wording is risky. They are all non-custodial: whoever holds the recovery phrase or private key controls the wallet, not the app. If the phrase is lost, the wallet's support team can't recover the funds either. Telling stuck users to "contact support" is how the fake-support scam usually starts.

Suggested direction:

Celo has no usernames or passwords. A wallet is controlled by its recovery phrase (seed phrase) or private key. To restore a wallet, import the recovery phrase into a wallet app. Without it, no one can recover the funds: not Celo, and not the wallet's maker. Never share your recovery phrase with anyone, including people who say they are support.

("No accounts" is also loose, since an address is an account, so I'd say "usernames or passwords" instead.)

[palango]

/home/manage/self-custody doesn't match this description. It is a Celo CLI + Ledger guide for ReleaseGold beneficiaries who gave their address to cLabs. It doesn't explain how to keep control of your own funds. I'd drop this bullet.

[palango]

/tooling/wallets/metamask/setup is the developer page ("Programmatic Setup", a wallet_addEthereumChain JS snippet). An end user is better served by the one-click AddNetworkButton on /build-on-celo/network-overview, or you could embed it here as home/celo.mdx does (import { AddNetworkButton } from '/snippets/AddNetworkButton.jsx'). The mislabel came from tooling/wallets/metamask/use.mdx, which lists the same page under "For end users". That one is a separate fix.

[palango]

The stablecoin contracts table puts mainnet and Celo Sepolia addresses side by side, so a reader can easily copy the testnet one. Worth adding "use the Celo Mainnet column".

[palango]

Re-checked on the same head (dfe9f28). The four inline comments from my earlier review still apply, and the recovery one (line 191) is the one I'd want fixed before merge.

I checked the open question from that review: neither the MetaMask extension (FEATURED_RPCS in shared/constants/network.ts) nor MetaMask mobile (PopularList in customNetworks.tsx) lists Celo as a built-in or popular network, so "MetaMask does not show Celo until the network is added" is fine as written.

This PR and #2350 conflict on the description line of home/wallets.mdx. Whichever merges second should keep the "connect MetaMask, find your address and move funds in or out" wording if this Troubleshooting section is in, since that is what the description is meant to match.

[GigaHierz]

Review points addressed in 6c2c588 (home/wallets.mdx):

• Wallet recovery entry: now "Recover a wallet" with the suggested wording; no "contact support".
• ## Related: the self-custody link is removed (it is the ReleaseGold beneficiary guide).
• MetaMask: embeds the add-network button for mainnet and links the network overview, instead of the developer setup page.
• Token entry: adds "use the Celo Mainnet column".
• description keeps the "connect MetaMask, find your address and move funds in or out" wording.

mint broken-links and the orphan check pass; the page renders under mint dev and the button shows (chain ID 42220). I did not click it, since that needs a wallet extension. #2350 edits the same file, so whichever merges second has to reconcile the description and ## Related; the two conflict only there.

[palango]

Thanks, all four points from my last review are fixed. The recovery entry says the right thing and no longer sends people to "support", the MetaMask entry uses the one-click mainnet button, the self-custody link is gone, and the token entry points at the Celo Mainnet column. Links resolve and CI is green.

One note for whichever of this and #2350 lands second: they conflict in three places, not two. The frontmatter (#2350 renames the title to "Wallets for users"), the top of the page, and Troubleshooting plus Related at the end. The top one matters most: the AddNetworkButton import sits next to the <Info> block #2350 replaces, so if the resolution takes #2350's side there, the import goes and the button breaks. When merging Related, keep #2350's dash format, which is what AGENTS.md asks for. #2352 merges cleanly with this.

[GigaHierz]

#2350 merged first, so I merged main into this branch (b5af7bb) to resolve the one conflict, in home/wallets.mdx. Nothing else changed:

• Title, intro and ## Related follow the merged wallet split ("Wallets for users", the developer-page link, and the fee-abstraction link).
• The description keeps the "connect MetaMask, find your address and move funds in or out" wording.
• The Troubleshooting section is exactly what you approved.

mint broken-links --check-redirects and the orphan check pass. The push dismissed the earlier approval, so this needs another look.