Support Squad - Weekly Bug Report

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!

:receipt: Namadillo Weekly Bug Report

Reporting Period: August 15-22

Submitted by: Support Squad

:locked_with_key: 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.

:chart_decreasing: Balance Display Inaccuracy
Symptom: Namadillo occasionally shows incorrect wallet balances.
Impact: Users report mismatches between expected and displayed amounts after shielding/unshielding operations.

:prohibited: 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.

:turtle: 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

7 Likes

:receipt: Namadillo Weekly Bug Report
Reporting Period: August 23–September 5
Submitted by: Support Squad


:locked: 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.


:chart_decreasing: Balance Display Inaccuracy
Symptom: Namadillo occasionally shows incorrect wallet balances.
Impact: Users report mismatches between expected and displayed amounts after shielding/unshielding operations.


:prohibited: 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.

:turtle: 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_button: New Addition – September 5
:puzzle_piece: 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.

:megaphone: 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

:receipt: 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:

:puzzle_piece: 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.

- :white_check_mark: Funds are not lost. Nothing to worry about—your assets are safe and automatically refunded if the chain is incorrect.

:megaphone: 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.

:receipt: Namadillo Weekly Bug Report

Reporting Period: September 12 – September 18

Submitted by: Support Squad

Hi everyone—

This week has been relatively quiet on the bug front. No major issues have been reported.

:magnifying_glass_tilted_left: Minor Observations

Some users have mentioned occasional trouble with Shielding and IBC transactions.

Details are limited at this time, and we’re actively monitoring for patterns or confirmations.

:megaphone: If you’ve experienced similar issues or noticed anything unusual, feel free to report.

1 Like

:receipt: Namadillo Weekly Bug Report

Reporting Period: September 18 – September 25

Submitted by: Support Squad

(This is this week’s report.)

Hi everyone—

Here are the issues we’ve tracked this week:

-–

:new_button: Namada → Osmosis IBC Transfer Unresponsive

Symptom: Some users report that when attempting IBC transfers from Namada (transparent) to Osmosis, the submit button becomes unresponsive or nothing happens after clicking.

Impact: Transaction cannot be initiated, leading to confusion or failed attempts.

Status:

- We’re still gathering details and waiting for reproducible reports.

- This issue may be intermittent or UI-specific.

-–

:new_button: Stride → Namada Deposit Failure

Symptom: When users attempt to deposit assets from Stride to Namada, gas estimation fails and they encounter various error codes or failed responses.

Impact: Although this issue originates from Stride (not Namada or Namadillo Interface), it creates a poor user experience for those interacting with Namada.

Notes:

