Skip to content
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

Stellar transaction sending fails with current public model T firmware #1997

Closed
bosomt opened this issue Dec 8, 2021 · 10 comments
Closed

Stellar transaction sending fails with current public model T firmware #1997

bosomt opened this issue Dec 8, 2021 · 10 comments
Assignees
Labels
bug Something isn't working as expected

Comments

@bosomt
Copy link

bosomt commented Dec 8, 2021

Describe the bug
Stellar transaction sending fails with current public firmware.

Firmware version and revision
2.4.3 public version revision 0x595b14254c1abb2be3f69e42c7932f1eca8cf1b1

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'https://accountviewer.stellar.org/dashboard'
  2. Sign/send stellar transaction
  3. See error

Screenshots
obrazek

@bosomt bosomt added the bug Something isn't working as expected label Dec 8, 2021
@bosomt
Copy link
Author

bosomt commented Dec 9, 2021

QA NOK

Tested in Exodus with same firmware version 2.4.3.
Signing/sending end in error.

obrazek

@cryptomar1o
Copy link

cryptomar1o commented Dec 10, 2021

Downgrading FW version to 2.4.2 does not solve the issue with Stellar Viewer, but it is now possible to sign a transaction with Exodus

Stellar viewer:
https://accountviewer.stellar.org/
Google Chrome Version 96.0.4664.93 (Official Build) (arm64)

Exodus:
21.12.3
macOS Big Sur Version 11.6 (20G165)

❌ 2.4.3 + Stellar viewer
❌ 2.4.3 + Exodus
❌ 2.4.2 + Stellar viewer
✅ 2.4.2 + Exodus

Successful transaction proceeded with Trezor Model T 2.4.2 + Exodus 21.12.3:
212f2d673395c1778144c29da87a1369e37785bb31817f25599fba825c97318a

@puruoni
Copy link

puruoni commented Dec 10, 2021

Trezor one is also the same, when I send it after signing with trezor-connect, I get the response "tx_bad_auth".

I only checked the firmware versions 1.10.3 and 1.10.4, but I got the same error. Too sudden, but is this caused by stellar network? Or trezor?

@matejcik
Copy link
Contributor

From what I can tell, the Account Viewer problem lies on Stellar side.

I am able to build and successfully send a virtually identical transaction with the same account on Testnet. However, Mainnet won't accept it. For now, I have no reason to believe that the signature is actually invalid.


Exodus appears to not send the asset field. We originally didn't require it, and assumed native if not specified. We now require it to be specified. This will need to be fixed on Exodus side. Do we have any way to contact them?

@prusnak
Copy link
Member

prusnak commented Dec 10, 2021

From what I can tell, the Account Viewer problem lies on Stellar side.

FTR - Account Viewer repo is here: https://github.com/stellar/account-viewer-v2

@matejcik
Copy link
Contributor

FTR - Account Viewer repo is here: https://github.com/stellar/account-viewer-v2

yeah but this isn't an Account Viewer problem either, looks more like their backend is hating on them or something.

@SpartanKang50
Copy link

With my Trezor and Stellarterm not communicating properly, my crypto is inaccessible and I’m losing thousands … what can be done about this? Is there any other way to access my funds??

@felixlucid
Copy link

With my Trezor and Stellarterm not communicating properly, my crypto is inaccessible and I’m losing thousands … what can be done about this? Is there any other way to access my funds??

Downgrading to Trezor Model T 2.4.2 does not solve the issue with StellarTerm. Assets held on SDEX remain entirely inaccessible via Model T on devices at any time upgraded to 2.4.3

@prusnak
Copy link
Member

prusnak commented Dec 11, 2021

It seems this will be fixed when we fix the issue in Trezor Connect - trezor/connect#970

@matejcik
Copy link
Contributor

closing in favor of trezor/connect#970
wrt the Exodus issue, I've contacted them so hopefully they can fix this on their side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working as expected
Projects
None yet
Development

No branches or pull requests

8 participants