TransportStatusError: Ledger device: Invalid data received (0x6a80)

[8zyuck]

Hi,

I found topic but its closed: #43

But when i try to send smart contract i get error: TransportStatusError: Ledger device: Invalid data received (0x6a80)

I have newest firmware I am using ledger flex and when Debug smart contract I have ticked Display contract data details.

Still get this error and I need to move my position fast, what should I do?

Best,

[grothem]

I have the same issue. To reproduce, just try calling the approve function on this token: https://etherscan.io/address/0xaAFD07D53A7365D3e9fb6F3a3B09EC19676B73Ce#writeProxyContract

I'm using my Ledger connected through MetaMask.

[0xcoffeehouse]

I am facing the same issue. Tested it with Ledger Nano X and Ledger Stax. It worked before with the same setup and the same tokens.

[matheus1lva]

same

[0xcoffeehouse]

Some examples:

transfer or approve any of the following tokens (on Ethereum):

• 0x312ffC57778CEfa11989733e6E08143E7E229c1c (token created by AAVE)
• 0x917459337CaAC939D41d7493B3999f571D20D667 (token created by Pendle)

[8zyuck]

Hi guys,

so I talked to ledger support and they said this:
It looks like the error you're seeing often happens when the ticker symbol is longer than 10 characters, which seems to be the case with your PT tokens (PT-USDe-31JUL2025). A common solution for this is to use the OKX wallet.

I ended up importing my seed phase into Trezor and that worked out just fine I did not try the OKX wallet, would be nice if someone tried it and let others know if it works

[0xcoffeehouse]

@8zyuck Thanks a lot for your reply!

• I have ordered a Trezor Safe 5 and a OneKey Pro to test it.
• I also just tested to import my existing Ledger into the OKX browser wallet extension.
• I can confirm that OKX Wallet + Ledger seems to fix this issue. I have been able to approve PT-USDe-31JUL2025.

However, a few more remarks:

• It 100% worked for the same tokens with Rabby + Ledger before. I did several approvals for the same token without an issue.
• It still works fine for PT-sUSDE-31JUL2025 (0x3b3fB9C57858EF816833dC91565EFcd85D96f634), which has an even longer ticker symbol than PT-USDE-31JUL2025, so this seems to be not the only root cause.

[8zyuck]

Hi,

yeah seems strange, well glad you got it sorted out, and we know that OKX wallet soves the issue. Let us know how does OneKey pro works :-)