- This was previously reported here: [GitHub Issue #1832] ([Namadillo]: Unable to IBC Shield from Stride: StridePeriodicVestingAccount Error · Issue #1832 · namada-net/namada-interface · GitHub)

- The likely cause is Stride RPC failing to estimate gas correctly on the Stride side.

- :white_check_mark: Funds are not lost, but transactions fail to execute.

- Workaround:

  • Create a new Stride account via Keplr.

  • Transfer tokens between Stride accounts first, then deposit into Namada.

:megaphone: If you’ve experienced similar issues or noticed anything unusual, feel free to report it here. Your feedback helps us stay proactive and responsive to the community’s needs.

:receipt: Namadillo Weekly Bug Report

Period: Sept 26 - Oct 02 • By: Support Squad

:puzzle_piece: Stride Deposit Failure

  • stOSMO deposits from Stride fail on submit (all browsers).
  • Cause: gas estimation on Stride RPC.
  • Workaround: create new Stride account via Keplr → transfer between Stride accounts → then to Namada.
  • Ref: GitHub #1832

:chains: Peer Drops & Missed Blocks

  • Validators report peers dropping and missed signed blocks.
  • Logs show abnormal negative timeout values in the CometBFT consensus module.
  • Cause unclear; suspected CometBFT issue.
  • Devs request full CometBFT logs around events to assist debugging.
1 Like

:receipt: Namadillo Weekly Bug Report
Reporting Period: October 2 – October 9
Submitted by: Support Squad
(This is this week’s report.)

Hi everyone—

It’s been a good week overall. No new major issues have been reported. :tada:

:white_check_mark: Resolved
We received a few reports related to Shielded Sync and Shielded transactions. These were minor and have been successfully resolved by the Support Squad team.

:megaphone: If you encounter anything unusual or have feedback to share, feel free to report it here. Your input helps us keep Namadillo running smoothly for everyone.

1 Like

:receipt: Namadillo Weekly Bug Report

Reporting Period: October 9 – October 16

Submitted by: Support Squad

Good Day, Everyone —

No new issues have been reported this week. However, we want to highlight one ongoing concern:

-–

:puzzle_piece: Ledger Hardware Wallet – Issue Resurfacing

Symptom: Previously reported issues with Ledger hardware wallet are resurfacing for some users.

Impact: Users may experience inconsistent behavior or failed interactions when using Ledger devices with Namadillo.

Status:

- This issue has been reported before and remains unresolved.

- We’re monitoring incoming reports and will escalate if new patterns emerge.

:megaphone: If you’ve encountered this issue recently or have additional context, please report it here. Your feedback helps us track and prioritize fixes effectively.

1 Like

:receipt: Namadillo Weekly Bug Report

Reporting Period: October 16 – October 23

Submitted by: Support Squad

(This is this week’s report.)

Hi everyone—

There’s nothing new to report this week. No issues have been flagged, and everything appears to be running well.

:megaphone: if you notice anything unusual or have feedback to share, feel free to report it here.

1 Like

:receipt: Namadillo Weekly Bug Report
Reporting Period: October 30 – November 6
Submitted by: Support Squad
(This is this week’s report. Previous week was skipped, sorry :ghost:)

Hi everyone—

There’s nothing new to report this week. No major issues have been flagged, and everything appears to be running smoothly. :tada:

:rocket: Infrastructure Update!!!

Heliax has launched their own high-quality infrastructure services to support the Namada ecosystem.
For a smoother and more reliable experience, we recommend using the Heliax-hosted Namadillo interface:

Some users may need to clear their browser cache and cookies to ensure the interface loads correctly.

:books: You can find a full list of Heliax-hosted services here: Namada Documentation - Services and Infrastructure

:megaphone: If you encounter anything unusual or have feedback to share, feel free to report it here. Your input helps us stay proactive and responsive to the community’s needs.

:receipt: Namadillo Weekly Bug Report

Reporting Period: November 6 – November 14

Submitted by: Support Squad

(This is this week’s report. Apologies for the late submission.)

Hi everyone—

There’s nothing new to report this week. No major issues have been flagged, and everything appears to be running smoothly. :tada:

:megaphone: If you notice anything unusual or have feedback to share, please report it here.

:receipt: Namadillo Weekly Bug Report

Reporting Period: November 14 – November 20

Submitted by: Support Squad

(This is this week’s report.)

Hi everyone—

We want to highlight one ongoing issue affecting some users:

-–

:new_button: Ledger Hardware Wallet – Stax Users

Symptom: Ledger Stax users are experiencing problems with Shielding, Unshielding, and MASP transactions.

Impact: Transactions may fail or behave inconsistently when attempted with Ledger Stax devices.

Status:

- This issue was reported previously and remains under active work. You can track the progress here:

We apologize for the inconvenience and appreciate your patience while we work toward a fix.

:megaphone: If you’ve encountered this issue recently or have additional context, please report it here. Your feedback helps us track and prioritize fixes effectively.

1 Like

:receipt: Namadillo Weekly Bug Report

Reporting Period: November 20 – November 27

Submitted by: Support Squad

Hi everyone—

There’s nothing new to report this week. No major issues have been flagged, and everything appears to be running smoothly. :tada:

:megaphone: As always, if you notice anything unusual or have feedback to share, please report it here. Your input helps us stay proactive and responsive to the community’s needs.

1 Like