-
Notifications
You must be signed in to change notification settings - Fork 226
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
Ledger device: Invalid data received(0x6a80) #43
Comments
I'm having this issue currently |
#metoo |
Full firmware upgrade of the ledger and reinstall of Ethereum app fixed it |
Closing, it seems this is fixed in firmware version 1.5.5 |
For sending custom tokens, enable contract data in the Ethereum app on-device. This error will also show up if you don't have contract data enabled when trying to send custom tokens, even with firmware 1.5.5 and Ethereum wallet 1.2. |
I'm getting this error even when firmware 1.5.5 and Ethereum Wallet 1.2.4 |
Having this problem with Ledger firmware 1.5.5 and Callisto app 1.1.9. Both "contract data" and "display data" options enabled. |
I'm on firmware 1.5.5 and Ethereum Wallet 1.2.4 and when interacting with https://cdp.makerdao.com (withdrawing eth) I get this error. |
Getting the same error for some input data |
Same error with 1.5.5 with Metamask + Chrome & Brave too |
Latest Brave/Chrome with 1.5.5, same error here. |
Same for me on MyCrypto App and 1.5.5 firmware. Contract/display data disabled. Ok, this was the important hint:
|
HI STILL I HAVE THIS PROBLEM I CHANGED 3 DIVICES PROBLEM NOT SOLVED |
chill out a sec. ledger live is the desktop software; you need to update the device firmware. good luck. |
@drajay9628 "For sending custom tokens, enable contract data in the Ethereum app on-device." |
@Bird-NZ that worked for me - thanks |
Worked for me on uniswap, thanks |
thanks a lot, this solved the issue on my side as well! |
Yep, this worked for me, thanks so much! |
Yep, confirmed - the problem has been caused by the disabled contract data. Check the instruction on the Ledger docs. |
Contract data -> YES
Display data -> YES
When an Ethereum transaction's input data is not sufficiently padded it rejects the transaction.
For example, a transaction with the input data
0x123
would fail, while a transaction with the input data0x123000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
would succeed.In both cases, when display data -> NO
The transaction is accepted
Also related MyEtherWallet/etherwallet#2044
The text was updated successfully, but these errors were encountered: