OMSWalletValidationException before any request.
Verification can target any wallet. Pass walletAddress to verify a signature from a specific address, even while signed out. Omit it to verify against the active wallet’s address, which then requires an active session and a wallet of the method’s family.
Sign and verify a message
The message API accepts onlyString. It does not provide a byte-array or hexadecimal-message overload.
false for a signature that OMS does not validate; request or session failures throw an OMSWalletException.
To verify a signature from a specific wallet, pass its address:
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 EIP-712 typed data
Typed data usesJsonElement. Build the complete EIP-712 payload expected by the application and contract:
isValidTypedDataSignature also accepts walletAddress. Verification does not create a transaction.
Sign and verify Tron messages and typed data
For a selected Tron wallet, use the Tron-specific methods. They do not take a network.signTronTypedData and isValidTronTypedDataSignature sign and verify TIP-712 typed data. Build the complete TIP-712 payload as a JsonElement, as in the EIP-712 example. Address values in the payload may be Base58Check strings that start with T.
walletAddress.