Skip to main content
Signing clients extend their read-only counterparts with the ability to build, sign, and broadcast transactions. They require a signer (wallet) and are created via static factory methods.

Signers

A signer is any object that holds keys and can produce signatures. CosmJS supports two signing modes: Both implement getAccounts() to list available accounts. The signing client auto-detects which mode to use based on whether the signer has a signDirect method.

SigningStargateClient

Factory Methods

Transaction Methods

Convenience Methods

Fees

The fee parameter accepts three forms:

Options

  • registry — protobuf type registry for encoding messages (defaults cover all standard Cosmos SDK message types)
  • aminoTypes — converters between protobuf and Amino for Amino signers
  • gasPrice — required when using "auto" fees; supports static pricing or dynamic fee market pricing via DynamicGasPriceConfig

SigningCosmWasmClient

Extends CosmWasmClient with signing and smart contract transaction methods.

CosmWasm-Specific Transaction Methods

SigningCosmWasmClient also includes all the convenience methods from SigningStargateClient (sendTokens, delegateTokens, etc.) as well as signAndBroadcast, sign, and simulate.

Next Steps

Send Transactions

Step-by-step guide to sending transactions.

Fees and Gas

Understand gas limits and fee calculation.