Component
Other (please describe)
Describe the feature you would like
foundry-wallets already provides a useful integration layer on top of Alloy signers for CLI applications.
It covers the common work that downstream tools otherwise have to reimplement:
- wallet-related CLI options
- signer resolution from flags / env / files
- support for local keys, mnemonics, keystores, Ledger, Trezor, AWS KMS, GCP KMS, Turnkey, browser wallets
- a unified runtime signer type
- multi-wallet flows
Right now, downstream tools either:
- build directly on
alloy-signer* crates and reimplement this wrapper/resolution layer themselves, or
- depend on Foundry internals through git/path dependencies
Publishing foundry-wallets would give downstream CLI authors a reusable crate for the full signer matrix that Foundry already supports.
The useful public surface is already there:
WalletSignerWalletOptsMultiWalletOptsRawWalletOpts
Even if the API remains somewhat Foundry-shaped, publishing it as-is would still be valuable and would avoid repeated reimplementation across Alloy-based CLIs.
Additional context
No response
Component
Other (please describe)
Describe the feature you would like
foundry-walletsalready provides a useful integration layer on top of Alloy signers for CLI applications.It covers the common work that downstream tools otherwise have to reimplement:
Right now, downstream tools either:
alloy-signer*crates and reimplement this wrapper/resolution layer themselves, orPublishing
foundry-walletswould give downstream CLI authors a reusable crate for the full signer matrix that Foundry already supports.The useful public surface is already there:
WalletSignerWalletOptsMultiWalletOptsRawWalletOptsEven if the API remains somewhat Foundry-shaped, publishing it as-is would still be valuable and would avoid repeated reimplementation across Alloy-based CLIs.
Additional context
No response