Platform
One coherent control platform, not twelve unrelated engines.
Every ChainGuard layer reasons over the same banking subjects: customers, wallets, transactions and cases. Intelligence, compliance, decisions and evidence therefore stay consistent end to end on Bitcoin and account-based networks.
Shared model
Four subjects every layer agrees on.
Most compliance stacks fail at the seams between tools. ChainGuard avoids the seams by giving every layer the same four objects to reason over.
Customer
The institution’s own account holder, with identity and economic context
Wallet
A registered address or unspent-output cluster attributed to that customer
Transaction
An observed transfer on Bitcoin or an account-based network
Case
The investigative container that ties the other three together over time
Architecture
Eight layers, stacked in the order a transfer moves through them.
Read from the bottom up: data enters, becomes intelligence, is checked against compliance and policy, produces a decision and its evidence, then meets operational control and governance.
Governance
Maker/checker, role-based access, versioned policy and model governance.
Administration and observability
User, permission, secret and system-health management for the deployment.
Execution control
Operational readiness against custody, liquidity and core banking. These controls remain separate from the compliance outcome.
Evidence
Policy version, triggered rules, source facts and approval history captured per decision.
Decision
Versioned banking policy applied to risk and context to reach an auditable outcome.
Compliance
KYC/KYB, beneficial ownership, sanctions, Travel Rule and wallet ownership.
Intelligence
Entity attribution and bounded flow tracing over Bitcoin input/output relationships and account-graph activity.
Banking subjects
Customers, wallets, transactions and cases as the shared entities every other layer reasons over.
Workflow by path
Select a path to see how it moves through the platform.
Four operational paths, one control sequence. Use the arrow keys to move between them.
- 1Customer initiates a deposit on Bitcoin or an account-based network
- 2Wallet ownership and Travel Rule status checked
- 3Source-of-funds tracing runs against the incoming transaction
- 4Banking policy evaluates risk, customer context and flow intelligence
- 5Decision reached: allow, hold, review, reject or escalate
- 6Evidence recorded; operational readiness validated against core banking
See the platform work on your own deposit, withdrawal and registration flows.
Map ChainGuard to your institution’s transaction, policy and evidence workflows.