-
-
Notifications
You must be signed in to change notification settings - Fork 262
stellarSignTransaction did not return the correct signature #970
Comments
This is debugging information. Why is the sequence received by Trezor T different from the sequence passed to stellarSignTransaction? Hi @mroz22, do you have any ideas?
|
trezorctl works fine, it got the correct sequence
|
If the sequence number is a small value, then everything seems to work fine, is this related to exceeding MAX_SAFE_INTEGER? |
Yes, this is happening due to sending number parameter which is higher then MAX_SAFE_INTEGER What we should do now? probably change conect interface in that way that it will be able to accept also string here instead of number |
Yes, I think we should define it as string type in JavaScript. (The source code of Trezor Model T is written in Python, and Python can handle it accurately.) I am not familiar with JavaScript, the |
I have already found the root of this problem and I am preparing fix. Thanks for reporting. |
@mroz22 While you are on it, can you also please set the |
fwiw i believe that whoever is using the official Stellar SDK will always specify the asset, and that is what callers should be doing |
Hi @mroz22, I found that other projects did not use the transformTransaction function provided by the connect library, but made a separate copy. Do you have any ideas? https://github.com/stellar/laboratory/blob/master/src/helpers/trezorTransformTransaction.js |
Can you please open issues in the respective projects to not do this and rather use a function provided by Connect? There is no good reason why they should do this. And mainly this behaviour leads to more issues and makes fixing stuff much more complicated. |
Sorry for this, I will raise this issue elsewhere. |
Just to clarify. Do we still want this? I wasn't sure whether anything changed after closing trezor/trezor-firmware#1997 (comment) |
I couldn't find this method "transformTransaction" inside the "trezor-connect" package. The "lib" folder does not contain the "plugins" folder. |
hey @shiny-mountain plugins folder is available only from |
Yes, that's what we need. In the near future, Stellarterm will start using this |
@mroz22 Will transaction signing be fixed in the next version of the package? |
yes, it is likely to happen in couple of hours. |
ok, then we will update Stellarterm immediately with the new version |
@mroz22 I installed "8.2.4-extended" version but I don't see the "plugins" folder in it |
It works fine on my end, see stellar/account-viewer-v2#366 |
Oops, my mistake. It was just necessary to change "^8.2.4-extended" to "8.2.4-extended" |
Thank you so much for your attention to this matter. I'm a Trezor Model T user affected by this issue and was referred here by the Support Team. As of now, I am still unable to sign transactions on the SDEX via StellarTerm with my Model T 1.4.3 FW. Please let me know the update status for the fix. Thank you! |
I'm a Model T StellarTerm user with vested interest in the resolution of this transaction signing problem. Could you give me the status of the fix intergration on StellarTerm and inform me whether I should be able to start transacting on the platform? Thank you for your support. |
Hi @felixlucid, it works fine on my end, what error did you get? Let's move to stellarterm/stellarterm#951 to continue the discussion. |
environment info
tx info
Expected signature
I got this signature through trezorctl, so I think there is no problem with Trezor firmware.
signature returned by stellarSignTransaction
code
The text was updated successfully, but these errors were encountered: