Overview#
A financial crime analyst builds an investigation around a cluster of cryptocurrency wallets believed to be part of a money laundering network. She creates trace records linking each wallet address and key transaction hashes to the investigation, attaches risk scores, and adds contextual annotations. Those trace records form the backbone of the blockchain evidence in the case, organised, searchable, and linked to the entity graph for relationship analysis.
The Crypto Trace domain provides the investigative record layer for cryptocurrency analysis: structured trace records that connect blockchain evidence to investigation context.
Key Features#
- Wallet address and transaction hash trace record management.
- Multi-blockchain support with chain-specific tracking.
- Optional risk scoring for traced wallets and transactions.
- Dual-database persistence with graph replication for relationship analysis.
- Organisation isolation with tenant-scoped access.
- Secrecy level enforcement via RBAC clearance checks.
- Metadata support for trace context and annotations.
- Audit trail for all trace operations.
Use Cases#
Financial crime investigators trace cryptocurrency wallet addresses across blockchain networks, building a structured investigative record that links blockchain evidence to the entities and accounts already identified in the case.
Money laundering analysts construct relationship graphs between wallets, transactions, and real-world entities by combining trace records with graph database queries, visualising fund flows across the network.
Sanctions compliance teams risk-score wallet addresses against known threat profiles, flagging wallets with high risk scores for further review before processing any transaction that touches them.
Cross-blockchain investigators managing complex cases spanning multiple chains maintain unified trace records regardless of which blockchain a wallet or transaction belongs to, keeping the full investigation picture in one place.
Integration#
Integrates with blockchain analysis, investigation, and entity management domains. Supports dual-database writes for transactional and graph-based queries.
Open Standards#
- GraphQL (June 2018 specification): all trace record queries, mutations, and paginated list responses are exposed through a Strawberry GraphQL schema, enabling strongly typed, client-driven access to investigative data.
- FATF Recommendation 16 (Virtual Assets / Travel Rule): sanctions screening of wallet addresses against OFAC and OpenSanctions datasets supports the AML/CFT due-diligence obligations placed on virtual asset service providers under FATF R.15, R.16.
- Traffic Light Protocol (TLP 2.0, FIRST): each trace record carries a secrecy level drawn directly from TLP:WHITE, TLP:GREEN, TLP:AMBER, and TLP:RED, controlling who may access or share a piece of blockchain evidence within and beyond the organisation.
- RFC 4122 (UUID): every trace record is assigned a version 4 universally unique identifier at creation, ensuring globally collision-resistant identifiers across multi-tenant deployments.
- ISO 8601: transaction timestamps and record lifecycle timestamps (created, updated) are stored and serialised as ISO 8601 date-time strings, guaranteeing unambiguous temporal ordering across time zones.
- JSON (RFC 8259): the extensible metadata field is persisted as JSONB and serialised as JSON at the API boundary, allowing arbitrary investigative annotations without schema migration.
- OAuth 2.0 / JWT (RFC 6749 / RFC 7519): all GraphQL operations are protected by the platform's JWT-based authentication layer; only bearers of a valid, organisation-scoped token may create, read, update, or delete trace records.
Last Reviewed: 2026-02-24 Last Updated: 2026-04-14