bug: invalid sender error when using Trezor with forge script with --broadcast flag
#7342
Assignees
Labels
A-compatibility
Area: compatibility
Cmd-forge-script
Command: forge script
T-bug
Type: bug
T-to-investigate
Type: to investigate
T-to-reproduce
Type: requires reproduction
Comments
2 tasks
zerosnacks
added
T-to-reproduce
zerosnacks
changed the title
invalid sender error when using Trezor with forge script with --broadcast flag
|
Possibly related fix: trezor/trezor-firmware#3952 (comment) just got released, highlighted in #7660 (comment) Requires updating Alloy to |
3 tasks
|
Related PR: alloy-rs/alloy#1045 including possible fix: trezor/trezor-firmware#3952 (comment) |
2 tasks
|
Marking as resolved by https://github.com/alloy-rs/alloy/releases/tag/v0.2.0 and Foundry having been bumped to 0.2.0 in https://github.com/foundry-rs/foundry/pull/8305/files#diff-2e9d962a08321605940b5a657135052fbcef87b5e360662bb527c96d9a615542 |
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#7141 probably introduced some regeression for trezor signers: https://t.me/foundry_support/51031
"Invalid sender" error when using Trezor with forge script and the --broadcast flag.
Command:
forge script script/myscript --rpc-url $MAINNET_RPC_URL --mnemonic-derivation-paths "myderivation" --trezor --broadcast -vvvv --sender myaddr --sig "something"The text was updated successfully, but these errors were encountered: