#Ledger Stax issue - solving via CLI

1 messages Ā· Page 1 of 1 (latest)

violet shadow
#

Hi there šŸ‘‹, sorry for the inconvenience. This is known and there's a workaround if I remember it correctly. Please gimme some time.

#

cc @patent pulsar

#

Can you confirm that if you have the latest update installed on your Ledger device? If you could send a screenshot it'll be more helpful

frail veldt
#

latest ledger app v3.0.4

Screenshot_2025-11-17_at_10.46.21.png
patent pulsar
#

which OS are you on?

#

(I won't be around much today but there are older threads where I think the fix is posted)

#

you sure you have the latest namada app on your device?

frail veldt
#

app v3.0.4 is it latest?

#

MacOS (chrome)

#

Ledger Stax

#

the issue only happens on shielded tx (shieldedā†’unshielded):
ā€¢ ledger freezes on the 5/7 page
ā€¢ namadillo flips rpc/ibc indicator yellowā†”green
ā€¢ device reboots

violet shadow
#

Please try this and let us know

frail veldt
# violet shadow Please try this and let us know

got it, thanks the issue matches exactly what iā€™m seeing on ledger stax.
the workaround in that github thread mentions using a non-ledger signer for the unshield step.

my question is: how do i actually do that in the current namadillo build?
iā€™m in keychain-only mode, the ui only exposes keychain/ledger, so i have no browser/software signer option at all.

is there a supported way to enable an alternate signer just for one unshield tx?
or should i use the cli method from the github comment?

violet shadow
#

Also Try this: Namadillo settings āš™ļø --> MASP --> Invalidate Shielded Context

frail veldt
#

tried unshielding 0.01, 0.1 and also reset masp context still freezing on page 5, ledger reboots every time.

since namadillo is in keychain-only mode for me (no software signer option), i guess the only remaining workaround is doing an unshield via CLI with a temporary software signer?

if thatā€™s the recommended approach, could you point me to the exact command sequence?
just need to get shielded ā†’ transparent once, then i can withdraw via ledger normally.

violet shadow
#

<@&1376642872182440133> and <@&833650360345559091> if anyone could help on this matter, šŸ™

humble hornet
#

@frail veldt I don't follow what you mean by namadillo in keychain-only mode for you. I think you should be able do the following workaround:

  • download Namada keychain extension (on Chrome store, for example)
  • get your Ledger seed phrase and import to derive your keys in software wallet on keychain extension
  • use https://namadillo.app to unshield. Still might want to try with small amounts first

You can also do CLI unshielding if you are familiar with those kinds of tools. That should be fairly straightforward as well if you have CLI experience, can help point you to the relevant docs if so

frail veldt
#

thanks and just to clarify, i obviously canā€™t get my ledger seed, so i assume you meant creating a separate software case in the keychain extension, not importing the ledger mnemonic.
iā€™ll install the browser keychain extension and try unshielding via software case on namadillo.app with a tiny amount first, then larger.
if that doesnā€™t land, iā€™ll switch to the CLI path.

frail veldt
#

importing my ledger seed into a software wallet isnā€™t acceptable for me (for obvious security reasons).
iā€™ll go the CLI route instead and unshield via a temporary software signer there.
if there are any specific flags or recommended command sequences for MASP unshielding, feel free to point me in the right direction iā€™m setting up the CLI environment now.
appreciate the help so far.

patent pulsar
#

I'm not sure if there are macos built binaries, if not I think linux binaries should work but not 100%

#

actually let me check about this

#

you may need to build it but that's a pain. which macos arc are you on? (intel or m* cpu?)

frail veldt
#

m

#

thx you coz its nice trip for me)

#

i see namada-v101.1.4-Darwin-arm64.tar.gz

patent pulsar
#

yes exactly

#

that's the one

#

was just about to write lol

#

grab that and lmk when you have it installed and you can run namadac in the terminal

frail veldt
#

downloaded the namada-v101.1.4-Darwin-arm64.tar.gz binary.
planning to run the CLI unshield workaround next:
ā€¢ unpack the binary, move namada into PATH
ā€¢ generate a temporary software signer
ā€¢ use CLI to unshield a small amount first (shielded ā†’ transparent)
ā€¢ once transparent balance shows up, switch back to Ledger for IBC withdraw
just checking this is the correct flow, right?

patent pulsar
#

think you are making this too complicated, just lmk when you have the cli up and running

#

I don't understand where the idea to create a temporary software signer comes from

frail veldt
#

i have call come back after 30-45 min and continiue

patent pulsar
#

what you would do - once you have the cli installed and accessible from terminal (you can run namadac) - is to

  • import the transparent account using namadaw (namadaw derive --use-device)
  • import shielded account (namadaw derive --shielded --use-device)
  • make sure the imported accounts are the one you are expecting (namadaw list)
#

