Titan Locker
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.
AUDIT PASSED — ContractWolf's findings have been acknowledged and resolved. Full report (PDF): ContractWolf_Audit_TitanLockerV2.pdf.
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. These contracts have no upgrade proxy, so a fix only takes effect for locks created against a new address; the original TitanLockerManagerV2 (0x26b0654a0756dcd036d4e7215324f3d2be34d79e) keeps running unchanged, and every lock already on it is completely unaffected either way, since none of the findings above involve custody of an existing lock.
| Contract | Address | Status |
|---|---|---|
| TitanLockerManagerV2 (original) | 0x26b0654a0756dcd036d4e7215324f3d2be34d79e | Live, unchanged, pre-audit-fix logic |
| TitanLockerManagerV2_1 (audit-fixed) | 0x102a70bDA2C833b3483A2eE55C14c7ea0fb7A01B | Live, 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 current pass counts.