Skip to main content
Function Signature
Parameters
  1. chainId: The chain identifier in CAIP-2 format (e.g., “eip155:1” for Ethereum mainnet)
  2. transaction: An EvaluateTransactionParam object containing:
    • to:* Destination address
    • value: (Optional) Transaction value in wei
    • data: (Optional) Transaction data for contract interactions
    • maxFeePerGas: (Optional) Maximum total fee per gas unit
    • maxPriorityFeePerGas: (Optional) Maximum priority fee per gas unit
    • gas: (Optional) Gas limit
    • gasPrice: (Optional) Gas price for legacy transactions
  3. operationType: Optional EvaluateTransactionOperationType with values:
    • .validation: Perform security validation only
    • .simulation: Perform transaction simulation only
    • .all: Perform both validation and simulation
Returns A BlockaidValidateTrxRes containing:
  • validation: Security validation results including:
    • classification: Type of potential security issue
    • description: Detailed description of the validation results
    • features: Array of detected security features, each containing:
      • type: Feature type
      • featureId: Unique identifier
      • description: Feature description
      • address: Related address if applicable
    • reason: Explanation of the validation result
    • resultType: Type of result
    • status: Validation status
  • simulation: Transaction simulation results including:
    • accountAddress: Address being analyzed
    • accountSummary: Summary of account state changes
    • addressDetails: Detailed information about involved addresses
    • assetsDiffs: Asset balance changes, containing:
      • asset: Asset information
      • in: Incoming transfers
      • out: Outgoing transfers
    • exposures: Risk exposure analysis
    • status: Simulation status
    • totalUsdDiff: Total USD value change
    • totalUsdExposure: Total USD value at risk
  • block: Block number used for evaluation
  • chain: Chain identifier
Example Usage
Implementation Notes
  • Always evaluate transactions involving large amounts or contract interactions
  • Consider both validation and simulation results for comprehensive security
  • Handle different validation statuses appropriately in your UI
  • Gas parameters should be adjusted based on current network conditions
  • For contract interactions, carefully validate the data field