Find exploitable contract behavior before launch. Get a scoped manual review, actionable findings, and a clear path through remediation, with public reports you can inspect before choosing CTDSEC.
Three examples from the wider public report archive, with reviewed scope and remediation status.
Review the DEXTools Token Creator audit for repository scope, token-factory findings, and the development team's responses. The report records one medium, one low, and one informational finding as acknowledged, with no high-severity findings listed.
The URMCDP report examines collateralized borrowing, interest accrual, liquidation, oracle behavior, and configuration changes. Its final table records three high-severity findings (one acknowledged and two resolved) and five medium-severity findings marked resolved.
The PWRAuctionCrossChain audit follows bidding, buyer identity, token claims, vesting, and administrative escrow controls across contract boundaries. The final table records four high and two medium findings as resolved, with one low and one informational finding acknowledged.
These are examples, not the entire portfolio. Explore all public audit reports.
Start with what your protocol does and when you expect to launch. To prepare a meaningful proposal, we clarify the repository and target revision, contracts in scope, assets at risk, dependencies, documentation, tests, and any exclusions.
Price and turnaround depend on that scope and the remediation work requested. A token factory and a lending system with external oracles need different review plans. Compare proposals on coverage, deliverables, and fix verification, not a headline price alone.
What affects audit cost? Review our auditor selection guide before requesting proposals.
The report should connect each finding to affected code, impact, and remediation guidance. When fix verification is included, provide a new revision and change summary so the review can distinguish resolved findings from accepted risks.
An acknowledged finding is not a verified fix. A report covers its documented code and assumptions; it is not insurance against every vulnerability or automatic coverage for later upgrades.
A smart contract audit should find exploitable behavior before attackers, market conditions, or governance edge cases do. CTDSEC reviews contract logic, threat models, privileged roles, deployment assumptions, upgrade paths, tests, and protocol economics with the mindset of an adversary.
The audit process is built for teams that need practical findings, clear severity classification, remediation guidance, and a final report that can be shared with users, investors, exchanges, partners, or governance communities.
The review is tailored to the target chain and codebase, but the audit always starts with assets at risk, trust boundaries, and the concrete ways the protocol can fail.
Smart Contract Audit with manual review, tool-assisted coverage, and remediation support.
Compare coverage for your language, network, and protocol.
Explore related audit coverage and preparation guidance.
Explore related audit coverage and preparation guidance.
Explore related audit coverage and preparation guidance.
Explore related audit coverage and preparation guidance.
Practical review questions and scoping guidance for your engineering team.
A practical smart contract audit checklist covering scope, access control, accounting, oracles, upgrades, tests, deployment, and remediation.
How protocol teams can prepare repositories, documentation, tests, deployment details, and scope before a smart contract audit.
What affects smart contract audit cost, including code size, complexity, blockchain ecosystem, documentation, testing, and remediation needs.
Short answers for teams preparing an audit scope.
It includes scope confirmation, manual code review, tool-assisted analysis where useful, severity-ranked findings, remediation guidance, and a final report for the agreed disclosure model.
Yes. Fix verification can be included after the team remediates reported findings, using a new commit and a clear change summary.
The quote depends on the agreed code scope, complexity, dependencies, and remediation review. Start with a project description; we can clarify repository access and timeline by email.
Tell us what you are building and when you plan to launch. Start with a short description; repository access and technical scope can follow.