Skip to content

Add Oath Wallet to the Monad mainnet registry - #506

Open
devdasx wants to merge 1 commit into
monad-crypto:mainfrom
devdasx:codex/oath-wallet-directory
Open

devdasx wants to merge 1 commit into
monad-crypto:mainfrom
devdasx:codex/oath-wallet-directory

Conversation

@devdasx

@devdasx devdasx commented Oct 31, 2026

Copy link
Copy Markdown

Summary

Adds Oath Wallet to the mainnet registry under Infra::Wallet, with the website, public source, documentation and X links.

Oath is a native iPhone/iPad wallet. Its public network configuration includes Monad mainnet (chain ID 143, native asset MON). The app is available on the App Store.

addresses is intentionally empty, as permitted by the README: this submission identifies a mobile wallet, not an Oath-deployed Monad smart contract. No addresses or contract-verification claims are supplied. Generated aggregate files are left to the repository workflow.

Validation

  • Targeted validate_protocol.py --network mainnet --protocol oath-wallet: passed, with the expected empty-address-map warning.
  • Full mainnet validation: 189 files passed, including existing empty-address warnings.
  • Full testnet validation: 19 files passed.
  • ruff check .: passed.
  • ruff format --check .: passed (3 Python files).
  • git diff --check: passed.
  • Checked the documented category, required metadata and absence of a previous Oath/Aperture entry or Oath PR.

Verification is limited to public source configuration and metadata validation. No independent security audit, released-binary equivalence, physical-device test or live Monad transaction is asserted by this PR.

I am Oath Wallet's founder. Please review the entry and let us know whether any additional evidence is needed before merging. If a separate submission is required for the public wallet/infrastructure directory, could you point us to that route and the appropriate review email? We can respond at care@oathwallet.org.

@devdasx

devdasx commented Oct 31, 2026

Copy link
Copy Markdown
Author

GitHub shows that the CI and Verify PR Contracts workflows need maintainer approval for this first contribution. Could a maintainer approve those runs? The matching local mainnet/testnet validators and Ruff checks passed, as recorded in the PR description. The change is limited to one wallet metadata file and does not modify workflows. Thank you.

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