Titan Locker
Contracts
Every Titan Locker contract address on Robinhood Chain and Stable Chain, verified and ready to check on-chain.
Titan Locker runs the identical audited TitanLockerManagerV2_1 contract on two chains — Robinhood Chain and Stable Chain — deployed at the exact same address on both, a deterministic result of deploying from the same wallet at the matching transaction nonce on each chain (independently verifiable; see the bytecode-verification guide linked below). Every contract below is deployed and fully source-verified — open any address on its chain's explorer to read the source directly rather than taking this page's word for it.
Robinhood Chain (chain ID 4663)
New locks — token locks, linear vesting, and Uniswap V3/V4 LP positions — are created on Titan Locker Manager V2.1, the ContractWolf audit-fixed redeploy. The original V2 and V1 managers stay deployed and read-only so locks already on them remain fully viewable and withdrawable; the app shows all three together.
Titan Locker Manager V2.1
CurrentBlockscoutCurrent manager — creates every new lock on Robinhood Chain: ERC-20/LP token locks, linear vesting (with optional cliff), and Uniswap V3/V4 LP-position locks, each as its own isolated child contract, with per-lock fee claiming. Same TitanLockerManagerV2 code as below, redeployed fresh with every ContractWolf audit fix — see the security audit for what changed and why it's a separate address rather than an upgrade.
0x102a70bDA2C833b3483A2eE55C14c7ea0fb7A01BTitan Locker Manager V2
SupersededBlockscoutSuperseded by V2.1 above — does not create new locks. Still deployed and read-only: locks created here before the audit fix stay fully viewable and withdrawable.
0x26b0654a0756dcd036d4e7215324f3d2be34d79eTitan Locker Manager V1
LegacyBlockscoutThe original manager, predating V2 entirely — does not create new locks. Still deployed and read-only: existing V1 locks stay viewable and withdrawable here.
0x713E56CeE7060F01F710bF26Aff988264dcfb311Util (linked into V2.1)
BlockscoutFee-calculation library linked into the current TitanLockerManagerV2_1 — handles both payment methods (flat ETH or a percentage of the deposited token). This is the same Util address as Stable Chain's, not the legacy one below.
0xFBfa1ce526f98deC2251D44d1DaF7c599223aFe6Util (linked into V1/V2, legacy)
BlockscoutThe original fee-calculation library, linked into the legacy V1 and V2 managers only — a genuinely different address from the V2.1 Util above, not a duplicate listing of the same contract.
0x772279251b563028a32cD1505e3F2f8485C746D9Stable Chain (chain ID 988)
Stable Chain launched directly on the audited V2.1 code — there is no legacy V1/V2 deployment to track there, and Titan Locker is the first token and liquidity locker live on this chain.
Titan Locker Manager V2.1
CurrentStablescanCurrent (and only) manager on Stable Chain — same audited bytecode as Robinhood Chain's V2.1, at the identical address.
0x102a70bDA2C833b3483A2eE55C14c7ea0fb7A01BUtil
StablescanFee-calculation library linked into Stable Chain's V2.1 — the same address as Robinhood Chain's V2.1 Util above.
0xFBfa1ce526f98deC2251D44d1DaF7c599223aFe6TitanLockerManagerV2_1 and its Util are deployed at the SAME addresses on both chains - don't take that on faith, verify it yourself with a direct eth_getCode comparison (runnable script on the Stable Chain hub).
Allowlisted Uniswap position managers
Locking a Uniswap position means the lock contract calls that position manager (to pull the NFT and later collect fees), so V2.1 only interacts with position managers the owner has explicitly allowlisted — per chain.
Robinhood Chain
| Protocol | Kind | Address |
|---|---|---|
| Uniswap V3 | NonfungiblePositionManager | 0x73991a25C818Bf1f1128dEAaB1492D45638DE0D3 |
| Uniswap V4 | PositionManager | 0x58daec3116aae6d93017baaea7749052e8a04fa7 |
Stable Chain
| Protocol | Kind | Address |
|---|---|---|
| Uniswap V3 | NonfungiblePositionManager | 0x3BdC3437405f7D801b6036532713fc1F179136a6 |
V4 has no deployment on Stable Chain yet, so only V3 is allowlisted there - the create-lock flow only ever offers position types actually available on the chain you're connected to. The allowlist itself is per-protocol, not per-user: once a position manager is allowlisted, anyone can lock any of their positions on it. Verify the live state by reading positionManagerKind(address) on the V2.1 manager.
Network details
| Field | Robinhood Chain | Stable Chain |
|---|---|---|
| Chain ID | 4663 | 988 |
| RPC endpoint | https://rpc.mainnet.chain.robinhood.com | https://rpc.stable.xyz |
| Block explorer | https://robinhoodchain.blockscout.com | https://stablescan.xyz |
| V1 manager deploy block | 2,402,462 | — (never deployed here) |
| V2 manager deploy block | 5,851,744 | — (never deployed here) |
| V2.1 manager deploy block | 13,944,087 | 32,806,912 |
Always check a contract address against this page before approving a token or sending ETH/USDT0. Never trust an address pasted somewhere else, even if it looks right.