-
Notifications
You must be signed in to change notification settings - Fork 141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Retesting stackingDAO with Ledger device #5864
Comments
The issue mentioned here: #5115 (comment) Using this page https://app.stackingdao.com/signer?pool=SP4SZE494VC2YC5JYG7AYFQ44F5Q4PYV7DVMDPBG.stacking-pool-v1 to commit signature wil lead to the "your ledger device has rejected the payload stating it is invalid" ❌ 0.23.3 and firmware version 1.1.1 with Ledger Nano S+ 0.24.2 and firmware version 1.1.2 with Ledger Nano S+ I assume this was resolved by the fix for #2725 |
#5115 got a little messy trying to cover seamingly related issues that are different.
They look similar because the same error is thrown but the error is very general and can mean many things. They have to be investigated on a case by case basis. "...Ledger has rejected the payload".
With 0.24.2 of the Stacks App on a Ledger Nano S+ with firmware version 1.1.2
You can connect wallet on app.stackingdao.com, reproduction steps:
If you try to sign a transaction to stack STX (convert to stSTX) that will fail. Due to a known issue with 0.42.2 which is being investigated, we hope to see a solution live soon expected with version 0.24.5 or higher of the Stacks app. Zondax/ledger-stacks#171
Using version 0.23.3 (the previous stable version of the Stacks app) and firmware version 1.1.1 on Nano S+ does allow you to sign the arbitrary message to connect and then Stack STX. Signing and broadcasting the transactions works without issue in that case.
I am not sure where the previously reported issue popped up. I am not seeing it with the old versions. Lets wait for 171 to be resolved by Zondax/Ledger and then revisit this.
The text was updated successfully, but these errors were encountered: