-
Notifications
You must be signed in to change notification settings - Fork 795
Ledger sign_tx can not work anymore. always show LedgerError(BadRetcode(BadKeyHandle)) #1189
Comments
Do you get the same bug if you use |
but how to get ethers-signers from ethers? |
I will try it now. thanks for reply. |
You can access all sub-packages via: |
I tried it, still error.
my code:
The error output:
Still have the BadKeyHandle message... |
OMG. I found a way it could work
|
it pop ledger, but still failed:
|
You are setting the chain id to 1 in |
Thanks for reply. but it still not work. I use ganache-cli ran a node with chain_id 999. and fill 999 in code. but it still error.
and it returns:
I have enought balance, and I could get it from provider, but it throw errror says I have 0 balance. It usually because the rpc server didn't recover the correct address from tx signature. |
Ah yeah, that makes sense. Should be easy to add that to the rest of the signers. It seems like the trezor signer uses the signer's chain in |
I think let's do it like in the private key? If there's a chain id specified in the transaction use that, else use the signer's chain id? |
when will it be merged? :) |
Great, it is good now! Thanks!! |
Version
ethers-signers = { version = "0.6.2", features = ["ledger"]}
ethers-core = "^0.6"
cargo tree | grep ethers
├── ethers-core v0.6.3
├── ethers-signers v0.6.2
│ ├── ethers-core v0.6.3 (*)
Platform
Darwin molindeMacBook-Pro-2.local 21.1.0 Darwin Kernel Version 21.1.0: Wed Oct 13 17:33:01 PDT 2021; root:xnu-8019.41.5~1/RELEASE_ARM64_T6000 arm64
Description
Ledger sign_tx can not work anymore. always show LedgerError(BadRetcode(BadKeyHandle))
I tried this code:
I expected to see this happen:
Instead, this happened: LedgerError(BadRetcode(BadKeyHandle))
The text was updated successfully, but these errors were encountered: