Skip to main content

Passed Account Balance Filter

The passed account balance filter evaluates the native asset balances of passed accounts involved in a transaction, preventing assets from indirectly leaving the wallet through transaction intermediaries.

I. Filter Positioning​

This filter serves as a security mechanism for controlling the native coin balances of passed accounts within the asset filtering system.
It restricts asset changes in accounts not directly owned by the wallet, mitigating the risk of bypassing the wallet balance filter.

  • Problem solved: Indirect accounts in a transaction may carry away assets
  • Difference from Wallet Balance Filter: Wallet balance filter only controls the wallet’s own balance; passed account balance filter controls indirect account balances

II. Target Scope​

  • Passed accounts (Accounts) involved in the transaction
  • Native asset balances of these accounts (e.g., SOL)

Note: Only native coin balances are considered. Token assets are controlled by the Passed Account Token Filter.

III. Parameters​

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

  • Whitelist Mode (InList)

    • Only accounts listed are included in subsequent risk control calculations
    • Accounts not in the list are excluded from this filter’s risk control scope

  • Blacklist Mode (NotInList)

    • Accounts listed are excluded from subsequent risk control calculations
    • Accounts not in the list are included in subsequent risk control calculations

Account lists are configured using on-chain account public keys (Pubkeys).

Whitelist and blacklist modes cannot be enabled simultaneously. Only one mode can be selected: Whitelist (InList) or Blacklist (NotInList).

IV. Typical Use Cases​

  • Prevent indirect accounts (not the wallet itself) from carrying large asset amounts through transactions
  • Combine with the wallet balance filter to form full-dimensional native asset constraints
  • Ensure passed account balances cannot bypass risk control rules in complex transactions, such as multisignature or program calls

V. Notes​

  • The filter itself does not determine transaction success; it only decides whether passed accounts are included in subsequent risk control calculations
  • Usually used together with the Passed Account Token Filter to ensure both native coin and token assets are effectively controlled