Security
Security model
CBTC combines Bitcoin threshold custody, independent event verification, Canton authorization and privacy, versioned Daml packages, authenticated service integrations, and reserve evidence. No single control should be presented as the entire security model.
Security layers
Bitcoin custody
FROST threshold signing across independent operators
Key lifecycle, signing policy, recovery, and correlated risk
Event verification
Attestor Network policy and evidence
Duplicate prevention, transaction validity, and authorization
Canton contracts
Daml authorization and party rights
Package versions, choices, privacy, and migration
Client integration
Authentication, least privilege, validation, and idempotency
Secrets, wrong-party risk, retries, and logs
Backing evidence
Proof of Reserve and reconciliation
Scope, cadence, stale data, and exclusions
Operations
Monitoring, change control, incident response, and support
Ownership, escalation, and recovery testing
Integrator responsibilities
Integrators must verify parties and Bitcoin destinations, pin compatible releases, protect credentials, validate contract state, reconcile ambiguous submissions, and use approved support channels. CBTC infrastructure cannot protect an application that sends an authorized command with incorrect inputs.
Privacy boundary
Canton limits contract visibility through sub-transaction privacy. Bitcoin transactions remain visible on Bitcoin. Application logs, support exports, and external systems can reveal information if operators do not protect them.
Audits
Each audit report identifies the contracts, services, release tags, and dates within its scope. An audit is evidence about reviewed components at a point in time. It is not a guarantee that every deployment or future release is secure.
Vulnerability reporting
Report suspected vulnerabilities through the private security contact listed in Security and trust index. Do not post unpatched vulnerabilities in public issues. Include the affected release, impact, reproduction steps, and safe contact details.
Known limitations
Check CBTC compatibility and release notes for supported versions, operational dependencies, known issues, and applicable audit scope.
Related pages
Next step
👉 Confirm the evidence and reporting path: Security and trust index.
Last updated