Resources
FAQ: Security & Audits
Common questions about Titan Locker's security: immutability, custody, audits, testing, and verified contracts.
Is Titan Locker audited?
The contracts pass Slither, Aderyn, Mythril, Foundry fuzz/invariant tests, and Halmos symbolic proofs, plus an adversarial review against known exploit classes. No paid third-party audit yet — treat it as a strong pre-audit baseline.
Are the contracts upgradeable?
No. They are immutable and non-upgradeable — no proxy, no admin upgrade path. New versions are separate deployments; existing locks are never affected.
Is Titan Locker non-custodial?
Yes. Each lock is its own contract owned by the user; the Titan Locker team never has custody and cannot move locked assets.
Can the owner (admin) seize locked funds?
No. The manager owner cannot move locked assets, shorten unlock times, or alter existing locks. Admin settings only affect new locks.
How are locks isolated from each other?
Every lock is a separate contract holding one asset, with owner-only value-moving functions — one lock can never touch another's funds or fees.
Are the contracts open source?
Yes, GPL-3.0. Source is public on GitHub and verified on Blockscout.
Is the source verified on the explorer?
Yes. The V2 manager and the per-lock contract are verified on Robinhood Chain's Blockscout, so anyone can read the exact code.
What happens if the team disappears?
Nothing changes for your locks. They're immutable on-chain and withdrawable by the owner after unlock regardless of the team.