Skip to main content

Passed Account Token Filter

The passed account token filter evaluates token assets held by passed accounts involved in a transaction, preventing tokens from indirectly leaving the wallet through transaction intermediaries.

I. Filter Positioning​

This filter serves as a security mechanism for controlling token assets of passed accounts within the asset filtering system.
It restricts token movements in accounts not directly owned by the wallet, mitigating the risk of bypassing the wallet token filter.

  • Problem solved: Indirect accounts in a transaction may carry away token assets
  • Difference from Wallet Token Filter: Wallet token filter only controls tokens directly held by the wallet; passed account token filter controls token assets of indirect accounts in a transaction

II. Target Scope​

  • Passed accounts (Accounts) involved in the transaction
  • Token assets held by these accounts (Token Accounts)

Note: Only token assets are considered. Native coin balances are controlled by the Passed Account Balance Filter.

III. Parameters​

The passed account token filter supports whitelist or blacklist-based matching strategies to determine which token assets of passed accounts should be included in subsequent risk control calculations.

  • Filter Mode (in_or_not)

    • Whitelist Mode (InList)
      Only the specified tokens of accounts in the list are included in subsequent risk control calculations
      Tokens of accounts not in the list are excluded from this filter’s risk control scope
    • Blacklist Mode (NotInList)
      Tokens of accounts in the list are excluded from subsequent risk control calculations
      Tokens of accounts not in the list are included in subsequent risk control calculations

  • Passed Account List (list)

    • Specifies the Pubkeys of passed accounts to be included in risk control

  • Token (token)

    • Specifies the target token Mint address
    • Only the specified token asset is included in the whitelist/blacklist matching

Note: This filter only determines whether token assets of specific passed accounts are included in subsequent risk control calculations. It does not directly control transaction success.

IV. Typical Use Cases​

  • Prevent indirect accounts from moving large amounts of tokens, bypassing wallet token filter risk controls
  • Restrict specific passed accounts’ tokens from being included in risk control, preventing false positives or abnormal asset outflows
  • Used together with the Passed Account Balance Filter to ensure both native coin and token assets in a transaction are effectively controlled