Back to Blog
CantonDamlSecuritySmart ContractsAuthorization

Canton / Daml Authorization Model: A Primer for Auditors

CODESPECTApril 15, 20261 min read

Why Canton / Daml is different

TODO(author): one-paragraph contrast with EVM's caller-based authorization.

Parties, not accounts

TODO(author): what a Daml party is, how it differs from an EVM address, and why multi-party authorization is first-class.

Templates and the authorization model

Signatories

TODO(author)

Observers

TODO(author)

Controllers and choice authorization

TODO(author)

Implicit vs explicit authorization

TODO(author)

Common authorization pitfalls

TODO(author): failing-closed misuse, missing signatory on delegated choices, interface-template auth mismatches.

What auditors should check

TODO(author): concrete list for Daml reviews.

Canton topology and trust

TODO(author): brief section on how Canton's synchronization model layers on top of Daml's auth model, and why both matter.

Explore Our Services

Ready to Secure Your Project?

Get a free 30-minute security assessment. We will review your codebase scope and flag the top 3 risk areas.

No commitment required. Typical audits start within 1–2 weeks.