Skip to main content
Signing produces a signature without preparing or submitting a transaction. Signing requires an active wallet session with a wallet of the method’s network family. Verification checks the active wallet by default, or any address you pass.

Sign and verify a message

signMessage returns a hex-encoded signature. Verification returns Bool.

Sign and verify a Solana message

For a selected Solana wallet, use the Solana-specific methods. Off-chain messages do not take a network because they are not cluster-specific.

Sign and verify typed data

Represent EIP-712 typed data with public JSONValue cases.
Use the same network and exact payload for signing and verification.

Sign and verify with a Tron wallet

For a selected Tron wallet, use the Tron-specific methods. They take no network. signTronTypedData and isValidTronTypedDataSignature sign and verify TIP-712 typed data, whose address values may be Base58Check strings.
tronTypedData is a JSONValue built the same way as the EIP-712 example above.

Understand verification context

Every verification method takes an optional walletAddress:
  • With walletAddress, verification needs no wallet session and checks that address.
  • Without it, the SDK uses the active wallet’s address, so a wallet of the method’s network family must be active.
Signing always needs an active wallet of the method’s network family. Indexer reads accept any address without a session.