Skip to content

docs(wallets): add Oath Wallet to compatible wallets - #2419

Open
OathWallet wants to merge 1 commit into
celo-org:mainfrom
OathWallet:devdasx/oath-wallet-directory
Open

OathWallet wants to merge 1 commit into
celo-org:mainfrom
OathWallet:devdasx/oath-wallet-directory

Conversation

@OathWallet

Copy link
Copy Markdown

The hole, and the fix

Adds Oath Wallet to the existing Celo compatible wallets section of learn/wallets.mdx, with its homepage, iOS App Store listing, maintainer and public source links. It follows the surrounding directory format.

The currently available App Store listing identifies iPhone/iPad support and its version 4.1.2 release notes explicitly name Celo balances, tokens, transaction history and sending. I am contributing this entry on behalf of Oath Wallet.

What this does NOT do / residual risk

This is a documentation listing, not a wallet integration or security certification. It makes no claim of Celo-native fee abstraction, CIP-64, phone-number mapping, Android or browser-extension support. No device test or live transaction was performed for this documentation change.

Judgement calls

Placed under compatible wallets rather than Celo native wallets because the supported capabilities described here do not establish Celo-specific native features. No existing entries were changed.

Stacking / conflicts

Branched off main at 9c5a6ea, independent of other contributions. One file changed, 11 lines added.

Verification evidence

Validated the exact content committed as a0d551e:

  • npx mintlify@4.2.920 validate: success build validation passed.
  • npx mintlify@4.2.920 broken-links --check-redirects: success no broken links found.
  • bash scripts/check-orphans.sh: No orphan pages found.
  • git diff --check: passed.
  • Mintlify local preview at /learn/wallets#oath-wallet: entry rendered in the existing compatible-wallet section at desktop width and 390 x 844 mobile viewport, with the same heading/list styles as adjacent entries. No browser console errors captured.

No runtime code, CI, dependencies, redirects, navigation or money/security paths changed; code mutation and transaction tests are not applicable to this directory-only edit. Preview screenshots are retained locally and can be supplied if useful.

Remaining ops steps

  • Maintainer review and normal documentation deployment after merge.

Checklist

  • Conventional title describes the intended result.
  • Relevant documentation validation and link checks passed.
  • Desktop and mobile-width local browser preview checked.
  • Listing scope and verification limits stated above.
  • No secrets in the diff.

Question for maintainers: please let us know if additional listing evidence or a different directory format is required.

@OathWallet
OathWallet requested review from a team as code owners October 30, 2026 23:40
@OathWallet
OathWallet requested review from karlb and seolaoh and removed request for a team October 30, 2026 23:40
@mintlify

mintlify Bot commented Oct 30, 2026

Copy link
Copy Markdown
Contributor

Preview approval required

This pull request comes from a fork, so Mintlify won't build a preview until someone with write access approves commit a0d551e.

Approve preview

@OathWallet

Copy link
Copy Markdown
Author

@codex review

@OathWallet

OathWallet commented Nov 1, 2026 •

Copy link
Copy Markdown
Author

Hi Celo team, could someone with write access approve the Mintlify preview for commit a0d551e and review the Oath Wallet entry? Mintlify is waiting for approval even though its check is marked neutral.

The entry describes Oath’s iOS support for Celo and includes the App Store, website and source links. The PR documents the local validation already performed. Please let us know if you need any changes to the listing or supporting evidence. Thank you.

Workflow status update (1 November, current commit a0d551e1df): the following GitHub Actions runs also report action_required. Could a maintainer authorize the relevant fork checks?

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant