Ledger Stax signing masp spends error encountered

[pimato]

It looks like I am not able to interact with my Ledger Stax on Namada now. I have shielded my funds via IBC transfer but definitely was able to unshield funds too. Something has changed and it is not working anymore.

Ledger Hardware: Ledger Stax
OS: OS-Version 1.6.2
Browser: Brave 1.79.123 (Offizieller Build) (arm64)

Keychain Version: 0.8.1
Revision: c667de5
SDK Version: 0.19.0

Using: https://namadillo.app/

Video:
https://github.com/user-attachments/assets/fbac90a3-c5cb-435b-b0d3-39eaf7e9c5b1

[jurevans]

@pimato hello! Thanks for reporting this! This is actually an issue that we're aware of (one of our engineers is looking into potential solutions). Try shielding/unshielding smaller amounts of NAM at a time - what is happening is the Ledger buffer cannot keep up with the size of MASP inputs/outputs of that transaction, reducing the quantity can get around this limitation. We are looking into ways of potentially optimizing the Tx so as not to overwhelm the Ledger.

Let's leave this issue open to refer others to!

[pimato]

@jurevans I am not sure how much lower I should get. I tried to unshield 1 NAM and the masp creation works but I always get stuck at the signature process on the Ledger. It seems that the exentions has everything ready but the Ledger is not receiving the data?

Extension view:

I would like to sign it but nothing happens.

Also it seems like the solutions seems like far away in terms of actually implementation. Its a bummer that the ledger support is presented on the main (namada.net) page but actually does not work.

[pimato]

Shielding seems to work:

[jurevans]

@pimato Thanks for the additional info! We've successfully tested every Tx across various Ledger HW wallets, but in the case of MASP, it is indeed extremely slow, and the device does not provide any visual queues that it is receiving/processing any data. Ignoring the known issue with large numbers of MASP notes (if you view Tx details in the extension, you can see the number and quantities of the MASP notes being used) - MASP Tx should succeed, but I agree the user experience is not good in the case of MASP. There is some work being done to improve the UX, as well as investigate improving Tx size and performance for anything MASP-related.

[pimato]

@jurevans
Can you give me a step by step process of how the MASP Tx succeeds? Because I tried to use small amounts (1 NAM) und big amounts and none are actually proceeding to the signing state on the hardware wallet. They way I understand your comments are that everything works fine, but on my end no masp interaction with my ledger seems to work.

Can you explain me how I am actually able to succeed to get something on my hardware wallet shown?

[jurevans]

@pimato

Can you explain me how I am actually able to succeed to get something on my hardware wallet shown?

If you approve a transaction in the extension, and the Ledger device never prompts you, regardless of how much time has pass, that is another issue. There shouldn't be anything special needed for these to succeed, aside from the suggestion to reduce quantity. We don't yet have a solution in place to improve MASP Tx performance on Ledger, but it is being worked on. We can try to reproduce the behavior you're seeing with the Ledger never prompting you after approval in the extension

[pimato]

@jurevans
Please look at the video attached.

I agree that high amounts will lead to an error message shown on the extension. But if there is no error message on the extension it should proceed with signing on the hardware wallet. Can you actually replicate my issue?

Step 1: Define Amount to unshield and wait for masp creation:

Step 2: Extension pops up:

Step 3: Ledger is unlocked and click "Proceed":

Step 4: Approve on device:

Nothing happens afterwards. The Ledger Stax has a 1 minute timer to get into locked mode again and nothing happens.

Just so you understand. Currently my funds are stucked in the shielded pool and there is no way to unshield them with the ledger hardware wallet. Please replicate my issue and confirm.

[pimato]

@jurevans some update:

After Step 4 the Ledger has seemed to be frozen as I played with the settings page on the namada app. I was able to go into settings two times then the whole device froze and the Extension showed me this:

You can replicate this issue without playing with the device (so it not gets into the classic ledger timelock state).