Skip to main content
Note: see the language section for more details.

Allow ABI-specific contract call parameters

See here for more information and examples.

Allow ERC-20 transfers for a specific token smart contract

Allow anyone to sign transactions for testnet (Sepolia)

Allow ETH transactions with a specific nonce range

Allow signing of EIP-712 payloads for Hyperliquid ApproveAgent operations

Inspect nested fields in EIP-712 message payloads

The eth.eip_712.message map supports nested field access using bracket notation, allowing policies to inspect typed data contents beyond just the domain and primary type. Syntax:
  • Nested struct fields: eth.eip_712.message['outerField']['innerField']
  • Array element fields: eth.eip_712.message['arrayField'][0]['innerField']
Example: Restrict Hyperliquid orders to a specific asset Hyperliquid’s HyperliquidTransaction:Order message contains an orders array of Order structs. Each Order uses short field names: a (asset index), b (isBuy), p (price), s (size), r (reduceOnly).
To allow only orders for a specific asset (e.g. ETH = asset index 3):
Array access is index-based ([0], [1], etc.). The condition message['orders'][0]['a'] == '3' only checks the first order — any additional orders in the array are not evaluated. To restrict all orders in a known-size batch, add a condition for each index: message['orders'][0]['a'] == '3' && message['orders'][1]['a'] == '3'.

Deny signing of NO_OP keccak256 payloads

Allow signing of EIP-712 payloads for EIP-3009 transfers

Allow signing of EIP-712 payloads for EIP-2612 permits for USD Coin

Allow signing of EIP-7702 authorizations