Skip to main content
Signing produces a signature without preparing or submitting a transaction. Signing and verification require an active wallet session.

Sign and verify a message

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

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.

Understand verification context

Both verification methods accept an explicit walletAddress, so you can choose the address checked by the service. They still use the active wallet ID as OMS verification context. The Swift SDK does not expose these methods as unauthenticated verification for arbitrary wallets. If no wallet is active, signing and verification throw a session error. Indexer reads are different: they accept any address without an active wallet session.