Hi, everyone,
We’ve been digging through user feedback, edge-case scenarios to surface the most pressing problems affecting our community. This post is meant to keep everyone in the loop, encourage transparency, and invite collaboration. If you’ve encountered similar issues or have insights to share, feel free to jump in!
Namadillo Weekly Bug Report
Reporting Period: August 15-22
Submitted by: Support Squad
Ledger Wallet Integration
Symptom: Ledger hardware wallets are failing to sign transactions within Namadillo.
Impact: Users are unable to complete transfers or interact with Namada via Ledger.
Status: Reported across multiple OS environments; under investigation.
Balance Display Inaccuracy
Symptom: Namadillo occasionally shows incorrect wallet balances.
Impact: Users report mismatches between expected and displayed amounts after shielding/unshielding operations.
Withdrawal & Unshielding Failures
Symptom: Transfers out of Namada fail despite increasing gas limit to 5 NAM (maximum).
Workaround:
Reducing transfer amount may allow the transaction to proceed.
Alternatively, users must manually unshield assets before initiating outbound transfers.
MASP Proof Generation Delay Symptom: MASP operations (e.g. shielding, unshielding, transfers) take 3–8 minutes to generate proofs. Impact: Severely degrades user experience and usability of Namada via Namadillo. Notes:
Issue appears to stem from protocol-level performance, not Namadillo itself.
CLI tests pending; will cross-reference with protocol issues once confirmed.
More here: Masp proof generation takes too long · Issue #2292 · namada-net/namada-interface · GitHub
4 Likes
Namadillo Weekly Bug Report
Reporting Period: August 23–September 5
Submitted by: Support Squad
Ledger Wallet Integration
Symptom: Ledger hardware wallets are failing to sign transactions within Namadillo.
Impact: Users are unable to complete transfers or interact with Namada via Ledger.
Status: Reported across multiple OS environments; under investigation.
Balance Display Inaccuracy
Symptom: Namadillo occasionally shows incorrect wallet balances.
Impact: Users report mismatches between expected and displayed amounts after shielding/unshielding operations.
Withdrawal & Unshielding Failures
Symptom: Transfers out of Namada fail despite increasing gas limit to 5 NAM (maximum).
Workaround:
- Reducing transfer amount may allow the transaction to proceed.
- Alternatively, users must manually unshield assets before initiating outbound transfers.
MASP Proof Generation Delay
Symptom: MASP operations (e.g. shielding, unshielding, transfers) take 3–8 minutes to generate proofs.
Impact: Severely degrades user experience and usability of Namada via Namadillo.
Notes:
- Issue appears to stem from protocol-level performance, not Namadillo itself.
- CLI tests pending; will cross-reference with protocol issues once confirmed.
New Addition – September 5
Shielded Rewards & Balance Inaccuracy
Symptom: Shielded rewards and shielded balances are displaying incorrect values across all asset types.
Impact: Users may see outdated or misleading totals, affecting trust and usability.
Fixes:
- User might need to invalidate the shielded context in the MASP settings.
- Clear browser cache to refresh local data and sync with current state.
If you notice any bugs, inconsistencies, or unexpected behavior—please report them! Every bit of feedback helps us improve Namadillo and support the community more effectively.
1 Like
Namadillo Weekly Bug Report
Reporting Period: September 5 – September 12
Submitted by: Support Squad
Hi again, everyone—
We’ve identified one issue affecting USDC withdrawals:
Chain Mismatch for USDC Withdrawals
Symptom: Namadillo interface is incorrectly selecting the COSMOS chain address instead of the NOBLE chain address when preparing USDC withdrawals.
Impact: USDC on Namada uses Noble USDC, which is only withdrawable to the NOBLE chain. While this behavior shouldn’t occur, if users don’t notice and proceed with the transaction, it appears successful—but the funds are not sent to the COSMOS chain. Instead, they are refunded to the user’s refund address.
Reference Transaction: Transaction #AB90...6204 Details - Namada (NAM) Mainnet Explorer
Notes:
- This issue is not limited to Keplr—it originates from Namadillo’s chain selection logic.
- This is a **rare** occurrence, but important to flag for awareness.
- Users should double-check the selected chain before confirming USDC withdrawals to avoid confusion or delays.
-
Funds are not lost. Nothing to worry about—your assets are safe and automatically refunded if the chain is incorrect.
If you spot anything else or have insights to share, feel free to report it here or reach out directly. Every bit of feedback helps us improve user experience on Namada.