-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Unlock using Trezor fails on loopring.io #20078
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
Comments
Have the same problem with Loopring wallet in OS |
I've just verified this is indeed still an issue on latest Brave. Highlight me if you need any more information. |
@bbondy Any progress on this internally? |
@srirambv are you able to reproduce this issue? |
Hmm, unlock account seems to work now! Unfortunately sending between L2 accounts just gets stuck in a loop of verifying the signing address. The following approval appears in Brave wallet before the prompt on my Trezor T to verify the signing address:
|
@abjugard By L2 account, do you mean that this transaction is happening on an L2, i.e. not Ethereum mainnet? If so, could you take a look at #23448 (comment) and let me know if that solves the issue. |
@nvonpentz It does not. Yes, I am trying to sign a transaction on loopring.io moving funds between two Loopring L2 wallets. |
Description
Unlock using Trezor fails on loopring.io
Steps to Reproduce
Actual result:
Unlock using Trezor fails on loopring.io
Expected result:
Should be able to unlock using Trezor via Brave wallet
Reproduces how often:
Easy
Brave version (brave://version info)
Brave: 1.32.115 Chromium: 96.0.4664.93 (Official Build) (64-bit)
Revision: 17531e0a70b4f8108f2418e8b5117f465077710b-refs/branch-heads/4664@{#1229}
OS: Windows 11 Version 21H2 (Build 22000.348)
Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
The signature received by the Loopring Web3 code is 130 characters long, but the code expects it to be 65 characters long.
The text was updated successfully, but these errors were encountered: