Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.extractor.live/llms.txt

Use this file to discover all available pages before exploring further.

Maintain a list of known malicious, sanctioned, or otherwise untrusted addresses. Any time one of them interacts with your contract, the trigger fires immediately — before the transaction has any further effect downstream.
This trigger fires on the initiating address (msg.sender), not intermediate contracts in a call chain. For full call-chain coverage, pair it with the AML Detector.

​
Use cases

Sanctions enforcement

Block or flag interactions from OFAC-listed wallets and known exploit addresses before they can interact with your protocol.

Post-exploit containment

After a security incident, add the attacker’s addresses to the blacklist immediately. Any follow-up interaction with surviving contracts triggers an instant alert.

Competitor or bot exclusion

Track if specific bots or competitor addresses are interacting with your contract at unusual frequency.

​
Configuration

1

Name

Enter a descriptive label, e.g. Sanctioned Address Alert.
2

Blacklisted entities

Comma-separated list of addresses to watch. Any transaction initiated by one of these will fire the trigger:
0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045,
0xAb5801a7D398351b8bE11C439e05C5B3259aeC9B
Keep your blacklist in sync with an external AML feed by periodically updating this field via the API. The Custom Addresses option in the AML Detector can automate this for larger lists.