Transaction Signing
Clique Wallet provides secure transaction signing for all supported blockchain networks. All signing operations occur within the TEE, ensuring private keys never leave the secure enclave.
Supported Signing Methods
EVM-Compatible Chains:
EIP-712 structured data signing for typed transactions
Standard message signing for arbitrary data
Transaction signing for Ethereum and EVM-compatible chains
Solana:
Native Solana transaction signing
Message signing for Solana applications
Support for Solana's transaction format and instruction sets
Hyperliquid:
Native HyperCore transaction signing, using EIP-712 structured data signing for typed transactions
Signing Process
Prepare Transaction: Your application prepares the transaction data according to the blockchain's requirements
Request Signature: Send the transaction data to Clique Wallet's signing endpoint
TEE Signing: The transaction is signed within the TEE's secure enclave
Return Signature: Only the signature is returned—the private key remains protected
Submit Transaction: Your application submits the signed transaction to the blockchain network
Security During Signing
All signing operations require user authentication through a valid session or API key
All signing operations occur within the TEE's hardware-protected enclave
Private keys are never exposed in plaintext during the signing process
Address verification ensures transactions are signed by the correct wallet
Transaction validation can be enabled to verify transaction parameters before signing
Whitelist Signing
Clique Wallet supports whitelist signing, allowing you to restrict which transactions can be signed. This provides an additional layer of security by ensuring that only approved transactions are processed, protecting against unauthorized or malicious transaction attempts.
How Whitelist Signing Works:
Transaction Filtering: When whitelist signing is enabled, only transactions that match the configured whitelist criteria are allowed to be signed
Flexible Configuration: Whitelists can be configured based on various transaction parameters such as recipient addresses, contract addresses, transaction types, or other criteria
Automatic Rejection: Any transaction that doesn't match the whitelist is automatically rejected before signing, preventing unauthorized operations
Use Cases:
Enterprise Security: Restrict signing to only approved addresses or contracts, ensuring compliance with organizational policies
Risk Management: Limit transactions to trusted recipients or protocols, reducing exposure to malicious contracts or phishing attempts
Operational Control: Maintain strict control over which operations can be performed, especially for high-value accounts or automated systems
Whitelist signing is an optional security feature that can be configured when needed to provide additional protection for your wallets and assets.
Last updated