feat(wallets): add infrastructure for Trezor session_id reuse across multiple signers #10822
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
session_id
across multipleTrezorSigner
#9388When using Trezor hardware wallets with passphrase enabled, each new TrezorSigner instance requires re-entering the passphrase, creating poor UX when multiple wallets are needed (e.g., forge script --trezor --mnemonic-indexes 0,1,2).
Solution
Implemented infrastructure for session_id reuse across multiple TrezorSigner instances:
Note: Session_id extraction currently returns None due to alloy-signer-trezor crate limitations, but infrastructure is ready for when upstream support becomes available.
PR Checklist