A liquidity lock can restrict withdrawal of the particular position or liquidity tokens placed under that lock. It does not automatically prevent transfer taxes, address restrictions, supply changes or malicious approvals.
Verify what is locked
Identify the chain, pool, position or liquidity-token contract, quantity, beneficiary and unlock conditions. Ask what fraction of relevant liquidity the lock covers. A lock for a different pool or a small position may say little about the route you will use.
GoPlus’s lock-data documentation distinguishes lock amount and end time and notes coverage limits for recognized lock addresses. A scanner’s badge is therefore a starting point for checking the actual lock, not a universal guarantee.
Check the economic conditions separately
Locked liquidity can still be shallow relative to your trade. A concentrated position may not provide usable liquidity at the current price. Token supply held outside the pool can also affect price through sales even when one liquidity position cannot be withdrawn.
Review token authority
The token contract may still let privileged accounts pause transfers or change rules. Access-control mechanisms are independent of whether a pool position is locked.
Do not infer that every sell will work merely because liquidity cannot be withdrawn until a future date. Verify the token’s behavior, current route and amount protections. A lock answers a limited custody-and-withdrawal question; it does not certify the entire trading environment.
Sources & verification (2)
Source-check date is recorded in the article details. URLs are provided for manual verification. Use Copy to keep this page open.
- Response Details | GoPlus Security
Scanner unknown states, mutable token restrictions and lock-data coverage limits.
https://docs.gopluslabs.io/reference/response-details - Access Control | OpenZeppelin Docs
Ownership, independent roles, admin roles and governance controls.
https://docs.openzeppelin.com/contracts/5.x/access-control