-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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 --hd-paths returns "Ledger device not available" #4692
Comments
+1 on this. Anything with the |
I was also having the same problem when using the eg: ➜ ✗ forge script --rpc-url $SEPOLIA_URL script/....s.sol --ledger --mnemonic-indexes 1 --sender 0x... --verify --broadcast |
@bschreck / @gpsanant / @brayansdt would be great to know if you are still facing issues around this Foundry has recently moved to Alloy's Ledger implementation so it is likely your issue may have been resolved |
I confirm this works with latest version but the derivation path in original comment is wrong (that is forge script script/Counter.s.sol --rpc-url RPC_URL --ledger --broadcast --hd-paths "m/44'/60'/1'/1/0" --sender SENDER
[⠒] Compiling...
No files changed, compilation skipped
Script ran successfully.
## Setting up 1 EVM.
==========================
Chain 137
Estimated gas price: 30.000000052 gwei
Estimated total gas used for script: 138729
Estimated amount required: 0.004161870007213908 ETH
==========================
Transactions saved to: /broadcast/Counter.s.sol/137/run-latest.json
Sensitive values saved to: /cache/Counter.s.sol/137/run-latest.json going to close the issue, @bschreck @gpsanant @brayansdt please reopen if you still hit problems. thank you! |
Component
Forge
Have you ensured that all of these are up to date?
What version of Foundry are you on?
forge 0.2.0 (f7a535d 2023-04-03T00:04:49.769079000Z)
What command(s) is the bug in?
forge script <script.s.sol> --chain-id 137 --rpc-url $POLYGON_RPC_URL --ledger --broadcast --hd-paths "m44'60'/0'/1/0" --sender
Operating System
macOS (Apple Silicon)
Describe the bug
I've tried many versions of the above command with different hd-path variants, removing the m and the last /0. I'm trying to deploy using the second address on my ledger, but even using the hd-path of the first address does not work. The command works fine if I leave out --hd-paths and deploy using the first address of my ledger as the --sender.
I get
The text was updated successfully, but these errors were encountered: