Hi Arbitrum community,
I’m Anzus from Gem Wallet, working across BD, community, and user support.
Gem Wallet is an open-source, self-custodial mobile wallet that supports Arbitrum.
Users can:
- Store, send, and receive Arbitrum ETH and supported ERC-20 tokens
- Buy Arbitrum ETH directly in the app
- Swap supported Arbitrum tokens
- Swap supported assets from other blockchains into Arbitrum ETH
- View addresses and transactions through Arbiscan
I created this thread to connect with the Arbitrum community, help users where possible, collect feedback, and pass useful suggestions to our developers.
If you use Gem Wallet on Arbitrum, please let us know what works well, what feels confusing, and what you would like us to improve.
Links:
For your safety, never share your secret recovery phrase or private key. For support questions, a public wallet address or transaction hash is normally enough to investigate an onchain transaction.
Thanks, and I look forward to hearing from the Arbitrum community.
1 Like
Thanks for introducing Gem Wallet to the community. I went through the Arbitrum documentation and the public GitHub repository (gemwalletcom/wallet) to evaluate the product beyond the surface‑level feature list. Sharing a structured review below.
What Gem Wallet does right:
-
Genuine technical architecture, not just a wrapper The wallet uses a shared Rust core (core/) powering both native iOS (SwiftUI) and Android (Kotlin/Compose) apps. This keeps blockchain logic consistent across platforms and reduces platform‑specific bugs a real engineering differentiator most competing wallets don’t have.
-
Verified security posture The GitHub repo links a third‑party CertiK security audit (April 2026) and a responsible disclosure/bug bounty program. Combined with GPL‑3.0 licensing, full source availability, and an F‑Droid listing (which open‑source‑purist users specifically trust), this is a credible security foundation.
-
Active, healthy development cadence ~8,900 commits, 105 releases (latest 2.109 shipped 2 days ago), 18 contributors including automated CI tooling. This is a continuously shipping project, not an announcement‑only wallet.
Where it currently falls short:
-
No Arbitrum‑specific differentiation Listed features (store/send/receive, in‑app buy, native + cross‑chain swaps, ArbiScan link, fee preview) are baseline parity with existing multi‑chain wallets (Rabby, Rainbow, MetaMask, OKX, Coinbase Wallet). No Arbitrum‑native tooling is mentioned no ARB governance/delegation UI, no curated Arbitrum ecosystem dApp directory, no L3/Orbit chain support.
-
Documentation‑repo disconnect on security/risk detail The Arbitrum‑facing docs never mention the CertiK audit, key‑management model, transaction simulation, or phishing/scam protection, even though this info exists at the repo level. Swap/cross‑chain flows also lack stated risk disclosures (slippage, bridge risk, routing/aggregator transparency).
-
Low adoption signal despite high dev activity Only 40 GitHub stars and 14 forks despite thousands of commits and 105 releases suggests visibility/community traction hasn’t caught up with engineering effort.
Questions for the Gem Wallet team:
-
What is Gem Wallet’s unique value‑proposition for Arbitrum users specifically, compared to existing wallets that already support the chain (Rabby, Rainbow, MetaMask, OKX, Coinbase Wallet, etc.)?
-
Are there Arbitrum‑specific UX improvements planned e.g., gas handling, token discovery, dApp integrations, or safety tooling (transaction simulation, phishing alerts, contract risk labels)?
-
Does Gem Wallet offer any novel security feature beyond standard self‑custody such as multi‑sig/social recovery, passkey support, or scam detection?
-
Is there a dedicated Arbitrum roadmap item e.g., native governance/delegation integration (Snapshot/Tally), ecosystem dApp directory, or Orbit/L3 support? (I saw a public GitHub Projects roadmap could you point to what’s specifically planned for Arbitrum?)
-
Beyond being open‑source, how does the team plan to leverage community contributions specifically for Arbitrum‑related development?
-
Can you share any adoption metrics (active Arbitrum wallets created, transaction volume, TVL routed through the app) to help delegates evaluate real usage vs. feature announcements?
Suggested next steps:
-
Surface the CertiK audit and security model directly on Arbitrum‑facing docs, not just the repo README.
-
Publish an Arbitrum‑specific roadmap item tied to governance/ecosystem integration.
-
Share adoption metrics if available
@Anzus_GemWallet
2 Likes
Thank you for taking the time to review Gem Wallet and share such detailed feedback. I appreciate both the positive points and the areas you believe we can improve.
To be transparent, Gem Wallet does not currently claim to have features that are exclusive to Arbitrum. Our main goal is to provide a simple, open-source and self-custodial mobile wallet where users can manage Arbitrum alongside assets from many other networks.
I agree that our Arbitrum documentation could make our security information easier to find, including the CertiK audit, security practices and reproducible builds. I will pass this suggestion to our documentation team.
Regarding adoption, Gem Wallet has more than 500,000 total downloads. However, we do not currently publish Arbitrum-specific user or transaction numbers, so I do not want to share figures that I cannot confirm.
I work mainly in BD and user support, so I’m not the right person to make promises about technical features or the development roadmap. I will share your questions about governance, Orbit networks, token discovery, security warnings and other Arbitrum-specific improvements with our developers.
Community members can also submit issues and suggestions through our public GitHub repository. Part of my role here is to collect useful feedback from Arbitrum users and make sure it reaches the right people on our team.
Thanks again for the honest review. This is exactly the kind of feedback I created this thread to receive.
1 Like
