Quick answer: Daml audits are a distinct discipline, not Solidity reviews with different syntax. The reviewer pool is small, public reports are scarce, and sourcing is the real bottleneck. Expect $15,000 for a focused single-workflow review up to $70,000+ for a full protocol review. Before you commit budget, check whether the Canton Development Fund will cover part of it.
Canton is increasingly becoming the blockchain infrastructure of choice for institutional financial applications, with regulated institutions, market infrastructure providers and financial firms building and connecting applications across the network.
That institutional adoption matters for security. The applications being deployed on Canton can sit much closer to real financial assets, regulated workflows and institutional counterparties than the average onchain application, making the quality of the underlying smart contracts, privacy model and authorisation logic particularly important.
So, you've decided to build on Canton. Your application is taking shape, your Daml contracts are ready, and you're approaching launch.
Now you need an auditor.
And that's where things can get difficult.
There are hundreds of firms advertising Solidity and EVM audits. The number with meaningful Daml and Canton experience is considerably smaller, and public audit reports are still relatively scarce.
Here's how to navigate it.
What makes Daml different?
Daml isn't Solidity with different syntax. Built by Digital Asset for regulated financial contracts, it encodes consent, authorisation and privacy into the type system itself. And on Canton, the ledger is synchronised but data isn't globally visible: only the parties to a contract can see it.
That makes auditing Daml a genuinely distinct discipline. Here's what a competent Daml and Canton review actually looks at, how to evaluate a firm, which firms are building capability, and how to fund the work.
What a Daml audit actually reviews
Authorisation correctness. Every contract change needs the right combination of signatory and actor authority, and that authority doesn't chain automatically through nested choices. Reviewers verify nothing can be created, archived or transferred without the consent the design intends, and that delegation can't be exercised more broadly than scoped.
Privacy containment. Canton's need-to-know visibility can still leak data: through over-broad observers, transaction witnesses, or divulgence when a choice fetches an unrelated contract. In a regulated context, a forgotten observer isn't a bug, it's a compliance failure.
State hygiene. Changing state means archiving one contract and creating another. Sloppy lifecycles leave dangling observers, stale references, or "zombie" proposals that stay exercisable long after their context has passed.
Liveness. Every workflow must be able to complete. Reviewers hunt for dead-end states that strand a contract on the ledger with no path forward.
Most of this the compiler won't catch. That's why reviewer experience with Daml and Canton matters more here than in almost any other ecosystem.
Sourcing Daml auditors is a bottleneck
There's no public leaderboard for Daml auditors and few public reports, so teams often spend weeks running down references before a first quote.
When TermMax was preparing to launch on Canton, they were introduced to Procur3, where they were able to source a Daml-specialised auditor through a private RFP: competitive bids in three days, rather than a two-month vendor search.
Procur3 is a neutral marketplace. We don't perform audits, so for a hard-to-source discipline like Daml on Canton the useful thing is simply seeing the qualified market in one place, on the evidence, and letting firms compete for the work.
How to evaluate a firm
Whoever you're speaking to, ask three questions:
- How many Daml audits have you delivered, and can you share reports or references?
- Which senior reviewers will be on my engagement, and which Daml or Canton audits have they personally worked on?
- Do you have direct experience with Canton domain and privacy semantics?
Firms building Daml and Canton capability
Listed alphabetically, not ranked: a survey of firms with demonstrated or emerging Daml capability, not a tiered endorsement. The market is small but growing fast.
- CertiK: high-volume, institutional-format reporting, post-audit monitoring.
- Hacken: full-stack security practice; has published in-depth original research on Daml design patterns and security on Canton.
- Halborn: mature institutional-blockchain practice; has audited Digital Asset infrastructure and Canton components.
- Nethermind: deep protocol engineering and formal methods practice, with research-led review of consensus, settlement and infrastructure-layer systems.
- No.Witness Labs: a focused specialist building dedicated Daml and Canton capability.
- OpenZeppelin: publishing Canton security research and open-sourcing Daml tooling plus a Canton contracts library.
- Quantstamp: auditing since 2017, deep enterprise and institutional track record.
- Sigma Prime: rigorous, research-driven review of consensus-layer and settlement-critical systems.
Notable mentions
Firms are upskilling in Daml every month, and the list above will look different in six months. These are established practices on Procur3 worth approaching as the ecosystem grows. Put the three questions above to them directly, and ask specifically about Daml and Canton before you assume capability either way.
- Adevar Labs: boutique practice working across EVM and non-EVM stacks.
- Guardian Audits: DeFi-focused manual review backed by a strong automated tooling practice.
- HackenProof: bug bounty and continuous coverage rather than a scheduled audit, useful as a layer after review.
- Hashlock: institutional and compliance-oriented client base.
- QuillAudits: high-volume multi-chain practice with broad language coverage.
If a firm you rate isn't on either list, the three questions still apply. New genuine specialists are appearing all the time.
What does a Daml audit cost?
As a rough 2026 benchmark, Daml audit engagements typically start at around $9,000 for a focused, single-workflow review and can run to $70,000+ for a full protocol review involving multiple workflows, complex privacy analysis or formal verification.
As with any smart contract audit, scope is the biggest variable. Codebase size matters, but so do workflow complexity, number of parties and roles, the sophistication of the authorisation model, testing requirements and how much of the broader Canton integration needs reviewing. For a rough EVM-equivalent baseline you can sanity-check against, our audit cost calculator returns an indicative market range in about 30 seconds.
The important thing is not simply finding the lowest quote. With a relatively specialised language like Daml, you want to understand who is actually doing the work and what relevant experience sits behind the price.
Funding your Canton audit
Security work on Canton doesn't always have to come out of your own budget. The Canton Development Fund backs ecosystem development, including security audits, through grants delivered in quarterly milestones.
Beyond its published roadmap, the fund stays open to individual, community-generated proposals. Applicants need to demonstrate three things: strong ecosystem demand, genuine community support, and a clear Development Fund Champion backing the proposal.
So if your protocol is delivering meaningful infrastructure or DeFi to Canton, it's worth exploring whether your audit could qualify for grant support before you finalise your budget.
Details and the proposal process: github.com/canton-foundation/canton-dev-fund
Then, ship
If you're building on Canton, the audit process shouldn't become the thing that delays your launch.
Work out exactly what needs reviewing, speak to firms with genuine Daml experience, understand who will actually be assigned to the engagement, compare multiple proposals, and check whether Development Fund support is available before committing your budget.
Then get the contracts reviewed, fix what comes back, verify the remediation and get back to building.
Good luck with the launch.
Frequently Asked Questions
How much does a Daml smart contract audit cost? Daml engagements typically start around $15,000 for a focused, single-workflow review and run to $70,000+ for a full protocol review involving multiple workflows, complex privacy analysis or formal verification. Scope drives the number more than codebase size: workflow complexity, number of parties and roles, authorisation model sophistication and the breadth of Canton integration under review all move it.
Can a Solidity auditor review my Daml application? Yes, if they have upskilled and had exposure to the working of Daml. Daml encodes consent, authorisation and privacy into the type system, and Canton's ledger synchronises without making data globally visible. The failure modes are different from EVM ones, and most of them are not caught by the compiler. Ask any firm for direct Daml and Canton experience before signing.
What does a Daml audit actually cover? Four areas above all: authorisation correctness, privacy containment, state hygiene across contract archive and create cycles, and liveness, meaning every workflow can actually complete rather than stranding a contract with no path forward.
How do I find auditors with real Daml experience? There is no public leaderboard and few published reports, so direct comparison is difficult. Ask each firm how many Daml audits they have delivered, which named senior reviewers will be on your engagement, and whether they have hands-on experience with Canton domain and privacy semantics. You can also post your scope on Procur3 and let qualified Daml-specialist firms bid.
Can the Canton Development Fund pay for my audit? Possibly. The fund supports ecosystem development including security audits, delivered through quarterly milestones, and accepts community-generated proposals outside its published roadmap. You will need to show ecosystem demand, community support and a Development Fund Champion backing the proposal. Worth exploring before you finalise your security budget.