Skip to main content
SigningStargateClient works with EVM wallets without any special configuration. When signing transactions, the client inspects the algo field from the wallet’s AccountData and automatically selects the correct pubkey encoding.
Gas simulation (simulate()) always uses standard secp256k1 pubkey encoding regardless of the wallet’s algo field. This means "auto" fees may produce incorrect simulations with EVM wallets. Use explicit StdFee values instead of "auto" when working with DirectEthSecp256k1HdWallet.