Automate institutional-grade compliance by integrating Chainalysis Sanctions screening with Thirdweb Engine's smart contract orchestration. Build secure, automated workflows that instantly validate wallet addresses against global sanctions lists before executing on-chain transactions.
This workflow monitors contracts events and screens addresses interacting with that contract to flag santions/OFAC and high risk accounts. The data and flagged accounts are auto-logged into a Gsheet and a notification is sent. This allows teams to make sure they remain compliant and block any bad actors from interacting with their platform. ### Quick Setup: 1. Connect your Gsheets account 2. Input the contract address you want monitored 3. Input the chain the contract address is deployed on 4. Drop in the Gsheet Spreadsheet URL where you want the data to be logged 5. Specify the tab you want the data to be logged in the Spreadsheet (input 0 if first tab) 6. Test and Publish!
Screen Address for Sanctions
ActionCheck whether a blockchain address is on any sanctions list tracked by Chainalysis (OFAC SDN, EU, UN, etc.). Returns a boolean sanctioned flag, unique categories, and the full identifications list with source URLs. Chain-agnostic (EVM, BTC, Solana). Ideal for: compliance workflows, pre-transaction screening, counterparty risk checks, AML monitoring, audit trails.
Thirdweb Engine: Write Contract
ActionExecute a write transaction on a smart contract via your Thirdweb Engine. Queues the transaction and returns a queueId for tracking. Use get-transaction-status to poll for confirmation. Ideal for: state-changing contract calls, token transfers, minting.
Thirdweb Engine: List Backend Wallets
ActionList all backend wallets configured in your Thirdweb Engine instance. Returns wallet addresses, types, and labels. Ideal for: discovering available wallets, populating wallet selection dropdowns, verifying wallet setup.
Thirdweb Engine: Get Transaction Status
ActionCheck the status of a queued transaction on your Thirdweb Engine. Returns current status, transaction hash (once sent), and on-chain result (once mined). Ideal for: polling after a write-contract or send-transaction action, workflow conditions on tx status.
Thirdweb Engine: Read Contract
ActionRead data from a smart contract via your Thirdweb Engine instance. Calls a read-only function and returns the result. Ideal for: checking balances, reading state, fetching on-chain data for workflow conditions.
Thirdweb Engine: Send Transaction
ActionSend a raw transaction via your Thirdweb Engine. Takes pre-encoded calldata, destination address, and value. Queues the transaction and returns a queueId. Ideal for: arbitrary contract interactions, value transfers, custom calldata not covered by write-contract.