Owners can configure destination address screening protocols with integrated app support from Cube3 and Cyvers to evaluate cyber, fraud, and compliance risks. It is enabled by default across all organisations in Liminal Vaults. Admins and Members have view-only access to the Address Screening configuration.

The feature supports the following wallets:

1. Cold MPC and Multisig wallets, and
2. Hot withdrawal wallet.

Refer to the following links for quick access:

1. Supported use cases: Explore the supported use cases for address screening.
2. Configure address screening: set custom behaviours for different risk scores for withdrawal, multisig, and mobile wallets.
3. Disable Compliance Alerts for address screening: Eliminate the compliance alert category when evaluating the risk score.

📘

Note

• Address screening is unavailable for a hot deposit wallet.
• Enable: It is enabled by default across all organisations in Liminal Vaults.
• Disable: Owners can disable address screening for hot withdrawal wallet transactions created via the Create a Transaction Request API. It cannot be disabled for Cold Multisig and Warm MPC Mobile Wallets.

What is Address Screening

Address screening helps identify fraud and malicious addresses before a destination address is whitelisted or a transaction is executed, preventing financial and compliance risks.

Liminal has integrated with Cube3 and Cyvers to evaluate addresses for fraud and cyber security related risks by screening destination addresses. Address screening has the following features:

• Automated risk evaluation - In Liminal Vaults web and mobile app, when you initiate address whitelisting, approve address whitelisting policy, initiate transactions, and sign transactions, a risk score (low,medium, high, critical) is displayed based on the risk severity. You can make informed decisions and prevent losing funds to malicious addresses.
• API security for withdrawal hot wallets - All destination addresses passed in the request body of the Create transaction requests API will be screened by Cube3 for Cyber, Fraud and Compliance related risks.
• Personalised risk score severity settings - Configure personalised severity range for automatically blocking risky transactions. All risky transactions irrespective of severity will display a warning before approving or canceling the transaction if the settings have been set to “warn only”.

How Address Screening Works

Liminal has partnered with Cube3 and Cyvers to evaluate your addresses and transactions based on their respective alert categories. An address is screened against each category and assigned a risk score via risk score evaluation. The final result is calculated based on compliance validation, taking into account the final risk scores of Cyvers and Cube3.

1. Cyvers: analyses addresses to identify connections with risky entities, assigning them a risk score to help detect potential threats and ensure safe transactions. It detects potential risks under security, scam, and compliance categories as explained below:
   1. Security: Real-time threat detection and prevention for blockchain assets.
   2. Scam: Identifying fraudulent transactions and phishing attacks.
   3. Compliance: Helping crypto firms meet AML and risk management requirements.
2. Cube3: assigns dynamic risk scores to addresses, smart contracts, and transactions using AI-driven analysis, detecting cyber, fraud, and compliance-related risks as explained below:
   1. Cyber: Securing blockchain networks from threats like hacking and smart contract exploits.
   2. Fraud: Illicit activities such as phishing scams in blockchain transactions.
   3. Compliance: Ensuring adherence to regulations (e.g., AML, KYC, Travel Rule) in blockchain operations.

📘

Note

1. You can disable Compliance alerts from Cube3 and Cyvers during destination address screening. When Compliance alerts are disabled, the destination address is screened, and the decision to block or warn is based only on the other categories, i.e., cyber and fraud-related categories.

   Refer to the Disable Compliance Alerts for Address Screening guide to learn how to ignore Compliance alerts.

2. You can set customised thresholds to auto-block transactions or warn you depending on the severity of the risk associated with the transaction.

3. Address screening cannot be disabled for Cold Multisig and Warm MPC Mobile wallets.

4. Address screening can be disabled for hot withdrawal wallet transactions created via Create a Transaction Request API

Risk Score Evaluation

An address is either passed or flagged when it reaches a score within its threshold among its respective alert categories. Owners can configure the threshold settings to personlise the minimum severity to block transactions and include/exclude compliance alerts.

Security Validation

The Security validation is evaluated using statistical normalization on the risk score assessment from both Cube3 and Cyvers.

📘

Note

Reach out to our support team if you think the destination address risk score is a false positive. We will review the address and get back to you within 4 hours.

Supported Networks

Cyvers screening is supported on Liminal for the following networks:

• Ethereum (ETH and ERC-20 Tokens)
• BSC Chain (BNB and BEP-20 Tokens)
• Polygon (MATIC/POL and ERC-20 Tokens on Polygon)
• Avalanche (AVAX and ERC-20 Tokens on Avalanche)
• Arbitrum (ERC-20 Tokens on Arbritrum)
• Optimism (ERC-20 Tokens on Optimism)
• BASE (ERC-20 Tokens on Base)
• Tron (Coming Soon)

Cube3 screening is supported on Liminal for the following networks.

• Ethereum (ETH and ERC-20 Tokens)
• BSC Chain (BNB and BEP-20 Tokens)
• Polygon (MATIC/POL and ERC-20 Tokens on Polygon)
• Avalanche (AVAX and ERC-20 Tokens on Avalanche)
• Arbitrum (ERC-20 Tokens on Arbritrum)
• Optimism (ERC-20 Tokens on Optimism)
• BASE (ERC-20 Tokens on Base)
• XRPL (Ripple)
• Bitcoin (BTC)
• Litecoin (LTC)
• Solana (SOL and SPL tokens)
• Tron (TRX and TRC-20 Tokens)