Overview#
Sanctions lists change. New wallets are added when threat actors are designated; existing wallets are updated when additional addresses are identified. An organisation running cryptocurrency compliance checks needs its wallet screening data to reflect those changes in near-real-time, not after a monthly manual import. The Crypto Wallet domain maintains a high-performance replica of sanctioned and non-sanctioned crypto wallet data, synchronised from authoritative sources, ready for instant compliance screening.
Key Features#
- Wallet data synchronisation from sanctions entities.
- Real-time cryptocurrency transaction monitoring.
- Sanctions screening for wallet addresses.
- Cross-chain wallet tracking across multiple blockchains.
- Rate-limited sync operations (1 per hour per user).
- Audit logging for all sync operations with user, timestamp, and result.
- Secure credential management for external services.
- Error handling with detailed operation logging.
Use Cases#
Compliance teams at financial institutions synchronise sanctioned wallet data on a regular basis, maintaining an up-to-date screening dataset that reflects the latest designations without requiring manual intervention for each update.
Cryptocurrency exchange compliance officers screen wallet addresses against the current sanctions dataset in real time as customers attempt to transact, blocking prohibited transactions before they are processed.
Financial crime investigators use cross-chain wallet tracking to monitor addresses of interest across multiple blockchains, maintaining a unified view of wallet activity regardless of which chain a transaction occurs on.
Regulatory compliance programmes verify cryptocurrency transactions against the maintained wallet dataset as part of automated due diligence workflows, producing audit records of every screening check performed.
Integration#
Integrates with sanctions entity management, blockchain analysis, and wallet enrichment services for end-to-end crypto compliance workflows.
Open Standards#
- GraphQL (June 2018 specification): All wallet sync operations, screening queries, enrichment lookups, and statistics are exposed through a typed GraphQL API, with mutations and queries defined using a strongly-typed schema.
- OFAC Specially Designated Nationals (SDN) list / UN and EU sanctions lists: Wallet sanctions screening explicitly checks addresses against OFAC SDN, UN, and EU consolidated lists, and risk scores reflect the designation sources present on each record.
- OpenSanctions data model: Sanctioned wallet entities are ingested from the OpenSanctions dataset, with the CryptoWallet entity type, public key address field, and topics taxonomy used directly as the source of truth for wallet attribution.
- Ethereum ERC-20 / ERC-721 / ERC-1155 token standards: Token transfer tracking identifies and classifies fungible (ERC-20) and non-fungible (ERC-721, ERC-1155) token movements as part of wallet activity enrichment.
- Ethereum Virtual Machine (EVM) chain specification: The multi-chain service targets all EVM-compatible networks (Ethereum, Polygon, BNB Smart Chain, Arbitrum, Optimism, and 40+ others), using uniform address formats and transaction models defined by the EVM specification.
- JSON (ECMA-404 / RFC 8259): Wallet properties, attribution evidence, and all sync payloads are serialised as JSON, and the sync service exchanges JSON request and response bodies over HTTP.
- OAuth 2.0 / JSON Web Tokens (RFC 7519): Internal service-to-service calls are authorised via scoped service JWTs minted with explicit audience and scope claims.
- SHA-256 (FIPS 180-4): Blockchain forensic reports generated from wallet intelligence data include a SHA-256 cryptographic verification hash to support chain-of-custody integrity.
Last Reviewed: 2026-02-05 Last Updated: 2026-04-14