> For the complete documentation index, see [llms.txt](https://docs.compliance.phalcon.blocksec.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.compliance.phalcon.blocksec.com/manual/quick-start.md).

# Quick Start

This guide walks you through the basic steps to effectively use the Phalcon Compliance application to monitor risks. Follow these core workflows to configure risk engines, screen address risks, and receive timely alerts.

{% hint style="info" %}
**Want to integrate via API?** See the [API Documentation](https://docs.compliance.phalcon.blocksec.com/api-documentation/introduction.md) for authentication, endpoints, and code examples.
{% endhint %}

## Review and Configure Risk Engine <a href="#review-and-configure-risk-engines" id="review-and-configure-risk-engines"></a>

A risk engine is a customizable set of rules that defines the risks to detect and triggers alerts. It is the core engine of your compliance monitoring system.

<figure><img src="https://1419887533-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPfx6yOSRmp0GCnHv5rhy%2Fuploads%2Fgit-blob-bd2073ae3c02f979b06dd56b8f72f7e1e33d2898%2Fimage.png?alt=media" alt="Risk Engine Overview tab showing rule coverage and overlap warnings"><figcaption></figcaption></figure>

### Review Default Rules <a href="#review-default-risk-engines" id="review-default-risk-engines"></a>

Default rules are provided as a versioned set based on FATF guidelines and industry best practices. For the current list, see [Default Rules](https://docs.compliance.phalcon.blocksec.com/manual/configure/risk-engines/default-engines.md).

Steps:

* Navigate to the Risk Engine page (/risk-engines).
* Open the **Rules** tab and review each rule's trigger conditions (e.g., numerical thresholds and risk indicators).
  * To customize detection logic, create or clone a Custom Rule and adjust its conditions to match your business needs and regional requirements. Default Rule detection logic cannot be edited.
* Ensure that the required rules are enabled in the rule list or rule details.

## Screen Addresses or Transactions

### Screen Addresses

Each address is automatically screened against all active address-type risk engines. You can screen addresses individually or through bulk import.

<figure><img src="https://1419887533-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPfx6yOSRmp0GCnHv5rhy%2Fuploads%2Fgit-blob-cd2d03f5691dbc403389d164d3b8d8eb83c48f40%2Fimage.png?alt=media" alt="Searching for an address in the search bar"><figcaption></figcaption></figure>

We searched for the address 0xc7A2aBc3b88f1465c4b3A4E7Bf2D2d59897851BB (Bybit hacker) and added it to Phalcon on the Ethereum chain.

<figure><img src="https://1419887533-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPfx6yOSRmp0GCnHv5rhy%2Fuploads%2Fgit-blob-c433a326de2b20dafdf354836cd4e402aebaa01b%2Fimage.png?alt=media" alt="Adding an address to Phalcon on Ethereum" width="375"><figcaption></figcaption></figure>

After screening, the address appears in the address list. Review its risk summary and unresolved alerts to identify findings that need investigation.

<figure><img src="https://1419887533-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPfx6yOSRmp0GCnHv5rhy%2Fuploads%2Fgit-blob-04e46a8b3ec0cb32766d5a1821a1568f342df773%2Fimage.png?alt=media" alt="Address list showing risk summaries, unresolved alerts, last screening time, and tags"><figcaption><p>Example address list including Trust Wallet Drainer 2. The addresses and alert counts shown differ from the import example above.</p></figcaption></figure>

Click the address to view its details, including basic information, screening information, and triggered alerts.

<figure><img src="https://1419887533-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPfx6yOSRmp0GCnHv5rhy%2Fuploads%2Fgit-blob-a0cd039608e0d65f7a05c675e342628a3065d320%2Fimage.png?alt=media" alt="Address details page with Basic Information, Risk Summary, Entity Risk, and alerts"><figcaption><p>Example details page for another screened address. Results and alert counts depend on the address and screening time.</p></figcaption></figure>

#### Continuous Monitoring

Enable monitoring for an address to continuously track risk changes:

* Automatically detect new risks when transactions occur.
* Receive alerts when the risk status changes — when a new risk is detected or an existing risk is resolved.
* No manual rescreening is required — the system automatically adjusts the screening frequency based on address activity.

You can enable monitoring from the address details page or the action menu in the address list. For details, see [Monitor](https://docs.compliance.phalcon.blocksec.com/manual/monitoring/monitor.md).

### Screen Transactions

Each transaction is automatically checked against all active transaction-type risk engines. On the Transactions page, you can screen transactions individually or through bulk import.

After searching for the transaction hash `0xde64ab6dccf27bda99fa7efdc2fcc58475859dae4fd95a8da267dc0994ab5971`, the system automatically retrieves and decodes the transfer details, allowing users to select the transfers to screen.

<figure><img src="https://1419887533-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPfx6yOSRmp0GCnHv5rhy%2Fuploads%2Fgit-blob-40a97fe916a4a4c28db961fc109d9643415952cd%2Fimage.png?alt=media" alt="Selecting transfers to screen from a transaction" width="375"><figcaption></figcaption></figure>

After screening, the transaction was identified as having a **Critical** risk level and triggered **2 unresolved alerts**, requiring immediate action.

<figure><img src="https://1419887533-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPfx6yOSRmp0GCnHv5rhy%2Fuploads%2Fgit-blob-f5a92f7cdff81700c36354bc94e0ee9d5b5cf4cf%2Fimage.png?alt=media" alt="Transaction screening result showing Critical risk level"><figcaption></figcaption></figure>

Click the transaction to view its details, including basic information, token transfers, and triggered alerts.

<figure><img src="https://1419887533-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPfx6yOSRmp0GCnHv5rhy%2Fuploads%2Fgit-blob-81a41c4b9b3e6c1fd443a70551162824d6073c5a%2Fimage.png?alt=media" alt="Transaction details page with Risk Summary, Entity Risk, Transfer Overview, and alerts"><figcaption><p>Example details page for another screened transaction. Results and alert counts depend on the transaction and screening time.</p></figcaption></figure>

## Add Notification Channels

Add notification channels to immediately notify users when alerts are triggered. Phalcon supports multiple notification channels, including email, Telegram, Slack, Lark, Discord, Pagerduty, and Webhook.

Here, we use Telegram as an example.

<figure><img src="https://1419887533-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPfx6yOSRmp0GCnHv5rhy%2Fuploads%2Fgit-blob-b4654c501c17c23392ef695b47592f7371188846%2Fimage.png?alt=media" alt="Creating a Telegram notification channel" width="563"><figcaption></figcaption></figure>

To activate the Telegram notification channel, users should add @PhalconComplianceBot as a contact in Telegram. Click the link below to add this bot.

[@PhalconComplianceBot](https://t.me/PhalconComplianceBot)

Then use the `/getchatid` command to obtain the chat ID. @PhalconComplianceBot uses this chat ID to send alerts to the user's Telegram.

<figure><img src="https://1419887533-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPfx6yOSRmp0GCnHv5rhy%2Fuploads%2Fgit-blob-9edc90ab727a98ce219cc1791b69ae1457f32543%2Fimage.png?alt=media" alt="Getting chat ID from @PhalconComplianceBot"><figcaption></figcaption></figure>

You can also add the bot to a group, and alert notifications will be sent to that group.

A notification channel should be linked to a specific risk engine to receive notifications for alerts triggered by that risk engine.

<figure><img src="https://1419887533-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPfx6yOSRmp0GCnHv5rhy%2Fuploads%2Fgit-blob-f88fbff2114be02af121ad7d89cdb48dffeb2780%2Fimage.png?alt=media" alt="Binding notification channels to risk engines"><figcaption></figcaption></figure>

For more details about the steps to create each notification channel, visit [Notification Channels](https://docs.compliance.phalcon.blocksec.com/manual/configure/notification-channels.md)

### Summary

After completing the steps above, users have successfully created risk engines, learned the address screening process, and linked notification channels, thereby establishing a seamless compliance workflow.

## Default Rules <a href="#default-risk-engine-list" id="default-risk-engine-list"></a>

For a complete list of all preset rules and their descriptions, see [Default Rules](https://docs.compliance.phalcon.blocksec.com/manual/configure/risk-engines/default-engines.md).
