Testing Namada Mobile Wallets

[CryptoDruide]

Luminara sees mobile access to be key to real adoption.
Namada fee-sharing could support wallet devs long-term (see proposal), and there’s an active $20k bounty for wallet development.

Namada mobile wallets are emerging with at least 3 so far: One in stealth, another is preparing for demo. TNSO’s wallet (https://namadawallet.com) is ready for download so we’re starting with this. We’ll expand this thread as others are ready for testing.

Goal: gather feedback about the experience with suggestions for improvement.

Before we Start
We can’t verify the security of apps thoroughly. Please test responsibly.
Use a non-critical phone or isolate testing.

Android:

• Set up a secondary user profile (if supported)
• or use Android Studio on desktop

iPhone:

• No easy sandboxing available for public App Store apps

Security Tips:

• Deny anything non-essential.
• Use test keys only.

What to Evaluate

• Functionality & Coverage: Do core actions and essential features work as expected?
• UX: Is the experience intuitive and smooth for all users?
• Security & Stability: Any crashes, glitches, or unexpected behavior?
• Overall Quality: Does the product feel production-ready and safe for use?

Share Your Feedback

• Device + OS version
• What worked well
• What didn’t (technical bugs, or UI issues?)
• General thoughts (suggestions, concerns, or anything else)

Thanks for testing!
The more testers, the better the insights.

[CryptoDruide]

Features you can currently test in the TnSo App:

• Keys creation & import
• Transparent transfers
• Shielded sync
• Staking / Unstaking
• Governance list
• Balance display
• Transaction history
• Guides

[dismad]

I will test today, this is great

[dismad]

@CryptoDruide

What to Evaluate

• Functionality & Coverage: Do core actions and essential features work as expected?
• UX: Is the experience intuitive and smooth for all users?
• Security & Stability: Any crashes, glitches, or unexpected behavior?
• Overall Quality: Does the product feel production-ready and safe for use?

Share Your Feedback

• Device + OS version
• What worked well
• What didn’t (technical bugs, or UI issues?)
• General thoughts (suggestions, concerns, or anything else)

Device + OS

• Galaxy S22 Ultra
• Andriod 13 / One UI version 5.1

Mobile wallet notes

• Beautiful graphics, looks sharp!

• Seed phrase section should encourage writing down seed phrase and not copying or taking a picture

• needs to display QR code ( send funds from another phone / IRL person near by) so we can more easily get funds INTO the new wallet

• wallet tab doesn’t “refresh” when sliding finger down, have to go to a different tab then back to Wallet tab to see updated amounts

• needs a shield button ( shield emoji? ) right next to amounts displayed to encourage shielding

• First stake tx worked, but aftewords I couldn’t do another (see video)

• I think a wallet like this will be GREAT for governance, so easy to read and vote

Overall this product is ready for power users only, but shows huge potential. Thank you for all the work thus far!

Pictures

Videos

Transparent Swap

Overview of Wallet

[CryptoDruide]

Thank you very much for your test. Your feedback is very valuable !
Your comment about the addresses makes me think that, in addition to the QR code, having the ability to name and save trusted addresses could be a useful and practical feature.

[GE.Tnso]

Hey, thanks for feedback.
New android app version 1.1.5 is available now.

Changes:

1. Supported shielded address import/creation
2. Added QR code for transparent address on Wallet screen
3. Added refresh for swipe down gesture on Wallet screen
4. All validators are now available on the Stake screen
5. Fixed wallet alias display issue

[Quantum-Crypt]

Thank you! I’ve received 1 NAM and tried staking multiple times (0.5, 0.8 NAM etc.) using the Android wallet v1.1.5.
Each time I get the error:

Stake results:
[“*error”:“[*error”:“called Option::unwrap() on a None value”]"]

Also, my shielded address shows Error (code -1) and never loads. Could this be the reason staking fails?

I also tried to transfer NAM, but there are still no wallets that support NAM. The CLI lacks stability due to compatibility issues.

[GE.Tnso]

@Quantum-Crypt

Stake results:
[“*error”:“[*error”:“called Option::unwrap() on a None value”]"]

Please provide your device model.
Also, u can try to restart app: remove the app from background stack of your device and launch app again. You can do it using android context menu

@Quantum-Crypt

but there are still no wallets that support NAM

didn’t catch, what do u mean?

@Quantum-Crypt

Also, my shielded address shows Error (code -1) and never loads. Could this be the reason staking fails?

I don’t think so. What do u see when u presses “View Keys” on Wallet Screen?
Video/screenshots might help

[Quantum-Crypt]

My test result:

Phone model Samsung A72, OS Android 14.

[Quantum-Crypt]

Regarding crypto wallets:
At the moment, there is no anonymous and non-custodial crypto wallet that supports NAM. Popular wallets such as Cake Wallet, Samourai, and Keplr do not support NAM. While Unstoppable Wallet displays NAM in the market listings, it is currently not possible to add NAM to the wallet or manage it directly.

[GE.Tnso]

@Quantum-Crypt

Unstoppable Wallet displays NAM in the market listings, it is currently not possible to add NAM to the wallet or manage it directly.

Did you have a previous version of the app installed before 1.1.5?
I suppose there’s a backward compatibility issue.
Also we’ll research staking issues deeper in a coming days

Please try to re-import your existing account: Wallet → Add keys → Import existing keys.
And let us know if you get the same issues

@Quantum-Crypt

Regarding crypto wallets:
At the moment, there is no anonymous and non-custodial crypto wallet that supports NAM. Popular wallets such as Cake Wallet, Samourai, and Keplr do not support NAM. While Unstoppable Wallet displays NAM in the market listings, it is currently not possible to add NAM to the wallet or manage it directly.

Sorry I know almost nothing about others wallets, but you can test Namada transfer on the Namada infra: you need 2 accounts, for instance, create account in the mobile app and another one using Namadillo. And test transfers between your accounts

[Quantum-Crypt]

Yes, I had a previous version installed before 1.1.5

Thanks. I will re-import and create a second Namada account and check.

[Quantum-Crypt]

I managed to fix the issue where the shielded address wasn’t showing up. At first, I re-imported the seed phrase, but then an even bigger problem occurred — the balance wasn’t displaying, and all fields for the three keys were empty (see the screenshot). So I decided to delete the Namada Wallet, then reinstalled it, and everything started working: the shielded address appeared, and staking began to function correctly.

As for transactions, I tried connecting Namadillo and updated Keychain to version 0.8.1 — but it still doesn’t work. The thing is, Keychain works well on desktop, but right now I’m far from my PC. I tested it using Firefox Nightly in desktop mode. I barely managed to install Keychain, since it’s not compatible with mobile browsers. Now I’m trying to set up CLI transactions in Termux.

By the way, will Keychain be made compatible with mobile browsers in the future?

[Quantum-Crypt]

Just confirming my mobile testing participation.

• Device: Android (Termux, Firefox Nightly)
• Full bug report and build logs on GitHub: Issues building Namada CLI on Android (Termux) — errors, incompatibilities · Issue #4753 · namada-net/namada · GitHub
• Tried Namada Wallet, Namadillo + Keychain, CLI build attempts.

My shielded address for bounty consideration:
znam15vuhcxhvknyqh9jcurrj7zj8yhkhf6cekdchluwpaejlqhx80ste8r6r6fyl0vm0mpee50c6pqf

Thanks for the opportunity!

[CryptoDruide]

Device & OS

Pixel 6A
Android 16

Functional Feedback

Keys creation: OK
Wallet import: Transparent address and PK OK, however my shielded address is different.
Note: The wallet I initially created was removed after importing the second wallet. It’s no longer visible in the wallet tab.

Transparent transfer: OK
Shielded tab: generates an error:

Staking: First attempt returned an error, but the stake was successful.
Second attempt: success message displayed as expected.
Error message:

Unstaking: OK
Governance list: OK
Balance: Transparent balance is OK, but the shielded balance is not visible.
Transactions history: OK
Guide: I can only access one guide (“Your Security”)

Questions

1 - Validator list in the staking tab: How are they ordered?

UX and Design feedback

Wallet creation 1: Hide the text or add a disabled button background color:

Wallet creation 2: Align the copy icon vertically next to the addresses (see blue dots).:

Wallet import: What do you think about using a separate input field for each word instead of a large text area?

Staking:
1 - Show validator images.
2 - Consider adding an active “Stake” icon (e.g., with a yellow border) next to the “Unstake” icon. Since the claim option is currently inactive, the “Unstake” icon can be confusing.

Validator details: Would be great to display more information, such as a description.
Stake & Unstake token amount: A “Max” button would be useful (e.g., like on Aave).

Transfer:
Ensure horizontal alignment between the pictograms and the buttons:

Transactions History:
Display a “No transactions yet” message when the history is empty instead of showing a blank screen.

Account:
1 - The “Transaction History” and “Important Guides” buttons should each take up half the screen width.
2 - Capitalize the first letter of “password”, “wallet” and “us”

Overall thoughts

This is a really great start!
Most of my design feedback is minor, and the app already shows a lot of promise.
Really excited to see what’s coming next (shielded balance & transfer, IBC transfer, network editing, and more…)

[GE.Tnso]

Thanks for feedback!

We’ve released a new app version: 1.2.0

1. Shielding for NAM.
2. Shielded balance displaying.
3. Fixed empty state on Transactions History screen.
4. Fixed texts on Account screen.
5. Shielded sync adjustments.

[Quantum-Crypt]

I installed Namada Wallet on two identical Samsung A72 phones running Android 14. On the first try, I successfully transferred from one wallet to the other. However, when sending 0.1 NAM from one transparent address to another (starting from a total of 0.4 NAM), only 0.2500 NAM remained after the transaction:

Next, I tried to send NAM back from the second wallet to the first one, but some bugs or glitches occurred - it seemed the transaction didn’t go through to the first wallet, yet the amount disappeared from the second wallet:

In the end, I checked the first wallet - the amount from the second wallet never arrived:

I also noticed that at the moment, it’s not possible to undelegate (unstake) in the app. The first time I delegated 0.5 NAM, and 0.4 NAM remained on the balance - apparently, a 0.1 NAM fee was taken. But overall, staking works: after two days, I received my first staking reward:

[Quantum-Crypt]

For testing purposes, I also attempted to clone the installed Namada Wallet app from the regular (main) environment into an isolated second workspace (work profile).

The cloning process itself was successful.
However, when I tried to launch the cloned Namada Wallet app, it unexpectedly required Google Play to proceed.

As soon as I opened it (Namada Wallet), the system prompted me to “open or complete action via Google Play”, with no alternative options available. The app would not launch independently.

Here’s the screenshot of the prompt:

I also searched for a clean APK version of Namada Wallet - one that would be free of Google dependencies or libraries.

However, even the standalone APK (installed outside of Google Play) still requires Google Play for installation or launch. It cannot run independently without invoking Google Play Services.

Here’s the screenshot:

After testing and experimenting, I removed the cloned Namada Wallet from the second (isolated) workspace. Then I exited the second space and tried launching the original Namada Wallet in the regular (primary) environment.

However, upon opening, the app shows a loading screen and then automatically redirects to Google Play - as if it’s no longer launching the app itself, but the store page instead.

This is unexpected, especially since I didn’t modify or move anything in the original environment. It’s important to note that I cloned (copied) the app in the second space - I did not move or transfer it.

Here’s the video demonstrating the issue:
Video demonstration of the issue here:
Watch on GoFile
↔️ Or: Gofile - Cloud Storage Made Simple
GIF:

Summary:
All tested applications were successfully cloned, installed, and launched without requiring Google Play services for installation or execution.
Only Namada Wallet prompted a Google Play requirement for launching, even when using a clean APK outside the Play Store.

Suggestions:
To improve accessibility, usability, and trust in the Namada ecosystem, I strongly recommend:

Removing all dependencies on Google Play Services.

In the future, consider publishing Namada Wallet on F-Droid - a well-respected platform for open-source and privacy-friendly applications.

Doing so would align with Namada’s core values of decentralization and user sovereignty, while attracting more privacy-conscious users.

[Quantum-Crypt]

Bug Report: Namada Wallet v1.2.0 - Sync Failures, Crashes, and Wallet Naming Bug (Google Play Version).

After updating to Namada Wallet v1.2.0 via Google Play, I’ve encountered persistent issues related to shielded sync, app stability, and a critical bug in wallet creation - observed on two different Samsung devices.

Device 1:
Model: Samsung Galaxy A72, OS: Android 14

Device 2:
Model: Samsung Galaxy S25 Ultra, OS: Android 15

App Source: Installed and updated via Google Play

App Version: Namada Wallet v1.2.0

Problems Observed:

1. Shielded Balance Sync Fails

Status gets stuck on: Syncing… (up to 15 min)

Or shows error: Error fetching block height

Followed by app freeze or full crash.

2. Frequent Crashes, with system alerts like:
   “Namada Wallet has stopped due to an error.”

“Frequent crashes detected. Consider putting the app into deep sleep to improve performance.” -

3. Wallet Name Bug (Critical):
   When creating or importing a wallet using any name other than my_wallet, the app fails to initialize key data:

Fields for transparent, public, and shielded addresses remain empty

App cannot proceed to the final screen (Finish button does nothing)

This makes it impossible to use a custom wallet name or rename an existing one.

4. Steps Taken (on both devices):
   Cleared app cache and data

Fully uninstalled and reinstalled

Rebooted the system - issue persists after all actions.

Notes:
App was tested only via regular installation from Google Play

No cloning, modifications, or isolation environment used

Same error patterns occurred on both devices across Android 14 and 15.

Suggestions:
Please review the shielded sync mechanism and crash-handling logic - especially around block height fetching

Investigate the wallet naming bug to allow custom names (or at least proper error messages)

Enable wallet renaming in future releases

Ensure compatibility with both Android 14 and 15.

---

I add with editing:

I just checked Namada Wallet, and now it showed an error with the Transparent balance:

In version 1.2.0, Governance became unavailable; in the previous version, everything was displayed:

Minor improvements in the staking menu; the Unstake button is clickable, it proceeds further, but the amount is still not removed from staking:

IBC Transfer is not working, there are errors with Shielded. It either crashes the app or the Namada Wallet app closes by itself:

I checked and tested it now on a Samsung Galaxy A72 phone, Android 14.