Skip to main content

Risk Control Triggers

Risk control triggers are the actions executed when a wallet hits a risk control rule.
They are designed to protect assets, block abnormal transactions, or generate approval workflows.

I. Wallet State​

In trigger design, the wallet state is a core concept that determines when and how triggers are executed.

  • Locked State

    • When the wallet is locked, no transactions can be executed
    • Design purpose: prevent assets from being drained in a single attack after private key compromise

  • Unlocked State

    • When the wallet is unlocked, transactions can be executed normally
    • Triggers may temporarily change the wallet state based on rules to ensure security

Wallet state is a prerequisite for trigger execution.
Triggers select actions based on the current wallet state.

II. Trigger Types​

Based on different security and business requirements, risk control triggers can perform the following actions:

1. Lock Wallet​

  • Function: Lock the wallet and block all transactions
  • Implementation:
    • Locking can be triggered by backend monitoring
    • Wallet owners can unlock via multisignature
    • Users may also choose to disable automatic locking for this trigger, in which case the system will no longer lock the wallet
  • Use Cases:
    • Automatically lock the wallet when high-risk or abnormal behavior is detected
    • Protect assets in case of private key leakage

2. Reject Transaction​

  • Function: Block execution of the current transaction
  • Use Cases:
    • Single transaction amount exceeds the configured limit
    • Transaction invokes an unauthorized program or instruction
  • Characteristics:
    • Immediately blocks the risky transaction without changing wallet state
    • Can be used together with the lock wallet trigger

3. Generate Approval Transaction​

  • Function: Convert the transaction into a multisignature transaction requiring approval
  • Use Cases:
    • All user transactions require approval
    • High-risk transactions require additional confirmation
  • Characteristics:
    • Approval participants and workflows can be customized
    • The transaction will not be executed until approval is completed

III. Design Principles​

  • Security First: Triggers are designed to protect asset security
  • Flexible and Controllable: Users can choose whether triggers are allowed to execute automatically
  • Auditable: All trigger actions are traceable, ensuring transparency and compliance

IV. Typical Use Cases​

  • The wallet hits a high-frequency or high-amount transfer rule and is automatically locked
  • A single transfer exceeds the limit, the transaction is rejected, and the event is logged
  • Daily operations require approval, generating a multisignature approval workflow