Skip to main content

Transaction Parameter Rule

The Transaction Parameter Rule is a conditional rule used to trigger risk control based on the byte data of parameters passed in a transaction, ensuring that specific transaction operations are executed within a safe range.

Core Function​

  • Parameter-level control: Determine whether to trigger risk control based on the byte parameters of a transaction
  • Precisely constrain specific operations: Can restrict specific methods or function calls

Parameters​

  • from / to

    • The start and end positions of the byte parameters in the transaction data, used to extract the range for evaluation

  • is_hit_trigger

    • Indicator of whether the trigger condition is met
    • When triggered, the corresponding risk control event is executed

  • byte_rule

    • Defines the specific byte matching rule, such as whitelist/blacklist or custom logic
    • Can be configured according to specific business scenarios

Note: This rule only takes effect when the asset filter is the Program Address Filter; it does not directly select assets.
Note: This rule is intended for operations requiring fine-grained control over transaction parameters and should be configured carefully.

Typical Use Cases​

  • Restrict a wallet to call only a specific method of a program
  • Ensure that calling a program requires passing parameters in a specified format
  • Prevent transactions from including illegal or abnormal data
  • Combine with direct-effect rules or composite rules to enhance security for complex transactions

Additional Notes​

  • Scope: Applicable only to parseable transaction byte data; cannot directly control amounts or counts
  • Flexible combination: Can be combined with the Program Address Filter