Titan Locker Security Audit — ContractWolf
Titan Locker passed a professional ContractWolf security audit of TitanLockerManagerV2/TitanLockerV2 — 4 findings, all resolved, shipped as version 2.1.0 on TitanLockerManagerV2_1. Read the full report.
Updated 3 min read
Is Titan Locker audited?
Yes. ContractWolf ran a professional Standard Audit — manual and automatic analysis — against TitanLockerManagerV2 and TitanLockerV2, verified 07/18/2026. It found 4 issues (1 Major, 2 Medium, 1 Informational, 0 Critical), and every one was fixed and shipped as version 2.1.0. ContractWolf's own verdict: AUDIT PASSED.
Who audited Titan Locker?
ContractWolf, an independent smart-contract security auditor. Their engagement covered the full TitanLockerManagerV2/TitanLockerV2 contract pair — every locking, vesting, and fee-collection path — using both manual line-by-line review and automated analysis.
What did the ContractWolf audit find?
4 issues, all resolved: a Major transaction-order-dependence risk on the token fee, two Medium logic errors (dust-lock fee rounding and misreported Uniswap V4 fee amounts), and one Informational missing-validation issue.
| Finding | Severity | Fix |
|---|---|---|
| SWC-114 — Transaction Order Dependence (a token-fee change landing between submission and mining could confiscate the deposit) | Major | Token fee capped at 5% (from 100%); callers can also set their own max-fee guard that reverts if exceeded. |
| Bps rounding let dust locks pay zero fee | Medium | Fee now rounds up (ceiling division) instead of down. |
| collectFees() misreported amounts for Uniswap V4 locks | Medium | Collected amounts are now captured via a real balance delta. |
| Missing validation allowed zero-amount locks | Informational | Zero-amount locks now revert instead of being created for free. |
Every fix has dedicated test coverage across the Hardhat, Foundry fuzz/invariant, and Halmos symbolic-proof suites — see the contracts repository for the full results.
Which contract carries the audit fixes?
TitanLockerManagerV2_1 (0x102a70bDA2C833b3483A2eE55C14c7ea0fb7A01B) — a fresh deploy of the same TitanLockerManagerV2 code carrying every ContractWolf fix, and the manager every new lock is created on. These contracts have no upgrade proxy, so a fix only takes effect for locks created against a new address. The original TitanLockerManagerV2 (0x26b0654a0756dcd036d4e7215324f3d2be34d79e) is superseded: its code is unchanged and still deployed, the app no longer creates locks on it, and every lock already on it stays fully withdrawable — none of the findings above involve custody of an existing lock.
| Contract | Address | Status |
|---|---|---|
| TitanLockerManagerV2 (original) | 0x26b0654a0756dcd036d4e7215324f3d2be34d79e | Superseded: read-only, pre-audit-fix logic, existing locks withdrawable |
| TitanLockerManagerV2_1 (audit-fixed) | 0x102a70bDA2C833b3483A2eE55C14c7ea0fb7A01B | Current: creates every new lock, verified, carries all 4 fixes |
Where can I read the full audit report?
The full ContractWolf audit report is public. For the most authoritative copy, verify it directly on ContractWolf's own site and GitHub - not just our word for it.
Was Titan Locker tested beyond the paid audit?
Yes — the ContractWolf audit sits on top of an already-extensive baseline: Slither, Aderyn, Mythril, Foundry fuzz and invariant testing, Echidna, and Halmos symbolic proofs, plus a Hardhat/Mocha test suite. See Fees & security for the full toolchain.
Who else independently verifies Titan Locker?
Beyond the audit, DefiLlama lists Titan Locker and tracks its TVL and fees with its own adapters, and Quick Intel's token scanner recognises Titan Locker locks. See Titan Locker on DefiLlama & Quick Intel.