when that's in order, you can start the actual unshielding and probably also you should make sure you can see the proper balances. the tricky step is to do the shielded sync on cli which tbh is a bit of a pain

#

you will need to find an rpc and an indexer and a masp-indexer to use on namada.community

#

(emberstake is usually a solid choice)

#

I can get back a bit later with some pointers on the exact commands, but basically once you have your shielded account set up, you would do a shielded sync up against a masp indexer, then you can query the balance and make sure you see the tokens before progressing to unshielding

#

the shielded sync step is a bit tricky as it takes somewhat complicated and counterintuitive formats for the indexers url-wise.

#

Ledger Stax issue

#

Ledger Stax issue - solving via CLI

patent pulsar
#

you can also do a shielded sync directly against the ledger which is more straightforward but will take a long time

#

remember the --node flag with an rpc for all cli client operations unless you are running your own node

humble hornet
#

I'll also be around more in like 60 min if you need some more hands-on help

humble hornet
frail veldt
#

quick update on my issue i managed to work around the problem without CLI, directly via the web interface, but the underlying bug is clearly still present.

here is what happened:
ā€¢ i tried unshielding a very tiny amount of NAM (0.000001) that worked
ā€¢ after that i reset the MASP context
ā€¢ tried to unshield OSMO ā†’ ledger rebooted instantly at the ā€œconnectingā€ stage, even before showing tx pages
ā€¢ realized the fee asset was set to NAM, switched fee to OSMO, increased the unshield amount (not tiny), and then the unshield succeeded
so unshielding NAM works after MASP reset, but unshielding OSMO triggers ledger crashes unless fee = OSMO and the amount isnā€™t extremely small.
this is a pretty hard UX failure the device rebooting on shielded tx makes it feel like something is fundamentally wrong and users get stuck in shielded state with no obvious way out.
questions:

1ļøāƒ£ is this behavior known and currently being worked on?
2ļøāƒ£ is the root cause related to MASP proof size, fee-asset parsing, or something in the ledger app itself?
3ļøāƒ£ do you have plans to prioritize a fix? (this is a major UX blocker easy to get trapped with funds shielded)

patent pulsar
#

@humble hornet

frail veldt
#

just to add the issue on my side is fully resolved now, i managed to unshield and withdraw everything successfully.
if you could still share answers to the questions above, iā€™d appreciate it mostly to understand the underlying cause and whether a fix is planned, since the behavior was quite sharp UX-wise.
thanks again for the support and for taking the time to help out. after that, feel free to close the thread.

patent pulsar
#

you are quite verbose, sir šŸ™‚ let's wait for Brent to respond to you above!

frail veldt
#

sounds good) waiting for brentā€™s take. thanks for the assist.

humble hornet
#

Hey @frail veldt - first of all, thx for describing in great detail, super super appreciated

#

glad to hear that you've sorted yourself out with a workaround too. I'll answer your questions

#
  1. I don't think this behavior was known (I could be wrong personally), and as such there is not a solution actively being worked on here.
  2. There are others who could guess better than myself (and I can run it by them), but it could definitely be related to some shortcomings in the Ledger app or Stax firmware itself and the large size of the MASP proofs. The Stax is not a piece of hardware that we've come across in our user base admittedly (almost all have either the X, Nano S+, or Nano S). Fwiw, we've come across hardware shortcomings in the Nano S, which supports Namada staking, etc but cannot support shielded txs, as the Namada Ledger app w/ shielded functionality is too large for the device.
  3. Honestly, I would not consider this fix high priority. We are limited on engineering resources currently, and the devs we do have are very focused on critical value-returning work like implementing shielding fee systems and bridging to EVM, Solana, etc. Open to hear if you think this should be higher priority, but the Stax does not seem to be a common piece of hardware we've come across, and ofc working on this will not return any immediate value to the project, given engineering constraints. Hope this makes sense to you right now, but we will definitely track this issue
frail veldt
#

appreciate the detailed reply, @humble hornet

just to add my perspective: i do think this is worth keeping on the radar. anyone who actually wants to use shielded pools and move assets in/out via ledger will hit this wall and the UX impact is pretty brutal. feels like a hard stop if the device freezes or reboots while funds are in the shielded set.

maybe itā€™s masp proof size, maybe stax firmware, maybe something in the ledger app not sure. but stax is getting more popular, and in general people moving larger amounts almost always use a hardware wallet. so having reliable shielded ops on ledger becomes pretty important long-term.

anyway, iā€™m good now managed to fully unshield and withdraw. thanks again for the help and context.
sidenote: iā€™m a decent-sized holder of both namada and anoma, been accumulating on dips. would love to see a more focused holder/dev channel at some point something beyond public announcements. feels like that would help alignment + visibility into where things are headed.

thanks again for taking the time. happy to provide more details if useful.

patent pulsar
humble hornet
frail veldt
#

yeah, its avalible thx