An LP token represents a claim on a particular pair. A locker can custody specified LP tokens until a timestamp, but it does not prove token value, market depth, owner honesty, contract safety, or project legitimacy. The source-reviewed legacy record has no setter to change its withdrawer or timestamp after creation. That property does not make the compromised factory safe for new deposits, and the underlying LP may belong to a retired DEX.
Never grant an allowance to the legacy locker. New locks use only the immutable replacement after chain/runtime/spender/fee checks. A legacy withdrawal is limited to a source-authenticated matured record whose withdrawer matches the connected wallet.
Navigate independently to lester-labs.com/locker. Do not paste a locker address from a chat, social post, search result, or mutable environment value.
Verify the exact locker runtime and read the lock token, amount, unlock timestamp, withdrawer, and withdrawal state. Confirm the connected wallet exactly matches the recorded withdrawer.
The existing timestamp cannot be edited. Wait until it has passed, then confirm the proposed call is zero-value `withdraw(lockId)` to the exact source-pinned locker.
Review the decoded transaction, sign only if every check matches, and verify the LP-token transfer and updated withdrawal state through an independently selected RPC or explorer.