Chain Configuration
The minimum configuration you need for a new chain:Chains with Custom Modules
Most application-specific chains (Osmosis, dYdX, Stride, etc.) define custom modules beyond the standard Cosmos SDK set. Register their types and converters as described in the Custom Modules guide:Custom Account Parsers
Some chains use non-standard account types (e.g.EthAccount on EVM-compatible chains). The default accountFromAny parser won’t recognize them, causing account lookups to fail. Pass a custom accountParser to handle these:
accountParser option is available on both StargateClient (read-only) and SigningStargateClient (signing). The parser receives an Any-encoded account from the auth module and must return an Account object with address, pubkey, accountNumber, and sequence.
HD Derivation Paths
Different chains may use different BIP-44 coin types in their HD derivation path. The default ism/44'/118'/0'/0/0 (coin type 118, the Cosmos Hub standard). Override this for chains that use a different coin type:
Multiple Accounts
To derive multiple accounts from the same mnemonic, pass multiple HD paths:Next Steps
Custom Modules
Build a complete module integration for your chain’s custom message types.
Code Generation
Use Telescope or ts-proto to generate TypeScript types from your chain’s protobuf definitions.
Cosmos EVM Chains
Special considerations for EVM-compatible Cosmos chains.