search

AXErunners / electrum-axe

lightweight client for AXE network
https://axerunners.github.io
MIT License
224 stars 84 forks source link

Trezor support Firmware v1.8.1 #40

Closed BlinkVoid closed 5 years ago

BlinkVoid commented 5 years ago

Hi team, I've enountered some difficulties in using trezor with the electrum wallet and now I can't access the funds.

  1. Initially, was able to open eletrum wallet with trezor (wallet successfully detected trezor and was able to choose first of the two xpath options to open the wallet.) - retested with unplug and plug trezor backin, was able to access the wallet using trezor to unlock.
  2. Transferred funds in and when I tried to transfer for colleteral (1000AEX per transaction), encountered problem as: "invalid coin name".
  3. Tried to update the firmware to v1.8.1, while the eletrum program was still open. After update, "invalid coin name" error disapeared, and proceeded to sign transaction phase. Here, electrum start to prompt failed to connect with trezor wallet, after several failed attemps in signing the transaction, decided to close eletrum and try redo the transaction.
  4. Encountered same problem when trying to open eletrum: image image Any ideas how I can solve this?

Thanks

Kurbeks commented 5 years ago

Does trezor itself work after update? Like in wallet.trezor.io, get's detected?

BlinkVoid commented 5 years ago

Yes, it does. Works fine with the website, it can be detected and I can log into the wallet account. Do you think it's the firmware?

On Thu., 27 Jun. 2019, 00:58 Kurbeks, notifications@github.com wrote:

Does trezor itself work after update? Like in wallet.trezor.io, get's detected?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/AXErunners/electrum-axe/issues/40?email_source=notifications&email_token=AAYTGHHUVJMJLBVHENQTE63P4N7YVA5CNFSM4H3S76ZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYT2BCI#issuecomment-505913481, or mute the thread https://github.com/notifications/unsubscribe-auth/AAYTGHFKMB5UDMBI5PPVOELP4N7YVANCNFSM4H3S76ZA .

charlesrocket commented 5 years ago

Is there more in debug/logs? My guess you driving with webusb and not bridge.

BlinkVoid commented 5 years ago

Looks that way, I'll update more details later today.

Planning to test on a different computer as well.

Cheers

On Thu., 27 Jun. 2019, 05:04 -k, notifications@github.com wrote:

Is there more in debug/logs? My guess this that you driving with webusb and not bridge.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/AXErunners/electrum-axe/issues/40?email_source=notifications&email_token=AAYTGHGVXD5PB6FFT4KYXKDP4O4TBA5CNFSM4H3S76ZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYUQN4Y#issuecomment-506005235, or mute the thread https://github.com/notifications/unsubscribe-auth/AAYTGHFC3ZAMP6CCAADA4J3P4O4TBANCNFSM4H3S76ZA .

BlinkVoid commented 5 years ago

Is there more in debug/logs? My guess you driving with webusb and not bridge.

Exactly like you suspected, trezor switched to webusb. Tried on second computer, eletrum successfully read data from Trezor using WebUSB. the signing issue seems to originated from compatibility issue with the older firmware, once updated, it is able to recognise the coin and transact accordingly.

Will now go ahead and close the issue. If you are still interesed with the logs, I'll find it and post it afterwards.