I requested the SignEd25519 method to return an error:

[APDU_CODE_DATA_INVALID] Referenced data reversibly blocked (invalidated)

this is my transaction data:

04004597993318909e62ef6dc57a90cf2be0de8174930e27b64a9f288b2e42e504020700e40b54020000002f00000003000000e143f23803ac50e8f6f8e62695d1ce9e4e1d68aa36c1cd2cfd15340213f3423ee143f23803ac50e8f6f8e62695d1ce9e4e1d68aa36c1cd2cfd15340213f3423e

I'm signing a transaction using gaiad binary (v13.0.1) on the CLI, but ran into an error with no error message. Checked with another binary (kujirad, v0.9.1), same issue. Tried upgrading to ledger-go v0.14.3 with no change in behaviour. I suspect its related to this new version of Ledger OS.

gaiad tx bank send cosmos1…2d cosmos1…2d 1uatom --from ledger 

Default sign-mode 'direct' not supported by Ledger, using sign-mode 'amino-json'.
Error: 
Usage:
  gaiad tx bank send [from_key_or_address] [to_address] [amount] [flags]

Flags:
…

Some debugging led me to this line:

if sw != 0x9000 {
  return response[:swOffset], errors.New(ErrorMessage(sw))
}

sw had a value of 0x6984.

Setup:
ledger-go v0.14.3
ledger Nano X
ledger OS v2.2.3
Cosmos App v2.34.12

github.com/zondax/[email protected]/ledger_hid.go has UsagePageLedgerNanoS = 0xffa0

I used admin.ListDevices and got

============ 0001:0014:01
VendorID      : 2c97
ProductID     : 1
Release       : 201
Serial        : 30303031
Manufacturer  : Ledger
Product       : Nano S
UsagePage     : 0
Usage         : 0

So if I set UsagePage : 0
It works for me.

I haven't investigated further, it could be just my machine, my distro (Ubuntu 22.04), my ledger...

🔗 zboto Link