Skip to content
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

[Bug]: Ledger X on cosmos sdk v0.47.x & Apple M1 #18423

Closed
1 task done
zakarialounes opened this issue Nov 9, 2023 · 4 comments
Closed
1 task done

[Bug]: Ledger X on cosmos sdk v0.47.x & Apple M1 #18423

zakarialounes opened this issue Nov 9, 2023 · 4 comments
Labels

Comments

@zakarialounes
Copy link

zakarialounes commented Nov 9, 2023

Is there an existing issue for this?

  • I have searched the existing issues

What happened?

Summary: [Mac M1] Ledger X not detected and not able to make any transaction.

Connection:

Regardless of the sdk version used, when the connection doesn't work, here's the error message:
Error: ledger nano S: hidapi: failed to open device

On Lum v1.6.2-1 (sdk v0.47.5)

If I modify the go.mod to use zondax/ledger-go v0.14.3 instead of the v0.14.1, then the connection problem using a Ledger X device on Apple Macbook M1 is solved.

On Kyve v1.3.1 (sdk v0.46.13)

If I modify the go.mod to use zondax/ledger-go v0.14.3 instead of the v0.14.1, then the connection problem using a Ledger X device on Apple Macbook M1 is solved.

On cheqd-noded (sdk v0.46.10)

Even using zondax/ledger-go v0.14.1 the connection with Ledger X works.

Impossibility to submit a tx using a Ledger X:

gas estimate: 155828
auth_info:
  fee:
    amount: []
    gas_limit: "155828"
    granter: ""
    payer: ""
  signer_infos: []
  tip: null
body:
  extension_options: []
  memo: ""
  messages:
  - '@type': /cosmos.distribution.v1beta1.MsgWithdrawDelegatorReward
    delegator_address: kyve1gjtvly9lel6zskvwtvlg5vhwpu9c9wawv2lpf3
    validator_address: kyvevaloper1gjtvly9lel6zskvwtvlg5vhwpu9c9waw76lp8n
  non_critical_extension_options: []
  timeout_height: "0"
signatures: []
confirm transaction before signing and broadcasting [y/N]: y
Error: 
Usage:
  kyved tx distribution withdraw-rewards [validator-addr] [flags]

As you can see there is no error message..

Cosmos SDK Version

Between v0.46.13 and v0.47

How to reproduce?

@julienrbrt
Copy link
Member

Have you tried to build those binary with a higher version of ledger-cosmos-go?
See #18319 (comment), this problem looks related.
We will release v0.47.6 soon with that dependency bump as well.

@zakarialounes
Copy link
Author

Have you tried to build those binary with a higher version of ledger-cosmos-go? See #18319 (comment), this problem looks related. We will release v0.47.6 soon with that dependency bump as well.

Thanks @julienrbrt for sharing the link. It's a perfect match. I searched but couldn't find it. Sorry for the duplication.

Regarding ledger-cosmos-go I tried, but got the following build error:

../../go/pkg/mod/github.com/cosmos/[email protected]/crypto/ledger/ledger_real.go:20:10: cannot use device (variable of type *ledger_cosmos_go.LedgerCosmos) as SECP256K1 value in return statement: *ledger_cosmos_go.LedgerCosmos does not implement SECP256K1 (wrong type for method SignSECP256K1)
                have SignSECP256K1([]uint32, []byte, byte) ([]byte, error)
                want SignSECP256K1([]uint32, []byte) ([]byte, error)
make: *** [install] Error 1

I'll pass the info on to the blockchains concerned so that they can use 0.47.6 soon.

@zakarialounes zakarialounes closed this as not planned Won't fix, can't repro, duplicate, stale Nov 9, 2023
@julienrbrt
Copy link
Member

Hi, you can still use the latest 0.12 version, which will have the same fixes than in 0.13.
I believe the latest is 0.12.4

@zakarialounes
Copy link
Author

Hi, you can still use the latest 0.12 version, which will have the same fixes than in 0.13. I believe the latest is 0.12.4

Indeed! Thank you @julienrbrt 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants